Sequencing
What to build first with two weeks instead of six months, ordered by expected return, using the effort and impact values from the check registry rather than intuition.
4 min read · updated 2026-07-26· last reviewed 2026-07-26
Sort by impact divided by effort, then apply one hard constraint: the foundation group ships before anything else, regardless of what the arithmetic says.
The constraint exists because the foundation checks are prerequisites rather than improvements. Structured data on a site serving the same content on two hostnames is decoration on a broken frame: the markup is correct and the site is still telling a crawler it is two sites.
The rest of "Sequencing"
843 words covering 6 sections, with the implementation code for 5 checks. The table of contents below is the full outline, so you can see exactly what is behind this.
Already bought it? Read it in your library.
What this chapter covers
- The ordering rule
- The principle
- The implementation
- Two weeks
- The principle
- Why not the rest
- A quarter
- The principle
- Do not build a programmatic tier before you have the data
- The principle
- Instrument before optimising
- The principle
- The quarterly review
- The principle
Checks this chapter covers
Each one has a command you can run against your own site.
- →Ship the foundation group before anything elseseq-foundation-first
- →With two weeks, do foundation, metadata, one schema graph and robots. Nothing else.seq-two-week-plan
- →Do not build a programmatic tier before you have data worth templatingseq-content-before-programmatic
- →Instrument before optimising, so improvements are attributableseq-measure-before-optimise
- →A scheduled review of the two chapters that age fastestseq-quarterly-review