Ask Claude about your Google Search Console.

Add Google Search Console to ChatGPT as a custom MCP server. What the setup looks like, and the plan requirement that decides whether you can do it at all.

ChatGPT

6 min setup

VS Code (GitHub Copilot)

Connect Google Search Console to GitHub Copilot in VS Code with one .vscode/mcp.json entry, then ask agent mode about GSC. You skip Google Cloud setup.

Add Google Search Console, GA4 and PageSpeed data to OpenAI's Codex CLI with one TOML block and a bearer token. You never create a Google Cloud project.

Codex CLI (OpenAI)

Query Google Search Console (GSC) from your terminal with Gemini CLI. Register GSC PAP as an MCP server in settings.json, with no Google Cloud project.

Gemini CLI (Google)

Give Windsurf, now Devin Desktop, your Google Search Console data. Add GSC PAP as a remote MCP server with one bearer token and no Google Cloud project.

Windsurf (Devin Desktop)

Continue MCP setup for Google Search Console: add one mcpServers entry with a bearer token in VS Code or JetBrains. You do not need a Google Cloud project.

Continue (extension)

Bring Google Search Console into Zed's AI assistant as an MCP context server. You add one settings.json block and a token, with no Google Cloud setup.

Zed Editor

Direct HTTP (curl, custom agents)

Call the GSC PAP MCP server from curl or your own agent. It is JSON-RPC over HTTP with a bearer token, so you need no MCP client or Google Cloud project.

Also set up and documented: JetBrains IDEs, opencode, Cline, Warp, LM Studio, Goose, Google Antigravity, Roo Code, Kilo Code, Amp, Kiro, Raycast, GitHub Copilot CLI, n8n, LibreChat.

See all 27 integrations

Try it on yours

What people do with it

Real SEO workflows you can run by asking your AI assistant. Each guide includes the exact prompt, the underlying GSC PAP tools it calls, and what the answer looks like.

How to find striking distance keywords in Google Search Console

Striking distance keywords rank just off page one of Google. Find them in Search Console, pick the ones worth fixing, and learn what to change on the page.

How to find keyword cannibalization in Google Search Console

Check for keyword cannibalization in Google Search Console: find queries where your pages compete, judge whether it hurts, and fix the cases that do.

GSC clicks vs GA4 sessions: why they differ and how to tie clicks to conversions

A Search Console click and a GA4 session measure different things. Why the numbers never match, what gap is normal, and how to compare and combine them page by page.

11 min read

Audit Core Web Vitals across your site with AI

Audit Core Web Vitals with Claude through a hosted PageSpeed Insights MCP server: Lighthouse lab data and real-user CrUX field data for your top pages.

Google Search Console historical data: how to keep it past 16 months

Google Search Console keeps 16 months of historical data, then deletes it. Here is what it includes and how to keep it longer, from BigQuery to an archive.

Build a weekly SEO health report with Claude

Automate a weekly SEO report with Claude: one saved prompt pulls Search Console changes, quick wins, decaying pages, GA4 conversions and Core Web Vitals.

Bulk URL inspection in Google Search Console: diagnose indexing issues at scale

Search Console inspects one URL at a time. The URL Inspection API allows 2,000 checks a day per property. How to inspect in bulk and find indexing issues.

Track keyword rankings in Google Search Console, past the 16-month limit

See a keyword's position history in Google Search Console, what that average really measures, and how to keep ranking history past the 16-month limit.

6 min read

Google Search Console anonymized queries: measure the traffic you can't see

Search Console hides anonymized queries from query rows but counts them in totals. Learn what they are, why no tool reveals them, and how to measure them.

6 min read

Good position, no clicks: find the SERP features eating your CTR

Ranking third and getting no clicks usually means something sits above you: an AI Overview, a featured snippet or a map pack. How to check which, query by query.

Find the pages quietly losing organic traffic, before the rankings go

Content decay is slow enough to miss on a dashboard. How to find the pages whose clicks keep sliding, tell decay from seasonality, and decide what to refresh.

Traffic changed: how to compare two Search Console periods and find out why

Clicks are down 18% and nobody knows why. How to compare two periods properly, avoid the three traps that fake a drop, and find the queries and pages behind it.

AI queries in Google Search Console: how to tell people, AI Mode and agents apart

