Internal linking for local pages: hubs, spokes and breadcrumbs

A location page nobody links to is a page search engines struggle to find, crawl or trust. Linking is not decoration on a local pages build; it is half the architecture.

Orphans do not rank

The classic failure: forty area pages generated, reachable only through the sitemap. No menu link, no hub, no cross-links. Crawlers find them late, internal authority never reaches them, and analytics shows them as a flat line. If a page matters enough to exist, something on the site must point at it.

Give every service a hub

A hub page per service (“Boiler installation”) describes the service once, properly, and links down to every area page beneath it. Area pages link back up. The hub collects links from the navigation and elsewhere on the site and distributes that authority downward. With hierarchical URLs the hub is simply the parent: /boiler-installation/ above /boiler-installation/rye/.

Related areas, kept sensible

Linking each area page to a handful of geographically nearby siblings helps people who searched the next town over and gives crawlers lateral paths through the estate. Keep it to a handful, ordered by real proximity. A footer block linking all forty areas from every page is a link farm, not navigation.

Breadcrumbs close the loop

Home, service hub, area page: a visible breadcrumb with BreadcrumbList markup states the hierarchy to both people and machines, and earns the breadcrumb display in search results. It also quietly enforces discipline, because a page that does not fit anywhere in the trail probably does not fit the site.

Links should survive your tooling

If the links between your pages only exist while a plugin renders them at runtime, removing the plugin dissolves your architecture. Links written into the saved page markup at generation time are ordinary links: they survive deactivation, show in diffs, and need no co-operation from the theme.

Where Townsmith fits

Townsmith generates area pages with hub pages per service, geo-ordered related-area links, breadcrumbs, and every internal link written into the markup of real WordPress pages. Deactivate the plugin and the pages, links and hierarchy all still stand; the blueprints documentation covers how hubs and URL schemes interact.