Linking Local Pages Together: Patterns and Hubs for a Cafe
You have five or six local pages, a city page, a neighborhood page, a street page, maybe a campus page, and none of them link to each other, or they link in a jumble that helps neither a reader nor Google find their way around. Short answer: build one hub page that links down to each specific page, have each specific page link back up to the hub, and add sideways links only where a real visitor would genuinely want to go next.
The rule behind all of this is simple to state and easy to forget in practice: links should follow the visitor's next question, not a count you are trying to hit. By the end of this post you should be able to draw your own link map on one sheet of paper, choose anchor text that plainly says what a page is, add a small footer or navigation block, and run a five minute check for orphan pages nobody can reach.
The Hub and Spoke Pattern
Picture a hub page, something like a general city page for your cafe, sitting at the center, with a specific link down to each local page it covers, a neighborhood page, a street level page, a campus page, whatever pages you actually have. Each of those specific pages links back up to the hub, so a visitor who lands on any one of them can always find their way to the fuller picture.
That is the whole pattern. It is deliberately simple because a simple pattern is one you can actually maintain as pages get added or changed, where a complicated web of cross links between every page and every other page quickly becomes something nobody remembers to update correctly.
Sideways links, meaning a link from one specific local page directly to another specific local page rather than through the hub, belong only where a visitor's actual next question would take them there. Someone reading your campus area page might genuinely want to know about your closest neighborhood page if the two areas border each other and share regular customers. That is worth a direct link. A campus page linking sideways to a page on the other side of town that shares nothing in common with it is not following a visitor's question, it is just adding a link for the sake of having one.
One way to test whether a sideways link belongs is to imagine explaining it out loud to a visitor standing in front of you. If you can say, in one honest sentence, why someone reading this page would want to go to that other page next, the link earns its place. If the explanation requires stretching, since they are both technically local pages, or since it fills out the page a bit more, that is a sign the link is there for the site's sake rather than the visitor's, and it is worth cutting.
What Google's Documentation Says About Links
Google Search Central's documentation on crawlable links is specific about one thing worth building your pattern around: links need to use a real href attribute pointing to an actual URL for Google to reliably follow them, rather than relying on JavaScript click handlers or other non standard methods that a crawler may not process the same way a person's browser does. Keeping your hub and spoke links as plain, real links rather than something clever avoids a problem you would otherwise have to debug later.
On anchor text, the documentation's guidance is to make link text descriptive of the destination page rather than generic. A link reading learn more or click here tells a visitor and a crawler nothing about what is on the other end. A link reading our Riverside neighborhood page tells both exactly what to expect, and that clarity is worth building into every hub and spoke link you create, both for the visitor deciding whether to click and for anything trying to understand your site's structure.
None of this documentation promises a ranking outcome from following these patterns, and this post is not going to claim one. What the documentation does establish plainly is that clear, real, descriptive links help a page get found and understood, which is a foundation worth having in place regardless of what effect, if any, it has on ranking specifically.
This distinction matters because a lot of casual advice about internal linking online implies a direct, guaranteed ranking boost from adding more links, and that is not something the underlying documentation itself states. The honest framing is that crawlable, descriptive links remove a barrier to a page being found and understood correctly. That is valuable on its own terms, and it does not need an exaggerated ranking promise attached to justify doing it well.
Choosing Anchor Text That Actually Says Something
The anchor text rule in practice is straightforward: say what the page is, in plain words, every time. Not neighborhood page, but our Riverside neighborhood page. Not location, but our Fifth Street location. Not blog, but our coffee blog. This sounds almost too simple to write down, but it is the single most commonly skipped detail in real hub and spoke setups, because generic anchor text is faster to type and nobody notices the cost until later.
Avoid stuffing anchor text with every possible keyword variation for a page, since that reads as unnatural to a visitor and does not reflect how anyone talks about your shop. A link should read like a sentence a real person would say if pointing someone toward that page out loud, not like a list of search terms strung together.
This same principle applies whether the link sits in a paragraph of body text, a footer block, or a small navigation menu. Wherever the link lives, the words carrying it should tell a visitor plainly and honestly what they will find if they click.
It is also worth using slightly different anchor text for the same page in different places when it makes sense naturally, rather than repeating the exact identical phrase everywhere. A link in body text might read visit our page for the Riverside neighborhood, while a footer link to the same page might simply say Riverside neighborhood. Both are honest and descriptive. Neither one needs to match word for word, since the goal is clarity for a real reader in each specific spot, not a mechanically repeated phrase.
Building the Footer or Navigation Block
A small, consistent footer or navigation block listing your hub page and each local page it covers is often the easiest way to implement this pattern site wide without needing to remember to add the right link inside every piece of body text you write. Keep it short and plainly labeled, our locations or our neighborhoods, followed by a clean list of the actual pages, rather than folding it into a sprawling sitewide footer stuffed with every place name you can think of.
This is worth stating directly because it is a common overcorrection: a footer crammed with dozens of place names, neighborhoods you do not serve, cities you only mention once, does not help a visitor and does not reflect the honest structure of your site. Keep the footer block limited to the pages that exist and that a visitor might want to reach from any page on your site.
If your local pages already have some natural context for a sideways link, a paragraph on a neighborhood page that could reasonably mention the specific campus page nearby, add that link inline with descriptive anchor text, in addition to the footer block, not instead of it. The footer handles the reliable, sitewide structure. Inline links handle the specific, contextual connections a footer alone cannot capture.
How Many Cafes Actually Need This
It is worth being honest about who this post is really for. Across the national census of more than 1,000 shops across six regions (snapshot date September 15, 2026), the location_count field, parsed carefully since a handful of entries were not clean numeric values, shows 753 rows equal to exactly one location. That means a meaningful share of shops in this dataset are single location businesses that would not need a hub and spoke structure across multiple physical locations in the first place, though a single location cafe can still benefit from this same pattern across neighborhood, campus, or event pages tied to that one shop.
If your cafe has one location and one set of local pages built around that single address, the hub and spoke pattern still applies, just at a smaller scale, a general about or location page as the hub, with neighborhood or event specific pages linking back up to it. The pattern is not exclusively for multi location businesses, it is for any site with more than a couple of local pages that need a clear way to relate to each other.
A shop that later opens a second location faces a related but distinct question, since a new location typically means a new hub level decision: does the new location get its own hub page beneath a shared brand level hub, or does it sit as a spoke off the existing single hub. That decision deserves its own dedicated thinking once it applies to you, and it is worth planning for early rather than retrofitting a structure after the second location's pages are already built and scattered without a clear hub relationship.
The Five Minute Orphan Check
An orphan page is one that exists on your site but that nothing else links to, meaning a visitor could only reach it by typing the exact address or finding it through an external search result, never by browsing your own site. Orphan pages are easy to create by accident, a local page built early on that never got added to the footer block once the pattern was established later.
The check itself is quick. Pull up Search Console's links report, which shows internal links Google has found on your site, and compare that list against every local page you know exists. Any page missing from the internal links list is a candidate orphan worth checking by hand: visit your hub page and every local page directly, clicking through your own site the way a visitor would, and note whether you can reach every page you know exists using only the links on the pages themselves.
If you find an orphan, the fix is almost always the same: add it to the footer or navigation block described above, and add at least one inline link from a related page if one exists. This is a check worth running any time you add a new local page, not just once as a one time cleanup, since a new page built without being added to the existing pattern becomes an orphan the moment it goes live.
It is worth keeping a simple, dated note of when you last ran this check, even just a line in a notebook or a shared document. A site with five local pages today might have eight in a year, and without some kind of record, it becomes easy to lose track of which pages were checked recently and which have quietly gone unchecked since the last time someone thought to look.
Related Reading
More from Hillcane on this topic, plus the pages on the site that sit next to the work.
Frequently Asked Questions
What is the hub and spoke pattern for local pages?
One hub page links down to each specific local page, each local page links back up to the hub, and sideways links between specific pages are added only where a visitor's real next question would take them there. It is a simple, maintainable pattern rather than a complex web of cross links between every page.
Does Google's documentation require a specific number of internal links per page?
No. Google Search Central's documentation on crawlable links is about two things: links that use a real href attribute pointing to an actual URL, rather than JavaScript click handlers a crawler may not process, and descriptive anchor text that says what the destination is. It sets no link count per page, and neither does this post. The working rule here is to follow the visitor's next question: hub down to spokes, spokes back up, sideways only when earned.
What makes anchor text good versus generic?
Good anchor text names the destination plainly: our Riverside neighborhood page instead of learn more, our Fifth Street location instead of location, our coffee blog instead of blog. It should read like something a person would say aloud when pointing someone to that page, not a string of keyword variations. Wording can differ by spot, such as a full phrase in body text and a short Riverside neighborhood in the footer, as long as each stays descriptive.
Do single location cafes need a hub and spoke structure?
Yes, at a smaller scale. In Hillcane's census of 1,109 shops across six regions, snapshot September 15, 2026, 753 rows show exactly one location once the location count field is parsed carefully, since a few entries are not clean numbers. A single location cafe can still make its main location or about page the hub, with neighborhood, campus or event pages linking back to it and the hub linking down to each one.
Should my footer link to every neighborhood or city I mention anywhere on my site?
No. A footer crammed with neighborhoods you do not serve or cities you mention once does not reflect your site's real structure and does not help a visitor. Keep a short, plainly labeled block, such as our locations or our neighborhoods, listing only the hub and the local pages that exist and that someone might want to reach from any page. Use inline body links with descriptive anchor text for the more specific connections.
How do I find orphan pages on my site?
Open Search Console's links report, which lists the internal links Google has found, and compare it with every local page you know exists. Any page missing there is a candidate orphan. Then click through your own site by hand, starting from the hub and each local page, and confirm you can reach every page using only on page links, not a typed address. Fix an orphan by adding it to the footer block and one related inline link.
What is a sideways link and when should I use one?
A sideways link connects two specific local pages directly instead of routing through the hub. Use one only when a visitor reading one page would want the other next, for example a campus area page and the neighborhood page bordering it that shares its regular customers. Test it by explaining the link aloud in one honest sentence; if the reason is only that both pages exist or it fills out the page, cut the link.
Does following this pattern guarantee a ranking improvement?
No, and this post does not claim that. Google Search Central's documentation establishes that real href links and descriptive anchor text help a page get found and understood correctly, which removes a barrier; it does not promise any ranking outcome, and no data available to Hillcane supports one. Much casual advice online implies a guaranteed boost from adding links. The honest case is structural: every page stays reachable and clearly labeled for a visitor and a crawler.
How often should I check for orphan pages?
Every time you add a new local page, not only as a one time cleanup. A page published without being added to the footer or navigation block becomes an orphan the moment it goes live. The check takes about five minutes: compare Search Console's links report with your list of pages, then click through the site by hand. Keep a dated note of each run, since five local pages today can become eight within a year.
Can inline body text links replace a footer navigation block?
They work best together. A small footer or navigation block, labeled something like our neighborhoods, provides reliable sitewide structure that does not depend on remembering to mention a page in body text. Inline links carry the specific, contextual connections a footer cannot, such as a neighborhood paragraph naming the nearby campus page with descriptive anchor text. Both should be plain href links to real URLs, which Google Search Central's documentation says crawlers reliably follow.
Work with Hillcane
A hub page links down to each local page, each local page links back up, and sideways links follow a visitor's real next question, not a count. That is the whole pattern.
If you want help mapping out your own local pages the right way, reach Hillcane at hillcane.co/contact or call (256) 384-2449.
Comments