Skip to content

SEO audits in Gemini CLI via MCP

Gemini CLI can call Crawlwise audits and AI crawler checks over MCP. Note that Gemini wants httpUrl, not url, in settings.json.

1. Add the server

One command adds the Crawlwise MCP server.

bash
gemini mcp add crawlwise --transport http https://crawlwise.site/mcp

Or in ~/.gemini/settings.json

json
{
  "mcpServers": {
    "crawlwise": {
      "httpUrl": "https://crawlwise.site/mcp",
      "headers": {
        "Authorization": "Bearer cw_live_YOURKEY"
      }
    }
  }
}

2. Sign in

The first tool call opens the Crawlwise sign-in page. Approve it and the tools stay connected. If your client cannot do OAuth, create a key at /account/api (Pro and above) and send it as Authorization: Bearer cw_live_….

3. Check it worked

Restart Gemini CLI and run /mcp.

4. No MCP? Pipe the CLI

The CLI works without an account for a first look (1 page a day). Its llm format is written for an agent: only defects, each citing its check.

bash
npx crawlwise audit https://example.com --format llm

Prompts to try

  • Audit https://example.com with crawlwise and fix the priority items. Re-audit until none are left.
  • Use crawlwise to check whether GPTBot, ClaudeBot and PerplexityBot can read https://example.com.
  • Crawl my verified site with crawlwise and list broken internal links and redirect chains.

The agent should fix only what is under priority. Items marked not measured are tests that returned no result, not defects.

Gemini CLI wants httpUrl, not url.

All agents · Integrations · MCP reference · Claude Code · OpenAI Codex · GitHub Copilot · ChatGPT · OpenCode · GitHub Action