Measurement and Optimization
Search Console Query Review
Turn query and page performance data into evidence-based research, refresh, internal-link, consolidation, snippet, technical, or monitoring actions.
Free editable Markdown · SEO analysts, content strategists, and site owners ·
Accessible HTML preview
Blank template
The downloaded file contains the same fields in editable Markdown.
Review configuration
- Property and reviewer
- [Enter]
- Date range and comparison
- [Enter]
- Search type
- [Enter]
- Country and device
- [Enter]
- Page/query filters
- [Enter]
- Export reference/date
- [Enter]
- Site releases/migrations
- [List]
- Data limitations
- [Enter]
Query-intent group
- Intent label
- [Navigate / Use / Learn / Compare / Troubleshoot / Other]
- Example queries
- [List representative, privacy-safe]
- Clicks/impressions/CTR/position
- [Record with period]
- Current appearing pages
- [List]
- Best intended page
- [Enter]
- Reader task
- [Describe]
- Query mix change
- [Enter]
- Evidence gap
- [Enter]
Page inspection
- URL/title/H1
- [Enter]
- Direct answer and unique value
- [Enter]
- Evidence/freshness
- [Enter]
- Snippet expectation
- [Enter]
- Internal links and next step
- [Enter]
- Index/canonical/redirect status
- [Enter]
- Overlapping internal pages
- [List]
- User/support evidence
- [Enter]
Decision and review
- Observation
- [Data fact]
- Hypotheses/alternatives
- [List]
- Action
- [Research / Refresh / Link / Consolidate / Technical / New page / Monitor]
- Owner and scope
- [Enter]
- Baseline and annotation
- [Enter]
- Recheck window
- [Enter]
- Outcome/limitations
- [Enter]
- Next decision
- [Enter]
How to use this template
- Save property, filters, periods, export, releases, and technical context.
- Group queries by real reader intent and map them to current and intended pages.
- Inspect each page's usefulness, evidence, snippet, internal links, and overlap.
- Separate observations from hypotheses and choose the least speculative action.
- Annotate implementation and recheck page-query behavior with qualitative evidence.
Define a reproducible view
Record property, date range, comparison, search type, country, device, page, query filter, and any data limitations before interpreting totals. Use enough time to reduce noise while respecting product releases, migrations, seasonality, and demand changes. Export the working data and note when it was obtained. Metrics are aggregated and contextual; average position is not a fixed rank, and click-through rate changes with result features, brand familiarity, device, and query mix. Validate indexing, canonical, redirects, and site changes separately when technical issues are suspected.
Group queries by reader task and page assignment
Read query language for distinct intents: navigate to the brand, use a tool, understand a method, compare, troubleshoot, find pricing, or download a resource. Do not create one page for every phrase variation. Map each intent group to the page that currently appears and the page that should best satisfy it. Inspect the live page for direct answer, evidence, title and description, structure, freshness, internal links, and next step. Look for one query group spread across duplicate pages or one page appearing for conflicting tasks.
Choose action from diagnosis, not metric superstition
High impressions and low clicks may justify snippet and intent inspection, but not an automatic title rewrite. Falling clicks can reflect position, demand, result layout, competition, indexing, or page quality. Choose research, refresh, internal link, consolidation, technical fix, new page, or monitoring with explicit evidence. Save a baseline, annotate changes, and review after sufficient processing time without promising a ranking gain. Pair search data with page quality, support evidence, analytics, and reader research.
See the fields in context
Fictional example: score interpretation queries
Query metrics are intentionally omitted; this does not report GPTHuman Search Console data.
- Pattern: An imaginary group asks how to interpret a detector score, while a product page and methodology page both appear.
- Inspection: The methodology explains limits; a help article better serves the practical task.
- Action: Improve contextual links and direct-answer wording before considering a new duplicate page.
- Alternative: Monitor because a short period overlaps an imaginary interface release.
- Recheck: Compare page assignment and reader outcomes after processing, without promising rank.
Frequently asked questions
Should every high-impression query become a new page?
No. Group variations by intent and improve the best existing page unless a materially different task requires a distinct resource.
Is low CTR proof of a bad title?
No. Position, result features, brand, device, query mix, and intent also affect clicks.
How should average position be interpreted?
As an aggregate across impressions and contexts, not one stable rank for every user.
When should changes be reviewed?
After enough time for collection and search processing, considering volume, seasonality, and concurrent site changes.