AutomateLab AI SEO Magic Button
Related Servers
Alternatives to AutomateLab AI SEO Magic Button
- 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
Related 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.-
- AlicenseAqualityBmaintenanceChecks what GPTBot, ClaudeBot, PerplexityBot and 50+ other AI crawlers can read on a site and what its access policy allows, checks whether a page permits search, answers, training or agent use (with a signed receipt), generates llms.txt, robots.txt and JSON-LD, and reads your Answer Analysis. Nine tools for Claude Desktop, Cursor and other MCP clients.9139 npmMIT
- AlicenseAqualityBmaintenanceAn MCP server that lets an AI agent audit a page for SEO and GEO — on-page tags, structured data, robots.txt, sitemaps, hreflang, and whether ChatGPT, Claude, Perplexity and Gemini can actually crawl and cite you. No API keys required.17395 npm1MIT
- AlicenseAqualityCmaintenanceEnables running SEO and AI/GEO visibility audits on websites, reading audit results, competitor analyses and expert reports, and importing or retrieving editorial calendars, all from any MCP client such as Claude Desktop, Claude Code or Cursor.1147 npmMIT
- 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
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.