Guide · Local SEO website architecture
A well-structured Melbourne service-business website usually moves from the homepage to a Services hub, then into category pages that organise related services, and finally into individual service pages that answer a specific customer need. A small business with one obvious service group may not need a redundant category layer, but businesses with several genuine service groups should make those categories clear. Problem or location pages come later and must earn their place through distinct value or evidence. If the same service answer applies across a suburb, use clear coverage information instead of publishing a thin suburb copy. Every important page should be reachable through a crawlable internal link, with links, redirects, canonicals and the sitemap pointing to the same preferred URL.
You can plan the site without turning every service wording and Melbourne suburb into another page. The choices below are the ones I make with business owners.
By Ajay Dabhi, Local SEO specialist in Melbourne
Published 23 July 2026
Serving a local area does not change the foundations. Pages still need a clear purpose, useful content, logical organisation, crawlable links, reliable rendering and consistent preferred URLs. Google Search Central’s SEO Starter Guide explains that logical organisation and crawlable links help people and search engines understand relationships and discover pages. It does not prescribe one perfect structure.
Local service customers often want to know whether you do the work, cover their part of Melbourne and have proof. They also need an easy way to call or enquire. A useful guide should lead them back to the service page that owns the commercial decision.
That is the approach I use for Local SEO for Melbourne service businesses. I begin with real services and customer choices. Extra pages come later, once there is a reason for them.
I start with Home, a Services hub, category pages for coherent service groups, and individual service pages beneath the right category. A useful category page explains the family of services, helps customers choose and links to every child service; it should not be an empty layer. Problem and location pages sit under the relevant service owner only when they add value. Guides and case studies provide support. About holds business evidence. Contact is where a customer calls or enquires.
By "canonical owner", I mean the preferred page for an intent. Giving that job to one page avoids two URLs offering substantially the same answer. The map is a decision aid, not a blueprint every business must copy.
Figure 1 · Mind map
Purpose: See how Services leads to category pages, then to individual service owners and their supporting pages.
I ask what customer decision a proposed page would own, whether its answer is genuinely different, what evidence belongs there and how someone would reach it. Weak answers usually mean the material belongs on an existing page.
The table uses four status words. "Base" is a normal site function. "Owner" holds a distinct commercial decision. An "evidence-led" page must earn its place. "Support" helps an owner without taking over its job.
Figure 2 · Decision table
Purpose: Decide whether a proposed page has a real role or should be combined with an existing page.
| Page type | Create when | Do not create when | Primary parent or owner |
|---|---|---|---|
| Homepage · base | The site needs one clear root for the principal offer, market, proof and pathways | A second city homepage would duplicate the same business | Site root |
| Services hub · base | Customers need one place to browse several genuine services | It would be a thin keyword list or repeat the homepage | Homepage |
| Service category page · category owner | A coherent group of related services needs category-level guidance before customers choose an individual service | It would duplicate the Services hub, add an empty layer or merely repeat its child pages | Services hub |
| Individual service page · owner | The need, process, proof or buying decision is materially different and the service is real | Only the wording changes or the page would repeat another service | Relevant service category page |
| Problem or urgent page · evidence-led | The problem creates a separate decision and can be answered usefully | It is a renamed service page with the same answer | Relevant service owner |
| Location page · evidence-led | The area changes useful details and the business has real local evidence | Only the place name changes or coverage text would do the job | Relevant service owner or area hub |
| Guide or FAQ · support | A question deserves standalone depth and naturally supports a service owner | It is a thin query variant or has no useful link path | Relevant service owner |
| Case study or evidence · support | Permissioned, specific evidence helps a customer evaluate a service | Results, reviews or locations would be invented or overstated | Relevant service owner |
| About · base | Real people, history, credentials and operating evidence need a clear home | It would contain only generic brand claims | Homepage / global navigation |
| Contact · base | The site must give accurate call, form, hours and coverage details | Visitability, hours or address would be implied inaccurately | Global endpoint |
| Utility · support | The business needs privacy, terms or another genuine utility route | It is being created to target commercial demand | Footer / relevant process |
Consider a fictional Melbourne mobile bicycle repair website. This is a teaching example, not a client result, benchmark or recommendation for a real company. It services bikes across a defined metro area and handles e-bike diagnostics and commercial fleet maintenance, with different processes and proof for each service.
I would keep Home, About and Contact, then add a Services hub. Under it, a Repairs and Servicing category would group mobile servicing and e-bike diagnostics, while a Commercial Services category would own fleet maintenance. Each individual service gets a focused page because the decision and evidence differ. A useful preparation guide could link back to mobile servicing.
I would consider one location page for Melbourne CBD fleet servicing, and even that is conditional. The business has photographed permissioned fleet work there, and its CBD access, scheduling and dispatch details differ. If that creates a useful local answer with distinct fleet intent, the page may earn its place. Otherwise, I would keep the material on the fleet page or in a case note.
/ Home/services Services hub/services/repairs-and-servicing category page/services/repairs-and-servicing/mobile-bike-servicing/services/repairs-and-servicing/e-bike-diagnostics/services/commercial-bike-services category page/services/commercial-bike-services/fleet-maintenance/areas/melbourne-cbd-fleet-servicing only if distinct intent, proof and local detail pass review/guides/prepare-for-a-mobile-bike-service if it answers a real customer question/about/contactThe route list is deliberately restrained. The business may cover Fitzroy, Carlton, Brunswick and Northcote, but it does not have unique material for each place. Coverage alone does not make those suburbs separate page topics.
Customers and crawlers follow links, not a folder diagram. The main path should run from Home to the Services hub, from Services to every category page, and from each category to all of its individual services. Individual service pages should return to their category parent. Guides and case notes point to the category or service page they support, while sibling services cross-link only when the next option would help the reader.
Each commercial page also needs a clear path to Contact. There is no fixed link quota. I want a browseable hierarchy without orphaned pages or anchor text that misrepresents the destination.
Figure 3 · Internal-link flow
Purpose: Follow navigation, support, parent-child and conversion links through one concrete service-business example.
parent
parent to category
child returns to category
supports · related when useful
next action
When a location page sounds like a good idea, I run it through these six questions before anything is published:
A weak answer on a core test usually means concise coverage text belongs on the homepage, relevant service page or Contact page. That tells customers where you work without forcing a thin answer onto another URL.
Be careful with service × city and service × suburb combinations. Many substantially similar pages can create doorway-style content, repeat one answer and muddle ownership. Useful location pages are still possible, but they are optional and evidence-led. A changed place name does not create local value.
Once the page choices make sense, I check these practical foundations. None guarantees rankings:
After launch, I verify the live URL, canonical, sitemap, redirects, broken links, duplicate owners and orphans. Then I measure Local SEO through qualified enquiries and booked jobs. A cleaner diagram does not prove that one change caused a result.
A small site can be coherent when Services, categories and individual service pages have clear roles and useful paths. Add a category when it genuinely organises a service family, and add an individual service page when it answers a different decision. Repeated suburb claims make a site larger, not clearer.
Figure 4 · Stack comparison
Purpose: Compare a clear minimum, justified expansion and an overbuilt suburb stack on the same structural rows.
Before opening a blank page, inventory the real service categories and assign every individual service to one primary parent. Give each approved intent one preferred owner, then decide what to keep, combine, redirect or withhold. Build the Services-to-category-to-service link paths, check them before release, and let later evidence guide revisions.
Figure 5 · Checklist
Purpose: Turn the architecture model into an ordered build and review process.
If you cannot tell which pages should stay, combine or change, I can review the page stack and explain the next steps. I will also give you a straight answer on whether Local SEO makes sense, without promising rankings or a fixed outcome.