AutomateLab AI SEO Magic Button
This server crawls a website and generates a prioritized, agent-executable AI-SEO (AEO/GEO) audit plan rather than making edits itself.
Audit a whole site: pass a
domain(hostname or origin, e.g.example.com) and it crawls and audits pages, scoring each one.Control scope: limit the crawl with
pages(1–50, default 10).Filter noise: set
include_infoto include or exclude purely informational, non-actionable findings (off by default).Get a portable plan: returns structured
plan.jsoncontent containingdomain,pages_audited,generated_at, and anitemsarray.See prioritized fixes: each item has a
url,category(schema/structure/citation/content),severity(critical/high/medium/low/info),title, and anexpected_score_deltascore-lift estimate.Execute later: every item includes a self-contained
action(tool + baked params) and anacceptancecheck, so an agent can run it and verify results.Comes with a markdown checklist alongside the plan, and is read-only, idempotent, and non-destructive.
Allows pushing generated SEO plan items into a Notion board for task tracking and management.
ai-seo-magic-button
Point it at your site, get a whole-site AEO/GEO audit plus a ready-to-run plan your agent can execute. One magic button for AI-SEO - runs as a Claude skill, a Claude plugin, and an MCP server, so it works in any MCP host (Cursor, Cline, Windsurf, Claude Desktop).
It produces an actionable plan, not direct edits: a portable plan.json plus
a markdown checklist, where every item is self-contained and agent-executable.
You then run your agent against the plan to execute it.
Under the hood it is a thin orchestration layer over two engines:
@automatelab/ai-seo-mcp
(audit + score + rewrite) and
@automatelab/citation-intelligence
(what AI engines cite). No API keys are needed for the core audit→plan flow.
The two-step flow
Run it → it crawls your site, audits every page, and generates
plan.json+ a markdown checklist, prioritized by estimated score lift.Run your agent against the generated plan to execute it (rewrites, schema, llms.txt, robots) - then verify the score actually lifted.
Related MCP server: automatelab-ai-seo
Install
As an MCP server (any host)
// e.g. claude_desktop_config.json / Cursor / Cline
{
"mcpServers": {
"ai-seo-magic-button": {
"command": "npx",
"args": ["-y", "ai-seo-magic-button", "mcp"]
}
}
}Exposes one tool: generate_seo_plan { domain, pages? } → returns the full
plan.json (as structured content) plus the markdown checklist.
As a Claude Code plugin
/plugin marketplace add AutomateLab-tech/ai-seo-magic-button
/plugin install ai-seo-magic-button@ai-seo-magic-button-marketplaceAs a Claude skill
Copy skill/ into your .claude/skills/ (or install via the plugin above). The
skill is the conversational magic-button UX - see skill/SKILL.md.
CLI
npm install && npm run build
# audit -> plan.json + plan.md
node dist/cli.js audit example.com --pages 10
# execute the plan's tool-driven items (writes to ./magic-button-out)
node dist/cli.js apply plan.json
# re-audit and diff the score (proof the plan worked)
node dist/cli.js verify plan.json
# optional: push items into an agency-os Notion board (else local checklist)
node dist/cli.js sink plan.jsonThe child engines resolve via npx by default. To use local builds:
export AISEO_MCP_PATH=/abs/path/ai-seo-mcp/dist/index.js
export CITATION_MCP_PATH=/abs/path/citation-intelligence-mcp/dist/index.jsWorked example
$ node dist/cli.js audit example.com --pages 2
https://example.com
pages audited: 1 · avg score: 48 (D)
fixes: 8 · est. lift: +78 points
1. [critical] +12 No JSON-LD structured data found on this page.
2. [critical] +12 No FAQ structure found (no FAQPage schema or H3 question headings).
3. [critical] +12 No sitemap found at standard locations.
6. [high] +10 Rewrite for AEO: this page
7. [medium] +4 Low authority signals - missing Organization/author schema.
8. [medium] +4 No canonical link element found.A full sample plan.json is in examples/plan.example.json.
Each item carries a self-contained action (the tool + baked params) and an
acceptance check - see docs/plan-format.md.
How it is built
One shared core lib, four thin surfaces. See
docs/scope.md for positioning and
docs/plan-format.md for the schema + core-lib boundary.
src/core/ audit + plan + apply + verify + sink (the only place with logic)
src/cli.ts CLI surface
src/mcp-server.ts MCP server surface (generate_seo_plan)
skill/ Claude skill surface
plugin/ Claude plugin surfaceLicense
MIT
Maintenance and verification
See the maintenance guide for interpretation limits, current tool names where applicable, and reproducible verification.
Available Tools
1 toolgenerate_seo_planGenerate a whole-site AI-SEO planARead-onlyIdempotent
Crawl a site, run a whole-site AEO/GEO audit (via the ai-seo + citation-intelligence engines), and return a portable, agent-executable plan.json plus a markdown checklist. This produces an actionable PLAN, not direct edits.
Inputs: domain (required), pages, include_info. Returns: items, domain, generated_at, pages_audited
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
There is only one tool, so no selection ambiguity is possible. Its purpose (crawl + full-site AEO/GEO audit + generate plan.json and checklist) is stated clearly and distinctly.
The single name `generate_seo_plan` follows a clean verb_noun snake_case convention. With one tool there is no risk of mixed conventions.
One tool for an entire 'SEO Magic Button' server is thin, sitting at the low end of the 3-15 range. It is offset by the tool being substantive (crawl + multi-engine audit + plan generation in one call), but there is still only a single entry point.
The stated purpose of producing an actionable plan is covered, but the surface is a one-shot generator with no follow-up operations such as retrieving/list existing plans, checking audit status, or applying/executing the generated plan. The description explicitly disclaims direct edits, so agents may hit a dead end after planning.
Maintenance
Related MCP Connectors
Open-source AI SEO over MCP: audits, ranks, keywords, backlinks + AI visibility (GEO).
SEO MCP: Search Console, GA4, SERP and domain data, rank tracking, AI citations and site fixes.
Audit any URL for ChatGPT, Claude & Perplexity GEO citation readiness, llms.txt & Schema.org.
SEO, GEO and ADA/WCAG audits, AI citation tracking and site crawls for AI assistants.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for website SEO + GEO analysis. Scan any URL to get scores across 5 categories (SEO, GEO, Performance, Security, Accessibility) with actionable fix recommendations. Enables AI coding assistants to audit websites and implement fixes autonomously.-
- AlicenseAqualityBmaintenanceAutomateLab AI-SEO audits, scores, and rewrites web pages for AI citation eligibility, AEO and GEO. No API keys or registration. Works with Claude, Cursor, Codex, and other MCP clients. Product and documentation: https://automatelab.tech/products/mcp/ai-seo/2088 npm3MIT
- AlicenseAqualityDmaintenanceEnables AI agents to perform comprehensive SEO audits on web pages, including meta tags, headings, links, images, performance, and more, via a CLI or MCP server.181MIT

atomno-mcp-seo-auditofficial
AlicenseAqualityCmaintenanceMCP server for technical SEO audits, powered by the detail.web engine. Run a site audit straight from your AI agent to get a health score, issues across 8 categories, and a GEO sub-score.81MIT