Why 150 planned pages beat 1,000 blog posts
An argument about structure, not effort. Two competent teams, the same hours, different outcomes.
Short answer: this is an argument about structure, not effort. A planned set decides the full set of pages a subject requires and then builds them, while volume publishing produces posts on a calendar and hopes coverage emerges. Both approaches spend the same writing hours, and only one of them can show you what is missing.
- 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.
What is the difference between volume publishing and planned coverage?
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.
| Approach | How the pages get chosen | What it can tell you about gaps |
|---|---|---|
| Volume publishing | Produces posts on a calendar and hopes coverage emerges. | A calendar cannot show you what is missing. |
| Planned coverage | Decides the full set of pages a subject requires, then builds them. | A map can, because absence is visible against a plan. |
What we read from that, and this part is our judgement rather than anything an outside source states: the choosing is the whole difference, and a team that never made the map has no way to audit its own coverage.
Same writing hours. The difference is whether the map existed before the writing.
Where does volume publishing lose?
Volume publishing loses in four places, and none of them is a writing problem. Posts written to a calendar cannibalise one another, leave gaps the calendar itself cannot reveal, decay against the date printed on them, and pile up as dead weight. Each one is structural, so more posts make each one worse.
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 does this matter more with AI assistants 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. A planned set covers those surrounding questions on purpose, where a pile of posts covers whichever of them the calendar happened to land on.
That rewards a planned set and punishes a pile.
What is the honest case against planning first?
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 cost lands in full before any of the benefit arrives, which is the part most arguments for planning leave out.
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.”
The protocol behind every check we run is published before we run it: read the full method.
Rankings are never guaranteed. Anything we could not trace to a primary source is absent from this page, not estimated. The audit runs the same six layers described on the pricing page, and Share of Answer is scored quarterly.
Youssef runs visibility work for established local businesses: Google Maps, organic search and AI answers, measured quarterly against a published protocol. Where a number cannot be checked, it does not go in the report.
More about Youssef