SEO Audit Console

by houtini-ai

482 downloads Not rated yet

About

Technical SEO audits in Claude: Search Console history, a first-party crawl and DataForSEO merged into one prioritised audit with paste-ready fixes.

Explore

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name SEO Audit Console
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "seo audit console": {
            "server": {
                "command": "npx",
                "args": [
                    "-y",
                    "@houtini/seo-audit-console"
                ],
                "env": {
                    "GOOGLE_APPLICATION_CREDENTIALS": "",
                    "SAC_DATA_DIR": "",
                    "DATAFORSEO_USERNAME": "",
                    "DATAFORSEO_PASSWORD": "",
                    "DATAFORSEO_CACHE_DAYS": "",
                    "FIRECRAWL_API_KEY": "",
                    "SUPADATA_API_KEY": "",
                    "MAJESTIC_API_KEY": "",
                    "MAJESTIC_CACHE_DAYS": ""
                }
            }
        }
    }
}

McpServers

{
    "server": {
        "command": "npx",
        "args": [
            "-y",
            "@houtini/seo-audit-console"
        ],
        "env": {
            "GOOGLE_APPLICATION_CREDENTIALS": "",
            "SAC_DATA_DIR": "",
            "DATAFORSEO_USERNAME": "",
            "DATAFORSEO_PASSWORD": "",
            "DATAFORSEO_CACHE_DAYS": "",
            "FIRECRAWL_API_KEY": "",
            "SUPADATA_API_KEY": "",
            "MAJESTIC_API_KEY": "",
            "MAJESTIC_CACHE_DAYS": ""
        }
    }
}

Transport

"stdio"

Package

"@houtini/seo-audit-console"

Registry

"npm"

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.

The complete technical SEO audit, at conversation speed.SEO Audit Console is an SEO MCP server that merges yourGoogle Search Consolehistory, afirst-party crawlof your site, and on-demandDataForSEOmarket data into one prioritised audit inside Claude - from crawlability, indexation, canonicalisation, structured data, Core Web Vitals and hreflang right through to keyword cannibalisation, striking-distance queries, content gaps, competitor analysis, link prospecting (withMajesticTrust Flow) and AI-search readiness. Ninety-three checks, every finding ranked by the clicks it could recover, every fix written for you: paste-ready redirects, JSON-LD, internal links and grounded content briefs. What used to be a fortnight of crawling, exporting and cross-referencing spreadsheets is twenty minutes and a prompt - and your data never leaves your machine.

Built byHoutini.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 guidetakes 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 simracingcockpit.gg ⣾ 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 ✓ 93 checks · 220 findings · ranked by expected clicks per dev-hour #1 CTR far below position-expected /how-to-install-mods XL #2 Page losing clicks (trend) site-wide XL #3 Keyword cannibalisation "beamng drive mods" L #4 Robots-blocked page earning traffic /category/wheels L you › generate the fix for #1 ▍

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

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.