What Pages Should a Business Website Have? Stop Copying Your Org Chart
The pages on your website should follow how a stranger decides, not how your company is organized - here's the list, and what to cut first.
Every website rebuild starts the same way. Someone opens a doc, lists every department, and gives each one a page. Sales gets a page. HR gets a careers page. The founder wants an About page with a nice headshot. Nobody in that meeting stops to ask whether a visitor actually needs any of it.
Your site ends up shaped like an org chart because nobody owns deletion
Adding a page is free internally - fill out a brief, hand it to whoever builds the site, done. Cutting a page costs political capital. The comms lead doesn't want the News section gone. The ops manager wants their team bio kept up. So the site keeps growing, one department request at a time, until it mirrors your internal structure instead of a stranger's train of thought.
A website isn't a shelf where every department gets a spot. It's the shortest distance between a stranger's doubt and their decision.
What pages should a business website have - start from the decision path, not the department list
Before you write a single page, map what a visitor needs to believe, in order, before they act. Almost every B2B or considered-purchase buyer moves through the same four questions: do you understand my problem, can you actually solve it, can I trust you with it, and what do I do right now. Every page on your site should answer one of these. If it doesn't, it's not a page - it's clutter.
- Do you understand my problem? - your homepage, in one sentence, without a company summary
- Can you solve it? - a page walking through your method or process, step by step
- Can I trust you? - proof, and proof doesn't have to mean a client logo wall
- What do I do now? - one page, one action, no ambiguity about the next step
Your homepage has exactly one job
Most homepages try to do five things at once: introduce the company, list services, state values, show a hero image, and squeeze in a mission statement. A visitor gives you about five seconds before deciding whether to keep reading. In that window they need to understand what problem you solve - not who you are. Save the who-you-are for the About page, if you decide to keep one at all.
Proof doesn't require a client logo wall
If you're early-stage and don't have marquee clients to display, don't fake it. Walk visitors through exactly how you work - your process, your framework, the questions you ask before you take on a project. A clear, specific method reads as more credible than three logos of companies nobody's heard of. Confidence in how you work is proof, even without a name attached to it.
The same principle scales differently by business
A five-person consultancy might answer all four questions on one scrolling homepage - no separate pages needed. A company selling a six-figure enterprise tool may need a dedicated page for each stage, because a buyer who isn't deciding alone needs more to forward internally. The number of pages should track how much explanation the buyer needs, not how many teams you have to represent.
The pages you cut matter more than the ones you add
When people ask us what pages a business website should have, the honest answer usually starts with what to remove. Three pages almost never earn their place: a generic About Us page that repeats the homepage in vaguer language, a News or Press section that turns into a graveyard of three-year-old announcements, and a team page with a headshot and one line for every employee. None of these move a visitor closer to a decision. They exist because someone internally wanted them, not because a buyer needed them.
If a page doesn't answer one of the four questions a stranger is silently asking, it doesn't belong on your website - it belongs in an internal deck nobody outside your company will ever read.
Frequently asked questions
What pages should a business website have?
At minimum: a homepage that states the problem you solve in one sentence, a page explaining your method or process, some form of credible proof, and a single clear next step like a contact or booking page. Everything else is optional and should only exist if it helps a visitor decide faster. Extra department pages, generic About sections, and team bios rarely earn their place unless they answer a real question a buyer is asking.
Does a business website need an About Us page?
Not always, and if you keep one, it needs a real job. Most About pages repeat the homepage in vaguer language and add nothing to a visitor's decision. If you keep it, use it to answer a specific trust question - why you started this, who's actually running it - instead of a generic mission statement nobody reads.
How many pages should a small business website have?
There's no fixed number - it depends on how much explanation your buyer needs before deciding, not on how many departments your company has. A simple service business might answer everything on one scrolling homepage. A business with a longer, more considered buying process may need four or five focused pages. Count decision stages, not internal teams.
Do I need a case studies page if I don't have client logos yet?
No - a clear explanation of your method or process can do the same job as a case study wall. Buyers trust specificity: how you work, what questions you ask, what your framework looks like. A detailed process page often reads as more credible than three logos nobody recognizes, especially early on.