io.github.houtini-ai/seo-crawler-mcp

Official registry Archived Data and databases

Crawl and analyse websites for SEO errors using Crawlee with SQLite storage

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @houtini/seo-crawler-mcp
Claude Code
claude mcp add seo-crawler-mcp -e 'OUTPUT_DIR=<OUTPUT_DIR>' -e 'DEBUG=<DEBUG>' -- npx -y @houtini/seo-crawler-mcp@2.0.1
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "seo-crawler-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@houtini/seo-crawler-mcp@2.0.1"
            ],
            "env": {
                "OUTPUT_DIR": "<OUTPUT_DIR>",
                "DEBUG": "<DEBUG>"
            }
        }
    }
}

Environment variables

  • OUTPUT_DIR required Directory where crawl results are saved
  • DEBUG Enable verbose debug logging (set to 'true' to enable)

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. SEO Crawler MCP - retired
  2. Where to go
  3. What this means for you
  4. Migrating

SEO Crawler MCP - retired

This project has been superseded by SEO Audit Console.

SEO Crawler crawled your whole site into SQLite and gave Claude 25+ analysis queries over the result. The crawler survived the move - it was rewritten to be stdio-safe and it is now the crawl half of a bigger tool.

SEO Audit Console keeps the crawl and adds the thing the crawl could never tell you on its own: what people actually searched for to get there. It merges the crawl with your Google Search Console history and on-demand DataForSEO data, then ranks every finding by the clicks it could recover rather than by severity.

A flat crawler sells you severity. This ranks by yield.

Where to go

git clone https://github.com/houtini-ai/seo-audit.git

Docs and setup: github.com/houtini-ai/seo-audit

What this means for you

  • The npm package still installs. @houtini/seo-crawler-mcp is deprecated, not unpublished. Nothing you have running will break.
  • This repository is archived. The code stays readable and every existing link keeps working, but there are no further releases, and issues and pull requests are closed.
  • The crawler got better on the way over. It no longer depends on Crawlee (which logged to stdout and corrupted MCP's JSON-RPC framing), it seeds discovery from sitemaps and known GSC URLs rather than links alone, and it guards against redirects that wander off-host.

Migrating

Start a crawl on the new tool and it builds its own database:

start_crawl for https://example.com/

Run refresh_property instead if you want the crawl, the Search Console sync and URL inspection in one pass.


Part of the Houtini open-source MCP set. Questions: hello@houtini.com.

Frequently asked questions

What is io.github.houtini-ai/seo-crawler-mcp?

Crawl and analyse websites for SEO errors using Crawlee with SQLite storage

How do I install io.github.houtini-ai/seo-crawler-mcp?

It runs on your machine. In Claude Code: claude mcp add seo-crawler-mcp -e 'OUTPUT_DIR=<OUTPUT_DIR>' -e 'DEBUG=<DEBUG>' -- npx -y @houtini/seo-crawler-mcp@2.0.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.houtini-ai/seo-crawler-mcp need an API key?

Yes. It expects OUTPUT_DIR, which you set in its configuration.

Is io.github.houtini-ai/seo-crawler-mcp open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains io.github.houtini-ai/seo-crawler-mcp?

It is published by houtini-ai. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.