SEO Runbook

Site Architecture Plan

Design a website architecture around audience tasks, search intent, navigation, internal links, content gaps, and migration risk.

Try this Runbook

Goal

Create a practical site architecture that helps people and search engines find distinct, useful pages without duplication, orphaning, or unsupported migration work.

Success Criteria

  • Each proposed page has a unique audience job, search intent, and business purpose.
  • Navigation, hierarchy, and internal-link relationships are explicit.
  • Existing valuable URLs and migration risks are accounted for.
  • Duplicate, thin, and unsupported page ideas are identified.

Inputs

  • Business goals, audiences, products, and conversion paths
  • Current sitemap, navigation, URLs, and page performance
  • Search themes, customer questions, and journey evidence
  • Planned content, products, locations, or markets
  • Technical, CMS, localization, and compliance constraints
  • Known redirects, backlinks, and high-value landing pages

Constraints

  • Do not create a page for every keyword variation.
  • Do not recommend deleting, merging, or redirecting URLs without performance and ownership review.
  • Keep navigation based on user tasks and information relationships.
  • Label search-demand or crawl assumptions that lack evidence.

Instructions

  1. Group audience needs and search themes by distinct intent and business job.
  2. Inventory current pages and mark keep, improve, consolidate, redirect candidate, or investigate.
  3. Propose top-level sections and child pages with one purpose per page.
  4. Define primary navigation, breadcrumbs, contextual links, and hub relationships.
  5. Identify orphan risks, overlap, missing coverage, and crawl-depth concerns.
  6. Create a staged implementation and migration plan with validation gates.

Output

  • Architecture principles
  • Proposed sitemap with page purpose
  • Current-to-proposed URL decisions
  • Navigation and internal-link model
  • Content gaps and overlap
  • Migration stages, risks, and validation checklist

Quality Check

Confirm that every proposed page serves a distinct need, important pages are reachable through clear paths, and all destructive URL changes remain reviewable recommendations.

Stop Rules

Stop when current URLs or business priorities are unavailable for a redesign. Do not publish navigation changes, redirects, canonicals, or deletions without technical and content-owner approval.

From procedure to operation

Put this Runbook into a controlled workflow.

Learn how an SOP becomes a Runbook, choosemeaningful review points, thencompare plans and capacity.

Ready to handoff busywork?

Start my free trial