Hub Pages: A Home For The Pages Your Site Was Losing
How the pull-model redesign gives every long-tail page a home two clicks from the front door.
Introduction
Most websites have a home page, a blog, and then a long tail of pages nobody ever finds — product pages, service pages, guides, comparisons — each one only reachable if a visitor happens to already know the exact URL. Search engines have the same problem: a page buried three or four clicks from the home page reads as unimportant, no matter how good the content actually is. We're building a fix for that into Page Builder: Hub Pages.
What a Hub Page actually is
A Hub Page is a single, curated page that groups a set of related pages by topic — not by date, the way a blog index works, but by what a visitor is actually trying to find. A short intro paragraph sets the context, then the page is organized into named sections, each listing the pages that belong there, ending in one clear call to action. Two real, working examples of the pattern: Reverb's /uses/ page groups its use cases by audience (Education, Social Media, Team Chat, and so on); Bitrix24 does the same thing by industry. The idea, credited to SEO consultant Edward Sturm's "Compact Keywords" methodology: keep every important page within two clicks of the home page, group them somewhere a visitor would actually look, and link that grouping page from the site's footer. A hub page isn't a sitemap and it isn't a blog feed — it's a deliberately curated shortcut to the pages that matter most.
| text | url |
|---|---|
| /uses/ | https://reverb.chat/uses/ |
How a page joins a hub
The key design decision: a page doesn't have to change what it already is to join a hub. A blog article stays a blog article — keeps its own listing in the blog index, its own sidebar, its own article schema — and can also be tagged into a hub, appearing there grouped alongside pages of completely different types (a service page, a comparison page, whatever fits the same topic). That's an important distinction from how blog articles join a blog index or press articles join a press room, where the page's type alone determines where it's listed. A hub tag is additive: it says "also show this page here," without touching anything about how the page already works anywhere else. Concretely, that means writing a new article and tagging it into a hub is a two-field decision in that article's own editor — which hub, and which named section within it — not a separate step of going and editing the hub page by hand. The hub always reflects exactly what's currently tagged into it.
Hubs and languages
A hub page is a normal page, so it can be translated exactly like any other page on the site — and it needs to be, for a real reason: a hub is a curated list, and a list mixing two languages together isn't curated, it's confusing. Each language gets its own hub, linked together the same way any other translated page is linked, which means the existing language switcher just works on a hub page automatically, with zero extra work. An article's hub tag always points at the hub in that same article's own language.
Why it matters
None of this duplicates content or competes with a blog index for the same search traffic — a hub page and a blog index serve different intents (topic-first browsing versus recency), and every page still has exactly one canonical address either way. What a hub actually buys is structure: pages that would otherwise be orphaned three clicks deep become reachable in one, grouped in a way a visitor (and a search engine) can actually make sense of.