seo-audit · git:20260711.2d30535 · 2026-07-11 · sha256 c866c60bd7802b08

seo-audit git:20260711.2d30535A

Immutable. This exact content never changes and is served at /api/v1/blob/c866c60bd7802b08.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_fvqixbiqis6re4wy/c866c60bd7802b0866d6c37be3ccbae0986c1f4d525d8f6cfbb3a53c18253e60.json

Then /plugin install seo-audit@markdownregistry-fvqixbiqis6re4wy in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: seo-audit
description: >-
  Run an SEO audit of a site, section, or single page. Trigger on "проверь
  SEO", "seo audit", "почему нас не видно в гугле", "оптимизируй страницу под
  поиск", or after shipping new public pages. Delegates the deep pass to the
  seo-strategist subagent and turns the result into applied fixes.
---

# SEO audit

## Steps

1. **Scope**: one page, a section (e.g. /race/*), or the whole site. Identify
   the repo templates behind the target pages.
2. **Snapshot what a bot sees**: `curl -A "Googlebot" <url>` and check the
   returned HTML for title/meta/OG/schema BEFORE JS. For an SPA, this is
   where server-side meta injection either works or doesn't.
3. **Delegate**: spawn the `seo-strategist` subagent with the scope, the
   fetched evidence, and repo paths. For big scopes spawn one per section in
   parallel.
4. **Apply**: implement the top fixes it returns (meta/OG/schema/sitemap/
   robots changes are code; content gaps become a page list with target
   queries). Anything touching prediction pages must respect the access
   gating policy (free teaser visible to bots, paid content locked).
5. **Verify**: re-curl the fixed pages, validate schema (Google Rich Results
   test via WebFetch), confirm sitemap entries, request re-indexing steps.
6. Track: keep the running SEO roadmap in the project's docs so audits build
   on each other instead of restarting.