Daily Search Console Checks with OpenClaw: Server-Side Analysis, So the Agent Never Does the Maths

A developer has published seo-gsc-wizard, a set of six MIT-licensed OpenClaw skills that run Search Console checks on a schedule and message you only when something needs fixing. The core design choice: the statistical analysis runs server-side, so the model explains a result rather than calculating one.

Why the analysis location matters

The author's argument is that most Search Console MCP servers return raw rows. Ask "which pages are decaying?" and the agent gets thousands of query/page rows, the client truncates them to fit the context window, and the model computes trends over whatever survived — without telling you it only saw part of the data. In an unattended 7am automation, nobody notices.

The fix is a server that does the statistics itself (anomaly detection, change points, decay, cannibalisation) and returns finished results. That doesn't make it hallucination-proof — a model can still misquote a correct number. So the skills require every figure to name its tool and date range, and to state when the model derived a number itself.

The six skills

• site-audit
• content-decay
• cannibalization
• quick-wins
• weekly-report
• indexing-health

Each is a plain SKILL.md you can read before running; there are no scripts in the skill folders. The weekly report offsets its windows by 3 days for Search Console's data lag, checks change points and Google updates before blaming a page, and correlates movement with your logged site changes.

Setup

Clone and copy the skills into your workspace:

git clone https://github.com/jbobbink/seo-gsc-wizard
cp -r seo-gsc-wizard/skills/* ~/.openclaw/workspace/skills/

Create a read-only key under Account → API keys in GSC Wizard, then add the server to ~/.openclaw/openclaw.json:

{
  mcp: {
    servers: {
      "gsc-wizard": {
        url: "https://mcp.gscwizard.com/mcp",
        transport: "streamable-http",
        headers: { Authorization: "Bearer <read-only key>" }
      }
    }
  }
}

Then probe it:

openclaw mcp doctor gsc-wizard --probe

Three mistakes the author keeps seeing in guides: the key is mcp.servers, not mcpServers (that's the Claude Desktop format many guides copied over); omitting transport makes OpenClaw default to SSE, and Streamable-HTTP-only servers silently fail to connect; and HEARTBEAT.md isn't read any more, so don't build on it.

Scheduling

openclaw automations create "10 8 * * 1" \
  "Run the weekly-report skill for sc-domain:example.com." \
  --name "SEO weekly report" --tz "Europe/Amsterdam" \
  --session isolated \
  --announce --channel slack --to "channel:C0123456789"

For a daily check, schedule the indexing-health skill on weekdays, or write a skill that only replies when something needs a human. The author notes an agent posting a wall of green every morning gets muted within a week, and recommends --session isolated over Heartbeat, which runs every 30 minutes by default.

Security notes

• Use a read-only key. Write tools reject it before they run, so even a prompt-injected agent can't change anything. All six skills work with it; only optional extras like IndexNow resubmission need a write key.
• Once the probe passes, move the key into OpenClaw's secrets mechanism instead of a literal header.
• Keep browser and web_fetch away from the agent that holds the key.
• Read any SEO skill before installing it. After ClawHavoc, SEO skills are an obvious disguise because they legitimately ask for API keys.

The skills are free and MIT-licensed, but the server needs a GSC Wizard account (paid plan, 7-day free trial). The author discloses they built both, and that the server reads Search Console, Bing and GA4 data through the Google accounts you connect, scoped to your user.