Skip to main content
Use the reporting metadata alongside the numbers. A useful SEO answer identifies the property, date range, filters, grouping dimensions, and coverage.

​
Core metrics

When comparing aggregate CTR, divide total clicks by total impressions. Averaging row-level CTR values gives each row equal weight and can misrepresent the result. Google explains the metrics in its Search Console performance report guide.

​
Dates and freshness

Search Console date boundaries use Pacific time. Use explicit inclusive start and end dates when reproducibility matters. For a routine complete-period review, choose a range ending at least three days ago and check the response’s freshness warnings. This is a conservative workflow convention, not a guarantee that every source is complete on that date. Advanced analytics accepts data_state: "final" or "all". Use final data for completed-period comparisons. If you include preliminary data, label it.

​
Missing rows and coverage

A missing query or page is unknown, not automatically zero. Search Console returns bounded results and may omit data. Google documents that the Search Analytics API does not guarantee all rows. In HyperGSC, sorting applies to the returned page of rows. It does not establish the global top results for an arbitrary metric across Google’s complete dataset. Read pagination, truncation, and coverage warnings before drawing conclusions.

​
Compare like with like

Keep the property, search type, filters, grouping, and period lengths consistent. Look at query mix, device, country, demand, and seasonality before attributing a traffic movement to a site edit. A one-point improvement in average position and a rise in clicks are observations. They do not, by themselves, prove that a recorded SEO change caused the improvement. See search analytics for request examples and weekly search reviews for an analysis workflow.