A useful architecture normally gives clear roles to the homepage, genuine service pages, selected location pages, supporting content and trust/foundation pages. Those pages should then be connected through normal crawlable navigation and internal links so people and search engines can understand the relationships.
This guide owns the general local-business architecture problem. If the business offers several services across many towns and you are deciding how to combine the two dimensions without creating every service x location page, use the specialist Service-Area Business Website Structure guide.
important pages from other relevant pages. Google also recommends crawlable links and descriptive anchor text.
Google does not publish a rule saying a particular folder depth, number of pages or URL pattern will make a local business rank.
Start with the business model and page purpose
Before deciding folders, navigation labels or URL slugs, define the business that the website represents.
Ask:
- Is this a storefront, service-area business, hybrid or multi-location company?
- What services can customers actually buy?
- Which services are materially different from one another?
- Where does the business genuinely operate?
- Does it have one real location or several genuine operational locations?
- Which questions need a page and which can be handled as sections?
- What proof exists: projects, photos, reviews, qualifications, process, policies or local evidence?
This prevents the website from becoming a collection of search phrases disconnected from operations.
A bakery with one shop needs a different architecture from a plumber travelling across a county. A solicitor with three real offices needs a different structure from a home-based service business that has one profile and travels to customers. The page types can overlap, but the hierarchy should reflect reality.
Keyword research and mapping should normally happen before final architecture. Local Keyword Mapping decides which intent each page is meant to own. Site structure then organises those owners into a coherent website.
The homepage: broad proposition and primary routes
The homepage should make the business understandable quickly.
For a typical local business it can establish:
- who the business is;
- the main service or service family;
- the principal geographic context;
- the most important routes into services or categories;
- core trust information;
- a clear next action.
It does not need to reproduce every service page and every location page in full.
A homepage becomes difficult to use when it tries to rank for every phrase by stacking long lists of services, towns and keyword variations. A clearer homepage introduces the main proposition and links into pages that own deeper needs.
For example, a business may mention its main service categories with concise descriptions and links to dedicated pages. It may also explain the area it serves and link to selected geographic pages where those exist. The detailed information stays with the appropriate owner.
Service pages: create them for genuine service intent
A service deserves a dedicated page when it represents a meaningful customer need that can be explained substantially and accurately.
Good reasons for a service page include:
- the service has a distinct buying decision;
- customers use materially different language for it;
- the process, limitations, evidence or pricing logic differs;
- the page can answer the service intent better than a small homepage section;
- it fits a clear service family or business category.
Weak reasons include:
- one keyword tool reports a slightly different phrase;
- a competitor has a page for it;
- a synonym can be put in a URL;
- the business wants more pages for “SEO”.
Close service variants can often share one strong owner. The purpose of the architecture is not to make the site as granular as possible; it is to make the distinctions useful.
If a business has a large service catalogue, service families can create a sensible hierarchy. A homeimprovement company might have a parent category for roofing with child pages for roof repair, new roofs and flat roofing if those are genuinely distinct services. A small specialist business may not need a category layer at all.
Location pages: selected, justified and useful
Location pages can be valid, but the existence of a town name in keyword research does not automatically justify a page.
A location page should represent a genuine local need and a place the business actually serves. It should be capable of containing useful, accurate information for customers in that area rather than repeating a generic service page with the town swapped.
The Location Pages hub owns the broader strategy. Once a service-area page has genuinely qualified, the Service-Area Location Pages guide explains how to build it.
The general architecture point is simple: selected location pages are one page type inside the site, not a reason to rebuild the entire website as a town directory.
Supporting content should support the business
A local business can publish useful content beyond commercial service and location pages. The best supporting content usually comes from real questions and real work.
Useful types include:
- project and case-study pages;
- customer questions that need deeper answers;
- practical guides;
- maintenance or preparation advice;
- original photos and first-party evidence;
- resources or tools.
Supporting content should strengthen understanding of the business and help customers make decisions. It should not exist because somebody decided the site needs “four blog posts a month”.
A completed project can show what a service looks like in practice, what the constraints were and what was achieved. That can support a service page and a relevant location page without duplicating either one.
Foundation and trust pages have real user jobs
Most local-business websites also need pages such as:
- About;
- Contact;
- privacy and legal information;
- booking or enquiry process;
- pricing approach where appropriate;
- terms, guarantees or service limitations where relevant.
These pages help visitors understand who they are dealing with and how the business operates. Do not turn them into ranking-factor folklore. An About page is useful because it can establish the real business, people, experience and context. A Contact page is useful because it gives accurate ways to get in touch. Those are legitimate purposes without claiming a direct “trust page ranking boost”.
Hubs are useful when there is a real cluster
A hub page is useful when a subject contains several meaningful child pages and the visitor benefits from an overview.
For example:
- a broad services hub can introduce several service families;
- an areas hub can help visitors choose among selected geographic pages;
- a resources hub can route users to guides and tools.
A hub should not be a thin list of links. It should answer the broad topic, explain how the child pages differ and help the visitor choose the next step.
Small sites may not need many hubs. Creating category pages purely to increase folder depth adds complexity without necessarily adding value.
Navigation should expose the important structure
The main navigation should help users reach the most important parts of the business without becoming a complete XML sitemap in a menu.
Typical global navigation might include:
- Services;
- Areas or Locations, where justified;
- Projects or Work;
- About;
- Contact/Booking.
Important pages can also be reached through hub pages, contextual links, breadcrumbs and footer navigation.
The architecture should avoid two extremes:
Too flat: every page is dumped into the main navigation with no grouping.
Too buried: important service pages are technically indexable but only reachable through obscure links several steps away from the parts of the site that describe them.
Google’s current sitelinks guidance explicitly recommends a logical structure, linking important pages from relevant pages, and concise, relevant internal anchor text. That is a useful principle even when sitelinks themselves are not the goal.
Crawl paths matter more than decorative architecture diagrams
A diagram can look tidy while the actual site is poorly linked.
For an important page, ask:
- Is there a normal HTML link to it from a relevant parent or hub?
- Can a visitor discover it without using search?
- Does the child link back to the parent where appropriate?
- Do relevant sibling or supporting pages connect contextually?
- Is the page isolated after publishing?
The detailed implementation belongs to Internal Linking for Local Business Websites. At the architecture stage, the goal is to make sure every important page has an understandable place and route.
URL structure: simple, descriptive and stable
URLs should help people and developers understand what a page is about. Keep them simple and avoid unnecessary parameters or repeated words.
Examples of sensible patterns include:
/services/boiler-repair//locations/antrim//projects/office-refit-belfast/
But the folder itself is not the strategy. You could create a perfectly tidy /services/town/service/ hierarchy full of thin pages. A neat URL does not make a weak page useful.
Likewise, a page does not become unimportant because its URL has no category folder. Google documentation emphasises crawlable URLs, logical site structure and links; it does not publish a formula where shorter folder depth automatically ranks better.
The practical priorities are:
- one stable canonical URL for the page’s purpose;
- a URL that does not need to change every year;
- normal internal links to the page;
- no parallel duplicate URLs for the same content;
- redirects when a published URL genuinely has to move.
Avoid duplicate architectures
A site can create duplication not only through copy, but through page roles.
Common architecture problems include:
- a
/services/roof-repair/page and a/roof-repair-services/page with the same purpose; - one service page under a services folder and another under a town folder targeting the same generic service intent;
- separate pages for singular/plural or minor wording variants;
- manufacturer pages that simply restate the generic service page;
- many town pages that all lead to the same broad service and contain little distinct local value.
This is why architecture should come after mapping. A clear canonical owner prevents two parts of the website from accidentally being built around the same user need.
A general local-business page-role matrix
| Page type | Main job | Should not become |
|---|---|---|
| Homepage | Explain the broad business and route users | Every service and town repeated in full |
| Service page | Own a distinct commercial service intent | A thin synonym page |
| Location page | Serve a useful geographic intent | A town-name swap |
| Hub | Explain and route a real topic cluster | A link-only archive |
| Project/case study | Show real work and evidence | Another disguised service landing page |
| Guide/resource | Answer a distinct informational need | Publishing volume for its own sake |
| About/Contact/foundation | Establish identity, trust and practical information | Claimed ranking-factor shortcuts |
Real Project: the current McKnight’s Flat Pack Assembly structure
McKnight’s Flat Pack Assembly is a one-base service-area business in Ballyclare. It travels to customers and currently has a relatively compact live structure rather than a service x town grid.
A simplified view of the current live architecture is:
Homepage
- / - Flat Pack Furniture Assembly in Ballyclare
Service/category pages
/bedroom-furniture-ballyclare/office-furniture-ballyclare/living-room-furniture-ballyclare/dining-furniture-ballyclare/childrens-furniture-ballyclare/hallway-furniture-ballyclare/bathroom-furniture-ballyclare/garden-furniture-ballyclare
Manufacturer pages
/ikea-furniture-ballyclare/dunelm-furniture-ballyclare
Selected area pages
/antrim/newtownabbey
Supporting/foundation content visible in navigation or the site
- projects/work content;
- About;
- Booking;
- Pricing;
- FAQs;
- legal pages.
This structure is useful because the different page types have different jobs.
The homepage owns the broad Ballyclare service proposition and introduces service categories and nearby coverage.
The service pages own room/category needs such as office or bedroom furniture assembly. They are not simply town pages.
The IKEA and Dunelm pages own manufacturer-led intent. The live IKEA page includes specific ranges such as KALLAX, ALEX, MICKE and BILLY and explains product checking. The Dunelm page includes a genuine Olney furniture project. That gives those pages a different purpose from the general furniture service.
The Antrim and Newtownabbey pages are geographic service-area pages. They explain coverage and local context for customers in those areas rather than creating a separate page for every furniture category in each town.
The site also shows a useful architectural restraint. The homepage lists nearby places including Burnside, Doagh, Parkgate, Templepatrick, Ballyrobert, Straid, Ballynure and Ballyeaston. Those locations have not each been turned into a separate page simply because they are served.
The architecture is not perfect or frozen. For example, some live area-page sections contain a large amount of local housing and climate detail. That may be useful where it directly affects access, wall type or furniture handling, but the site should keep reviewing whether each local paragraph genuinely helps the customer rather than merely making the page look different.
That is an architectural lesson as well as a content lesson: a page deserves a place in the hierarchy because it owns a useful purpose, not because enough words can be written for it.
See the McKnight’s Flat Pack Assembly case study for the broader implementation record.
Why service-area businesses need a specialist architecture guide
The Flat Pack example introduces a second problem that does not affect every local business: the company has several services and several served areas.
It would be easy to multiply:
8 service categories x Ballyclare + Antrim + Newtownabbey + every surrounding village and create dozens of URLs.
That is not the same problem as general site structure. The specialist Service-Area Business Website Structure guide explains how to choose between strong service owners, selected area pages, manufacturer pages, project evidence and the rare cases where a service x location page might be justified.
A practical architecture process
- Define the business model. Storefront, service-area, hybrid or multi-location.
- List the real services. Group close variants into sensible families.
- Map search intent to owners. Use the keyword map before drawing folders.
- Choose the homepage role. Broad proposition, main services and primary geographic relevance.
- Create only distinct service pages. One useful owner for each meaningful service intent.
- Qualify geographic pages. Do not create town pages automatically.
- Add supporting evidence. Projects, questions, photos and resources where they have a real job.
- Include foundation pages. About, Contact and practical business information.
- Design navigation and hubs. Make important pages easy to discover.
- Plan internal links. Parent-child and contextual relationships should reflect the architecture.
- Keep URLs stable. Avoid creating parallel or disposable structures.
- Review the whole site before adding pages. New content should fit an existing purpose or create a genuinely new one.
Key takeaway
A good local-business website is organised around real services, genuine locations and clear page purposes. It does not need a page for every keyword, every town or every possible combination.
Once the hierarchy is settled, move to Internal Linking for Local Business Websites to make the structure visible through navigation and contextual links.
For the broader topic, return to the Local Business Website SEO hub.
Sources and evidence used
- Google Search Central - Sitelinks - checked 2 September 2026.
- Google Search Central - Link best practices - checked 2 September 2026.
- Google Search Central - URL structure best practices - checked 2 September 2026.
- Google Search Essentials - checked 2 September 2026.
- McKnight’s Flat Pack Assembly homepage - checked 2 September 2026.
- McKnight’s Antrim page and Newtownabbey page - checked 2 September 2026.
- McKnight’s IKEA page and Dunelm page - checked 2 September 2026.