Pillar, Hub, Spoke, Cluster: Clarify SEO Page Type Terminology
Ask a group of SEO professionals to define "hub page" and you might get different answers. Some use it interchangeably with "pillar." Others reserve it for navigation-first pages that link out without holding content themselves. Several experts frame the pillar/cluster model slightly differently, and some refer to them different from how web developers use "parent" and "child."
Where they agree is on the substance underneath the labels: broad topics need one strong anchor page, supporting content should link back to it, and that structure is what signals topical authority to search engines. The difference lives almost entirely in what to call each piece, not in what good architecture looks like.
That architecture is also doing real work: how your pillar, spokes, and parent pages interlink is how search engines and AI platforms map what your site actually knows about a topic, the same mechanism behind GEO and AEO. A site with scattered, disconnected pages on a subject reads as thin coverage. A site where the pillar, its spokes, and the surrounding pages all link back to each other reads as depth, and depth is what gets a page cited in an AI answer instead of just ranked on page one, which is why SEO matters more than ever in the AI age.
This is a working reference for SEO and web content page types and terminology that come up most, what each one describes, where they overlap, and where the SEO and web development industry might find differences.
Quick Reference
Term | Type of term | What it describes |
Pillar | SEO strategy | Broad, comprehensive page targeting a high-volume topic |
Hub | SEO strategy | Central page organizing and linking to related content |
Spoke | SEO strategy | Supporting page targeting a specific subtopic |
Cluster | SEO strategy | The pillar/hub plus its spokes, as a linked group |
Cornerstone | SEO strategy | A site's most important, most authoritative pages |
Parent | Site architecture | A page with other pages nested beneath it in the URL structure |
Subpage / Child | Site architecture | A page nested beneath another in the URL structure |
The first five are strategic terms, describing the role a page plays in your content and linking strategy. The last two are structural terms, describing where a page sits in your site's hierarchy. A page can be both, or neither, and that's exactly where the confusion starts.
Pillar page
A pillar page targets a broad, high-volume topic, service, or industry, usually the kind of page you'd point to as a core service or solution page. It's long-form, covers the topic comprehensively, and exists to rank for the head term while linking out to more specific supporting content.
Purpose:
Rank for broad, high-volume keywords
Establish topical authority on the subject
Organize and link to related, more detailed pages
Example: a "Complete Guide to CRM Software" pillar linking out to spokes on CRM pricing, integrations, and reporting features.
A pillar page is a type of hub page, but not every hub page is a pillar page. That distinction matters more than it sounds like it should, which is the whole reason the next section exists.
Hub page
A hub page organizes and connects related content around a shared topic. Functionally, it's often doing the same job as a pillar: centralizing a topic and linking to supporting pages. Where the terms diverge is in emphasis. "Pillar" implies the page itself is the comprehensive resource. "Hub" implies the page's job is navigation, sending visitors to the content that actually answers their question.
Purpose:
Organize related content around a shared topic
Improve navigation and content discoverability
Support internal linking and topical relevance
Here is the distinction: fold a hub and all its spokes into a single page and you get a pillar; keep them separate and you have a hub-and-spoke model. Others use "hub" and "pillar" as functional synonyms and let context do the work. Neither camp is wrong. It's worth knowing which type a collaborator is using before assuming their goal.
Spoke page
A spoke is a supporting page built around a subtopic, linking back to its pillar or hub. It's a content strategy and internal linking term, not a structural one, which is the distinction worth holding onto: a spoke does not have to be a literal child page in the URL hierarchy.
Purpose:
Rank for specific, longer-tail keywords
Support the pillar or hub's topical authority
Add depth on a narrower slice of the broader topic
Characteristics:
More narrowly scoped than the pillar it supports
Targets a more specific search intent
Links back to the main page it supports
Child page is a structural hierarchy term. Spoke page is a content strategy term. They frequently describe the same URL, but not always, and treating them as automatically interchangeable is how "is this page a spoke" and "is this page a subpage" end up being two different questions with two different answers.
Cluster
A cluster is the pillar or hub plus its full set of spokes, considered as one interlinked group: one central page, multiple supporting pages, all connected through internal links back to the center and, ideally, to each other.
The cluster is the unit that actually does the ranking work. A single pillar page can only cover so much ground before it either gets unwieldy or starts diluting its own focus. The cluster lets you go deep on subtopics in dedicated pages while the pillar holds the broad term and the internal linking signals topical relevance across the whole group.
Cornerstone content
Cornerstone content, a term Yoast popularized and still uses in its own tooling, refers to a site's most important, most authoritative pages: the ones you most want to rank, and the ones internal linking should be routing authority toward.
It's conceptually adjacent to a pillar page and often describes the same page in practice, but the term itself doesn't specify a hub-and-spoke or pillar-and-cluster structure. Cornerstone is about priority and authority. Pillar is about structure and topic breadth. A page can be cornerstone content without sitting inside a formal cluster, and a cluster's pillar page is almost always cornerstone content by definition.
Parent page
A parent page contains or organizes child pages beneath it in the site's URL structure. This is a web architecture term, describing hierarchy, not strategy.
Example:
Parent: /services/
Child: /services/seo/
Child: /services/ppc/
Subpage / child page
A subpage sits underneath another page in the site hierarchy. That's the entire definition. It says nothing about whether the page is strategic, SEO-focused, or part of a topic cluster.
Example:
/crm-software/ (parent)
/crm-software/reporting/ (subpage)
An SEO-focused spoke can be a subpage. Plenty of subpages aren't spokes at all, they're just pages that happen to live under another one in the URL path, with no strategic linking role attached. Spoke doesn't require a literal parent/child URL relationship, and a subpage doesn't automatically become a spoke just by existing underneath a parent. Keeping "where does this page sit" separate from "what job does this page do" resolves most of the confusion between these two categories.
Why the distinction is worth making
None of these terms have a standard. Most agencies use a version of this framework, but the exact edges move depending on who's talking. What doesn't move: the underlying difference between a strategic role (what job is this page doing for your topical authority and internal linking) and a structural position (where does this page live in your URL hierarchy). Get that distinction settled with your team before the specific labels get confusing and then everyone can be on the same page type (a bit of humor).
If you're mapping a content architecture or untangling an existing site where "pillar," "hub," and "parent" have been used inconsistently across briefs, templates, and CMS folders, that's exactly the kind of structural cleanup Sync Search Digital can manage. Get in touch if you want help creating governance, process and a clear SEO content roadmap.
