Guide

How to use Claude for SEO with your own Search Console and GA4 data

Claude writes good titles, briefs and summaries, but it cannot see your rankings. Connect it to Google Search Console and GA4, and it answers SEO questions from your own clicks, queries and landing pages. This guide shows the setup and six prompts to copy.

Last updated

What Claude can do for SEO, with and without data

Without data, Claude answers from what it knows about SEO in general. When you ask about your own site, it can only guess. With Search Console and GA4 connected, it fetches the numbers it needs for each question.

SEO taskClaude without dataClaude with Search Console and GA4
Weekly traffic checkClaude cannot see your traffic, so it can only list things to check.Clicks, impressions, CTR and position against the week before, with the queries and pages that moved.
Rewrite titles and meta descriptionsClaude writes titles from the page text and guesses which searches matter.Claude writes titles for the searches that already show the page, ranked by impressions.
Find out why traffic droppedA general list of possible causes, such as updates, seasonality or technical errors.The pages and queries that lost clicks, whether those pages are still indexed, and whether visits from Google fell too.
Check landing page qualityAdvice on what a good landing page looks like.Engagement rate and key events for each landing page that gets organic search visits.
Check indexing and sitemapsSteps to follow in the Search Console interface.Index status, last crawl, Google's chosen canonical and sitemap errors, read from Search Console.

Claude reaches outside data through MCP, the Model Context Protocol. An MCP server gives Claude a few tools, and Claude calls them when your question needs them. QuerySail runs two hosted MCP servers, one for Google Search Console and one for Google Analytics 4. There is nothing to install and no Google Cloud project to set up.

Choose your Claude app

Claude's free plan allows one custom connector. That is enough for Search Console on its own. To use Search Console and GA4 in the same chat, add both connectors, which needs a paid Claude plan.

Connect Claude to Search Console and GA4

  1. Create a QuerySail account. The trial needs no card.
  2. Open Account → Connections. Select Connect Search Console, then Connect Google Analytics if you use GA4, and approve read-only access on Google's consent screen each time.
  3. On claude.ai or in Claude Desktop, open Customize → Connectors, select + Add, then Add custom connector. Paste an endpoint below as the server URL and sign in with your QuerySail account. On a paid Claude plan, repeat for the second endpoint.
  4. In a chat, select + → Connectors and turn on both QuerySail connectors.
  5. Ask "Which Search Console and Google Analytics properties can you access?" to check the connection.
https://mcp.querysail.com/gsc/mcp
https://mcp.querysail.com/ga4/mcp

For Claude Code, add each server with one command, then run /mcp, choose the server and sign in:

claude mcp add --transport http --scope user querysail-gsc https://mcp.querysail.com/gsc/mcp
claude mcp add --transport http --scope user querysail-ga4 https://mcp.querysail.com/ga4/mcp

Claude Code can also use the QuerySail skills, which tell it which tool to call for each question and how to report the numbers. The install commands and the steps for other apps are in how to connect Search Console to ChatGPT and Claude and how to connect GA4 to ChatGPT and Claude.

Six SEO prompts for Claude

The prompts use the sample site Sample Outdoors. Its Search Console property is sc-domain:sample-outdoors.example and its GA4 property is Sample Outdoors (web). Run the prompts in one chat, so each step can use the results before it. Replace the names and dates with your own.

1. Run a weekly check

For sc-domain:sample-outdoors.example, compare the last 7 days with the 7 days before. Show the totals, then the 5 queries and the 5 pages that gained or lost the most clicks.

Tool: compare_performance

Claude gets both totals with absolute and percent changes, plus the top gainers and losers. The tool takes one breakdown per call, so Claude calls it once for queries and once for pages. For seasonal sites, ask to compare with the same weeks last year instead.

2. Find pages that get seen but not clicked

For the last 28 days, list pages with more than 1,000 impressions and a CTR below 0.02. For each page, show its top 3 queries by impressions and their average position.

Tool: get_performance

A page with many impressions and few clicks often has a title that does not match the search. QuerySail returns CTR as a fraction, so 0.02 means 2%. Claude filters the rows it fetches, and Google returns only the top rows, so rare pages can be missing. Low CTR is normal for pages in position 8 or worse, so look first at pages already in the top 5.

3. Rewrite the title and description

For the first page in that list, write 3 title tags under 60 characters and 2 meta descriptions under 155 characters. Use the words from its top queries. Do not promise anything the page does not cover.

No tool call. Claude works with the rows it already has.

