Site architecture for topical authority: pillar, hubs, branches and articles
Site architecture is the way a site's pages are grouped, ordered and linked: which page sits above which, what each one is responsible for, and how a reader or a crawler moves between them. When it follows the topic instead of the order pages were written in, both readers and search engines can see what the site covers. This article describes four levels that fit stores, content sites and service businesses alike.
On this page — 4 sections
What is site architecture, and why does it matter for topical authority?
Quick answer
Site architecture is the grouping, order and linking of a site's pages. It matters because search engines judge a topic by how completely and clearly a site covers it. A clear hierarchy shows the coverage; a flat pile of posts hides it, even when the content is good.
Most sites grow by accident. A blog post goes up when someone has time, a product category is added when stock arrives, a service page appears when a client asks. After two years the site has two hundred pages and no shape: related pages don't link, and the most important page sits four clicks from the home page.
Architecture fixes that by giving every page a parent and a job. A reader on an oud perfume store in Riyadh who lands on an article about storing oud oil should be one click from the oud oils category, and that category one click from the home page. The same path tells a crawler how the pages relate.
What does each level of the hierarchy do?
Quick answer
The pillar states what the whole site is about. Hubs split that subject into its main parts. Branches cover one specific need inside a hub. Articles answer the narrower questions that support a branch. Each level links up to its parent and down to its children.
| Level | Its job | Online store (Riyadh) | Content site (Egypt) | Service business (Dubai) |
|---|---|---|---|---|
| Pillar | Defines the whole subject | Home page: Arabian perfumes | Home page: Egyptian home cooking | Home page: AC maintenance |
| Hub | One main part of the subject | Oud oils | Main dishes | AC repair |
| Branch | One specific need | Cambodian oud oils | Molokhia recipes | Split AC not cooling |
| Article | A narrower supporting question | How to tell real oud oil from blends | Why molokhia turns slimy, and how to fix it | Why an AC blows warm air at night |
Not every site needs all four levels everywhere. A small hub with three pages can link straight to articles. The point is that every page knows its parent, and no page is left without one.
How deep should a page sit?
Quick answer
As shallow as the hierarchy allows. A common practitioner rule is that any page you care about should be reachable within three or four clicks of the home page. Google's own guidance is narrower and firm: every page you want found should be linked from at least one other page.
Depth is counted in clicks, not in URL folders. A page at /oud/cambodian/ that is linked from the home page menu sits one click deep, whatever its URL says. A page linked only from page 9 of a blog archive is buried, even with a short URL.
- Pillar to hubs: the main menu or a clear section on the home page.
- Hubs to branches: the hub page itself lists and summarises every branch.
- Branches to articles: a "related questions" block inside the branch, written for the reader.
- Articles back up: each article links to its branch near the top and again at the end.
A cooking site in Cairo that publishes three recipes a week reaches page 30 of its archive within two years. Without hubs, recipes from the first year are effectively invisible to new readers and harder for a crawler to revisit.
What breaks a site's architecture?
Quick answer
Four patterns cause most of the damage: a blog that sits outside the hierarchy, tag pages that duplicate categories, everything placed one level below the home page, and near-identical pages for each city or variant. Each one blurs which page is responsible for which query.
- The blog as a side room: articles live under
/blog/and never link to the categories or services they support. In a Jeddah dental clinic, an article on implant pain should lead to the implants page, not only to "more posts". - Tags competing with categories: a store with a "sofas" category and a "sofas" tag now has two pages fighting for one query.
- Everything flat: fifty service pages linked from one long menu. Readers can't scan it, and no page is shown as more important than another.
- Copy-paste variants: the same AC repair text with a different city name. Make a separate page only where the need, price or regulation actually differs.
This article is part of the Topical Authority series — What topical authority is, how to choose the subject you want to own, and how structure, links and publishing pace build it.
About the author
Mohamed Youns
Semantic SEO Engineer · Author & system developer
Mohamed Youns writes about how search engines understand content — the same standards he applies when building semantic systems at Nut Hub. nut-hub.org