Crawlinx

Free technical-SEO audit as an MCP server — built for AI coding agents.

smithery badge

Crawlinx is a hosted Model Context Protocol server that lets your AI agent audit a website's technical SEO and act on the results. It crawls a site (50 pages by default, up to 200 via max_pages), runs 156 technical-SEO checks, and returns an LLM-ready Markdown report with a prioritized fix plan — small enough to keep in context on a real site.

• ☁️ Remote server over Streamable HTTP — no local install, no API key, no signup
• 🔎 156 checks — titles, meta, canonicals, orphan pages, noindex, internal PageRank, JS render-diff, images, performance, sitemap
• 🤖 Agent-native — compact reports, per-issue drill-down, and scan diffs so an agent can scan → fix → verify in a loop
• 🔗 Public shareable reports — every scan has a URL

Homepage: https://crawlinx.com · Docs: https://crawlinx.com/api

Install

The server is remote — you only need the endpoint https://crawlinx.com/mcp. No key.

Claude Code

claude mcp add --transport http crawlinx https://crawlinx.com/mcp

Cursor / Windsurf / Cline / Claude Desktop

Add to your MCP config (mcp.json / settings):

{
  "mcpServers": {
    "crawlinx": {
      "type": "http",
      "url": "https://crawlinx.com/mcp"
    }
  }
}

A machine-readable manifest is served at /.well-known/mcp.json.

Tools

Tool	What it does
scan_url	Start a free SEO audit of a URL (crawls max_pages pages — default 50, max 200); returns a scan id.
get_report	Fetch a finished report as structured JSON.
get_report_markdown	Fetch a finished report as compact, LLM-ready Markdown (health score + prioritized fix plan + issues collapsed by code). Set full=true for the complete report.
get_issue_detail	Expand one issue code: every affected URL plus step-by-step remediation.
diff_scan	Diff a scan against the previous scan of the same domain to confirm fixes landed and nothing regressed.

Example prompts

• "Audit https://example.com and give me the top 5 SEO fixes."
• "Scan my site, then fix the duplicate <title> issues in the codebase and re-scan to confirm."
• "Which pages are orphaned (no internal links) and how do I link them?"

Typical workflow

1. scan_url → get a scan_id
2. poll get_report_markdown until the crawl finishes
3. get_issue_detail(scan_id, code) to expand a specific issue before changing code
4. apply fixes
5. re-scan, then diff_scan(scan_id) to verify

The crawler

Audits run as CrawlinxBot, which honors robots.txt, limits request rates, and does not bypass access controls. See crawlinx.com/bot. Site owners can opt out via robots.txt or the removal form.

Maintenance & rankings

This MCP is a living product — aggregators (Smithery Quality Score, polygraph.so security grades, MCP Bench) actively rank and grade it, and the Official Registry cascades our listing everywhere. Keep the endpoint healthy and re-publish on changes. See MAINTENANCE.md.

About

This repository documents the hosted Crawlinx MCP server. The audit engine is operated as a service at crawlinx.com; this repo is the public reference and install guide for the MCP integration.