mcpField
A
A Seo Mcp

A Seo Mcp

Local
github.com/AutomateLab-techBusiness & Marketing2Updated 1w ago

About A Seo Mcp

A Seo Mcp is an MCP server for auditing how well web pages support AI citation and discovery. It serves SEO teams and site owners with page and site checks, citation scoring, and content rewrites, and can also run audits in GitHub Actions.

Key features

  1. 01Audit schema, robots.txt, and sitemap
  2. 02Check llms.txt and AI crawler access
  3. 03Score citation readiness and page eligibility
  4. 04Generate llms.txt files
  5. 05Rewrite content for AEO and GEO
  6. 06Save audit reports as Markdown

Use cases

  1. 01Find citation blockers on a site
  2. 02Check pages before publishing content changes
  3. 03Run score-gated audits in GitHub Actions
  4. 04Prepare content for answer and generative engines

MCP support

Exposes 20 tools to MCP clients for page and site audits, scoring, file generation, rewrites, and report saving. The README also describes the same audit engine as a GitHub Action.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"ai-seo": {
"command": "npx",
"args": [
"-y",
"@automatelab/ai-seo-mcp"
]
}
}
}
Run commandnpx -y @automatelab/ai-seo-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@automatelab/ai-seo-mcp0.1.1

Tools

20

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
urlstringYesPublic URL to audit. Must be a fully-qualified http(s) URL that returns HTTP 200 (redirects are followed). The tool fetches this URL once and runs every sub-audit (schema, robots, technical, sitemap, AI-Overview eligibility) against the response.
include_raw_htmlbooleanNoIf true, return the full raw HTML in the response under `raw_html`. Default false. Set true only when you need to inspect markup that wasn't captured by the structured findings; the payload can be large.
respect_robotsbooleanNoIf true (default), the tool checks robots.txt before fetching and skips disallowed paths, returning a robots_blocked finding instead. Set to false ONLY for auditing your own site where you've intentionally blocked crawlers and need the audit to bypass that block.
generate_reportbooleanNoIf true, return a standalone HTML scorecard in the `report_html` field. The HTML is self-contained (no external dependencies) and can be saved as a .html file or pasted to Gist/CodePen. Default false to keep audits cheap.
renderenumNoRendering mode. `static` (default) fetches raw HTML via HTTP — fast (<1s) but misses JS-rendered content typical of SPAs (React/Vue/Angular landing pages). `headless` spins up Playwright Chromium, waits for networkidle, and audits the rendered DOM — adds 3-10s per audit and requires `playwright-core` installed plus a one-time `npx playwright install chromium`. Use `headless` when the static audit shows `content_quality: "spa_empty"` or you know the target is JS-rendered.static | headless

Details

From the project README

@automatelab/ai-seo-mcp

AI Citation Toolkit for the Model Context Protocol

npm version license node

Audit why AI systems do or do not cite your pages. MCP server. No API keys.

Works inside Claude, Cursor, Windsurf, Codex, and any MCP client that speaks stdio.


What it checks

  • AI crawler access - GPTBot, OAI-SearchBot, ClaudeBot, and PerplexityBot allowed or blocked in robots.txt
  • llms.txt - present, spec-compliant, links alive
  • Structured answer extraction - FAQ headings, BLUF paragraphs, answer-ready blocks
  • [[schema]] completeness - FAQPage, Article, Organization, Person; flags deprecated patterns
  • Entity clarity - named entity density and sameAs coverage that help AI systems identify the subject
  • Citation formatting - canonical URL hygiene, og:url, hreflang, noindex traps
  • Sitemap freshness - lastmod signals that tell crawlers the page is current

Run an audit. Get a list of citation-blockers, ranked.

You: Run an AI-SEO audit on https://automatelab.tech/launching-the-ai-seo-mcp/.

Result (truncated):

{
  "url": "https://automatelab.tech/launching-the-ai-seo-mcp/",
  "score": 61,
  "grade": "C",
  "dimension_scores": {
    "schema": 45, "technical": 80, "structure": 40,
    "robots": 90, "freshness": 85, "authority": 40,
    "entity_density": 21, "sitemap": 100
  },
  "findings": [
    {
      "severity": "critical",
      "category": "structure",
      "message": "No FAQ structure found (no FAQPage schema or H3 question headings).",
      "fix": "Add FAQ H3 headings ending in '?' with answer paragraphs, and a FAQPage JSON-LD block.",
      "estimated_impact": "high"
    },
    {
      "severity": "warning",
      "category": "authority",
      "message": "Low authority signals - missing Organization or author Person schema.",
      "fix": "Add Organization JSON-LD and Article.author as a Person node with sameAs links.",
      "estimated_impact": "high"
    }
  ]
}

