Most small businesses need fewer website pages than they think.
A useful starting structure is often:
- Home
- Services
- About
- Work / Reviews / Proof
- Contact
Then add pages only when the business or customer journey gives you a reason.
The goal is not to make the website look large.
The goal is to make it easy to understand.
A ten-page site full of repeated filler is not automatically better than a focused five-page site where every page has a clear purpose.
Gavin's take
I do not start with a target page count. "Five-page website" is convenient packaging, but it is not a strategy. I would rather work backwards from the questions a real customer needs answered and build the structure around those. Sometimes that produces four pages; sometimes one service genuinely deserves several. The number matters far less than whether each page has a job.
Start with customer questions
Instead of asking:
How many pages should I buy?
Ask:
What does somebody need to know before they contact or buy from me?
Usually, the customer needs to understand what the business does, whether it is relevant to them, where it operates, whether it can be trusted, what the actual services are, what things cost and how to take the next step.
Your site structure should answer those questions.
Before deciding how many pages to create, it can help to answer the more basic question of whether the business needs a website at all.
1. Home page
The homepage should quickly establish: what the business does, who it helps, where it operates if relevant, why the visitor should care, and what they should do next.
It should not be a vague corporate welcome message.
A headline like:
Welcome to ABC Solutions
wastes the most important piece of page real estate.
Something like:
Domestic and commercial electricians across County Longford
immediately gives the visitor useful information.
The homepage can also introduce: main services, proof, projects, testimonials, process, and contact.
Its job is to orient the visitor and move them deeper into the site.
2. Services page
If you have several services, give them a clear home.
For a simple business this can be one strong page.
For a larger service offering, important services may justify their own pages.
For example:
/services/
could introduce: boiler servicing, heating repairs, bathroom plumbing, and emergency callouts.
Then each important service can eventually have a dedicated page if there is enough real information and search/customer value.
Do not make a separate page for every tiny service variation simply to increase page count.
3. About page
People buy from businesses, not just service lists.
An About page can explain who runs the company, the experience that matters, why the business exists and what is different about how you work.
The page should build trust, not read like a corporate history book.
It does not need to read like a corporate history book.
For independent professionals and local businesses, personality can be a significant competitive advantage.
4. Work, projects, portfolio or case studies
If customers care about the quality of previous work, show it.
This can be especially valuable for: builders, designers, photographers, trades, consultants, landscapers, agencies, and professional services.
A project example is stronger when it explains: the problem, what you did, and what the outcome was.
Do not just dump 40 images into a gallery with no context if the context helps sell the work.
5. Contact page
Make it extremely obvious how to contact the business.
Include the channels that customers actually use: phone, email, contact form, WhatsApp, booking link, address, and map where relevant.
Avoid forms that ask for twelve pieces of information before somebody is allowed to enquire.
The Contact page should reduce friction, not create it.
Do I need a separate pricing page?
Sometimes.
If your pricing is simple and transparent, a dedicated Pricing page can be useful.
If the price depends on several variables, you can still provide starting prices, typical ranges, examples and a clear explanation of how quotes work.
I generally like transparent pricing because it helps qualify leads and removes uncertainty.
Built by Gavin, for example, publishes starting prices directly rather than forcing every visitor through a sales call.
Do I need an FAQ page?
Maybe.
If customers repeatedly ask the same meaningful questions, FAQs are useful.
Examples: areas covered, payment, turnaround, cancellations, guarantees, preparation, and booking.
But do not manufacture 40 questions purely because somebody told you FAQs are good for SEO.
Put questions where they genuinely help.
Sometimes an FAQ section belongs on the relevant service page rather than on a giant standalone page.
Do I need a blog?
No.
A generic blog is not a requirement.
What can be extremely valuable is a useful knowledge library.
That distinction matters.
A traditional small-business blog often turns into:
Happy Christmas from the team!
We are delighted to announce...
Five reasons quality matters...
Then nobody updates it for 18 months.
A knowledge library can instead answer evergreen customer and search questions: what a service costs, what is involved, what buyers should look for, how the process works and which option is right for them.
That content can: attract organic search, be surfaced by AI-assisted search, educate prospects, give you material to share socially, and link naturally back to services.
That is exactly why Built by Gavin is building this Guides section.
Do I need location pages?
If local search matters, some geographic pages can make sense.
But do not automatically create a page for every town in the country and change only the place name.
A location page should provide genuine value for that place or service area.
For many small businesses, county or major-area pages are a better starting point than hundreds of thin town pages.
Location pages can be useful, but only when they add genuine local value. See location pages for local SEO before creating a page for every town in a service area.
Do I need individual service pages?
Use a separate service page when: the service is commercially important, customers search for it independently, it needs substantial explanation, the audience differs, and there are specific examples/FAQs.
Keep services together when: they are very similar, each page would contain almost identical copy, and there is not enough useful information to justify separate URLs.
This is good for users and avoids creating low-value pages purely for search engines.
Do I need legal/privacy pages?
Depending on what the site does and what data it collects, you may need appropriate privacy/cookie/legal information.
This is not something to improvise from generic website copy.
The requirements depend on: jurisdiction, tracking, forms, cookies, e-commerce, and the business.
For Irish/EU businesses handling personal data, GDPR-related obligations matter.
Legal pages should reflect the actual website setup rather than being copied blindly from another site.
What I'd do
For a very simple new business, I would happily launch a focused one-page or small multi-page site if that is enough. But once different services, locations or customer questions need their own explanation, I would split them into proper pages. I would not create extra pages to make the project look bigger, and I would not force everything onto one page just to make it cheaper.
One-page website or multi-page website?
A one-page site can be excellent when: the offer is simple, there are only a few services, the main aim is enquiry, and the business is new.
A multi-page site becomes more useful when: services need depth, search traffic matters, there is substantial proof, audiences differ, and content is growing.
Do not force a multi-page architecture because it feels more "professional."
Gavin’s perspective
What Built by Gavin normally recommends
For many small businesses, I would begin with one of two structures.
Lean launch
In practice, that can mean Home, key service sections, About, proof, and Contact.
This can potentially live in one strong scrolling experience or a very compact site.
Established business site
This can involve Home, Services, relevant service pages, About, Work / Projects, Contact, selected useful Guides, and selected locality pages where justified.
That is normally enough structure to build a strong search and sales foundation without clutter.
If content is the part holding the project up, my guides to what a web designer needs from a client and getting a website built when you have no content explain how I would simplify that process.
Why I do not sell page count for its own sake
Page count is convenient for quoting.
But it is not a measure of quality.
An agency can sell:
"10-page website"
and fill several of those pages with generic copy.
Built by Gavin does not use generic off-the-shelf templates, and I do not think the goal should be to manufacture pages to make a proposal sound bigger.
Build the pages the business needs.
Then make those pages good.
The bottom line
Most small-business websites need a strong Home page, clear Services, an About or trust section, evidence of good work where relevant and an easy Contact route.
Pricing, FAQs, guides, individual service pages and location pages should then be added where they genuinely improve the customer journey or create useful search content — not because a package promised a particular number of pages.
The right website is not the one with the most pages. It is the one where every important page earns its place.
Want help working out the structure?
See my website options or tell me about the business.
I can map the site around what customers actually need rather than selling you an arbitrary page package.
---