Why adding more pages rarely fixes a website
When a site feels broken, the instinct is to add. More pages, more sections, more proof. Almost always the wrong move.
A pattern we see constantly: a founder looks at their site, feels something is off, and decides the answer is more. A new ‘How It Works’ page. A separate page per service. A blog. Six case studies instead of three. Everyone agrees it’ll help. Three months later the site feels less clear, not more.
More doesn’t explain. More competes.
Every page you add has to earn attention against every other page you added. Visitors don’t read a site left to right. They land somewhere, skim, and decide in seconds whether the thing is for them. Another page isn’t another chance to convince them — it’s another place for them to get lost.
When a page is underperforming, adding a sibling page almost never fixes it. What fixes it is rewriting the one page so it makes a clearer argument.
“The page that explains too much is usually covering for the page that didn’t explain enough.”
Why founders default to expansion
Adding feels productive. It produces visible output — new URLs, new content, new things to share. Editing feels like undoing. You end the day with fewer pages than you started, which reads as loss even when it’s exactly the right move.
There’s also a cultural bias at work. Internally, every team member wants their area represented. Sales wants a dedicated page. Marketing wants a resource hub. Engineering wants a technical overview. Each request is reasonable. Collectively they turn the site into a committee.
The subtraction test
Before adding anything, try this: what if the new content had to replace something existing? Not sit beside it — replace it. Almost every time, the act of picking what to remove reveals that the real problem wasn’t missing content. It was unclear priority.
The most confident sites we build end up with fewer pages than the client thought they needed. Sometimes a third fewer. The homepage gets tighter. The work section gets sharper. The about page becomes one paragraph instead of five. None of it is lost — it’s just no longer competing with itself.
When adding is right
There are genuine cases for expansion. A case study library that’s growing. A resource section with real, original thinking. A documentation site where depth is the product. The common thread: each new page has a distinct job, not an overlapping one. If a new page could reasonably live inside an existing page, it probably should.
If the site feels off, resist the urge to build outward. Go inward first. Rewrite the core. If, after that, you genuinely need more surface — you’ll know exactly what it should be.