SEO ORCHESTRATOR
ONE ENTRY, RIGHT ROUTE

The orchestrator is a router, not a single all-purpose audit. The documented /seo [command] [url] surface maps a user goal to one or more of 24 subskills and 18 specialist agents, then consolidates the available evidence into a decision-ready response.

Routing starts with the named command and the context already available. A focused page task can stay within one specialist. A broader site task can coordinate several specialists, but only when the target and evidence boundary justify that scope. Missing access is reported as a limitation, not filled with plausible data.

Primary product references: the pinned orchestrator contract and the reviewed current source were byte-identical when checked on 2026-08-27.

The command surface spans diagnosis, implementation guidance, research, local search, strategy, monitoring, and optional provider extensions. These examples are entry points, not evidence that every provider is configured.

Open the skills directory for the full command map and route-specific readiness notes.

1. Name the narrowest useful command

/seo audit https://your-site.com

Use a focused route when you already know the job. If the request is ambiguous, state the decision you need and provide the target domain, market, language, page type, or business context that changes the answer.

2. Review readiness before provider work

Confirm whether public pages are reachable, local files are available, and any optional provider credentials are configured. Ask for a cost estimate before paid DataForSEO, Ahrefs, or another provider request.

3. Review outputs before action

Check cited evidence and limitations. Treat recommendations as a reviewable plan, then approve only the edits, publication, spending, or account operations you intend.

The orchestrator reduces command-selection friction. It does not erase the differences between a static page review, live provider data, local file output, and a production change.

• Unsupported or incomplete command: the router needs a valid command and the route's required input.
• Blocked retrieval: authentication, paywalls, robots controls, 403 responses, or client rendering can reduce page evidence.
• Missing provider access: paid data remains unavailable without credentials and approval.
• Unknown business facts: addresses, offers, service areas, authorship, and other first-party facts require confirmation.
• Scope mismatch: a broad request can produce noise when a focused page, schema, local, or technical route would answer the decision.

When evidence is missing, the correct result is a smaller answer with explicit unknowns, not invented completeness.