using-semantic-seo-geeklisted

# Route Semantic SEO Work ## Scope Route work; do not replace specialist judgment. Use this skill to: - identify the user's primary deliverable; - select the minimum specialist set that covers it; - order dependent work and define handoffs; - surface missing inputs that materially change the route. Do not use this router to perform a specialist audit, strategy, rewrite, or implementation. ## Explicit-request rule Honor every explicitly named specialist. Never replace, suppress, or reinterpret an explicit specialist request because another route seems preferable. If the requested specialist appears mismatched, use it and state the concern; add a supporting handoff only when useful. If the user names several specialists, retain all of them and follow the user's order unless a dependency makes that impossible. ## Evidence labels Apply these labels whenever the routing decision depends on facts: - **Observed** — directly verified in a supplied site, file, report, or dataset. - **Sourced** — supported by a cited current primary source. - **Inferred** — reasoned from Observed or Sourced evidence; state the reasoning. - **Unknown** — not verified; state what evidence would resolve it. Do not present an Inferred or Unknown claim as Observed. ## Routing map - Crawlability, indexability, rendering, canonicals, sitemaps, redirects, or structured-data delivery: `technical-seo`. - Site hierarchy, topic coverage, page relationships, URLs, or internal-link planning: `topical