AdPlug
Guide · Search Console to Claude

How to Connect Google Search Console to Claude

Connecting Claude to Google Search Console lets it read your clicks, queries, pages and index status straight from Google, without an export or a CSV in sight. This guide covers the five setup steps with screenshots, the first prompts worth running, and how to put Search Console next to your Google Ads data.

Updated 2026-10-14 · 6 minute read

Google Search Console MCP server URL

Paste this into Claude when you add a custom connector.

https://api.adplug.app/mcp/google-search-console
Sign up freeSee setup steps →Example prompts →

01

Two ways to connect, and who each is for

An open-source Search Console MCP server

There are dozens on GitHub. Most run on your own computer, and you set up your own Google Cloud project and credentials before they can sign in to Google. Free, and fine if someone on the team is happy in a terminal.

A hosted MCP connector (this guide)

AdPlug's Search Console MCP covers every Search Analytics report, 14 ready-made analyses, URL Inspection next to a live check of the page, sitemap audits, and your organic queries next to your Google Ads search terms. You sign in with Google and add one address to Claude. The same connection also works in ChatGPT, Cursor, and Claude Code.

02

Which Claude plans can do this

Custom connectors work on Claude's Free, Pro, Max, Team, and Enterprise plans, on claude.ai and the desktop app, per Anthropic's custom connector guide. The Free plan allows one custom connector. Search Console always needs a connector of its own (AdPlug's all-platforms address carries the ad platforms only), so on Claude Free it takes that one slot.

On Team and Enterprise, an Owner adds the connector first under Organization settings → Connectors. Each member then connects their own account from Settings → Connectors.

03

Setup in 5 steps

From a new AdPlug account to Claude answering questions about your search traffic takes about three minutes. There's no Google Cloud project, OAuth client, or API key to set up.

  1. Create your AdPlug account

    Go to adplug.app/signup, sign in with Google or email, and follow the short onboarding. It ends on your AdPlug dashboard.

    AdPlug Create your account screen with a Continue with Google button and name, email and password fields.
    AdPlug sign-up. One click with Google, or an email and password.

  2. Connect Google Search Console to AdPlug

    In onboarding, or any time on the Connections page, click Connect Google Search Console and sign in with the Google account that opens your sites in Search Console. Every property that account can see becomes available to Claude through the one connection.

    AdPlug Ad Platform Connections page with an arrow pointing to the Connect Google Search Console button on the Google Search Console card.
    Click Connect Google Search Console to start Google's sign-in.

    Google then asks you to let AdPlug “View and manage Search Console data for your verified sites”. Leave that box ticked. Without it AdPlug refuses the connection and asks you to connect again.

    Google Ads already connected?

    Search Console has its own Google sign-in, even when it's the same Google account, so you can disconnect one without touching the other.

  3. Add the connector to Claude

    In Claude, open Settings → Connectors (or go straight to claude.ai/customize/connectors) and click Add custom connector. Name it AdPlug - Google Search Console, paste the address below, and click Add.

    https://api.adplug.app/mcp/google-search-console
    Claude's Add custom connector form with the name AdPlug - Google Search Console and the remote MCP server URL https://api.adplug.app/mcp/google-search-console filled in, above the Add button.
    Claude's Add custom connector form with the Search Console name and address.

    Your AdPlug dashboard shows the same name and address with copy buttons. Pick Search Console only in the scope picker first.

    Claude card on the AdPlug dashboard marked Connected, showing the server name AdPlug - Google Search Console and the MCP URL https://api.adplug.app/mcp/google-search-console, each with a Copy button, above three setup steps.
    The Claude card on your AdPlug dashboard, with Search Console only selected. It turns green once Claude is connected.

    Already use AdPlug for your ads?

    Keep that connector and add this one next to it. The all-platforms address carries the ad platforms only, so Search Console always gets its own connector.

  4. Authorise Claude to use AdPlug

    Click Connect on the new connector. Claude opens AdPlug's sign-in: use the same email as your AdPlug account and click Approve. The connector turns Connected and its eight Search Console tools are ready in any new chat.

    AdPlug Authorize access screen asking whether an application may access your AdPlug account, with Deny and Approve buttons.
    AdPlug's authorise screen. Approve to let Claude use your AdPlug connection.

  5. Test the connection

    Start a new chat with the connector switched on in the tools menu and ask:

    “List my Search Console properties.”

    Claude calls the google_search_console_list_sites tool and returns every property your Google account can see, with its type (Domain or URL prefix) and your permission level. If your properties are listed, the connection works end to end.

    Claude answering 'List my Search Console properties' through the AdPlug - Google Search Console connector, with each property's address, type and permission level.
    Claude's reply to the test prompt, with the AdPlug - Google Search Console connector on.

04

What you can ask Claude

These work as soon as Search Console is connected. Swap [site] for your domain and Claude finds the property that covers it. More copy-paste prompts live in the prompt playbooks.

List your properties

“List my Search Console properties.”

Why traffic dropped

“Organic clicks on [site] fell this month. Compare the last 28 days with the 28 before: which pages and queries lost the most, was it rankings, CTR or demand, and did a Google update land in that window?”

Striking distance

“Find queries on [site] ranking between positions 5 and 20 with real impressions. Rank them by the clicks I'd gain at position 3 and tell me which page should win each one.”

Why isn't this page indexed?

“Inspect https://[your-site].com/[page]. Is it indexed? Compare what Google saw with the live page and tell me what to fix first.”

What AI Overviews take

“Compare my CTR at each position on [site] with a year ago, and list the queries losing clicks at the same rank. I want to see what AI Overviews and AI Mode are taking.”

Every site at a glance

“Summarise every property I can see: clicks and impressions for the last 28 days, the change against the 28 days before, biggest sites first.”

06

How changes work

Google's Search Console API allows four changes, and AdPlug covers all of them: submit or resubmit a sitemap, remove a sitemap, add a property, and remove a property. Claude previews each one first (for a sitemap, the preview loads it live and shows its current status in Search Console), then applies it with the same values. Each applied change counts as one AI edit.

The free plan is view only: Claude can preview a change, but applying it needs a paid AdPlug plan. On a team, the owner can set a teammate to View only for Search Console. Report calls and executed changes are recorded in your AdPlug Usage and Audit Log.

No Request indexing button

Google has no API for Request indexing on normal pages. Its Indexing API is limited to job postings and livestream pages, and AdPlug doesn't use it. Submitting a sitemap is the supported route, and URL Inspection tells you why a page isn't indexed.

07

Troubleshooting

Click any item to expand the answer.

Claude returns no Search Console properties
The Google account you connected has to be a user on at least one property. Open search.google.com/search-console with that account and check the site is there, then reconnect on the Connections page with the Google account that has it.
AdPlug says Search Console access was unticked
Google's consent screen lets you untick each permission. Connect again and leave “View and manage Search Console data for your verified sites” ticked.
Claude does not use the connector
Connectors are switched on per chat. Open the tools menu in the message box and make sure AdPlug - Google Search Console is on, or name it in the prompt: “Use AdPlug to list my Search Console properties.”
I can't add another custom connector
Claude's Free plan allows one custom connector, and Search Console can't share the all-platforms address https://api.adplug.app/mcp, which carries the ad platforms only. Remove the old connector, or move to a Claude plan that allows more.
The numbers don't match the Search Console website
Search Console reports in Pacific Time and its last two days or so are still filling in, so AdPlug's date ranges end on the latest finished day unless you ask for fresh data. Totals also include anonymized queries that never show up as rows, which is why the rows rarely add up to the total. AI Overviews and AI Mode are counted inside the web totals, and Google keeps 16 months of data.
A change is refused on the free plan
AdPlug's free plan can preview a change but not apply it, and Claude tells you so before you refine it. Applying changes needs a paid plan.

08

Questions people ask

Can I connect Claude to Google Search Console?
Yes. AdPlug runs a hosted Search Console MCP server: you sign in with Google, add one address to Claude as a custom connector, and Claude can read your search performance, inspect URLs, and check your sitemaps. There's no Google Cloud project, OAuth client, or API key to set up.
Which Claude plans can add a custom connector?
Custom connectors work on Claude's Free, Pro, Max, Team, and Enterprise plans, on the web and the desktop app. The Free plan allows one custom connector, and Search Console always needs its own, because AdPlug's all-platforms address carries the ad platforms only. On Team and Enterprise, an Owner adds the connector under Organization settings, Connectors, and each member then connects their own account.
Is Search Console a separate connection from Google Ads?
Yes. Search Console has its own Google sign-in, even when it's the same Google account as your Google Ads, and its own connector in Claude. You can disconnect one without touching the other.
Can Claude request indexing for a page?
No. Google has no API for the Request indexing button on normal pages. Its Indexing API only covers job postings and livestream pages, and AdPlug doesn't use it. Claude can submit or resubmit a sitemap instead, and inspect a URL to tell you why it isn't indexed.
Which Search Console reports can't Claude see?
Google has no API for the Page indexing, Links, Manual actions, Security issues, or Crawl stats reports, nor for removals or disavow, so Claude can't read them. It works from the Performance report, URL Inspection, sitemaps, and Chrome UX Report data for Core Web Vitals.
Can Claude make changes in Search Console?
Yes, the four that Google's API allows: submit or resubmit a sitemap, remove a sitemap, add a property, and remove a property. Claude previews each change first and then applies it with the same values, and each one counts as one AI edit. AdPlug's free plan previews changes but doesn't apply them.
Is connecting Claude to Search Console free?
AdPlug's free plan covers one platform, and Search Console can be that platform: view only, with 500 requests in the first month and 50 a month after that. Pro and Max include every platform, so Search Console can sit next to Google Ads for the paid vs organic analysis.
Does the same connector work in ChatGPT, Cursor, or Claude Code?
Yes. https://api.adplug.app/mcp/google-search-console is a standard MCP server, so the same connection works in Claude, Claude Code, ChatGPT, Cursor, and other MCP clients.