How do I connect Google Search Console to Claude?

Open PaidSync in Claude's connector directory and click Connect, or in Claude open Customize, then Connectors, search PaidSync and click Connect. Sign in to PaidSync and press Approve, then ask Claude to connect Search Console and list your properties. No API key is needed. Full steps are above.

Is PaidSync free to use with Claude?

Yes. The free plan gives you 15 tasks per month at $0. Paid plans start at $99/month for Pro, with 4,000 tasks at $199, and Team plans from $249/month for 5 seats.

What Search Console data can Claude access?

Claude can query clicks, impressions, CTR, and average position by query, page, country, device, and date. The full Search Analytics API is exposed, including 16-month historical data.

Does PaidSync support multiple GSC properties?

Yes. If your Google account has access to multiple properties, PaidSync exposes all of them. You can ask Claude to compare performance across domains in the same conversation.

What OAuth scopes does PaidSync request for Search Console?

PaidSync requests https://www.googleapis.com/auth/webmasters.readonly, Google's read-only Search Console scope, for performance, property and sitemap data. It does not request the full webmasters scope.

Does this work with Claude Code and claude.ai?

Yes. claude.ai and the Claude Desktop app share the same connector list, on every plan including Free. Search PaidSync under Customize, then Connectors, and click Connect. Claude Code uses the remote MCP URL https://mcp.paidsync.ai/mcp. Both access the same GSC tools.

Why is the Search Console integration read-only?

PaidSync's Search Console connection is read-only by design: it reads your search data and never changes your property. Google's own API can also submit sitemaps and add sites; PaidSync does not.

Do I need a paid Claude plan to use PaidSync with Search Console?

No. Connectors work on every Claude plan, including Free, in both the Claude Desktop app and claude.ai. Claude Code connects with one terminal command and the same PaidSync login. PaidSync has its own pricing. Free for 15 tasks a month with no credit card, then priced by usage, from $99 a month for 600 tasks.

Does PaidSync also connect Search Console to ChatGPT and Gemini?

Yes. The same PaidSync account works with ChatGPT, Claude, Gemini, Perplexity and Microsoft Copilot. Connect Search Console once and use it from any of them.

Connect Google Search Console to Claude in 2 Minutes

How to connect Search Console to Claude with PaidSync

This is the route through Claude's connector directory. No API key is needed, because Claude connects with a PaidSync sign-in (OAuth).

Before you start

Any Claude plan works, including Free, and there is nothing to install.
Signing in with Google? There is no separate sign-up. You pick Continue with Google in step 2, and your free PaidSync account (15 tasks a month, no credit card) is created when you press Approve.
Prefer an email and password? Create the account at paidsync.ai/signup first. The sign-up link inside the sign-in window opens the website and does not bring you back to Claude.
Know which Google login is an owner or user of your Search Console property. You use it in step 3.
On a Team or Enterprise plan, an Owner first adds PaidSync for the organization under Organization settings, then Connectors. Each person then connects with their own PaidSync login.

Add PaidSync to Claude from the connector directory

Open PaidSync in the Claude connector directory and click Connect. Or, in claude.ai or the Claude Desktop app, open Customize, then Connectors, click + next to Connectors, search PaidSync, and click Connect.

Sign in with your PaidSync login. That OAuth sign-in is what lets Claude apply changes. Connectors work on every Claude plan, including Free.

Using Claude Code instead? Run claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp, then type /mcp inside a session to sign in.

On a client with no directory, add PaidSync as a custom connector with the server URL instead (on a Team or Enterprise plan, only an Owner can add one):

https://mcp.paidsync.ai/mcp

Save it, then sign in with your PaidSync login when Claude asks.

Sign in to PaidSync and press Approve

The PaidSync sign-in screen opens. Pick Continue with Google, or sign in with your PaidSync email and password. A PaidSync screen then asks whether to allow Claude to manage your ad accounts via PaidSync. Press Approve and Claude shows PaidSync as connected.

New to PaidSync and signing in with Google? Your free account (15 tasks a month, no credit card) is created when you press Approve. The screen also mentions ad accounts already connected inside PaidSync. On a new account that list is empty until you finish step 3.

Connect your Search Console property and ask Claude

In any chat, ask: "Connect my Search Console." Claude replies with a link that opens Google's own sign-in and consent screen. Sign in with the Google account that has access to your Search Console property and approve access. PaidSync asks Google for the read-only webmasters.readonly scope, so it reads your search data and never changes the property. PaidSync never sees your Google password.

Come back and ask: "List my Search Console properties." Claude uses list_gsc_properties to show every property your Google login can open, and you tell it which one to use. Connecting and listing properties uses none of your tasks. Then try: "What queries drove the most clicks in the last 28 days?" You can also connect Search Console from the PaidSync dashboard instead. Both routes use the same PaidSync login, so Claude sees the property either way.

The Cross-Channel Angle

