What is SEO Audit Console?
SEO Audit Console is a Model Context Protocol server for technical and content SEO auditing through Claude Desktop or Claude Code. It combines a site's Google Search Console history with a live crawl, connecting technical findings to search performance rather than treating crawl issues in isolation. It targets SEO consultants, in-house marketers and people learning how to assess a site's organic search performance.
The server runs locally and stores audit data on the user's machine. Installation options include an npm-based configuration and a Windows bundle for Claude Desktop. A Google Cloud service account with access to the relevant Search Console property is required for the core audit. Findings can be explored through Claude, a local browser dashboard or a self-contained HTML report.
Optional DataForSEO and Majestic credentials add competitive and backlink research, while a Chrome UX Report API key enables field Core Web Vitals data. These connections are not required for the core audit, and the paid data services introduce separate costs. The tool can propose fixes such as redirect rules, structured data and internal links; applying changes depends on the surrounding workflow and access to the site's codebase.
Key capabilities
- Search performance analysis Joins Search Console history with crawl data to connect findings to affected traffic.
- Site crawling Collects site data and analyses internal links, click depth and internal PageRank.
- Audit prioritisation Ranks findings by estimated recoverable clicks and development effort, with supporting evidence.
- Fix generation Produces proposed redirect rules, structured data and internal linking changes through Claude.
- Reporting Provides conversational results, a local browser dashboard and self-contained HTML exports.
- Competitive research Uses optional DataForSEO and Majestic connections for competitor and backlink analysis.
Where SEO Audit Console fits
SEO consultants and in-house marketing teams can use the server to collect audit evidence, investigate declining search traffic and prioritise technical or content changes. In Claude Code, it can fit into a workflow that connects findings with repository changes and subsequent crawling to check the result.
Before deployment, teams should verify service-account access to the Search Console property, the local runtime requirements and the credentials needed for optional data sources. Container deployments require separate dashboard networking configuration. Proposed fixes and traffic-recovery estimates should be reviewed before changes are applied.
Install
claude mcp add seo-audit-console --env GOOGLE_APPLICATION_CREDENTIALS=C:/path/to/service-account.json -- npx -y @houtini/seo-audit-consoleReviews of SEO Audit Console
Be the first to share your experience with SEO Audit Console.
Write a review
Loading review form…
Alternatives to SEO Audit Console
EngramEngram is a local persistent memory system for AI coding agents, storing decisions and session summaries in SQLite and exposed through MCP and an HTTP API.
Firecrawl MCP ServerA Firecrawl connector for web search, page extraction, site mapping and bounded crawling with Markdown or structured results.