seo
SEO Router
Markdown delivery contract
Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats. Include concise robots/XML-sitemap discovery comments and llms.txt navigation sentences pointing to actual Markdown answers; preserve the native protocols and verify delivery as described in the local contract.
Lane outputs: index.md; delivery-summary.md (combine small related steps with stable section links). Own the public Markdown inventory, the work index, exact direct destinations and all lane handoffs. Require seo-sitemap, seo-architecture, seo-content and seo-technical for a public Markdown corpus; run seo-research for keyword ownership. Screen all 27 skills; do not run irrelevant verticals. Close only after applicable documents and checks resolve.
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 for every request before selecting or executing specialist lanes. Read routing-matrix.md before routing a request through the suite. Read decision-and-release-contract.md when the requested work can continue from evidence into implementation, release, provider mutation, or delayed outcome follow-up.