Review a defined page and query group over comparable periods. Look for changes in impressions, clicks and the pages receiving them. Treat hidden queries and changing search appearances as limits; average position alone does not explain a business result.
End a Search Console review with a page decision: improve an answer, investigate a technical issue or leave the page alone.
Choose important pages using the four-pillar framework, then review them consistently.
1. Record the comparison
Open the intended property and Search results report. Save the dates, search type, country and device filters. Use comparable complete periods and note seasonality or releases.
Google's filtering guidance explains how filters combine. Preserve them with the review.
2. Filter to one page
In the Pages tab, click the exact page row and confirm the page filter appears above the chart. Switch to Queries to see the associated visible query rows. Keep the dates and other filters unchanged; export this view and label the file with the page and comparison periods. Group the queries by the reader's likely task, alongside clicks and impressions.
Open the page. Does it answer those tasks clearly? An unexpected do-it-yourself query on a service page warrants investigation; it does not automatically justify a tutorial rewrite.
3. Reverse the view
Click a query row to add its filter, then remove the page filter and switch to Pages. Check that the query filter remains. You are now asking which pages appeared for that query. Export that view separately. Leaving the page filter on would hide the other pages you are trying to find.
Read each page before treating multiple results as a problem. A guide and service page can serve different needs.
Google's dimensions documentation notes that most performance is assigned to canonical URLs. Use canonical debugging when the address differs from the expected page.

4. Check the limits
Query tables omit anonymized searches and may not contain every row. Google's dimensions guidance explains that query filters also affect how anonymized queries contribute to totals.
A filtered export is not the entire property. Review query mix before interpreting an aggregate change, and do not treat a search click as a qualified inquiry or order.
5. Write one supported action
Choose a specific edit or investigation. Record the page, observed query group, supporting view and intended reader benefit. Leave accurate useful pages alone.
Use SEO review to investigate the search issue and business intelligence to compare it with lead or order records. Our Search Console guide provides broader context.
Use this action record
- Page and query group.
- Dates and exact filters.
- Observation and reporting limitation.
- Proposed change, owner and release date.
- Comparable view to check next.
Preserve the original evidence. Later movement is an observation, not automatic proof that the edit caused it.
Example: two pages appear for one question
Illustrative complete four-week comparison for the same dashboard-cost query, country, device and search type:
| Page | Earlier clicks | Later clicks | Page review | Decision |
|---|---|---|---|---|
| Cost guide | 40 | 32 | Explains cost drivers but omits the requirements needed for a quote | Add the missing preparation explanation and relevant service link |
| Reporting service | 12 | 14 | Scope and enquiry path are clear | Preserve; review actual enquiry quality separately |
Those rows show two different page jobs, not proof of duplicate content or lost revenue. Query privacy and aggregation can prevent a table from reconciling to all report totals. Keep the exported view with the page decision in the search review workbook.
Compare the same query group, page filters, country, device and dates. If the guide attracts research questions but omits a useful link to the service, improve that path. If the service page fails to explain scope, repair the commercial answer. Do not automatically redirect the guide because both URLs appeared. Log the evidence, chosen edit and review date, and compare valid enquiries separately from Search Console clicks.
Sources
- filtering guidancesupport.google.com
- dimensions documentationsupport.google.com
