Many teams want a simple answer to “What rank is our site for this keyword?” Google Search Console answers a more useful question: how often did the site appear for a query, which pages appeared, and how many searchers clicked during a chosen period? Those observations can guide page improvements without pretending every person sees the same result.
Start with the searches that matter to the business
List the services, products, locations, and customer questions the business actually wants to serve. Then compare that list with queries Google reports for the verified Search Console property. A phrase can look commercially valuable but still be irrelevant to the business, so confirm the fit before planning content.
Read query and page evidence together
In Search Console’s Performance report, filter by a query and open the Pages dimension to see which URLs Google showed. The Search Analytics API can group data by both query and page. Use this to select a page for review and to notice when several pages appear for similar searches. Multiple URLs are a reason to inspect intent and internal links; they do not by themselves prove that pages are competing with one another.
Track a small set of measures
- Impressions: how often a result from the property appeared under Google’s counting rules.
- Clicks: clicks from Google Search, not leads or completed sales.
- CTR: clicks divided by impressions; compare similar queries and periods before diagnosing a snippet.
- Average position: an average of the topmost result position across impressions, not a fixed rank every searcher sees.
Google explains that Search results can differ by time, place, device, and search history. It also notes that Search Analytics API results are bounded and may return only top rows. A missing query or page in an API sample does not prove that the site never appeared for it.
Compare like with like
Save the reporting period and property with each snapshot. Compare periods of similar length, account for seasonality, and avoid overreacting to daily changes. Rolling 90-day totals overlap when captured on consecutive days, so label that comparison clearly. A complete month compared with the previous complete month is easier to interpret than two overlapping windows.
Turn a signal into reviewed work
- Confirm the query matches a real business priority.
- Identify the page Google associated with it, or verify the page in Search Console if the API sample is incomplete.
- Check whether that page answers the customer’s question with accurate, approved details.
- Make one focused change or record why no change is needed.
- Note who reviewed it and when it was published.
- After Google has had time to recrawl, compare later Search Console data and inspect the live page.
Keep traffic and business outcomes distinct
Search Console clicks, GA4 organic sessions, enquiries, and revenue are separate measurements. Check form submissions, calls, bookings, or sales in the system that records them. If conversion tracking is not configured, say that the outcome is not measured; do not infer it from ranking or traffic changes.
Primary sources: Google Search Analytics API: query method and dimensions · Google Search Console Performance report · Google: impressions, position, and clicks.