atomno-mcp-seo-audit
OfficialA technical SEO & GEO audit server that performs real HTTP measurements (not LLM guesses) to deliver deterministic health scores and actionable insights.
audit_site: Run a full technical SEO audit on any URL, returning a health score (0–100), letter grade (A–F), and categorized issues (security, SEO, performance, GEO). Checks TLS, redirects, TTFB, AI-crawler access, and more. Includes a GEO sub-score showing visibility in ChatGPT/Perplexity/AI Overviews (PRO).audit_diff: Re-audit a site and compare it against a previous snapshot, showing which checks improved or degraded over time (stateful PRO feature).list_checks: Browse the full catalog of audit checks grouped by category, with free/PRO badges.explain_issue: Get a detailed explanation for any check by itscheck_id, including why it matters and how to fix it.validate_robots: Validaterobots.txtcontent for syntax errors,Sitemap:directives, CSS/JS blocking, and explicit blocks for AI crawlers (GPTBot, ClaudeBot, etc.).check_sitemap: Fetch and analyze a sitemap XML by URL, reporting format, URL count, and common problems (404s, HTTP links, missing<lastmod>, 50k URL limit breaches).build_jsonld: Generate a ready-to-paste schema.org JSON-LD<script>block (Organization, Article, Product, FAQPage, etc.), with identification of missing required/recommended fields.build_meta: Generate<head>meta tags (title, description, canonical, Open Graph, Twitter Card) with length validation (title: 50–60 chars, description: 120–160 chars).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@atomno-mcp-seo-audit Audit example.com for SEO issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
atomno-mcp-seo-audit
MCP (Model Context Protocol) server for technical SEO & GEO audits, powered by
the detail.web engine — real measurements, not LLM
guesses. Run it from Cursor, Claude Desktop or any MCP client. 8 tools:
audit_site (deterministic 0–100 health score + letter grade, 78 checks across
8 categories, plus a GEO sub-score — visibility in ChatGPT / Perplexity /
Google AI Overviews), audit_diff (compare vs the previous snapshot),
robots.txt & sitemap.xml validators, JSON-LD & meta/OpenGraph builders, and
per-check fix explainers. Probes TLS, redirects, TTFB, AI-crawler access (GPTBot)
and llms.txt. Free tier + PRO+ (deep-crawl, GEO, 40+ deeper checks) — API
keys unlock the deeper engine on the PRO+ plan and up (see Free vs PRO+).
Why pair it with an LLM?
A language model on its own infers a site from training data and, at best, one
rendered page — it can't directly read your TLS certificate's expiry, measure
response time, parse sitemap.xml, or check whether GPTBot is blocked in
robots.txt. This server runs those checks for real: actual HTTP requests,
security headers, redirect chains, structured-data validation — and returns a
deterministic score (same site → same number), reproducible enough to put in
a client report. Think of it as the instrument and the LLM as the analyst that
interprets the readout — the two work best together.
Related MCP server: foglift-mcp
What you get
audit_site(url, depth=1, lang="ru")— one call returns:health score
0–100(higher is better) and a letter gradeA–F;issues grouped by category (security, SEO & indexing, performance, GEO, …), each with status
pass / warn / fail;a short human-readable summary.
audit_diff(url, lang="ru")— re-audits a site and compares it to the previous run: health/score delta and which checks got worse or better. The first call stores a baseline. This is something a one-off LLM question can't do — track a site over time. Stateful feature — needs a key on the PRO+ plan or higher.list_checks(lang="ru")— the full catalogue of engine checks grouped by category, with afree/PRObadge on each — so you (and the agent) can see exactly what the free tier covers and what PRO unlocks.explain_issue(check_id, lang="ru")— a deep-dive on a single check: why it matters and how to fix it. Pass acheck_idfromaudit_siteorlist_checks. Title and category are localized; detailed advice is currently in Russian (theadvice_langfield reports this).validate_robots(content, lang="ru")— paste arobots.txtand get back syntax issues, whether aSitemap:directive is present, whether CSS/JS is blocked from render bots, and which AI crawlers (GPTBot, ClaudeBot, …) are explicitly blocked. No fetch — validates the text you provide.check_sitemap(url, lang="ru")— fetches a sitemap by URL and reports its format (urlset/sitemapindex), URL count and common problems (404, non-XML content type,http://links, missing<lastmod>, the 50k-per-file limit). The fetch is SSRF-guarded on the server.build_jsonld(type, fields, lang="ru")— generates a ready-to-paste schema.org JSON-LD<script>(Organization, LocalBusiness, Article, Product, FAQPage, BreadcrumbList, WebSite) and tells you which required/recommended fields are missing. It never invents data — only what you pass in.build_meta(fields, lang="ru")— generates<head>meta tags (title, description, canonical, Open Graph, Twitter Card) and validates the title (50–60 chars) and description (120–160 chars) lengths.
Free vs PRO+
Free (no key) | PRO+ and up (API key) | |
Checks | core technical basics | 40+ deeper checks (E-E-A-T, Schema.org, Goldmine title) |
GEO | 4 GEO signals | GEO readiness sub-score + deep GEO checks |
Crawl | single page | deep-crawl up to 20 pages ( |
Which plan unlocks the API/MCP? Programmatic access (this server,
audit_diff, deep-crawl, GEO sub-score) is enabled on PRO+ (pro_plus), Business and Enterprise. The entry-level PRO plan and the Free tier are web-dashboard only — an API key issued on them authenticates but still returns the free result. If you need programmatic access, pick PRO+ or higher.
The audit engine itself stays on the server — this package is a thin client (HTTP calls + formatting only).
Install
uvx atomno-mcp-seo-auditOr add to your MCP client config (mcp.json):
{
"mcpServers": {
"seo-audit": {
"command": "uvx",
"args": ["atomno-mcp-seo-audit"]
}
}
}Configuration
All via environment variables:
Variable | Default | Purpose |
|
| Backend base URL |
| — | API key ( |
|
| HTTP timeout (seconds) |
|
| Default issue-title language ( |
The free tier needs no key and no signup — just run the command above.
Programmatic access (40+ deeper checks, GEO sub-score, deep-crawl, audit_diff)
requires a key from the PRO+ plan or higher — the entry-level PRO plan is
web-dashboard only and its key returns the free result. It is currently
provisioned on request: email kir@detailweb.ru or reach out via
audit.detailweb.ru. Once your account is active you
create keys yourself in Dashboard → Account → API keys (dwa_…, shown once)
and put the key in DETAILWEB_API_KEY.
Example
"Audit https://example.com"
The agent calls audit_site("https://example.com") and gets back the health
score, grade and the list of issues to fix.
License
MIT © atomno-mcp. The open-source client talks to a proprietary hosted backend.
🇷🇺 На русском
MCP-сервер технического SEO-аудита на движке detail.web. Запускайте аудит прямо из ИИ-агента (Cursor, Claude Desktop и любой MCP-клиент): health-score, проблемы по 8 категориям и GEO-суб-балл (видимость в ИИ-поиске — ChatGPT, Perplexity, AI Overviews).
Зачем в связке с нейросетью. Языковая модель сама по себе судит о сайте по
обучающим данным и в лучшем случае по одной отрисованной странице — она не
прочитает напрямую срок SSL-сертификата, не измерит время ответа, не распарсит
sitemap.xml и не проверит, заблокирован ли GPTBot в robots.txt. Этот сервер
выполняет такие проверки по-настоящему: HTTP-запросы, заголовки, редиректы,
микроразметка — и даёт детерминированный score (тот же сайт → то же число),
пригодный для отчёта клиенту. Это прибор, а нейросеть — аналитик, который читает
показания. Лучше всего работает связка.
Инструменты: audit_site (аудит + score + GEO), audit_diff (что
изменилось с прошлой проверки — stateful, тариф PRO+ и выше), list_checks (каталог
проверок free/PRO), explain_issue (почему важно + как исправить),
validate_robots, check_sitemap, build_jsonld, build_meta.
Установка:
uvx atomno-mcp-seo-auditВ конфиге MCP-клиента (mcp.json):
{
"mcpServers": {
"seo-audit": {
"command": "uvx",
"args": ["atomno-mcp-seo-audit"],
"env": { "DETAILWEB_LANG": "ru" }
}
}
}Бесплатный тариф (базовые проверки, одна страница) работает сразу, без ключа
и регистрации. Программный доступ (40+ глубоких проверок, GEO-суб-балл,
deep-crawl до 20 страниц, audit_diff) работает с ключом тарифа PRO+
(pro_plus) и выше — Business, Enterprise. Начальный тариф PRO
(1290 ₽) и Free — только веб-кабинет: ключ на них проходит авторизацию, но
результат остаётся бесплатным. Тариф пока выдаём по запросу: напишите на
kir@detailweb.ru или через audit.detailweb.ru.
После активации аккаунта ключ (dwa_…) создаётся в кабинете → Аккаунт →
API-ключи (показывается один раз) и подставляется в DETAILWEB_API_KEY в
env. Полное описание инструментов и настроек — в английской версии выше.
Available Tools
8 toolsaudit_diffA
Сравнить сайт с прошлой проверкой: что улучшилось, что деградировало.
Прогоняет свежий аудит и сопоставляет с предыдущим сохранённым снимком того же URL: дельта health/score и какие именно проверки стали хуже/лучше. Это то, чего разовый вопрос к LLM не умеет — отслеживание сайта во времени. Первый вызов сохраняет базовую точку (сравнивать ещё не с чем). Stateful PRO-функция: нужен DETAILWEB_API_KEY — без него available=false и подсказка про PRO.
Inputs: url (required), lang. Returns: object
audit_siteA
Прогнать технический SEO-аудит сайта — реальными измерениями, не догадкой.
Делает настоящие HTTP-запросы и проверяет факты, которые языковая модель не может узнать «из головы»: срок SSL-сертификата, security-заголовки (HSTS, защита от clickjacking), redirect-chain, robots.txt/sitemap.xml, микроразметку, доступ ИИ-краулеров. Возвращает ДЕТЕРМИНИРОВАННЫЙ health-score (0-100, выше = лучше) — тот же сайт даёт то же число, — буквенную оценку, список проблем по категориям и (для PRO) GEO-суб-балл. Без ключа — free-тариф. Используй, чтобы получить твёрдые факты, а затем объясни их пользователю.
Inputs: url (required), lang, depth. Returns: object
build_jsonldA
Сгенерировать готовый блок JSON-LD schema.org из переданных полей.
Не выдумывает данные — кладёт только то, что передали, и подсказывает, каких обязательных/рекомендованных полей не хватает. Возвращает готовый .
Inputs: type (required), fields (required), lang. Returns: object
build_metaA
Сгенерировать -мета-теги (title, description, canonical, Open Graph, Twitter Card) и проверить длины title (50–60) и description (120–160). Возвращает готовый блок тегов.
Inputs: fields (required), lang. Returns: object
check_sitemapA
Скачать и разобрать sitemap по URL: формат (urlset/index), число URL и частые проблемы (404, не-XML, http-ссылки, отсутствие lastmod, превышение лимита 50 000). Фетч защищён от SSRF на стороне сервера.
Inputs: url (required), lang. Returns: object
explain_issueA
Подробно объяснить одну проверку: почему она важна и как её исправить.
Принимает check_id из результата audit_site/list_checks. Заголовок и категория локализуются; развёрнутые советы пока на русском (поле advice_lang это сообщает). Для неизвестного id — found=false.
Inputs: check_id (required), lang. Returns: object
list_checksA
Список всех проверок движка с разбивкой free/PRO по категориям.
Помогает понять, что входит в бесплатный тариф, а что — только в PRO, и какие категории покрывает движок (security, SEO, GEO, E-E-A-T и т.д.).
Inputs: lang. Returns: object
validate_robotsA
Проверить содержимое robots.txt: синтаксис, sitemap-директива, блокировка CSS/JS от рендер-ботов и явные запреты ИИ-краулеров (GPTBot, ClaudeBot и т.д.).
Передайте текст файла — фетч не выполняется, проверка локальная на бэкенде.
Inputs: content (required), lang. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct aspect of SEO: full audit, diff comparison, sitemap/robots checks, meta/schema generation, and issue explanation. No overlapping purposes.
All tools follow a clear verb_noun pattern in snake_case (e.g., audit_site, check_sitemap, build_meta), making them predictable and easy to distinguish.
With 8 tools, the server covers core SEO audit functionality without being overwhelming or too sparse. Each tool earns its place.
The tool set covers the main lifecycle of SEO auditing: running audits, checking specific files, generating meta/schema, and explaining issues. Minor gaps like page speed or mobile checks exist but are not essential for the stated purpose.
Maintenance
Related MCP Connectors
Run full technical SEO audits of any website from your AI agent and get structured findings back.
Free MCP server that audits any public URL: technical SEO, Core Web Vitals, indexing checks.
Your agent needs to crawl a site and say what is wrong with it — broken tags, duplicate content, pages nothing can index, resources that never load. **What you can ask for** • "Crawl this site and list every page with a duplicate title or missing description." • "Which pages are non-indexable, and why?" • "Run Lighthouse on these URLs and give me the failing audits." • "Show the internal link graph and the orphan pages." • "Give me this page's raw HTML and its microdata." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-onpage/mcp and sign in with OAuth — there is no key to create or paste. 20 tools: submit a crawl and read its summary, pages, resources, links and waterfall; duplicate content and duplicate tags; keyword density; non-indexable and uncrawlable resources; parsed content, raw HTML, microdata, screenshots and Lighthouse. **Why this rather than the source** A crawler you drive from the agent, with the audit results as structured data rather than a PDF. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the broken pages here, then ask the same agent what those pages used to rank for — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Live AEO, GEO, JSON-LD Schema, robots.txt AI crawler, and Agent Readiness diagnostic auditor.
Related MCP Servers
- AlicenseBqualityBmaintenanceMCP server that enables AI agents to perform comprehensive web audits using Google Lighthouse with 13+ tools for performance, accessibility, SEO, and security analysis.111,269 npm75MIT
- 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.-
- 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.182MIT
- 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.17216 npm1MIT