/ Каталог / Песочница / seo-audit-skill
● Сообщество seo-skills ⚡ Сразу

seo-audit-skill

автор seo-skills · seo-skills/seo-audit-skill

108 SEO audit rules across 12 categories — Core Web Vitals, security headers, structured data, accessibility — run from Claude Code.

SEO Audit Skill wraps a CLI that crawls any URL and evaluates 108 rules across 12 categories: on-page SEO, Core Web Vitals, security headers, structured data, accessibility, crawlability, mobile, i18n, and more. Claude Code invokes it, interprets the report, and drafts actionable fixes grouped by impact.

Зачем использовать

Ключевые функции

Живое демо

Как выглядит на практике

seo-audit-skill.replay ▶ готово
0/0

Установка

Выберите клиент

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "seo-audit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/seo-skills/seo-audit-skill",
        "~/.claude/skills/seo-audit-skill"
      ],
      "_inferred": true
    }
  }
}

Откройте Claude Desktop → Settings → Developer → Edit Config. Перезапустите после сохранения.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "seo-audit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/seo-skills/seo-audit-skill",
        "~/.claude/skills/seo-audit-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor использует ту же схему mcpServers, что и Claude Desktop. Конфиг проекта приоритетнее глобального.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "seo-audit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/seo-skills/seo-audit-skill",
        "~/.claude/skills/seo-audit-skill"
      ],
      "_inferred": true
    }
  }
}

Щёлкните значок MCP Servers на боковой панели Cline, затем "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "seo-audit-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/seo-skills/seo-audit-skill",
        "~/.claude/skills/seo-audit-skill"
      ],
      "_inferred": true
    }
  }
}

Тот же формат, что и Claude Desktop. Перезапустите Windsurf для применения.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "seo-audit-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/seo-skills/seo-audit-skill",
        "~/.claude/skills/seo-audit-skill"
      ]
    }
  ]
}

Continue использует массив объектов серверов, а не map.

~/.config/zed/settings.json
{
  "context_servers": {
    "seo-audit-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/seo-skills/seo-audit-skill",
          "~/.claude/skills/seo-audit-skill"
        ]
      }
    }
  }
}

Добавьте в context_servers. Zed перезагружается автоматически.

claude mcp add seo-audit-skill -- git clone https://github.com/seo-skills/seo-audit-skill ~/.claude/skills/seo-audit-skill

Однострочная команда. Проверить: claude mcp list. Удалить: claude mcp remove.

Сценарии использования

Реальные сценарии: seo-audit-skill

How to run your first full SEO audit and prioritize fixes

👤 Site owners and SEO practitioners who inherit a site with unknown SEO health ⏱ ~30 min beginner

Когда использовать: New project, new site, or pre-launch checklist.

Предварительные требования
  • Skill installed — git clone https://github.com/seo-skills/seo-audit-skill ~/.claude/skills/seo-audit-skill
  • Node 18+ — nvm install 18
Поток
  1. Run full audit
    Run seo-audit-skill on https://example.com — all 108 rules, output markdown.✓ Скопировано
    → Report with per-rule pass/fail and a category summary
  2. Prioritize by impact
    Group the failures into 'ship this week' (high impact, low effort) vs 'backlog'. Explain the cutoff.✓ Скопировано
    → Ranked fix list with rationale
  3. Generate fix PRs
    For the top 5 'ship this week' items, draft the code changes in a PR-ready diff.✓ Скопировано
    → Diffs for meta tags, headers, and structured data

Итог: A sprint-sized SEO fix list with drafted diffs.

Подводные камни
  • Lighthouse scores vary run-to-run — Run 3 times, take median; skill supports --runs=3
  • Rules flag false positives on JS-heavy SPAs — Use --render=js to enable JS rendering; costs more time
Сочетать с: trae-skill

Run just the Core Web Vitals checks in CI

👤 Performance engineers wiring SEO to CI ⏱ ~20 min intermediate

Когда использовать: You want a CI gate that blocks regressions in LCP/CLS/INP.

Поток
  1. Scope to CWV category
    Run seo-audit-skill --category=cwv on our staging URL.✓ Скопировано
    → Just the CWV rules with values
  2. Wrap in CI
    Generate a GitHub Actions step that runs this and fails if LCP > 2.5s.✓ Скопировано
    → YAML snippet with threshold logic

