Skip to content

seo-audit

Use when running a full SEO optimization pipeline — technical audit, content analysis, keyword research, on-page optimization, structured data, AI citation visibility, performance deep dives, or schema validation. Also use when a site needs a comprehensive SEO review with an approval-gated action plan before execution.

ModelSource
sonnetpack: seo
Full Reference

Full SEO optimization pipeline — 11 phases, approval gate at phase 6. Reads every relevant file, pulls analytics data, audits technical health, checks AI citation visibility, evaluates content and schema, and produces a prioritized action plan. No execution happens without user sign-off.

ItemValue
Phases8 (including 2.5, 4.5, 5.5 sub-phases)
Approval gatePhase 6 — hard stop, no execution without sign-off
Delegated skillsai-visibility, schema-markup, web-performance, lighthouse-api, google-search-console-api
OutputPrioritized action plan + optional site-report HTML deliverable

Usage: Read the reference file matching your current task from the index above. Each file is self-contained with steps and inline gotchas.

I want to…File
Scan the codebase — build the page inventoryreference/phase1-codebase-inventory.md
Pull GSC data, CWV baselines, verify trackingreference/phase2-analytics-data.md
Run the technical SEO checklist — tags, schema, crawlreference/phase3-technical-audit.md
Run Lighthouse, escalate CWV failuresreference/phase4-performance.md
Analyze content quality, keyword gaps, schema auditreference/phase5-content-keywords.md
Compile the report and present the approval gatereference/phase6-report-approval.md
Execute approved items and verify afterreference/phase7-8-execution-verification.md
PhaseFocusOutput
1Codebase scanPage inventory table
2Analytics pullGSC + CWV data
2.5AI citation check (invoke ai-visibility)LLM visibility findings
3Technical auditIssue checklist
4LighthouseScore table by page
4.5Performance deep dive (invoke web-performance)Diagnosis + fix plan
5Content + keywordsGap analysis
5.5Structured data (invoke schema-markup)JSON-LD audit
6ReportApproval gate — STOP
7ExecutionAtomic fixes, commits
8VerificationRe-run failing checks
MistakeCorrect approach
Skipping the approval gateAlways stop at Phase 6, always
Optimizing for keywords with no GSC dataPull real data first — opinions are not rankings
Hardcoding aggregate ratingsPull from actual review data or omit
Hiding content on mobileEverything indexable must be visible on mobile
Title tags > 60 charsGoogle truncates — keep tight
Duplicate meta descriptionsEvery page needs a unique description
Skipping schema validationAlways validate — invalid schema does nothing
Committing all changes at onceAtomic commits — one fix per commit
Treating lab CWV as truthAlways compare against CrUX field data
Ignoring AI citation gapLLM visibility is a real traffic channel now
Inline schema auditingDelegate to schema-markup — it has the full spec
  • google-search-console-api — GSC data pull
  • lighthouse-api — performance audits
  • crux-api — field data comparison
  • ai-visibility — LLM citation check (Phase 2.5)
  • web-performance — CWV diagnosis + fix plan (Phase 4.5)
  • schema-markup — JSON-LD audit (Phase 5.5)
  • server-side-tracking — analytics foundation verification
  • local-seo-audit — location-specific SEO
  • content-strategy — editorial planning from content gaps
  • review-management — review volume and response strategy
  • cro-audit — high-traffic low-conversion pages
  • site-report — HTML deliverable generation

┏━ 🔍 seo-audit ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Full SEO optimization pipeline — 11 phases, ┃ ┃ approval-gated action plan before execution ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