Website Structure for SEO: Organizing Service and Location Pages

A service business that offers several services across several cities can easily need dozens of individual pages — one per service, one per location, sometimes one per service-location combination. Content quality on each page matters, but so does something that gets far less attention: how those pages are organized, linked, and surfaced to Google. A brilliant page that nothing links to and that Google struggles to find might as well not exist.

URL structure and hierarchy

There are two common patterns for organizing service pages, and both are workable — the mistake is usually inconsistency, not the choice itself.

Nested structure

/services/plumbing/, /services/plumbing/drain-cleaning/ — the URL itself documents the hierarchy. This scales cleanly as you add more services and sub-services, and it makes it obvious, from the URL alone, how a page fits into the rest of the site.

Flat structure

/plumbing/, /drain-cleaning/ — shorter URLs, no repeated path segments. This can work fine for a smaller site, but it gets harder to manage once you're covering many services and locations, since the URL alone no longer tells you (or Google) how pages relate to each other.

For location pages specifically, keep the pattern consistent across every city: /locations/newark-nj/ or /plumbing-newark-nj/ — either works, but mixing patterns across different cities creates confusion for both visitors and Google about which pages are equivalent to each other.

How many clicks from the homepage

"Click depth" — how many links a visitor (or a crawler) has to follow from the homepage to reach a given page — is a real factor in how much crawl priority and internal authority a page receives. A page buried five links deep, reachable only through an obscure path, sends a signal that it's not very important — even if the content on that page is excellent.

• Core service pages should be reachable within one or two clicks — typically directly from the main navigation.
• Priority location pages should be reachable within two to three clicks, often through a dedicated locations or service-area hub page linked from the main navigation or footer.
• Lower-priority combination pages (a specific service in a smaller, secondary city) can sit a bit deeper, but should still be reachable through a logical path — not only through the sitemap.

Internal linking to distribute authority

Internal links do two jobs: they help visitors navigate, and they tell Google which pages you consider important enough to link to, and from where. A homepage that links out to your top service and location pages passes some of its own authority — accumulated from external links, brand searches, and general site trust — down to those pages.

• Link from the homepage to your highest-priority service and location pages directly, not just through a generic "Services" dropdown that requires an extra click.
• Cross-link related pages contextually — a blog post about drain cleaning cost should link to the drain cleaning service page; a service page should link to the specific locations where that service is emergency-available.
• Use descriptive anchor text ("emergency plumbing in Newark" rather than "click here" or "learn more") — this gives Google additional context about the destination page's topic.
• Build a services and locations hub page if you serve enough combinations that navigation alone can't reasonably list them all — this is exactly the kind of page a multi-location business needs; see the multi-location SEO guide for the full approach.

Avoiding orphan pages

An orphan page is a page with no internal links pointing to it from anywhere else on the site — the only way to reach it is a direct URL, a sitemap entry, or an old external link. Orphan pages are common on service-business sites that have grown organically over time: an old promotional landing page, a location page built for a market that got deprioritized, a service page replaced by a newer one but never actually unlinked or removed.

These pages don't just sit there harmlessly — they dilute your site's overall quality signal and waste crawl attention Google could be spending on pages that matter. Periodically audit for them: crawl your own site with a tool that reports internal link counts per page, and compare that list against your full sitemap. Any page with zero internal links pointing to it is an orphan, and needs either a genuine home in your navigation and internal linking, or a decision to redirect or remove it.

XML sitemaps

An XML sitemap is a machine-readable list of the URLs on your site that you want indexed, submitted through Google Search Console. It doesn't guarantee indexing and it doesn't substitute for internal linking — but it does help Google discover new and updated pages faster than it would through crawling alone, which matters when you publish a new location or service page and want it found promptly.

• Keep the sitemap current — most CMS platforms and site builders regenerate it automatically, but verify this after any major restructuring.
• Exclude pages you don't want indexed (thank-you pages, internal search results, duplicate filtered views) rather than letting the sitemap balloon with pages that add no value.
• Submit the sitemap URL directly in Google Search Console, and check the Coverage report periodically for pages Google found but chose not to index.

Breadcrumb navigation

Breadcrumbs (Home > Services > Plumbing > Drain Cleaning) do double duty: they give visitors a clear sense of where they are and an easy path back up the hierarchy, and they reinforce the same hierarchy to Google through both the visible links and, ideally, matching structured data. Marked up correctly, breadcrumbs can also appear directly in the search result snippet in place of a raw URL, which makes the result easier to scan and slightly more likely to be clicked. See the schema markup guide for how BreadcrumbList structured data works alongside the visible breadcrumb trail.