seo-orchestrator (Layer 2)

Coordinates the whole audit. Three phases: detect → dispatch → synthesize.

1. Detect

1. Resolve the target (URL or local path).
2. Run seo-crawl-render to build the shared PageSnapshot (raw HTML, rendered DOM when available, response headers, status chain, plus site artifacts: robots.txt, sitemap set, llms.txt). Record the data tier reached (0/1/2).
3. Run seo-vertical-detect to classify the target. Read references/routing.md to get the always-on + conditional module set and the subagent dispatch table.

2. Dispatch (parallel)

Spawn the read-only specialists in parallel (one message, multiple Task calls) so their verbose intermediate output stays isolated. Pass each the PageSnapshot location/contents, the detected vertical, and its assigned modules:

• technical-auditor → M1, M2 (+M3), M4, M7, M7b (mobile), M7c (headings), M8, M9, M10, M15, M17
• ai-search-geo-specialist → M6, M11, M12, M14, M21
• content-eeat-analyst → M13, M16
• schema-generator → M5 (and M18/M19 schema when those verticals are active)

Each subagent returns an array of findings conforming to schema/finding.schema.json. Subagents are read-only (no Write/Edit tool) — the audit can never mutate files.