Each finding names the exact fix. No opaque scores, no guesswork.


Install

npx -y @automatelab/ai-seo-mcp

Requires Node 20 or later.

Claude Desktop

Add to %APPDATA%\Claude\claude_desktop_config.json (Windows) or ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "ai-seo": {
      "command": "npx",
      "args": ["-y", "@automatelab/ai-seo-mcp"]
    }
  }
}

Restart Claude Desktop. Any MCP client that supports stdio transport works - same command / args pattern.

Optional: headless rendering for SPAs

By default audit_page reads raw HTML — fast, but misses content on React/Vue/Angular SPAs. Pass render: "headless" to spin up Chromium and audit the rendered DOM (adds 3-10s per audit).

One-time install:

npm install playwright-core
npx playwright install chromium

Then call audit_page with render: "headless". Use static for everything else — most marketing sites and docs render fine without it.


Run it in CI (GitHub Action)

This repo doubles as a GitHub Action. Drop it in a workflow to fail a PR when any page regresses below an AI-citation score - the same audit engine, gated on every change.

- uses: actions/checkout@v4
- name: AI-SEO audit
  uses: AutomateLab-tech/[email protected]
  with:
    urls: "https://example.com,https://example.com/pricing"
    min-score: "70"            # fail if any URL scores below this
    respect-robots: "true"     # set false for staging / sites you own
    report-path: "ai-seo-report.md"   # optional Markdown report artifact
    fail-on-regression: "true"

The Action builds the auditor from the pinned ref, runs audit_page on each URL, writes a scorecard to the job summary, and exits non-zero if any URL falls below min-score (when fail-on-regression is true). Outputs: min_score_observed, urls_audited, report_path. Full example: examples/github-action-usage.yml.


Further reading


MCP tool surface (20 tools)
ToolPurpose
audit_pageComposite AI-SEO audit with 8-dimension scoring (schema, technical, structure, robots, freshness, authority, entity density, sitemap).
audit_schemaValidate JSON-LD against Schema.org rules and AI-citation best practice. Flags deprecated patterns.
audit_canonicalCanonical link integrity, trailing-slash hygiene, og:url consistency.
audit_siteSingle-call site sweep: audit_page + check_robots + check_sitemap + audit_schema with overall grade and top-5 fixes.
audit_sitemapSite-wide content audit: stride-sample N URLs from the sitemap, run audit_page on each, return distribution + worst pages + top findings.
check_robotsParse robots.txt and report per-crawler allow/disallow for all known AI crawlers. Surfaces the GPTBot-blocked-but-OAI-SearchBot-allowed trap.
check_sitemapValidate XML sitemaps: presence, URL count, lastmod freshness, image/video extensions.
check_technicalHEAD tag audit: canonical, OpenGraph, Twitter Card, hreflang, HTTPS, noindex, title hygiene.
score_ai_overview_eligibilityScore a page's probability of appearing in Google AI Overviews using current correlation factors.
score_citation_worthinessScore how citable a page or text block is for Perplexity, ChatGPT, Google AI Overviews, and Claude. Includes per-section chunk_analysis / extractability_score: how cleanly an LLM can lift a standalone answer from each heading.
score_agentic_browsingScore a page against the Lighthouse "Agentic Browsing" category (May 2026): llms.txt, WebMCP, accessibility-tree integrity, and layout stability.
score_test_citationSimulate "would an AI engine cite this for this query?" via MCP sampling, with deterministic heuristic fallback.
llms_txt_generateGenerate llms.txt and optionally llms-full.txt from a domain's sitemap.
llms_txt_validateLint an existing llms.txt for spec compliance and broken links.
rewrite_aeoRewrite content for Answer Engine Optimization (BLUF structure, FAQ format, schema additions).
rewrite_geoRewrite content for Generative Engine Optimization (entity definitions, comparison tables, synthesis-ready structure).
extract_entitiesExtract named entities, sameAs links, and citation-density score from a page's content and structured data.
diff_pagesCompare two URLs for AI citation-worthiness: side-by-side dimension scores, gap analysis, and prioritized fix recommendations for url_a.
report_saveRender an audit_page / audit_site result as a Markdown report and write it to disk under MCP_WORKSPACE_ROOT.

v0.4.0 renamed tools from flat snake_case to dot-notation (audit_page, check_robots, …) for a navigable hierarchy. Update any saved invocations.

Environment variables: see ENV.md.


Contributing

Bug reports, feature ideas, and PRs welcome. See CONTRIBUTING.md.

Security

To report a vulnerability, see SECURITY.md.

License

MIT - see LICENSE.

Built by automatelab.tech

Maintenance and verification

See the maintenance guide for interpretation limits, current tool names where applicable, and reproducible verification.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.