seo-audit · diff

git:20260711.2d30535 to git:20260922.a4bd47b

3 added, 3 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
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
+ 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.