how many pages does a website need? fewer than you think, more than one

web · Sep 29, 2026 · 4 min read

when people plan a website, they count pages the way they count rooms: one for each department, one for each service, one because "the other site has one". then the site launches with twelve pages, four of them thin, and the thin ones quietly work against the whole thing.

here is the honest math instead.

every page has a rent to pay

a page is not free once it exists. it costs in three currencies, forever:

  • writing. a page with nothing real to say is worse than no page — it reads as filler, and filler reads as a business with nothing to say.
  • maintenance. every page is another surface that can go stale. prices, hours, staff, offers. a stale page is not neutral; it argues against you.
  • findability. a thin page competes badly in search, and a bad page inside your site pulls your site's overall impression down with it.

so the question is never "how many pages should i have". it is "which pages can pay this rent, every month, with real content". a five-page site where every page is sharp beats a fifteen-page site where half the rooms are empty.

the baseline that works for most service businesses

  • home — what you do, for whom, and the one action you want taken. this page does most of the work. it deserves most of the effort.
  • services or work — what you actually offer, with proof: photos, cases, results, numbers. not a list of adjectives.
  • about — the person or team, told so a stranger can decide whether to trust you. the honest version, not the mission-statement version.
  • contact — unmissable, working, and answered. a contact form nobody reads is a promise the business breaks.

that is four. a blog can be the fifth, and it is the one page that can genuinely grow the business — but only if it will actually be fed. an abandoned blog is a visible heartbeat monitor, flatlined. if you will not write, do not launch a blog page. a site without a blog looks fine; a blog with three posts from two years ago looks abandoned.

when one page is the right number

one page is enough when the job is small and clear: a freelancer, a single service, a local craft business. one page that says what, shows proof, prices a band, contact. done. i have shipped these and they outperform bigger sites, because everything a visitor needs is on the first screen instead of behind five clicks.

the tell that you have outgrown one page is repetition: when you keep cramming different audiences into the same section, each audience getting half an answer. split when the content genuinely splits, not before.

when more pages win, on purpose

the opposite mistake also exists: the business with eight real services crammed onto one page, where a stranger looking for one of them finds all eight and none. search engines match pages to searches, and one page answers one search well. if people search differently for what you do — "wedding photographer parma" and "product photographer parma" are different searches with different intent — then the honest structure is a page per real audience, each written for that audience, not clones with the city name swapped.

the test for any page, new or existing: what would a stranger type into google to arrive exactly here? if you cannot answer, the page does not know what it is for, and neither will the search engine. if two pages have the same answer, merge them.

the rule underneath the math

pages are not inventory. they are doors. each one either opens onto something worth walking into, or it is a door painted on a wall — and a wall door wastes the visitor's trust, which is the only budget that matters.

so: start at four. add a page when a real, different audience asks a real, different question that deserves a real answer. subtract when a page stops paying rent. the number that survives this discipline is, by definition, the right one.

if the structure conversation is where your site keeps stalling, that is literally the work:

small and true beats big and vague. every time.