A template sitemap arrives with twelve entries on it, the domain is already bought, and the launch date is three weeks out. The useful question at that point is not how many pages a company site should have. It is which pages this particular sale requires, and what has to be true on each one before someone can act on it.
Working backwards from a page count gives you pages nobody maintains.
Let the purchase path set the floor, not the template
Four inputs decide the minimum: how a customer decides, the size of a typical deal, where trust has to come from, and whether the buying happens in one session or over several weeks.
| Business shape | Pages that must exist at launch | Reasonable to add later |
|---|---|---|
| Local service, one offer, phone-first | Home, Contact | Separate service page, gallery |
| Quoted B2B, a few distinct offers | Home, one page per offer, About, Contact, legal | Process, compliance, case pages |
| Self-serve product | Home, product and pricing, docs or FAQ, Contact, legal | Comparison pages, changelog |
| Long cycle, high value | Home, offer pages, About, process, Contact, legal | Case studies, security page, team |
Legal means whatever your jurisdiction requires — privacy notice, terms, and a company imprint where one is mandated. Those are not marketing pages and they are not optional.
The table is a starting position you argue with, not a rule. If a page sits in the "later" column and nobody can name the sentence that would go on it, it does not go on the list.
What has to be on each page before it goes live
| Page | Its one job | Must contain before launch |
|---|---|---|
| Home | Say what this is, for whom, where, and what to do next | One sentence naming the offer and the customer; the primary action visible without scrolling; one concrete proof point; a link to contact |
| Offer page | Answer "can they do my version of this" | Who it is for, what is included, what is not, turnaround, what the buyer has to supply, next step |
| About | Give a reason to trust the people | Who runs it, where they operate, what they do not do, how to verify the claims |
| Contact | Remove the last excuse | A form that works, an email address, a phone number someone answers, hours, a response time you can keep |
| Legal | Keep you out of trouble | Privacy notice, terms, required registrations |
| Thank-you and 404 | Catch people at the edges | Confirmation of what happens next; links back to the main offers |
The first screen is not a slogan slot
Many home pages open with a positioning line and a stock photo. A visitor arriving from a search result needs three facts before anything else: what you sell, who it is for, and what the next step costs them in effort. Put those in the first paragraph, as plain text, in the words buyers use when they describe the problem.
One primary action. Two equally weighted buttons — "Contact us" next to "Download brochure" — split the decision and usually reduce both.
If geography matters, say where you serve in the first screen, not in the footer. If you work remotely and location does not matter, say that too, because a visitor who cannot tell will assume you are local to someone else.
When one offer deserves its own page
The default is one page per offer only if these hold:
- A different buyer, or genuinely different questions from the same buyer.
- Different proof is needed — a certificate, a lead time, a spec sheet the others do not have.
- Enough to say to fill a page without padding. A screen and a half of real content is a fair bar.
- Someone will maintain it.
- People search for it under a different phrase than the parent offer.
Two or more failing means one page with anchored sections. Splitting because "more pages is better for SEO" produces thin pages that compete with each other for the same query, and they usually cannibalise rather than help. If you split later, use a URL that survives a redesign: /services/name, not /our-services-2026.
Filling the trust gap with no testimonials, cases or photos
Real options that require inventing nothing:
- Publish the process step by step, including what you need from the customer and how long each step usually takes.
- Say what you do not do. A page that excludes some work reads as more credible than one claiming everything.
- Show real work with the client's written permission, even if it is one photo and a paragraph.
- Give prices or ranges where the business allows it. "Contact us for pricing" costs you the visitors who only wanted a number.
- Name the person responsible and how to reach them.
- Link to things a reader can check independently — registration, certification, address, a partner's own site.
What you should never do is write your own testimonial, use a stock face captioned as a customer, or publish a case with figures you cannot back up. It reads fine until a buyer asks one question about it.
The pre-publish pass, page by page
- The title contains the offer, in the buyer's words.
- The first paragraph names who the page is for.
- Exactly one primary action, repeated at the end.
- No placeholder text, no "coming soon", no dead items in the menu.
- The form was submitted end to end by a human and the confirmation email arrived.
- Phone numbers are tappable; addresses are text, not baked into an image.
- The page loads on a phone over a slow connection without the layout jumping.
- There is a link to it from at least one other page.
Site-wide: a sitemap, a robots file that blocks nothing you need indexed, and analytics that record which page a form was submitted from — not only that a form was submitted.
Leaving room for page seven
Navigation that is a flat list of every page becomes a redesign the moment you add two. Group by what the buyer is trying to do and keep the top level short.
When you merge, split or rename after launch, redirect the old URL and keep the redirect. Internal links inside other pages are the usual thing that gets missed — the redirect works for search engines and for readers, but paragraphs that reference the old page still point at the old URL.
Deciding after launch on something other than taste
Give it a month, then read entrance data per page: which pages people land on, which pages nobody enters, which pages earn internal clicks, and where form submissions start and stop.
A page with no entrances, no internal links and no form activity is a candidate to merge into a page that does have traffic, not to delete. A page where two different questions keep showing up in the same visit is a candidate to split. New pages should come from a question you have seen more than once, not from a keyword tool's estimate.
Set a review date when you launch. Otherwise the next decision about the site gets made by whoever is annoyed enough to raise it, and by then the fix is a redesign.
Top comments (0)