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.
👤 Performance engineers wiring SEO to CI⏱ ~20 minintermediate
When to use: You want a CI gate that blocks regressions in LCP/CLS/INP.
Flow
Scope to CWV category
Run seo-audit-skill --category=cwv on our staging URL.✓ Copied
→ Just the CWV rules with values
Wrap in CI
Generate a GitHub Actions step that runs this and fails if LCP > 2.5s.✓ Copied
→ YAML snippet with threshold logic
Outcome: A CI gate that catches perf regressions before prod.
Pitfalls
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 minintermediate
When to use: Your pages aren't getting rich snippets despite having JSON-LD.
Flow
Scope to structured-data rules
Run seo-audit-skill --category=structured-data on these 5 URLs.✓ Copied
→ Per-URL list of schema errors and missing required fields
Generate corrected JSON-LD
For each error, produce the corrected JSON-LD snippet keyed to the page type.✓ Copied
→ Per-page snippets ready to paste
Outcome: Schema.org-valid JSON-LD deployed; ready to re-check via Google Rich Results Test.
Pitfalls
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 minintermediate
When to use: securityheaders.com gave you an F and you want to understand why.
Flow
Run security category
Run seo-audit-skill --category=security on https://example.com.✓ Copied
→ CSP, HSTS, X-Frame-Options, Referrer-Policy status
Generate headers config
Produce the nginx and Cloudflare Worker configs to set the missing headers safely (report-only CSP first).✓ Copied
→ Copy-paste configs with report-only CSP
Outcome: A secure header config rolled out behind report-only mode.
Pitfalls
Enforcing CSP breaks the site — Always start with Content-Security-Policy-Report-Only; watch reports for 1-2 weeks before enforcing