GSCout

How to Connect Google Search Console to Claude (2026 Guide)

Add Google Search Console to Claude as a custom connector in two minutes. No Google Cloud project, no local server: sign in with Google and paste one URL.

Time: 2 minutesSign-in: OAuth in the clientAccess: read-only

Connector URL

https://gscout.vibiz.app/mcp

Want to try first? Use https://gscout.vibiz.app/mcp/demo: no sign-in, sample data.

Steps

  1. Sign in to GSCout with Google and pick your Search Console property. The backfill starts right away.
  2. In Claude, open Settings, then Connectors, and choose "Add custom connector".
  3. Name it GSCout and paste the connector URL: https://gscout.vibiz.app/mcp
  4. Click Connect. Claude opens the GSCout sign-in; approve read-only access.
  5. In a new chat, enable GSCout from the tools menu and ask: "What are my striking-distance keywords this month?"

Good to know

  • Custom connectors are available on Claude Pro, Max, Team and Enterprise. On Team and Enterprise an owner may need to add the connector for the organization first.
  • Claude calls the analysis tools (striking_distance, content_decay and others) and gets small ranked results, so long chats stay within context.

What to ask Claude first

Troubleshooting

  • “No property is connected”: open gscout.vibiz.app/app/properties and pick one; the tool answer says the same.
  • Google says the app is unverified: choose Advanced, then Go to GSCout. Access is read-only.
  • 401 or “token expired”: remove the connector and add it again; your client will sign in once more.
  • Numbers differ from the Search Console chart: query rows exclude anonymized queries, see anonymized queries.

Other clients: ChatGPT, Cursor, Claude Code, Codex, Windsurf, Gemini CLI, Mistral Le Chat, VS Code