Most Small Business Sites Need Fewer Pages — and Clearer Jobs

Most small business websites need fewer pages than they are sold — usually a tight set of 5–9 URLs, each with one job a visitor can finish. Page count is the wrong question. Job clarity is the right one: homepage decides, services prove, contact converts, and everything else either earns its keep or becomes a distraction. This spoke sits under Websites That Feel Like Films.

The short answer

• Start with jobs, not a “recommended sitemap” from a theme demo.
• Non-negotiable for most local/service businesses: Home, Services (or 2–4 service pages), About/Proof, Contact.
• A service earns its own page when search intent, proof, and a distinct offer all exist — not because the brochure had a bullet.
• Bloated sitemaps dilute attention, slow launches, and leave half the pages half-written.
• Cutting pages is not cutting trust when the remaining pages carry real proof.

How many pages does a small business website actually need?

Enough to complete the path from “is this for me?” to “how do I hire you?” — and no more until a page has a job you can name in one sentence.

Business type	Typical page count that works	What usually gets cut
Local trades (HVAC, plumbing, cleaning)	6–10	Generic “Our Process,” duplicate service blurbs, filler blog
Professional services (design, consulting)	5–8	Separate “Values,” “Team” snowflakes, unused case study shells
Product / light ecom brand	6–12	Extra “Collections” with three SKUs, orphan campaign pages
One-location retail / studio	4–7	FAQ-as-page when a section would do, redundant location pages

If you cannot say what a visitor should do on a URL, it is not a page yet. It is a wish.

Which pages are non-negotiable?

For most small businesses selling a service, the floor looks like this:

1. Home — who you are for, what you do, primary CTA (call or form).
2. Services index or 2–4 service pages — scoped offers with proof, not a menu dump.
3. About / proof — people, credentials, photos of real work (section or page).
4. Contact — phone, form, service area, hours, what happens next.

Everything else is earned. Gallery, FAQ, financing, careers, blog, service-area pages — useful when maintained; dead weight when empty.

The trades playbook in Trades SMB Website Playbook goes deeper on phone-first paths. This post is about how many URLs you actually need before that craft matters.

The one-job-per-page test

Before you approve a sitemap, force every proposed page through this sentence:

“A visitor on this page is trying to _____, and success looks like _____.”

Examples that pass:

Page	Job	Success
Home	Decide if you are the right contractor	Tap Call or open Contact
AC Repair	Confirm you fix their problem in their area	Call or request quote
Contact	Hire you with minimal friction	Form submit or phone dial
Project / case study	Believe you have done this before	Click to Contact or related service

Examples that fail:

• “Our Culture” with no hiring CTA and no trust payoff for buyers
• “Resources” with three undated PDFs
• “Services” that lists twelve items with the same paragraph rewritten

If two pages share the same job, merge them. If a page has three jobs, split or cut until one remains.

When does a service deserve its own page?

Use this checklist. A service earns a URL when at least three boxes are true:

• People search for that service by name (or ask for it on the phone weekly)
• The offer, price band, timeline, or process is meaningfully different from sibling services
• You have proof unique to that service (photos, reviews mentioning it, certifications)
• You would run ads or GBP categories aimed specifically at it
• A single combined Services page would bury it below the fold for the people who need it

Pass example (HVAC-shaped): AC repair, furnace install, and maintenance plans often deserve separate pages because intent, seasonality, and proof differ. On AllCity HVAC-style builds, per-system pages work when each page has a job — not when every SKU from a manufacturer PDF becomes a URL.

Fail example: “Duct cleaning,” “duct sealing,” and “duct inspection” as three thin pages with identical stock photos. One “Duct services” page with clear subsections usually converts harder and stays maintainable.

Why bloated sitemaps hurt conversion

More pages feel like more professionalism. In practice they create:

Failure	What it costs
Half-written pages	Visitors bounce on thin content; you look unfinished
Split attention	Homepage CTAs compete with nav of twelve equals
Launch delay	Content becomes the critical path; site sits in limbo
SEO theater	Thin service-area clones that Google ignores or treats as doorway junk
Maintenance debt	Nobody updates the tenth page; stale hours and dead CTAs linger

A short site with sharp jobs beats a long site with soft ones. Craft belongs in composition and proof — see the pillar — not in inventing URLs to impress a competitor’s sitemap.

How to cut pages without cutting trust

Trust comes from specificity, not page count. Keep trust; cut redundancy.

1. Merge siblings — one Services page with strong sections beats five 150-word pages.
2. Demote to section — testimonials, FAQs, and financing often live better on Home or Contact than as lonely URLs.
3. Archive honestly — unpublished drafts do not need public routes “for later.”
4. Keep one deep proof — a real project story outperforms three vague “portfolio” tiles.
5. Protect the phone path — never cut Contact clarity to save a line in the nav.

Checklist before deleting a live URL:

