Skip to content
MCP server

Seo Audit Console

Technical SEO audits in Claude, joining Search Console data to a site crawl

Runs locallyStatus and history
Pricing
Open source
Platforms
CLI, Windows, macOS
Runs
Locally
Version
1.0.5
Listing updated
3 days ago

About Seo Audit Console

Seo Audit Console is an open-source MCP server for marketing and seo. It runs locally on your machine and is started by your AI client.

Most audits describe what a site says; this one adds what Google did with it. It pulls your Search Console history, crawls the site, and joins the two so each finding shows the traffic at stake. The README cites 143 checks, and its sample output shows 157, ranked by expected clicks recovered per developer hour, and it can write the fix such as a 301 rule, JSON-LD or internal links.

The core audit needs only a Google service account with access to a Search Console property you own. DataForSEO adds SERP, keyword, domain and market checks, Majestic enriches link prospects with Trust Flow, and a Chrome UX Report key switches on real-user Core Web Vitals. Data is stored in per-property SQLite databases on your machine.

It requires Node.js 22 or newer and is built by the consultancy Houtini. A one-click .mcpb bundle is offered for Claude Desktop.

Install

Run in a terminal

claude mcp add seo-audit-console --env GOOGLE_APPLICATION_CREDENTIALS='<GOOGLE_APPLICATION_CREDENTIALS>' --env DATAFORSEO_PASSWORD='<DATAFORSEO_PASSWORD>' --env MAJESTIC_API_KEY='<MAJESTIC_API_KEY>' --env CRUX_API_KEY='<CRUX_API_KEY>' -- npx -y @houtini/seo-audit-console

Add to claude_desktop_config.json

