Skip to the indexed answers
Digital Marketing Index

usdigitalmarketingindex.com SEO

How should a site hierarchy organize multiple unrelated service lines under one brand?

Give each service line its own branch: a hub page for the line, with that line’s service pages beneath it and nowhere else. Keep the pages that describe the company as a whole, such as about, locations, careers, and contact, in a shared layer that every branch links to. Label the navigation by service line in the customer’s words, and link across branches only where a real customer need crosses them. The result is a site where a visitor who came for one service never has to read about the others, and where the link structure tells search engines which pages belong together.

Separate service taxonomies

A branch is a hub plus its children, grouped under one path. The tree below sketches the pattern for a made-up company, Northgate Services, that offers three unrelated lines.

/                               home: routes visitors to a service line
├── /hvac/                      hub for the HVAC line
│   ├── /hvac/repair/
│   ├── /hvac/installation/
│   └── /hvac/maintenance-plans/
├── /commercial-cleaning/       hub for the cleaning line
│   ├── /commercial-cleaning/offices/
│   └── /commercial-cleaning/medical-facilities/
├── /it-support/                hub for the IT line
│   ├── /it-support/managed-services/
│   └── /it-support/network-setup/
├── /about/                     shared company layer
├── /locations/
├── /careers/
└── /contact/

Three decisions are built into it.

  • Each line has exactly one hub. The hub explains the line, lists its services, and links to every child.
  • Children live under their own line’s path. A page about server maintenance does not sit under HVAC because both contain the word maintenance.
  • Supporting articles belong to a line too. A guide to choosing a furnace goes in the HVAC branch, linked from the HVAC hub, not in a general blog where it sits beside an article on office cleaning.

Link structure is what makes the grouping visible. In its guidance for ecommerce sites, Google says navigation structures “can impact Google’s understanding of your site structure”, and that it can use “the number of links it needs to follow to reach a page and the number of links to a page” to infer a page’s relative importance (Google’s guidance on site structure). The same reasoning about links applies to a service site’s branches.

Shared company pages

Some pages are about the organization, not a line. Keep one of each.

Shared page What it holds What it must not become
Home The brand, the lines offered, a clear route into each A sales page for one line
About History, ownership, credentials that apply company-wide Three versions, one per line
Locations Where the company operates, with which lines at each place A substitute for service pages
Contact One set of contact routes, with line selection Separate pages with conflicting details

Credentials that apply to one line only, such as a trade license, belong on that line’s hub, not on the shared about page where they would appear to cover everything.

Navigation depth and labels

Keep every service page within a few clicks of the home page, through links a crawler can follow. The main menu should list the service lines by name, and each hub should link to all of its children.

Label with the words customers use. A menu item reading Solutions tells nobody which line is behind it. Heating and cooling, Commercial cleaning, and IT support do. The labels do double duty: Google’s link documentation notes that anchor text “tells people and Google something about the page you’re linking to” (Google’s guidance on crawlable links and anchor text).

URL paths that mirror the branches help readers of search results as well. Google’s starter guide says it “learns breadcrumbs automatically based on the words in the URL” (Google’s SEO starter guide).

Cross-service linking boundaries

Unrelated lines should not link to each other by default. A link from a furnace repair page to network setup helps no reader of the furnace page.

Work through this check before adding any cross-branch link.

Does one customer plausibly need both services together?
  no  -> do not link; the shared layer already connects the branches
  yes -> Is there a specific situation that joins them?
           no  -> do not link
           yes -> link once, in the paragraph that describes that situation,
                  with anchor text naming the other service

A legitimate case in the Northgate example: a medical office being fitted out needs both specialized cleaning and ventilation work. A paragraph on the medical facilities cleaning page about air quality can link to the HVAC maintenance page. A footer block linking every service to every other service is the pattern to avoid, since it erases the branches the hierarchy was built to show.

Two tests confirm the structure works.

  1. Pick any service page and trace the path to it from the home page. It should pass through its own hub and no other.
  2. Read each hub alone. It should describe one line completely, without borrowing content from another.

This hierarchy organizes services. How the same site should handle the places it serves, and whether nearby cities share a page, is a separate decision described in the guide to when nearby cities should share one service-area page.

Link trail

Reader comments on this answer

Add your comment to this answer

Your email address will not be published. Required fields are marked *