SEO Audit Console

SEO Console - the technical/content/research/opportunity SEO audit MCP server for Claude

A technical SEO audit you can hold a conversation with - built from your own Search Console data and a live crawl of your site, run inside Claude.

Almost every technical SEO audit I've been handed in twenty years is a crawler's opinion, and a crawler only ever sees half the picture. It tells you what your site *says*. It has nothing to say about what Google *did* about it: which queries you rank for, which pages earn the impressions, where the clicks land.

This one brings the other half. SEO Audit Console runs inside Claude, pulls your Google Search Console history, crawls your site properly, and joins the two so every finding carries the traffic at stake. A hundred and forty-three checks, ranked by the clicks the fix could recover rather than how alarming the check sounds, and it writes the fix for you: the 301 rule, the JSON-LD, the internal links. The core audit needs nothing but your own Search Console; DataForSEO and Majestic slot in later, when your questions grow into competitors and link building. Your data stays on your machine.

Built by [Houtini](https://houtini.com). We build automation for the grunt work of digital marketing - the data collection, the crawling, the merging, the checking - so your team's time goes on the thinking, the strategy and the client work that needs a human. This plugin is that idea applied to the technical SEO audit.

New to MCPs, or not sure where to start? The [Getting started guide](manual/getting-started.md) takes you from a completely fresh machine (no Node, no Git, never heard of a service account) to your first audit - every step screenshotted, including the one everyone misses. Ten minutes, honestly.

you  › run an SEO audit on mysite.com

⣾ search console 1.8M rows synced (19s - incremental) ⣾ crawl 868 pages · HTTP/2 · robots-polite · 8 parallel ⣾ link graph internal PageRank · click depth · in-degree ✓ 143 checks · 220 findings · ranked by expected clicks per dev-hour

#1 CTR far below position-expected /pricing XL #2 Page losing clicks (trend) site-wide XL #3 Keyword cannibalisation "project management app" L #4 Robots-blocked page earning traffic /category/guides L

you › generate the fix for #1 ▍

Quick start

It's on npm, so there's nothing to clone or build. You need Node.js 22 or newer (Node 20 is end-of-life) and a Search Console property you own.

The quickest start, on Windows, is one-click. Download seo-audit-console.mcpb from the latest release and open it in Claude Desktop (Settings → Extensions). It installs itself, dependencies and runtime included, and asks for your Google key in a form instead of any JSON editing. The bundle carries native modules built for Windows; on macOS or Linux (or if you'd rather wire it up yourself, or you're on Claude Code) use the config routes below, which fetch the right binaries for your system. Either way you still need the Search Console service account - see getting started.

Claude Desktop - add this to claude_desktop_config.json, then restart Claude:

{

"mcpServers": { "seo-audit-console": { "command": "npx", "args": ["-y", "@houtini/seo-audit-console"], "env": { "GOOGLE_APPLICATION_CREDENTIALS": "C:/path/to/service-account.json", "DATAFORSEO_USERNAME": "", "DATAFORSEO_PASSWORD": "", "MAJESTIC_API_KEY": "", "CRUX_API_KEY": "" } } } }

The first line is required. The others are optional: paste your key between the quotes, or leave them empty to switch the tier off. DataForSEO and Majestic are paid tiers; CRUX_API_KEY is field Core Web Vitals from a free Google API key restricted to the Chrome UX Report API. Empty means off. Template text such as your-key-here, or changeme is treated as empty too, and the server's log says so in one line (e.g. MAJESTIC_API_KEY looks like a placeholder; Majestic tier disabled.), so a tier you expected that stays off is worth a look at the log.

Claude Code - one command (add --env DATAFORSEO_USERNAME=… and the others the same way if you use them):

claude mcp add seo-audit-console --env GOOGLE_APPLICATION_CREDENTIALS=C:/path/to/service-account.json -- npx -y @houtini/seo-audit-console

GOOGLE_APPLICATION_CREDENTIALS alone is the whole core audit. The step everyone misses: the JSON key belongs to a Google Cloud service account, and that account's email has to be added as a user on your property in Search Console, or the tool can't see any of your data. Getting started walks through it with screenshots, plus the one-click Claude Desktop extension and the build-from-source route.

Then ask Claude: *"list properties"*, *"refresh mysite.com"*, *"run an SEO audit"*.

Opening the dashboard

Once a property has been refreshed or audited, there are three ways to see it:

You often don't need to ask: when a refresh, crawl, sync or audit finishes, the reply says the dashboard is updated and includes the browser link. The link is local to your machine (it only answers on 127.0.0.1), and the port changes each time the server starts, so use the link from the latest reply. Want one stable address? Run seo-audit-dashboard with SAC_DASHBOARD_PORT=8788 as a standing process and give the MCP the same port and data dir: it then hands out that dashboard's link (it checks the process on that port really is this dashboard, serving the same data, before it does). Add &theme=dark for dark mode, or &redact=1 to blur the numbers for a screenshot.

Running it under Docker or the Docker MCP gateway? The browser link points at a port inside the container, which your browser can't reach. Run the dashboard as its own small container on a fixed port instead, on the same data volume:

docker run -d --init --name seo-audit-dashboard --restart unless-stopped -p 127.0.0.1:8788:8788 -e SAC_DATA_DIR=/data -e SAC_DASHBOARD_BIND=0.0.0.0 -e SAC_DASHBOARD_PORT=8788 -v <your-data-volume>:/data node:22-slim npx -y -p @houtini/seo-audit-console@<your-version> seo-audit-dashboard

Then open http://127.0.0.1:8788/dashboard?siteUrl=sc-domain:mysite.com. Replace with the volume your MCP server writes to, and with the version it runs, so the two match (the server prints this command with its own version filled in). The volume must be writable: the dashboard's actions start jobs. In Git Bash on Windows, put MSYS_NO_PATHCONV=1 in front of the command so /data isn't rewritten as a Windows path. More in dashboard.md.

The manual

This README is the story and the quick start. The detail lives in the manual:

Surprisingly little has changed in twenty years

The technical audit I was writing for clients in 2006 is, structurally, the audit most agencies still sell today. A crawler runs, a template fills, a 60-page PDF lands. Everything a crawler could find, in severity order, with no idea which findings are worth money and which are cosmetic.

What *has* changed is what's possible. Google gives every site owner a complete record of its search reality - which queries, which pages, how many impressions, where you ranked. Your crawl tells you what your site says. Search Console tells you what Google did about it. And in my experience, the gap between those two datasets is where nearly all of the recoverable traffic hides.

So that's what I built. SEO Audit Console is a Model Context Protocol server that merges your Search Console history with a first-party crawl of your site (and, when you want it, DataForSEO) into one thing: a prioritised, evidence-backed audit you can interrogate inside Claude Desktop. It hands you paste-ready fixes. Every finding traces back to a real da