seo-audit · git:20260922.a4bd47b · 2026-09-22 · sha256 1f4a6d15ebf187d7

seo-audit git:20260922.a4bd47bA

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

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_fvqixbiqis6re4wy/1f4a6d15ebf187d74832e1c6dbdb355f7b9fb4af59377efe00ca0a3d65e5c87d.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 "check
  SEO", "seo audit", "why are we not showing up on Google", "optimize this
  page for search", 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.