Track Keyword Positions and Understand Changes
Understand LLMIC keyword position tracking, compare Search Console periods and distinguish average position from a scoped live ranking check.
A ranking number only makes sense when you know how it was measured. Search Console average position and a live search-result check answer different questions. Use LLMIC to review the right evidence, keep the comparison consistent and decide which landing pages need attention.
What this guide helps you do
Keyword rank tracking becomes more useful when position, page, date and source stay together. Learn how LLMIC compares Search Console averages with supported live observations without presenting either value as a permanent rank.
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
- Set the scope
Record property, keyword and target. - Choose the evidence
Search Console history or a live observation. - Compare like with like
Keep dates, device and location consistent. - Investigate the page
Turn a change into a specific review task.
Workflow illustration. These steps explain the process; they are not measured performance results.
Start with Search Console
Use the existing Google connection and open Position Tracking under Keywords & Rankings. Confirm the selected property and reporting period. Search Console summarizes the impressions Google recorded for that slice. Its average position is not a promise that you will see the same position in a search performed from your own browser.
Understand a live check
Where available, a live check observes a particular query with specific location, language, device and result-depth settings. Record those settings alongside the timestamp. External providers may charge per query, so review any maximum-credit confirmation before starting. Do not treat a cached or differently configured result as a fresh comparable observation.
Read movements carefully
Compare periods with equivalent scope. If a keyword changes from an average position of 12 to 8, the number is lower and the observed position is better. If no row was returned, do not invent a position or assume the keyword lost all visibility. Missing observations and confirmed absence from a checked range are different states.
Investigate before rewriting
An illustrative drop could relate to a different landing page appearing, a changed query mix or a technical problem. Inspect the returned URL and compare the relevant page evidence. Current crawl findings can suggest possible blockers, but they do not establish what caused a historical ranking change. Preserve the dates and explanation with your task.
Export a comparison readers can understand
Include the keyword, intended URL, evidence source, period or check time and relevant filters. Keep provider failures visible rather than converting them into poor rankings. For a result outside a checked range, say “not found in the checked results” with the actual depth. That is more accurate than saying the page never ranks.
Quick reference
| What you see | What to do next |
|---|---|
| Search Console average position | Interpret within the selected reporting slice. |
| Live result position | Read location, device, language, time and depth. |
| No returned observation | Keep the result unavailable rather than inventing zero. |
| Paid provider confirmation | Review the scope and maximum cost first. |
Your next step
Continue with connect Search Console, review competing landing pages, export useful reports. 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
Understand LLMIC keyword position tracking, compare Search Console periods and distinguish average position from a scoped live ranking check.
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.