Why 150 planned pages beat 1,000 blog posts
An argument about structure, not effort. Two competent teams, the same hours, different outcomes.
- Same writing hours. The difference is whether a map existed first.
- Volume publishing produces cannibalisation and invisible gaps.
- Assistants expand one question into several, which rewards coverage.
- Planning delays the first publication, and that is a real cost.
The two approaches
Volume publishing produces posts on a calendar and hopes coverage emerges, which is part of why the question of whether SEO is finished keeps getting asked by people who only ever tried the calendar. Planned coverage decides the full set of pages a subject requires, then builds them.
Same writing hours. The difference is whether the map existed before the writing.
Where volume loses
Cannibalisation. Twelve posts circling one question compete with each other, and two mediocre pages on one topic lose to one good page.
Gaps nobody sees. A calendar cannot show you what is missing. A map can, because absence is visible against a plan.
Decay. A post dated three years ago reads as stale whether or not it is wrong. A page organised around a durable question can be maintained.
Dead weight. Sites accumulate posts nobody reads or links to, and they still get crawled.
Why it matters more with AI in the mix
Assistants expand one question into several and retrieve against each. Coverage of the surrounding questions raises your chances of being retrieved at all.
That rewards a planned set and punishes a pile.
The honest counter
Planning has a cost and it delays the first publication. A business that needs something live this month is poorly served by three weeks of mapping.
The compromise we use is to map the spine, build it, then extend. Our own map is a spreadsheet of every page the site needs, including the ones we decided not to build and why.
“A calendar cannot show you what is missing. A map can, because absence is visible against a plan.”
