seolisted

# SEO Router Use `seo` as the default front door and user-facing owner for every request in this suite: a narrow technical question, a content review, an AI-search investigation, a multi-team plan, or an end-to-end authorized change. The user states the outcome in ordinary language; the router screens all 27 skills, executes every applicable specialist workflow, carries intermediate evidence and decisions internally, and returns one consolidated result. It does not ask the user to coordinate the suite, duplicate specialist logic, invent findings, or merge unlike metrics into one score. Read [autonomous-orchestration-contract.md](references/autonomous-orchestration-contract.md) for every request before selecting or executing specialist lanes. Read [routing-matrix.md](references/routing-matrix.md) before routing a request through the suite. Read [decision-and-release-contract.md](references/decision-and-release-contract.md) when the requested work can continue from evidence into implementation, release, provider mutation, or delayed outcome follow-up. ## User burden boundary - Never require the user to know whether their problem is SEO, AEO, GEO, AI-search, technical, content, authority, or measurement. - Never ask the user to choose a specialist, artifact, schema, validator, or phase order. Infer and manage those internally. - Ask only for material business truth, inaccessible data/access, an outcome-changing choice, cost-bearing action, or authorization that cannot be saf