Search Console mixes AI Mode follow-ups, AI agent searches and scripts into your query report. How to spot each one, with regex filters and real data.

14 min read

All guides

Who uses GSC PAP?

Anyone whose work touches Google Search Console and who already uses an AI assistant. The product makes the second tool answer questions about the first one.

SEO consultants

Audit client sites in Claude Desktop. Run quick-wins, find cannibalization, spot decaying pages without opening a separate dashboard for each client.

In-house SEO + content teams

Ask "what's broken this week" in your team chat without anyone touching the Search Console UI. Pipe answers into Slack via your AI client.

Solo developers

Connect your personal site. Get AI-driven SEO insights inline while you write content or fix code in Cursor / Claude Code.

Agencies

Run cross-client SEO reports through one Claude session. Each user keeps their own scoped GSC PAP token; no shared dashboards or seat licenses.

How it works

Three steps, sixty seconds. No GCP project setup, no client_id JSON, no Python venv.

Sign in with Google

Standard OAuth, read-only Search Console scope. Your refresh token is encrypted at rest with AES-256-GCM.

Get your token

We mint a long-lived bearer token, shown once. Copy it into your MCP client config - Claude Desktop, Cursor, or anything else.

Ask anything

"What are my decaying queries?" "Find cannibalization on this domain." 36 tools for Search Console, GA4 and PageSpeed, real data, real time.

Try it on yours

Built for technical users who care about access

We built this because we were tired of the OAuth client setup dance. Same here.

Your data, yours alone

Your Search Console archive is visible only to you. No other GSC PAP user can see it - ever.

Revoke anytime

One click revokes your token at Google + in our DB. Account deletion is real and permanent within 30 days.

Encrypted at rest

Refresh tokens are AES-256-GCM encrypted with envelope keys. Bearer tokens stored as SHA-256 hashes only.

Read-only by design

We only hold the read-only Google scope. Even if our service were compromised, no one can edit or delete anything in your Search Console.

vs self-hosting

Self-host is great for ops teams. For everyone else, the GCP setup kills momentum before the first query. The other hosted Search Console MCP servers are compared separately, prices included.

Self-host

Run gsc-pap-server on your own infra

Set up a Google Cloud project
Configure an OAuth web client
Manage a Python venv + dependencies
Edit JSON config files for each AI client
Maintain Postgres + Redis + Cloudflare Tunnel

Time to first query~45 minutes

Recommended

GSC PAP (hosted)

Free, plug & play, no infra

No Google Cloud project
No OAuth client config
No Python or dependencies to manage
No JSON files (one paste in your AI client)
No Postgres, no Redis, no infra ops

Time to first query60 seconds

Common questions

Quick answers. The full FAQ covers setup, privacy, supported clients, limits, and more.

Do I need a Google Cloud project to use GSC PAP?

No. The whole reason GSC PAP exists is to remove the Google Cloud setup step. When you sign in with Google through gscpap.com, you grant permission to our OAuth client (which we registered with Google one time). We then call the Search Console API on your behalf using your refresh token. You never touch the Google Cloud Console.

What Search Console data can GSC PAP access?

GSC PAP requests the webmasters.readonly OAuth scope - the same read-only level you would grant to any third-party Search Console viewer. Specifically we can read your verified site list, search analytics (clicks, impressions, CTR, position by query, page, country, device, date), sitemap submission status, and URL inspection results. This is exactly the data you see in your own Search Console UI. It also has the same gaps: Google leaves anonymized queries out of query rows in both the UI and the API, so GSC PAP cannot reveal them either. If you also connect Google Analytics, GSC PAP holds the analytics.readonly scope as well, and any Analytics data it keeps for you follows the same rules as your archive.

Is GSC PAP free? What are the limits?

Yes, GSC PAP is completely free during the public preview (v0.x). There is no credit card required, no trial expiration, and no premium feature gate. The only limits are technical ones to protect the service: 60 MCP tool calls per minute and 1,000 per hour per user. These limits are generous - typical AI assistant usage is 5-20 calls per question, so you can ask hundreds of questions per hour without hitting them.

How far back does my data go?

Google Search Console itself only retains the most recent 16 months of data. Anything older drops off Google's side and cannot be recovered, even with API access - this is a hard limit Google enforces on every Search Console user, including direct users of the official Google Search Console UI.