Which Google ranking data should a position checker report?

A Google position checker should report rankings by keyword, location, device and search engine, while also identifying SERP features that affect visibility. It should show the current position alongside historical trends, ranking URLs and actionable changes, so performance can be interpreted rather than reduced to a single number.

A useful Google position checker should report more than a single ranking number. It should show the keyword, ranking URL, search location, device, language, search engine, SERP features and date of the check, together with historical changes and visibility trends. This context is needed to distinguish a genuine performance change from a difference caused by personalisation, local intent, mobile results or a change in the search results page.

Keyword and target context

Every result should be linked to the exact keyword or query being monitored. The report should retain the keyword’s search intent, target page and any relevant keyword group or campaign. Grouping terms by topic, product, service or funnel stage makes it easier to assess whether a page is performing for a subject as a whole rather than relying on isolated terms.

Where the tracked keyword has several interpretations, the checker should make that clear. A product query, for example, may produce different results from an informational query containing similar words. Search intent helps explain why a page has moved and whether the selected landing page is appropriate.

Position and ranking URL

The core result should include the position recorded for the website and the URL shown in the result. Reporting the URL is essential because rankings can move between pages. This may indicate that Google has selected a more relevant page, that two pages are competing for the same topic, or that internal links and page content need review.

Position should be recorded consistently. The report should distinguish between an organic listing and other elements on the results page, and should indicate when the website is not found within the checker’s configured search range. A result outside that range should not be presented as though it were a precise position.

It is also useful to record the result type, such as a standard organic listing, a product result, a local listing or another enhanced result. This prevents different forms of visibility being combined without explanation.

Location, language and search settings

Ranking data should identify the country, region, town or other location used for the check, where location targeting is relevant. Local results can vary substantially between nearby areas, so a national check cannot be treated as a reliable substitute for a town-level check.

The report should also show the search language and any relevant regional settings. These details make checks repeatable and help explain differences between a customer’s manual search and the recorded result. Where the search is performed from a defined location rather than a broad market, that method should be visible in the report.

Device-specific results

Mobile and desktop rankings should be reported separately. The layout, result formats and user experience can differ by device, and a page may perform differently because of content presentation, speed, usability or the amount of space available for each result.

Combining mobile and desktop positions into one average can hide an important problem. A better report shows each device independently and provides a comparison that highlights meaningful divergence. Device data should be collected using a consistent configuration so that changes reflect search performance rather than altered checking conditions.

SERP features and real visibility

A position checker should identify SERP features that appear for the keyword and record whether the website is present in them. These may include local results, maps, featured answers, image results, video results, shopping results, news results, related questions and other enhanced formats.

SERP features matter because a standard organic position does not describe the whole results page. A page ranking below a prominent feature may receive less attention than its position suggests, while appearing in an additional feature can increase visibility without changing the standard organic position. Reports should therefore distinguish between organic position, feature presence and the website’s ownership or inclusion in that feature.

Where possible, the checker should record the feature’s position or prominence, the URL associated with it and whether it belongs to the tracked website. A SERP snapshot or comparable evidence can be particularly useful when investigating a sudden change, provided it is collected in a way that respects applicable search engine requirements.

Date, time and history

Each result needs a timestamp, including the relevant time zone where checks are scheduled. Search results change over time, and a date without a time or collection context can make short-term movements difficult to interpret.

Historical reporting should show the current position alongside previous checks, position changes and longer-term trends. Useful views include:

  • movement for an individual keyword and URL;
  • average or representative performance for a keyword group;
  • the number of terms improving, declining or remaining stable;
  • changes by location and device;
  • newly ranking and lost keywords;
  • changes in the URLs receiving visibility; and
  • changes in SERP feature ownership or appearance.

Trend data should not rely solely on averages. An average can improve because one term rises while several commercially important terms decline. Reports should allow results to be filtered by intent, business value, location, device and landing page.

Visibility and opportunity measures

Position data becomes more useful when accompanied by a visibility measure that reflects the layout of the results page. This may take account of ranking position, search features and the proportion of tracked queries for which the website is visible. The calculation should be documented so that the measure can be interpreted consistently.

Other useful indicators include the number of tracked keywords with a visible result, the share of keywords for which a target page appears, and changes in visibility for priority groups. These measures should support position data rather than replace it. A single visibility score cannot explain which query, URL or SERP feature caused a change.

Competitor and result-page context

A report can provide useful market context by showing which domains occupy important results for the same tracked queries, without treating competitor movement as a direct measure of success or failure. More importantly, it should show the type and quality of results appearing around the website: established pages, local listings, forums, media, product results or other formats.

This context helps assess the level of competition and whether the search landscape has changed. It can also reveal that a ranking decline is caused by additional result types entering the page rather than by a simple loss of relevance.

Data quality and interpretation

Reliable reports should make the checking method clear. They should record whether results were collected from a defined location, whether personalisation was excluded, which device configuration was used and whether the search engine settings remained consistent. If a check failed, returned incomplete data or encountered an unusual results page, that status should be visible rather than silently treated as a ranking change.

Results should also be compared with other evidence, including organic traffic, conversions, impressions, click-through rate and indexed-page changes. Ranking movement is an important diagnostic signal, but it does not measure business outcomes by itself. A page can gain impressions without a major position change, or retain its position while receiving fewer clicks because the results page has changed.

Actionable reporting

The most helpful position checker turns recorded data into investigation prompts. A report should make it possible to identify:

  • keywords that have declined and the URLs affected;
  • pages that are ranking for unintended keywords;
  • terms where two pages appear to compete;
  • mobile or local performance that differs from broader results;
  • queries where a SERP feature creates an opportunity;
  • new ranking terms that may deserve content or internal-link support; and
  • large movements that need technical, content or indexing checks.

It should not claim that a ranking change has a single cause without supporting evidence. Instead, the report should provide enough detail to guide the next check: review the affected page, compare the relevant SERP, inspect technical changes, assess search intent and then decide whether content, internal linking or broader SEO work is justified.

In practice, the strongest ranking report combines exact position data with the conditions under which it was collected, the URL that appeared, the features surrounding it and the direction of change over time. That combination allows performance to be interpreted accurately and gives an SEO team a reliable basis for deciding what to investigate next.

A position checker should report SERP features alongside standard organic rankings because the layout of a results page affects how visible a listing is. A page in an organic position may receive less attention when map results, shopping listings, videos, images or other enhanced results appear above it, while inclusion in one of these features can increase visibility without changing the organic position.

Useful reporting should show which features appeared for each keyword and whether the tracked website was included. Where available, it should also identify the associated URL and the feature’s position or prominence. This helps distinguish a genuine ranking change from a change in the results-page layout.

  • Record the standard organic position separately from feature visibility.
  • Show whether the website owns or appears in the relevant feature.
  • Compare feature changes over time for priority keywords.
  • Use the result-page context to identify opportunities for content, structured data or local SEO improvements.

Review your Google ranking data

Review your Google ranking data by keyword, URL, location, device and SERP feature to identify meaningful changes in visibility. Use these findings to prioritise the pages and search queries that need further SEO investigation.