NotFairNotFair
Start now

Integration · OpenClaw × Google Search Console

Run Google Search Console inside OpenClaw

NotFair connects OpenClaw to live Google Search Console through the same hosted MCP endpoint used across the product. Verified properties, Search Analytics, URL inspection, and sitemap inventory.

Supported
Hosted MCP URL https://notfair.co/api/mcp/notfair — the same endpoint as every other NotFair platform
10 Search Console tools
Writes follow this platform's real lifecycle — not Google Ads undo copied onto Google Search Console

Connect your Google Search Console account

Authorize once at notfair.co — then open OpenClaw and start asking real questions about your account.

Connect Search Console

Setup

Connect OpenClaw in three steps

OpenClaw uses NotFair's hosted Streamable HTTP endpoint. NotFair hosts Google OAuth for Search Console. You authorize verified properties; you do not create a Cloud project for the MCP client.

  1. 1. Add NotFair as a standard MCP server

    OpenClaw speaks MCP. No proprietary plugin is required.

    {
  "mcpServers": {
    "NotFair-GoogleSearchConsole": {
      "url": "https://notfair.co/api/mcp/notfair"
    }
  }
}

  2. 2. Authorize Google Search Console

    Open /connect/google_search_console on notfair.co, complete the hosted connection, and select the accounts or properties OpenClaw may use.

  3. 3. Keep writes gated

    Even in scheduled OpenClaw loops, NotFair write tools wait for approval unless your host policy is explicitly more permissive — and the platform lifecycle still applies.

Capabilities

What OpenClaw can do with NotFair

Read live Google Search Console data

Verified properties, Search Analytics, URL inspection, and sitemap inventory.

Counted tool surface

10 Search Console tools, measured from the production registrar and guarded by a drift test.

Hosted credentials

NotFair hosts Google OAuth for Search Console. You authorize verified properties; you do not create a Cloud project for the MCP client.

Platform-true writes

Most tools are reads. submitSitemap and deleteSitemap wait for approval and are inverses. This is not a Google Ads impact/undo product. Default Search Analytics uses finalized data (~2–3 day lag). inspectUrl covers one URL at a time.

Example workflows

Prompts that lead to real account work

Query review

“Show the top queries last 28 days using finalized Search Analytics data.”

Clicks, impressions, and freshness metadata.

URL inspection

“Inspect this URL for coverage, canonical, and crawl evidence.”

inspectUrl evidence for one URL.

Sitemap preview

“Preview submitting this sitemap. Do not execute until I approve.”

An approval-gated submit that can later be reversed with deleteSitemap.

Why NotFair for OpenClaw + Google Search Console

The hosted MCP endpoint is the same. The Google Search Console contract is not. NotFair keeps tool counts, OAuth, and write limits honest for this platform.

  • 10 Search Console tools — not a vendor-wide total reused as a Google Search Console count
  • NotFair hosts Google OAuth for Search Console. You authorize verified properties; you do not create a Cloud project for the MCP client.
  • Most tools are reads. submitSitemap and deleteSitemap wait for approval and are inverses. This is not a Google Ads impact/undo product.
  • Same remote endpoint in Claude, Codex, Cursor, Windsurf, Gemini CLI, and OpenClaw

FAQ

Common questions about using OpenClaw with Google Ads through NotFair.

Yes. NotFair's hosted MCP endpoint is the same across clients. OpenClaw speaks MCP and can call the same tools. Google does not publish an official Search Console MCP in the public sources used here.

NotFair does not copy Google Ads impact snapshots or undo onto Google Search Console. Most tools are reads. submitSitemap and deleteSitemap wait for approval and are inverses. This is not a Google Ads impact/undo product.

NotFair advertises 10 Search Console tools.

Other integrations

Switching clients, or curious how this compares?

ChatGPT + Google Ads

NotFair connects ChatGPT to live Google Search Console through the same hosted MCP endpoint used across the product. Verified properties, Search Analytics, URL inspection, and sitemap inventory.

Claude Code + Google Ads

NotFair connects Claude Code to live Google Search Console through the same hosted MCP endpoint used across the product. Verified properties, Search Analytics, URL inspection, and sitemap inventory.

Cursor + Google Ads

NotFair connects Cursor to live Google Search Console through the same hosted MCP endpoint used across the product. Verified properties, Search Analytics, URL inspection, and sitemap inventory.