Log inSubmit server
Seo Audit Console logo

Seo Audit Console

Run technical SEO audits in Claude using Search Console data, a live crawl, optional third-party APIs, and prioritized fixes.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Seo Audit Console

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "seo-audit-console": {
      "command": "npx",
      "args": [
        "-y",
        "@houtini/seo-audit-console"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "YOUR_VALUE_HERE",
        "DATAFORSEO_USERNAME": "YOUR_VALUE_HERE",
        "DATAFORSEO_PASSWORD": "YOUR_VALUE_HERE",
        "MAJESTIC_API_KEY": "YOUR_VALUE_HERE",
        "CRUX_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

seo-audit-console MCP server combines Google Search Console data with a live crawl of a site to produce technical SEO findings inside Claude. It ranks issues using Search Console traffic context and can generate fixes such as redirects, structured data, and internal-link changes. Optional DataForSEO, Majestic, and Chrome UX Report credentials add competitive, backlink, and field Core Web Vitals data. Use it when an audit needs both crawler findings and evidence of how Google is treating the site.

Use cases

  • Run a technical SEO audit against a Search Console property
  • Prioritize crawl findings by affected search traffic
  • Generate implementation suggestions for audit issues
  • Export a client-ready HTML audit report
  • Compare crawl findings with optional backlink or SERP data

Key features

  • Google Search Console history and property access
  • Live site crawling with traffic-aware findings
  • Prioritized technical SEO checks
  • Local dashboard and HTML report export
  • Optional DataForSEO, Majestic, and CrUX tiers
  • Generated fixes for selected audit findings

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @houtini/seo-audit-console (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars83Stargazers on the source repository.
npm downloads436Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Seo Audit Console works

What seo-audit-console does

seo-audit-console is an MCP server for conversational technical SEO audits in Claude. It connects to a Google Search Console property you own, collects Search Console history, and crawls the site being audited. The results combine search performance with crawl observations so findings can be considered alongside impressions, clicks, rankings, and affected pages.

The seo-audit-console MCP server prioritizes findings by their potential traffic impact rather than presenting an unranked list of crawler warnings. It can also write suggested implementation changes, including 301 rules, JSON-LD, and internal-link recommendations. The available audit coverage includes site structure, indexability, content and query patterns, internal links, and changes over time, as supported by the collected data.

The project belongs in the 🎯 Marketing category and is intended for teams that want audit analysis and follow-up questions in an MCP-compatible assistant rather than a separate crawler interface.

How it works

The core workflow starts with Google Search Console credentials and a property refresh. You can ask Claude to list available properties, refresh a property, or run an audit. Refreshing synchronizes Search Console data and crawls the site, after which the server can join the two sources during analysis.

The server stores data locally on the machine where it runs. After a refresh or audit, Claude can show a dashboard in the conversation with get_dashboard, open a local browser dashboard with open_dashboard, or create a self-contained HTML file with export_report. The browser dashboard listens on the local machine and reads the local database when reloaded.

The seo-audit-console MCP server can use optional services for broader questions. DataForSEO supports additional competitive and search research workflows, Majestic supplies backlink and Trust Flow-related data, and a Chrome UX Report API key enables field Core Web Vitals. These tiers can be disabled by leaving their environment variables empty.

Setup and configuration

Install the npm package with npx; the documented setup requires Node.js 20 or newer. For Claude Desktop, add the server to claude_desktop_config.json with npx -y @houtini/seo-audit-console as the command, then restart Claude. Claude Code can add the same stdio server with claude mcp add.

GOOGLE_APPLICATION_CREDENTIALS points to a Google Cloud service-account JSON file and is the key requirement for the core audit. The service account must also be added as a user on the relevant Search Console property. Without that property permission, the server cannot read the site's Search Console data.

Set DATAFORSEO_USERNAME, DATAFORSEO_PASSWORD, MAJESTIC_API_KEY, or CRUX_API_KEY only when the corresponding optional tier is needed. Placeholder values and empty strings are treated as disabled. Docker users may need a separate dashboard container with a shared data volume because a dashboard port inside a container is not directly reachable from the host browser.

Tools and capabilities

The documented workflow supports:

  • Listing accessible Search Console properties.
  • Refreshing Search Console data and crawling a property.
  • Running a prioritized technical SEO audit.
  • Showing an in-chat dashboard with get_dashboard.
  • Opening a local browser dashboard with open_dashboard.
  • Exporting a standalone HTML report with export_report.
  • Generating implementation-oriented fixes for audit findings.
  • Adding optional DataForSEO, Majestic, and CrUX data when configured.

Limitations and notes

The core audit depends on access to an owned Search Console property and a correctly configured Google service account. Third-party features are not available unless their credentials are supplied, and DataForSEO and Majestic are paid tiers according to the documentation.

The local dashboard is bound to 127.0.0.1 in the standard setup, and its port can change whenever the server restarts. Use the latest dashboard link returned by Claude. When running through Docker or a Docker MCP gateway, additional port and volume configuration is required.

seo-audit-console is designed around Claude Desktop and Claude Code in the supplied setup instructions. The collected data remains on the machine running the server, but access to the local files, credentials, and generated reports should still be managed by the operator.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Seo Audit Console

seo-audit-console is an MCP server that connects Claude to Google Search Console and a live site crawl for conversational technical SEO audits. Its main tools let you list properties, refresh data, run audits, view dashboards, open a local dashboard, and export HTML reports. Optional DataForSEO, Majestic, and CrUX services add further data.

Install it with npx and Node.js 20 or newer, then add `npx -y @houtini/seo-audit-console` to your Claude Desktop MCP configuration or run the documented `claude mcp add` command for Claude Code. Set `GOOGLE_APPLICATION_CREDENTIALS` to a service-account JSON file.

Set `GOOGLE_APPLICATION_CREDENTIALS` to a Google Cloud service-account JSON file and add that service account's email as a user on the Search Console property. Then ask Claude to list properties, refresh a site, or run an SEO audit.

The supplied setup instructions document Claude Desktop and Claude Code, not Cursor.

Ask Claude to export the report for a refreshed or audited property. The `export_report` tool creates one self-contained HTML file that can be shared with a client.

Related MCP servers

All in Marketing All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSeo Audit Console AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/seo-audit-console?style=directory)](https://allmcps.com/mcp/seo-audit-console)
HTML Embed
<a href="https://allmcps.com/mcp/seo-audit-console"><img src="https://allmcps.com/api/badge/seo-audit-console?style=directory" alt="Seo Audit Console on AllMCPs" /></a>