Plan SEO Before You Build: An Architecture-First Checklist

Most SEO work is remedial — fixing a site that was built without search in mind. It doesn’t have to be. The highest-ROI SEO happens before the build, when changing the plan costs nothing. Here’s the checklist we run before a single page is built.

1. Map every page to one primary intent

For each planned page, write down the single query it should win and the intent behind it (informational, commercial, transactional, navigational). If two pages map to the same query, you’ve found cannibalization before it exists — collapse them now.

One page, one job. If you can’t name the query a page targets, it probably shouldn’t be its own page.

2. Design the URL structure to mirror the hierarchy

URLs should read like a sitemap: short, lowercase, hyphenated, and nested to reflect real hierarchy (/services/ac-repair, not /page?id=42). Decide this once, up front — changing URLs after launch means redirects, lost equity, and risk.

Internal links are how ranking strength flows through a site, and they’re the thing dev teams most often forget. Before building, decide:

  • Which pages are your priority “money” pages.
  • Which supporting pages will link to them, with what anchor text.
  • How the primary navigation and footer reinforce the hierarchy.

A money page with no internal links pointing at it is a page you’ve hidden from Google.

4. Spec the on-page essentials into the template

Bake these into the components so they can’t be forgotten:

  • One <h1> per page, driven by the page’s primary intent.
  • Editable <title> and meta description fields (not auto-generated from the H1).
  • A clean heading outline (h2/h3 for real sections, not styling).
  • Image alt fields that are required, not optional.
  • JSON-LD structured data emitted from the template (Organization, BreadcrumbList, and page-type schema).

5. Plan for proof

Decide before launch how you’ll measure success: connect Google Search Console on day one so you start banking ranking data immediately. You can’t show a client what improved if you never captured the baseline.

Why front-loading wins

Every item above is nearly free before the build and expensive after it. An architecture-first approach turns SEO from a cleanup project into a property of the site. Planning a large build across a roster of clients is exactly what RankRight is built to make routine — map the intent, catch the overlaps, and hand developers a spec that’s right the first time.