Integration

Connect Google Search Console to Claude Code

Claude Code already reads and edits your codebase. Add GenieSeo as a remote MCP server and it can also read your live Search Console, GA4 and PageSpeed data, so it can find the page losing clicks and fix the template that renders it in the same session.

Setup in 3 steps

    1

    Create a GenieSeo account and connect Google

    Go to /signup and choose Continue with Google. Google asks for Search Console (the webmasters scope, read-write because sitemap submission needs it) and GA4 (analytics.readonly). Keep both ticked.

    2

    Add the server from your terminal

    GenieSeo is a remote server, so use the HTTP transport. With --scope userit's available in every project on your machine:

    bash
    claude mcp add --transport http --scope user genieseo https://seo.geniedial.in/mcp
    3

    Sign in with /mcp

    Start claude, type /mcp, select genieseo and choose to authenticate. Your browser opens the GenieSeo sign-in; approve it and come back. Claude Code stores and refreshes the token for you. If no browser opens, copy the URL Claude Code prints.

Command syntax, scopes and the OAuth flow follow Anthropic's Claude Code MCP documentation.

User, project or local scope

claude mcp add takes a --scope flag that decides where the server is saved. Pick based on who needs the SEO data:

ScopeLoads inStored in
localCurrent project only, just you (the default)~/.claude.json
userAll your projects~/.claude.json
projectThis repo, shared with the team via git.mcp.json

For a marketing site repo where several people do SEO work, project scope is the useful one. It writes this to .mcp.json:

bash
claude mcp add --transport http --scope project genieseo https://seo.geniedial.in/mcp
json
{
  "mcpServers": {
    "genieseo": {
      "type": "http",
      "url": "https://seo.geniedial.in/mcp"
    }
  }
}

The file holds only the URL. Each teammate signs in with their own GenieSeo account through /mcp, so nothing secret is committed. Claude Code asks each person to approve project-scoped servers the first time they open the repo.

Check that it's connected

Inside Claude Code, /mcp lists every server with its status. genieseo should show as connected with 40 tools: 23 for Search Console, 12 for GA4, 2 for PageSpeed Insights and the SEO task tracker. From the shell:

bash
claude mcp list           # is genieseo configured?
claude mcp get genieseo   # scope, URL, connection status
claude mcp login genieseo # sign in from the shell instead of /mcp
claude mcp remove genieseo

Then ask something that can only be answered with live data: "Use genieseo to list my Search Console properties." Claude Code should call list_properties and ask your permission the first time.

Prompts that combine Search Console with code edits

Chat assistants can tell you which pages underperform. Claude Code can also open the file that renders them. Run these from the root of your site's repo:

Low-CTR titles → edit the repo

"Using genieseo, find pages on sc-domain:example.com with more than 1,000 impressions and CTR under 1.5% in the last 28 days. For each, find the file in this repo that sets its <title> and meta description, propose a rewrite that matches the top query, and show me the diff before editing."

Indexing check after a deploy

"I just shipped the pages in src/app/guides/. Build their live URLs from the routes, run inspect_url_enhanced on each, and list any that aren't indexed or have a Google-selected canonical different from ours. Then check our canonical tags in code."

Striking-distance content

"Run get_keyword_opportunities for positions 4–20. For the top 5 pages, open the source file and suggest one section to add that targets the query we rank for but don't mention."

Sitemap sanity

"Read our sitemap generator in this repo, then call list_sitemaps_enhanced. Do the URLs we generate match what Search Console reports as submitted and indexed? Flag routes missing from the sitemap."

Ask for the diff before Claude Code edits. Search Console data lags two to three days, so judge a title change after a few weeks, not the next morning: compare_search_periods on the same page shows whether the rewrite moved CTR. Working on Core Web Vitals instead? See PageSpeed Insights in Claude Code.

Troubleshooting

genieseo shows "needs authentication" in /mcp

You added the server but haven't signed in yet, or the token was cleared. Select it in /mcp and authenticate, or run claude mcp login genieseo from the shell.

The browser sign-in never returns to Claude Code

Finish the GenieSeo sign-in in the browser that opened, then switch back to the terminal. On a remote machine or container with no browser, copy the URL Claude Code prints and open it locally, or use claude mcp login genieseo --no-browser.

No genieseo tools in this project

The server was added with the default local scope in a different directory. Run claude mcp get genieseo to see its scope, then re-add it with --scope user, or commit a project-scoped .mcp.json.

Tool calls fail with a permissions or property error

The Google account connected to GenieSeo can't access that Search Console property, or Search Console was unticked on Google's consent screen. Reconnect Google from the GenieSeo dashboard. Domain properties use the sc-domain:example.com format.

Headless or CI runs can't do OAuth

Use your personal token URL from the GenieSeo dashboard (https://seo.geniedial.in/mcp/u/<token>) instead of the OAuth URL. Treat it like a password: keep it in local or user scope, never in a committed .mcp.json.

Using Claude on the web or Claude Desktop instead? Here's how to connect Google Search Console to Claude.

FAQ

What is the claude mcp add command for Google Search Console?+

claude mcp add --transport http --scope user genieseo https://seo.geniedial.in/mcp. Then run /mcp inside Claude Code, pick genieseo and sign in with GenieSeo in your browser. The --scope user flag makes it available in every project.

Do I need a Google Cloud project or API key?+

No. GenieSeo is hosted and handles the Google OAuth client. You sign in once on seo.geniedial.in with Google, and Claude Code authenticates to GenieSeo with OAuth. There is no client_secrets.json or service account to manage.

Should I use user scope or project scope?+

User scope if only you need SEO data, across all your repos. Project scope writes the server to .mcp.json so teammates get it when they pull; each person still signs in with their own GenieSeo account, so no credentials are committed.

Can Claude Code change my Search Console settings?+

GenieSeo requests the webmasters scope, which Search Console needs for sitemap submission. Destructive tools such as delete_site and delete_sitemap are disabled on the hosted server, and Claude Code asks before it calls a tool unless you have allowed it.

SEO data next to your code.

40 tools · Search Console, GA4 and PageSpeed · One command

Related