What pages should a small business website have? A practical checklist.

A small-business website does not need a fixed number of pages. It needs enough pages to explain the business, separate genuinely different customer needs, provide proof and make the next action easy — without creating thin URLs simply to make the site look bigger.

Start with page purpose, not a fixed page count.

Lists of “the 10 pages every website needs” can be useful prompts, but they are not architecture. A five-person consultancy, restaurant, dental clinic, auto shop and online store have different customer journeys.

The better question is: what information does a customer need before taking the next step, and which topics are important enough to deserve their own URL?

Google’s people-first content guidance encourages sites to have a clear purpose and content that helps visitors achieve their goals. That principle fits website architecture well: every important page should help somebody do something or understand something.

Reference: Google: Creating Helpful, Reliable, People-First Content ↗

1. Core identity pages.

Home

The home page should explain what the business does, who it serves, why it is credible and where visitors should go next. It is not a condensed copy of every other page. It is the routing layer.

About

The About page should answer who is behind the business, why it exists, how it works and what makes it credible. This is a good place for real team or company information, credentials and background that would be awkward to repeat on every service page.

Contact

Make the next step clear. Depending on the business, that may be a form, phone number, booking tool, location information, service-area details or several of those. Avoid making customers search the footer for basic contact information.

2. Service pages: when does a service deserve its own URL?

A service deserves a dedicated page when it represents a distinct customer need and the business can explain it usefully. If two offerings have different audiences, processes, proof, common questions or search needs, separate pages can make sense.

Do not split tiny variations into separate pages simply to target more keywords. A thin page for every wording variation creates maintenance work and can make the site harder to navigate. Group closely related offerings where the customer would reasonably expect them together.

A strong service page usually explains the problem, the service, who it is for, the process or deliverables, relevant proof and the next step. Informational tutorials belong in Insights rather than being duplicated inside every service page.

3. Proof pages.

Case studies

Case studies can document a real problem, the work performed and the evidence available afterward. They are especially useful when services are complex or outcomes are difficult to understand from a portfolio screenshot alone.

Reviews and testimonials

Reviews can appear contextually on service or home pages without requiring a separate URL. A dedicated reviews page is useful only when it adds something more than duplicated review widgets.

Credentials and media

If awards, certifications, media coverage or professional credentials materially influence trust, give them a logical home. Do not create a separate page for every small badge.

4. Insights, guides and FAQs.

Informational content should answer questions people ask before or after they buy. Examples include comparisons, maintenance checklists, planning guides and troubleshooting explainers.

This content can support service pages through contextual internal links. The article answers the question; the service page explains the service itself. Keeping those roles distinct helps avoid publishing two URLs that answer essentially the same need.

FAQs do not always need their own page. A focused FAQ section on the relevant service page may be more useful. A separate guide is justified when the question requires enough depth to stand on its own.

5. Location pages: when are they useful?

A location page should represent a genuine service area or physical location and provide useful information specific to that place. A business serving Burnaby and Vancouver may have reason for separate local pages if the services, examples, proof or local context can be explained meaningfully.

Do not create dozens of near-identical city pages with only the place name changed. That adds little value and makes the site harder to maintain. Local content should be accurate and differentiated.

For a local service company, one strong core service page plus a small number of high-quality local pages is usually a clearer architecture than a large collection of copied city variants.

6. Legal, privacy and policy pages.

Privacy, terms, shipping, returns, accessibility statements and other policy pages depend on what the business does and the laws or platforms that apply. They are trust and compliance content, not SEO landing pages.

For ecommerce, shipping, returns and payment information may deserve clear policy URLs. For a local service business, privacy and terms may be enough. Get appropriate legal advice for requirements specific to the business.

Does this topic deserve its own URL?

Example structures for three small businesses.

Professional-services firm

Home → Services hub → individual core services → About → Case Studies → Insights → Contact → Privacy/Terms.

Local appointment-based clinic

Home → service or treatment pages → team/clinic information → patient resources → booking/contact → location information → policies.

E-commerce brand

Home → product categories → product pages → About → help/policies → cart/checkout → editorial content where it genuinely supports products and customers.

These are examples, not templates to copy blindly. The architecture should reflect the business model and the questions customers actually ask.

Navigation should expose priorities, not every URL.

The primary menu does not need to contain every page. Group related services, keep the top-level choices understandable and use internal links, hubs and footer navigation for secondary destinations.

A menu that grows without hierarchy can become a symptom of unclear information architecture. Before adding another top-level item, ask whether it deserves equal prominence with the existing sections.

On mobile, navigation needs even stronger prioritization because long menus become harder to scan and interact with.

Plan content around the questions that matter.

Before creating a new article, list the questions customers ask repeatedly and compare them with existing pages. Some questions deserve a new guide. Others can be answered with a paragraph, checklist or FAQ on the page people already use.

Publishing should reduce uncertainty for customers, not simply increase the URL count. A smaller library of useful articles is easier to maintain and more likely to support the website structure cleanly.

How this supports search visibility.

Google’s SEO Starter Guide emphasizes making sites understandable to search engines and users. Clear page roles, descriptive links and useful content help that process. But a larger page count is not automatically better.

Search visibility improves when the website has strong, distinct destinations for important topics and avoids duplicating the same purpose across multiple weak pages. That is why page planning should happen before content production.

Reference: Google Search Central: SEO Starter Guide ↗

What should you build first?

Start with the pages needed for customers to understand the business and take action. Add proof. Then add informational content where real questions justify it. Build local or specialized pages only when they can offer genuine differentiated value.

If you are planning a new business website rather than only its content architecture, Web Design & Development is the appropriate PWS next step. The Burnaby-specific evaluation guide is available at What Burnaby Businesses Should Look for in a Modern Website.

Review the architecture as the business changes.

A page structure that worked at launch may become outdated as services, locations or products change. Review the architecture periodically. Merge pages that no longer justify separate URLs, add pages only when a new customer need is real, and update navigation so the highest-priority destinations remain easy to find.