• Nothing ranks that you care about (or you have a 301 plan)
• The job moves to a surviving page with equal or better prominence
• Nav and footer no longer promise the old page
• Forms and call tracking still make sense on the new path

Worked example: contractor sitemap before and after

Sold as “complete” (14 pages): Home, About, Team, History, AC Repair, Heating, Installation, Maintenance, Indoor Air, Commercial, Residential, Gallery, Blog, Contact, Careers, Financing.

Ship-ready (8 pages):

Page	Job
Home	Qualify + call
AC Repair	High-intent service
Heating & Install	High-intent service
Maintenance Plans	Retention / recurring
About	People + licenses + real trucks/jobs
Work / Gallery	Visual proof
Service Area	Where you actually go (one honest page)
Contact	Convert

Team and History fold into About. Financing becomes a Contact or Home section. Blog waits until someone will write monthly. Commercial stays off until you have commercial proof and a sales path.

That cut is not “less business.” It is less fiction.

Service-area pages — when they help and when they spam

One honest service-area page (cities you actually serve, response expectations, map or list) is usually enough for a single-location trades company.

Add city pages only when:

• You have unique proof or offers per city (crew based there, reviews naming the city, different permits)
• Someone will maintain unique copy — not spun paragraphs
• You are willing to link them from GBP and keep NAP consistent

If every city page is the same paragraph with the city name swapped, skip them. Thin location pages are a credibility tax, not an SEO strategy.

Is a one-page site enough?

Sometimes. A one-pager works when:

• One offer, one geography, one CTA
• Proof fits above and below the fold without a scavenger hunt
• You are early and would rather ship than architect

It fails when services compete for attention, when searchers need distinct landing pages, or when industry visitors need a scannable About separate from the pitch. Most growing small businesses outgrow the pure one-pager before they outgrow a 6–8 page site.

If you are on the fence, ship a short multi-page set. Expanding later is easier than untangling a scroll novel.

Do you need a blog?

Only if you will publish on a cadence someone owns. An empty Blog in the nav signals neglect. Alternatives that often win for SMBs:

• FAQ sections on service pages
• Seasonal notes on Home (filter change reminders, storm prep)
• Project write-ups as case studies when you finish real jobs

If content is part of your acquisition plan, treat posts as a collection with a job — answers people already ask on the phone — not as a page-count inflate. Pair structure decisions with CMS Choices Clients Will Actually Use so editors can maintain what you invent.

How page count affects quote price

Studios price systems and content load, not “$X per page” in a vacuum — but page count still moves the number because each URL needs design states, content, QA, and often CMS fields.

Sitemap choice	Budget effect
5–7 clear pages, content ready	Baseline sprint
12+ pages, thin or missing copy	Content and IA become the project
Many near-duplicate service pages	You pay twice: build + rewrite later
One-pager now, structured growth later	Cheaper launch if scope is honest

Ask for a quote against jobs, not against a competitor’s 20-link footer. If a proposal celebrates page volume, ask which pages share a job.

Decision list: build, merge, or wait

• Build — unique intent + unique proof + owned CTA
• Merge — same audience, same offer, same success metric
• Wait — no content owner, no photos, no reviews yet
• Kill — exists only because a template included it

Run that list in a one-hour IA session before design starts. It is cheaper than redesigning a junk drawer homepage after launch.

Failure mode: the brochure dump

A common failure: the owner hands over a 24-page PDF and asks for “a page for each section.” The site launches late, half the pages say the same thing, and the phone number is still in the footer in 11pt gray.

What to do instead:

1. Extract the three offers that make money.
2. Map one page (or one Home section) per offer.
3. Put credentials and people on About.
4. Put every conversion action on Contact and in the header.
5. Park the rest of the PDF as downloadable one-sheets if industry buyers need them — not as orphan URLs.

Bravery is shipping the short site that sells, not the long site that matches the binder.

FAQ

Do I need a blog?

No, not by default. Add a blog only when someone owns a publishing cadence and the posts answer real buyer questions. An empty Blog link hurts more than it helps.

Should every service get a page?

No. A service gets a page when intent, proof, and offer differ enough that a combined page would bury the buyer. Thin duplicate service pages waste budget and attention.

Do I need a testimonials page or a section?

Usually a section. Put the strongest quotes near the CTA on Home and service pages. A standalone testimonials page helps only when you have dozens of reviews worth browsing.

What about service-area pages?

One honest service-area page is enough for most single-location businesses. Add city pages only with unique proof and a maintainer — not spun copy for every ZIP code.

Is a one-page site enough?

It can be for a single offer and geography. Most growing service businesses do better with a short multi-page set so services and contact do not compete inside one endless scroll.

How does page count affect quote price?

More pages mean more content, design states, QA, and CMS work. Clear 5–9 page sites are usually cheaper and faster than bloated sitemaps with half-finished URLs.

CTA

Fewer pages. Clearer jobs. A site that answers the phone.

Explore /websites or book a Website sprint at /contact?intent=websites-sprint.