Итог: A CI gate that catches perf regressions before prod.

Подводные камни
  • CI runner is slower than users — Use field data via CrUX where possible; treat lab data as a regression detector, not absolute target

Validate and fix structured data (JSON-LD)

👤 Developers wanting rich results in SERPs ⏱ ~25 min intermediate

Когда использовать: Your pages aren't getting rich snippets despite having JSON-LD.

Поток
  1. Scope to structured-data rules
    Run seo-audit-skill --category=structured-data on these 5 URLs.✓ Скопировано
    → Per-URL list of schema errors and missing required fields
  2. Generate corrected JSON-LD
    For each error, produce the corrected JSON-LD snippet keyed to the page type.✓ Скопировано
    → Per-page snippets ready to paste

Итог: Schema.org-valid JSON-LD deployed; ready to re-check via Google Rich Results Test.

Подводные камни
  • Schema valid but Google still doesn't show rich results — Validity is necessary, not sufficient. Check eligibility guidelines for the specific rich result type.

Audit and set security headers

👤 Developers wanting baseline security + SEO signal ⏱ ~45 min intermediate

Когда использовать: securityheaders.com gave you an F and you want to understand why.

Поток
  1. Run security category
    Run seo-audit-skill --category=security on https://example.com.✓ Скопировано
    → CSP, HSTS, X-Frame-Options, Referrer-Policy status
  2. Generate headers config
    Produce the nginx and Cloudflare Worker configs to set the missing headers safely (report-only CSP first).✓ Скопировано
    → Copy-paste configs with report-only CSP

Итог: A secure header config rolled out behind report-only mode.

Подводные камни
  • Enforcing CSP breaks the site — Always start with Content-Security-Policy-Report-Only; watch reports for 1-2 weeks before enforcing
Сочетать с: claude-code-owasp-skill

Комбинации

Сочетайте с другими MCP — эффект x10

seo-audit-skill + trae-skill

TRAE scaffolds SEO basics, seo-audit verifies them

Scaffold SEO with TRAE, run seo-audit to verify, fix gaps.✓ Скопировано
seo-audit-skill + claude-code-owasp-skill

Security-header subset of SEO overlaps with OWASP checks

Run seo-audit security category, then OWASP skill for deeper security review.✓ Скопировано

Инструменты

Что предоставляет этот MCP

ИнструментВходные данныеКогда вызыватьСтоимость
full_audit url: str, runs?: int, render?: 'js'|'static' First audit on a site 0
category_audit url, category: 'cwv'|'security'|'structured-data'|... Focused checks or CI 0
diff_fix_generator report, top_n? After audit, to turn findings into PRs Claude tokens

Стоимость и лимиты

Во что обходится

Квота API
None. Runs locally via headless Chromium.
Токенов на вызов
Report interpretation uses 5-15k Claude tokens depending on site size
Деньги
Free
Совет
Use --category= to avoid running all 108 rules when you only need a subset.

Безопасность

Права, секреты, радиус поражения

Хранение учётных данных: No credentials
Исходящий трафик: Fetches the target URL and its assets. Does not send report to any third party.

Устранение неполадок

Частые ошибки и исправления

Puppeteer fails to launch

Install Chrome dependencies: apt-get install libgbm1 libnss3 (Linux) or run npx puppeteer browsers install chrome

Проверить: node -e 'require("puppeteer").launch().then(b=>b.close())'
Rules flag modern JS framework features as problems

Use --render=js so the audit runs post-hydration

All CWV rules report N/A

Lighthouse lab mode; on slow connections it times out. Increase --timeout.

Альтернативы

seo-audit-skill в сравнении

АльтернативаКогда использоватьКомпромисс
Google Lighthouse CLIYou only need the canonical CWV/perf subsetNo structured-data or SEO-specific rules
Screaming FrogYou need enterprise-grade crawling of large sitesPaid, desktop app, not LLM-integrated

Ещё

Ресурсы

📖 Читать официальный README на GitHub

🐙 Открытые задачи

🔍 Все 400+ MCP-серверов и Skills