{
  "mcpServers": {
    "seo-audit-console": {
      "command": "npx",
      "args": [
        "-y",
        "@houtini/seo-audit-console"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "<GOOGLE_APPLICATION_CREDENTIALS>",
        "DATAFORSEO_PASSWORD": "<DATAFORSEO_PASSWORD>",
        "MAJESTIC_API_KEY": "<MAJESTIC_API_KEY>",
        "CRUX_API_KEY": "<CRUX_API_KEY>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "seo-audit-console": {
      "command": "npx",
      "args": [
        "-y",
        "@houtini/seo-audit-console"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "<GOOGLE_APPLICATION_CREDENTIALS>",
        "DATAFORSEO_PASSWORD": "<DATAFORSEO_PASSWORD>",
        "MAJESTIC_API_KEY": "<MAJESTIC_API_KEY>",
        "CRUX_API_KEY": "<CRUX_API_KEY>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "seo-audit-console": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@houtini/seo-audit-console"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "<GOOGLE_APPLICATION_CREDENTIALS>",
        "DATAFORSEO_PASSWORD": "<DATAFORSEO_PASSWORD>",
        "MAJESTIC_API_KEY": "<MAJESTIC_API_KEY>",
        "CRUX_API_KEY": "<CRUX_API_KEY>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "seo-audit-console": {
      "command": "npx",
      "args": [
        "-y",
        "@houtini/seo-audit-console"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "<GOOGLE_APPLICATION_CREDENTIALS>",
        "DATAFORSEO_PASSWORD": "<DATAFORSEO_PASSWORD>",
        "MAJESTIC_API_KEY": "<MAJESTIC_API_KEY>",
        "CRUX_API_KEY": "<CRUX_API_KEY>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "seo-audit-console": {
      "command": "npx",
      "args": [
        "-y",
        "@houtini/seo-audit-console"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "<GOOGLE_APPLICATION_CREDENTIALS>",
        "DATAFORSEO_PASSWORD": "<DATAFORSEO_PASSWORD>",
        "MAJESTIC_API_KEY": "<MAJESTIC_API_KEY>",
        "CRUX_API_KEY": "<CRUX_API_KEY>"
      }
    }
  }
}

Configuration

  • GOOGLE_APPLICATION_CREDENTIALSPath to the Google service-account JSON key with Search Console access.Required
  • SAC_DATA_DIRDirectory for per-property SQLite databases and reports. Defaults to ~/Documents/seo-audit-console.
  • DATAFORSEO_USERNAMEDataForSEO API username (optional, enables SERP/keyword/domain/market/recon checks).
  • DATAFORSEO_PASSWORDDataForSEO API password (optional).
  • DATAFORSEO_CACHE_DAYSTTL for the DataForSEO response cache, in days. Default 20.
  • MAJESTIC_API_KEYMajestic API key (optional). Enriches link_intersect with Trust Flow + Topical Trust Flow and re-sorts prospects by real authority.
  • MAJESTIC_CACHE_DAYSTTL for the Majestic response cache, in days. Default 30.
  • CRUX_API_KEYChrome UX Report API key (optional, free Google Cloud key). Switches on sync_crux: real-user Core Web Vitals (LCP, INP, CLS) and the crux-field-* checks.

What it does

Search Console plus crawl
Joins ranking data to site crawl findings.
Traffic-ranked findings
Orders issues by clicks the fix could recover.
Generated fixes
Writes redirect rules, JSON-LD and internal links.
Optional data sources
DataForSEO, Majestic and CrUX add depth.
Local storage
Per-property SQLite databases stay on your machine.
One-click install
An .mcpb bundle installs into Claude Desktop.

Good for

  • Find pages losing clicks and why
  • Detect keyword cannibalisation
  • Check pages blocked by robots.txt that still earn traffic
  • Size a market and research competitors with DataForSEO
  • Find link prospects ranked by authority

Pricing

Open source

Free to install; DataForSEO and Majestic are separate paid services

Prices change. Check houtini.com before you buy.

Seo Audit Console FAQ

What is required to start?

Node.js 22 or newer and a Search Console property you own, accessed through a service account.

Is DataForSEO required?

No, it is optional and enables SERP, keyword and market checks.

Where is data kept?

In SQLite databases on your machine, in a directory you can set.

Who builds it?

Houtini.

Is Seo Audit Console free?

Yes. Seo Audit Console is open source, so you can use and self-host it for free.

How do I add Seo Audit Console to Claude Code?

Run this command in your terminal: claude mcp add seo-audit-console --env GOOGLE_APPLICATION_CREDENTIALS='<GOOGLE_APPLICATION_CREDENTIALS>' --env DATAFORSEO_PASSWORD='<DATAFORSEO_PASSWORD>' --env MAJESTIC_API_KEY='<MAJESTIC_API_KEY>' --env CRUX_API_KEY='<CRUX_API_KEY>' -- npx -y @houtini/seo-audit-console

What are the best alternatives to Seo Audit Console?

The closest alternatives to Seo Audit Console are Google Ads + Meta Ads + SEO/GEO MCP, Calven, MCP, Red Center Studio free tools and ASOScan.

Alternatives to Seo Audit Console

  1. Hosted MCP connector for managing Google Ads, Meta Ads, GA4 and Search Console from chat

    • 8 tools
    • Remote
    • Freemium
    • 8.1K GitHub stars
    • Marketing and SEO
  2. Calven

    MCP server

    Product marketing context from Calven delivered into Claude, ChatGPT and other AI tools

    Not checked yet
    • Remote
    • Free trial
    • 3 GitHub stars
    • Marketing and SEO
  3. MCP

    MCP server

    MCP server for planning, scheduling and measuring social and ad campaigns with approvals

    • Remote
    • Freemium
    • Marketing and SEO
  4. Free website checks for AI readiness, DNS dependencies, domain health and Bubble errors

    • 5 tools
    • Remote
    • Free
    • Marketing and SEO
  5. ASOScan

    MCP server

    ASO data for your own iOS and Android apps: rankings, keywords, reviews, scores

    • Remote
    • Free trial
    • Marketing and SEO
  6. PostBaton

    MCP server

    Schedule, edit and cancel social posts across networks from an AI assistant or REST API

    Not checked yet
    • Remote
    • Freemium
    • Marketing and SEO