Google Search Console MCP for AI Agents

SearchCrew's hosted Google Search Console connection is being prepared for beta. Public signup, the hosted MCP endpoint, and Google authorization are paused until the production app has passed end-to-end verification.

Do not add the hosted endpoint to an MCP client yet. Check launch status for the current verification checklist.

The intended hosted flow

Once the hosted beta opens, the connection is designed to work in three steps:

1. Create a SearchCrew workspace.
2. Connect a Search Console property with read-only permission.
3. Add the verified SearchCrew MCP endpoint to your AI client and authorize access.

The final endpoint and client-specific commands will be published only after DNS, authentication, recovery, and authorization checks pass.

If you need access sooner, review the self-hosting guide. Self-hosting requires your own Google OAuth client and infrastructure.

Things to actually ask it

• "Which queries am I ranking on page two for that I'm close to pushing onto page one?"
• "Show me pages where impressions went up but clicks stayed flat — probably a title or meta problem."
• "Are any of my blog posts competing with each other for the same query?"
• "Is /pricing indexed? If not, what's blocking it?"
• "Which queries lost the most clicks over the last 28 days?"

What the integration is designed to read

The implementation includes two read-only tools over the property you connect.

Search performance. Clicks, impressions, CTR, and average position for your site, sliced by query, page, country, device, and date. Pull up to 16 months of history in a single question.

URL inspection. Whether a page is indexed and, if not, why: coverage status, last crawl, the canonical Google chose versus the one you declared, plus mobile and rich-result checks. Up to 10 URLs at a time.

The requested Google scope is read-only. The integration is not designed to change your Search Console account.

Planned pricing

The public pricing page shows the proposed plan structure. Billing is paused until operator, support, refund, and payment terms are complete.

FAQ

What does it cost?

Hosted billing is not open. Review pricing for the proposed tiers and launch status for readiness.

Do I need to give SearchCrew my Google password?

No. The connection uses Google OAuth, so you sign in with Google and grant read-only Search Console access. SearchCrew never sees your credentials, and you can revoke access from your Google account at any time.

Is it read-only?

Yes. SearchCrew requests read-only access (webmasters.readonly). Your agent can read performance data and inspect URLs, but it can't change your account.

Which AI clients work?

The intended hosted flow targets MCP clients including Claude Code, Claude Desktop, Cursor, Codex, and OpenClaw. Verified connection commands will be published when the beta opens.

How fresh is the data?

It's Google's own data, so the most recent few days can be incomplete. History runs back 16 months, the same as the Search Console interface.