The fastest content opportunity is often hiding inside a page that already earns impressions. Search Console shows the language Google users associate with that URL. When those queries are grouped carefully, they can reveal missing explanations, comparison needs and follow-up questions. Claude can accelerate the grouping, but the data and editorial judgement must lead.
Start with a page, not the whole property
Open Search Console, select Search results, move to the Pages tab and choose a URL. Then return to Queries so the report remains filtered to that page. Set a useful date range, compare periods if the page has declined and export the table. Google's Search Analytics documentation explains the available dimensions and reminds users that returned data is grouped and sorted rather than a complete record of every query.
Clean the export before analysis
- Keep query, clicks, impressions, CTR and average position.
- Remove rows unrelated to the page's real purpose.
- Flag branded terms separately from non-branded discovery.
- Add the current page copy and its conversion goal.
- Remove personal or sensitive data before uploading to any AI service.
Use a prompt that asks for evidence, not volume
A useful prompt is: I am providing the current page copy and a Search Console query export filtered to this URL. Group the queries by user intent and concept. Identify clusters with meaningful impressions that the page only partially answers. For each cluster, recommend whether to improve an existing section, add a new H2 or create a separate page. Quote the supporting query rows and explain the decision. Do not force irrelevant terms into the copy.
Distinguish expansion from cannibalisation
Not every query belongs on the current URL. If a cluster represents a different task, audience or funnel stage, it may deserve its own page. Check whether another URL already receives those impressions. The Keyword Cannibalisation Checker and cannibalisation guide can prevent one refresh from creating a new conflict.
Write the new section for the reader
Lead with the answer the query cluster needs, then add the detail necessary to make it reliable. Include first-hand examples, limitations, dates or sources where the decision depends on them. Use query language naturally, but do not paste a list of variants into the section. Search systems understand related wording, and readers notice awkward optimisation.
Strengthen the internal path
Link the refreshed section to a deeper supporting page when the reader needs more detail, and link relevant hub pages back to the refreshed URL. Use descriptive anchors that explain the destination. Run the finished page through the Internal Link Checker.
Measure the refresh as an experiment
- Record the publication date and changed sections.
- Confirm the updated page is crawlable and indexed.
- Track the target query clusters, not only the page total.
- Review impressions and position before judging clicks.
- Assess qualified conversions so extra traffic is not mistaken for business value.
For a repeatable reporting view, use the GSC Dashboard and the CTR opportunity guide to separate content coverage from snippet performance.
Free tool · no account needed
Build a page-level query view before deciding what your content needs next.
Runs entirely in your browser. No uploads, no tracking, no paywall.
Open the GSC Dashboard →