Check Whether Your Target Keywords Appear on the Right Pages
Import a keyword and URL CSV into LLMIC, check page placements, review the evidence and share clear instructions with your content team.
You have a keyword plan. Now you need to know whether the intended pages actually use those keywords. Keyword Content Mapping turns a two-column spreadsheet into a page-by-page review. It helps your execution team see what was found, where it appears and which changes deserve a closer look.
What this guide helps you do
Keyword mapping connects each target query with the page intended to rank for it. Import a keyword and URL CSV, then use LLMIC to check where the phrase appears and turn missing placements into clear editorial instructions.
Build availability: This guide describes the updated workflow checked against the September 2026 development build. Some controls may not yet be included in the public installer. Check the release notes and your app version before following those steps.
The workflow at a glance
- Prepare the CSV
One keyword and one target URL per row. - Check the crawl
Load evidence for those exact pages. - Review each match
Read the placement and surrounding wording. - Share the work
Export reviewed instructions or add tasks to Queue.
Workflow illustration. These steps explain the process; they are not measured performance results.
Start with the pages you want to rank
Create a CSV with keyword and url headers. For example, pair “website audit tool” with https://example.com/audit/. Several keywords can point to one page. Keep full URLs and meaningful query parameters. Do not replace a target with a similar page just to make a match appear.
Import and check your plan
Load a completed crawl, then open Keyword Content Mapping under Keywords & Rankings. Choose Your keyword plan, select Import CSV and inspect the preview. Resolve invalid rows before choosing Check target pages. This source uses saved crawl evidence; it does not need a Search Console or AI connection.
Read the evidence before assigning work
Review the title, meta description, headings, retained page text, image alt text and URL evidence shown for each target. A word-for-word phrase is different from normalized punctuation or related wording. Read the excerpt before changing a sentence. An unavailable page or incomplete capture cannot establish that a keyword is missing.
Turn a finding into a useful instruction
An illustrative instruction is: “Explain the website audit tool in the opening paragraph because the page currently discusses only pricing.” That is more useful than “add the keyword five times.” Keep wording natural, preserve factual meaning and avoid adding keywords to unrelated image descriptions. Use notes and review decisions before exporting the filtered CSV.
What if a target cannot be checked?
Confirm the exact target is in the loaded crawl, including path case and query string. Review failed responses and content capture. Crawl missing targets, then run the check again. A manual Done decision records your team’s work; it does not confirm that the live website contains the change. Recheck after publication.
Quick reference
| What you see | What to do next |
|---|---|
| Found | Read the recorded placement and excerpt. |
| Review wording | Decide whether the wording serves the same topic. |
| Not found in text | Check complete evidence before proposing an edit. |
| Unable to check | Obtain a successful, sufficiently complete capture. |
Your next step
Continue with run your first audit, prepare reviewed fixes, verify an implemented change. Return to the documentation home for the full workflow. Before sharing an export, check its website, dates and filters, and remove private information. If a control is missing or a result looks wrong, contact support with your app version and a sanitized example.
Frequently asked questions
Import a keyword and URL CSV into LLMIC, check page placements, review the evidence and share clear instructions with your content team.
Load a completed crawl that includes the pages you need to inspect. Confirm the crawl scope, capture time, rendering choice, and any filters before interpreting the result.
Review the affected URL, measured field, source or rendered evidence, and the rule that raised the item. Inspect nearby pages and templates because one shared component can create the same pattern across many URLs.
Create a task with the affected URL, observed evidence, intended outcome, smallest safe change, owner, and verification method. Keep the measured finding separate from the proposed fix.
Publish the approved change, run a fresh compatible crawl, and compare the new evidence with the saved result. A resolved local finding confirms the implementation changed; search performance requires separate observation over time.
The check cannot guarantee rankings, indexing, traffic, conversions, inclusion in an AI answer, or a future search-engine action. Interpret it with site context, search performance, and editorial judgment.
Save or export the evidence, assign the approved action, and use the related guides linked on the page for the next check. After implementation, repeat the same workflow against a fresh crawl so the result is comparable.