SEO analysis with Claude and Search Console: nine questions that replace an afternoon of filters
Connect Search Console to Claude in a few minutes and ask nine SEO questions, from cannibalization to content decay. Each one is ready to copy.
The HeyMetra Team Updated 6 min read
Key takeaways
- With Search Console connected to Claude through HeyMetra, SEO checks that take an hour of filters and exports become one question: cannibalization, falling clicks, near-miss rankings, content decay and more.
- Setup takes a few minutes: sign in with Google in HeyMetra, pick your site and add one address to Claude or ChatGPT. There is no Google Cloud project to create.
- Ask about full weeks or months that have ended. Search Console figures arrive two to three days late, so a period that ends today looks like a drop that never happened.
- Two of your pages showing for the same search is not a problem by itself. It is worth fixing when both pages answer the same question for the same reader.
- With Google Analytics 4 on the same HeyMetra connection, one question can show search clicks next to what those visitors did on the site.
Search Console has the answers to most SEO questions about your site, but getting them out means filters, two date ranges and often a spreadsheet. Connect Search Console to Claude with HeyMetra and each of those checks becomes one question in plain words. Below are nine of them, with the question to copy and what to do with the answer. The examples follow an online coffee shop, and each one works the same in ChatGPT, Grok, Perplexity and Claude Code. A few of the examples below are shown in those AI assistants.
Set it up in a few minutes
- Connect your site. In HeyMetra, choose Google Search Console, sign in with Google and pick your property.
- Add HeyMetra to Claude. Add
https://mcp.heymetra.com/mcpas a custom connector in Claude, or in ChatGPT’s developer mode. Grok and Perplexity take the same address. - Ask. Copy any question below and change the details to your site.
Everything happens in the browser, and the connection only reads, so Claude cannot change anything in Search Console. If you want to compare this with the do-it-yourself route, our guide to Search Console MCP servers lays both out.
One habit keeps the answers right: ask about full weeks or months that have ended. Google finishes its figures two to three days late, so “the last 7 days” asked today includes days with nothing in them yet.
1. Two pages competing for the same search
Two of your pages showing for one search can split the clicks. It can also be fine. Google’s John Mueller has said that “pages aren’t duplicates just because they happen to appear in the same search results page”. The case worth fixing is two pages that answer the same question.
| Page | Clicks |
|---|---|
| /products/hand-grinder | 96 |
| /blog/best-grinder-for-pour-over | 31 |
A product page and a buying guide usually serve different readers and can both stay. Two blog posts answering the same question are the ones to merge.
2. Pages seen more but clicked less
When a page’s impressions rise and its clicks fall, it is either showing up lower for broader searches or losing clicks to something above it.
You: Which pages had more impressions in October than in September but fewer clicks? Include their position for both months.
If the position fell, the page is reaching new searches it does not answer well yet. If the position held, look at what now sits above you. On question searches it is often an AI Overview, which Search Console’s own Generative AI report can confirm.
3. Searches you almost rank for
Searches where you sit 5th to 15th with real impressions are the easiest wins, because the page already ranks and a better title or a missing section can lift it into the top three.
The same HeyMetra connection works in ChatGPT. Here is this question asked there.
| Search | Position |
|---|---|
| how to make cold brew at home | 8.1 |
| ethiopian coffee beans | 6.4 |
| low acid coffee | 12.6 |
Then ask Claude to group them by page. One page often holds several of these searches, and improving it lifts all of them.
4. Pages slowly losing traffic
Content decay is a page losing a little every month. It never shows up as a sudden drop, so you only see it over a long stretch.
Grok uses the same connection too. Here is the decay question in Grok, with the answer drawn as a chart.
| Page | A year ago | Latest three months |
|---|---|---|
| /blog/french-press-guide | 3,120 | 1,980 |
| /blog/coffee-to-water-ratio | 2,410 | 1,890 |
| /collections/gift-sets | 1,760 | 1,420 |
| /blog/best-beans-for-espresso | 1,530 | 1,300 |
| /products/gooseneck-kettle | 980 | 870 |
Compare with the same months a year earlier, so a seasonal dip is not blamed on the page. Search Console keeps about sixteen months, enough for one year-on-year comparison.
5. Questions people bring to your pages
Long, question-shaped searches are where AI Overviews appear most, and where being the source an answer quotes matters more than ranking third.
You: List searches from the last three full months that start with how, what, why, can, does or is, or contain “vs”. Group them by the page that ranks.
Look for questions with impressions but no page that answers them directly, and for pages that rank for a question but hide the answer under a long introduction. Google’s own advice on AI search asks for content that answers the question people asked.
6. Brand and non-brand searches
Clicks on your brand name mostly come from people who already know you. Non-brand clicks show what SEO brings in.
You: Our brand terms are [shop name], [misspelling 1] and [misspelling 2]. Split clicks for the last six full months into searches with any of them and all other searches, by month.
Google hides searches that very few people typed, and almost all of those are non-brand. The non-brand share in the answer is the minimum.
7. Pages Google has not indexed
Checking index status page by page in Search Console is slow. Claude can check a whole section in one go.
You: Take every page under /collections/ that had impressions in the last three months and check whether each one is indexed. For those that are not, what reason does Google give, and which page did it choose instead?
Google allows 2,000 of these checks per site per day, so on a large site ask section by section.
8. After a core update
When traffic drops around a core update, first check whether the drop lines up with the update’s dates and where it sits.
You: The May 2026 core update ran from 21 May to 2 June. Compare clicks per page for the two full weeks before 21 May with the two full weeks after 2 June. Which sections of the site lost the most?
Google publishes the dates on its Search Status Dashboard. The answer shows where the loss is. It does not prove the update caused it; a site change or a seasonal dip can land in the same weeks.
9. Search clicks next to what visitors did
Search Console data ends at the click. Whether those visitors stayed and bought is in Google Analytics 4. Connect GA4 to the same HeyMetra workspace and one question reads both. This one is asked in Perplexity, through the same HeyMetra connection.
| Page | Clicks → purchases |
|---|---|
| /blog/cold-brew-guide | 4,210 → 12 |
| /collections/ethiopia | 1,880 → 41 |
| /products/hand-grinder | 1,640 → 37 |
A click and a GA4 session are counted differently, and cookie banners keep some visits out of GA4. Compare the pages with each other rather than matching the numbers exactly.
Before you act on an answer
- Check the dates. The answer should say which days it covers; if it does not, ask.
- Check by page for totals. A total of named searches is always lower than a total by page, because rare searches are hidden.
- Treat causes as a lead. Search data shows what changed and where. Why it changed usually needs a look at the live results and at your own recent changes.
- #seo
- #google-search-console
- #claude
- #keyword-cannibalization
- #ai-overviews
Frequently asked questions
Can Claude analyze my Search Console data?
Yes, once Search Console is connected. With HeyMetra you sign in with Google, pick your site and add HeyMetra's address to Claude; Claude then reads your searches, pages and index status directly and answers in the chat.
How do I find keyword cannibalization with Claude?
Ask for searches where two or more of your pages each get a good share of the impressions, with the clicks and position of each page. Then read the two pages: if they answer different questions, leave them alone.
Why does Claude's click total differ from the Search Console screen?
Usually because the answer covers only finished days, or because it adds up named searches, which leave out rare searches Google hides for privacy. Ask which days the answer covers and ask for totals by page.
Can Claude tell whether a Google core update hurt my site?
It can compare your clicks before and after the update dates Google publishes, page by page. That shows whether the drop lines up with the update, not proof that the update caused it.
Can it see AI Overview traffic separately?
Not through Search Console's API, which counts AI Overviews and AI Mode with normal web results. Search Console's own Generative AI report shows them separately in Google's screen. What Claude can do is list the question-style searches where those answers appear most.
Can Claude fix the problems it finds?
Not through HeyMetra. The Search Console connection is read-only, so it can find and explain problems but cannot submit sitemaps or change anything. The fixes happen on your site.