PaidSync's 6 Search Console tools read your search data next to Google Ads, so Claude can compare what you pay for with what you already rank for. That means Claude can run paid-organic analysis in a single conversation without any data exports or tab switching.

Ask Claude to find organic queries where you rank in positions 5 to 15, then check whether you are running paid coverage on those same terms. Claude pulls both data sets, compares them, and tells you exactly where organic clicks are costing more than a paid click would.

The reverse check works too. Ask Claude which Google Ads keywords you pay for where you already rank in the top five organically, and it runs analyze_paid_organic_overlap, which estimates the monthly spend on each overlap.

What Claude Can Do with Search Console

Top query report. Claude returns your top 50 queries by clicks for any date range, with impressions, CTR, and position. Filtered by device or country in one follow-up.
Position drop detection. Ask Claude to find pages that lost more than 3 positions week over week. It returns a ranked list with the delta and current averages.
CTR gap analysis. Claude identifies queries with high impressions but low CTR, the fastest path to organic traffic gains without new content.
Sitemap status. Claude can check your sitemap submission status and flag any indexing errors across your properties.
Paid vs organic comparison. With Google Ads also connected, Claude can overlay paid spend data against organic query performance and find gaps in coverage.

What each Search Console report tells Claude

Top queries

Ask Claude which queries brought the most clicks this month, last month or any date range. It runs get_gsc_search_analytics by query and returns clicks, impressions, CTR and average position for each one, and can filter to queries that contain a word or to one page.

Top pages

Ask which pages get the most organic clicks, and which rank but are not clicked (high impressions, low CTR). Claude runs the same tool by page. To see which pages are losing position, it compares two date ranges.

Sitemaps and indexing

Claude reads your sitemaps with get_gsc_index_coverage and compares submitted with indexed page counts for each one, with any sitemap errors and warnings. Sitemap errors can keep whole sections of a site out of the index. PaidSync does not read the Page indexing report or URL Inspection.

Country and device

Ask Claude to break clicks and impressions down by country or by device, one breakdown per request. It shows where your organic audience comes from and whether mobile search keeps up with desktop.

Search Console prompts to try in Claude

Each prompt runs on the PaidSync tools named after it and uses one or more of your tasks. None of them changes anything, because PaidSync's 6 Search Console tools read your search data.

"What are my top 20 organic queries by clicks this month, with the average position for each?" Runs get_gsc_search_analytics by query.
"Which pages get a lot of impressions but a low click-through rate?" Runs get_gsc_search_analytics by page, ranked by impressions.
"How many of the URLs in my sitemaps are indexed, and which sitemap has the biggest gap?" Runs get_gsc_index_coverage.
"Compare my organic search performance this month with the same month last year." Claude runs get_gsc_search_analytics for both ranges. Search Console keeps 16 months of data.
"Which of my top organic queries am I not bidding on in Google Ads?" Runs get_gsc_search_analytics and the Google Ads tool get_keyword_performance, which covers your top 100 keywords by cost, then compares the two lists.
"Which Google Ads keywords am I paying for where I already rank in the top five?" Runs analyze_paid_organic_overlap, which estimates the monthly spend on each overlap.
"Break down my organic clicks and impressions by country for the last 90 days." Runs get_gsc_search_analytics by country.
"Which queries bring clicks to my pricing page, and at what average position?" Runs get_gsc_search_analytics by query, filtered to that page.

How do I connect Search Console to Claude Code?

Working in the terminal? Claude Code connects to the same PaidSync server with one command:

claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp

Start a session, type /mcp, pick paidsync, and sign in with your PaidSync login in the browser window that opens. Claude Code stores the OAuth token for you. No key is pasted anywhere. The Claude Code setup page covers the shared .mcp.json for teams and a headless audit run.

Troubleshooting Search Console in Claude

The sign-in fails. Sign in to PaidSync the way you signed up, with Continue with Google or with your PaidSync email and password. Email users without an account create one at paidsync.ai/signup first, then click Connect in Claude again. If Google's own consent screen fails, ask Claude "Connect my Search Console" again for a fresh link.
Claude used the wrong property. PaidSync keeps no default Search Console property. Every request names the property, so tell Claude which one you mean, and it sends that property with each request. A domain property (sc-domain:example.com) and a URL-prefix property (https://www.example.com/) are separate properties with different numbers, so name the one you mean. Ask Claude to list your properties with list_gsc_properties if you are not sure. Listing uses none of your tasks.
A property is not listed. PaidSync lists the properties your connected Google login can open. In Search Console, an owner adds that login under Settings, then Users and permissions. Connected with the wrong Google login? Disconnect it in the PaidSync dashboard and connect again with the login that has access.
Claude says it has no Search Console tool. PaidSync shows Claude a short starter list of tools to keep the chat light. Ask Claude to call paidsync_context first. It returns your connected platforms and the full tool list, Search Console included, and Claude then runs those tools through paidsync_exec. If PaidSync is missing from Claude altogether, check that it shows as connected under Customize, then Connectors.