Claude uses the queries it already fetched. In Claude Code, you can also ask it to open the page's source file in your repository and make the change. After you publish, wait two to four weeks and run step 4 for that page to see if CTR changed.

4. Find out why a page lost traffic

Compare clicks for https://sample-outdoors.example/guides/best-hiking-boots/ for the last 28 days with the 28 days before. Did impressions, CTR or average position change most? Which queries lost the most clicks?

Tool: compare_performance

The answer splits the change in clicks into a part from impressions and a part from CTR. Fewer impressions with the same position usually means less demand. Steady impressions with a lower CTR and a worse position means the page shows lower for the same searches.

5. Check that the page is still on Google

Inspect that page. Is it indexed, when did Google last crawl it, and does Google use the canonical the page declares?

Tool: inspect_urls

This rules out a page that left the index, a noindex tag, a robots.txt block or a different canonical. The result describes the version Google last indexed, not a live test of the page today. If the page is not indexed, the guide on 'Crawled - currently not indexed' below shows the next steps.

6. See what visitors from Google did next

For Sample Outdoors (web), show sessions, engagement rate and key events by landing page for the last 28 days. Only include sessions where source / medium is google / organic. Sort by sessions.

Tool: run_report

Search Console stops at the click. GA4 shows whether those visitors stayed and converted. The google / organic filter keeps only Google's unpaid results, which is the traffic Search Console counts. A page with many organic sessions and a low engagement rate may not answer the search, even if it ranks well.

Example answer

This is the kind of answer step 4 and step 5 give together. We made up the numbers, and they do not come from a real site.

Made-up example. For https://sample-outdoors.example/guides/best-hiking-boots/, 2026-10-20 to 2026-11-16 (Pacific Time) against the 28 days before, clicks fell from 1,240 to 980, down 21%. Impressions stayed about the same, down 2%. CTR fell from 0.041 to 0.033, and average position went from 3.6 to 5.1. "best hiking boots" lost the most clicks, down 150. The page is indexed, Google last crawled it on 2026-11-12, and Google uses the declared canonical. Almost all of the change in clicks is in the CTR part, and average position fell at the same time. The page did not leave the index. The data does not show why the position fell.

Tips for better SEO answers from Claude

Limits to know

Other ways to use Claude for SEO

You can export a Search Console or GA4 report as a CSV file and upload it to a chat. That is free and works on any Claude plan, but each new question about another date range or breakdown needs a new export. SEO tool vendors such as Ahrefs and Semrush also offer MCP servers with backlink and keyword data that Search Console does not have. See the best SEO MCP servers to compare them. QuerySail suits you if you want your own Google data in Claude without exports or a Google Cloud project.

Try it on your own site

QuerySail costs $8 a month for both servers after a 7-day free trial with no card. For longer workflows, read how to find striking-distance keywords, how to fix pages that are crawled but not indexed and how to create a monthly SEO report.

Questions, answered

Something else? See support.

Is Claude good for SEO?

Claude is good at the writing and analysis parts of SEO: titles, descriptions, outlines, content briefs and reading data. On its own it cannot see your rankings or traffic, so its advice about your site is general. Connect it to Search Console and GA4 and it can base its answers on your numbers.

Can Claude access Google Search Console?

Yes, through an MCP server. QuerySail is a hosted Search Console MCP server. Add it as a custom connector on claude.ai or in Claude Desktop, or with claude mcp add in Claude Code, and Claude can fetch performance data, compare periods, inspect URLs and list sitemaps.

Which Claude app should I use for SEO?

Use claude.ai or Claude Desktop for reports and questions about your data. Use Claude Code if your site's source is in a repository, because Claude Code can also open and edit the pages it finds problems with.

Do I need a paid Claude plan?

Not for Search Console alone. Claude's free plan allows one custom connector, so you can connect one QuerySail server. To use Search Console and GA4 in the same chat you need two connectors, which needs a paid Claude plan. Your Claude plan is separate from QuerySail.

Can Claude change my Search Console or GA4 settings?

No. The QuerySail tools only read data. They cannot request indexing, submit sitemaps or change any setting in Search Console or Google Analytics.

Can Claude explain why my rankings changed?

Claude can show what changed: which queries, pages, countries or devices moved, and whether the pages are still indexed. The data does not prove a cause. Treat any reason Claude suggests as an idea to check.

Does this work in ChatGPT too?

Yes. The same QuerySail endpoints work in ChatGPT with developer mode, and in Codex, Cursor and VS Code. The prompts in this guide work there as well.

How much does it cost?

QuerySail costs $8 per month for both Search Console and Google Analytics, after a 7-day free trial that needs no card.