usdigitalmarketingindex.com SEO
What distinguishes an editorial topic hub from a conventional blog category archive?
Updated November 15, 2026
A topic hub is written and arranged by an editor. A category archive is generated by the publishing system. The hub introduces a subject, orders its articles by what a reader needs first, summarizes each one, and stays the same until someone revises it. The archive lists every post filed under a label, newest first, and changes whenever a post is published. The two serve different visitors: the hub serves someone learning a subject, and the archive serves someone looking for what was published recently or browsing everything on a label. Neither format is required by any search engine, and a site can use both.
Editorial hierarchy and summaries
A hub’s defining feature is that a person decided its contents. The layout sketch below shows the parts.
TOPIC HUB: /guides/home-insulation/
+--------------------------------------------------+
| Title: Home insulation |
| Introduction: what the subject covers, who it |
| is for, where to start (written, 2-3 paragraphs) |
+--------------------------------------------------+
| Start here |
| How insulation works (summary, link) |
| Choosing a material (summary, link) |
+--------------------------------------------------+
| By part of the house |
| Attic (summary, link) |
| Walls (summary, link) |
| Crawl space (summary, link) |
+--------------------------------------------------+
| Costs and incentives |
| Cost by material (summary, link) |
+--------------------------------------------------+
| Last reviewed: date, by named editor |
+--------------------------------------------------+
The order is editorial. Foundational articles come first whatever their publication date, and each link carries a sentence saying what the article answers. An article that no longer deserves a place is removed by decision.
A hub summarizes and routes. Keeping it from repeating the detailed guides it links to is a question of intent, treated in the guide to differentiating a category overview from a detailed guide.
Archive chronology and utility
An archive’s defining feature is that nobody has to maintain it.
CATEGORY ARCHIVE: /blog/category/insulation/
+--------------------------------------------------+
| Category: Insulation |
+--------------------------------------------------+
| Post title, date, excerpt |
| Post title, date, excerpt |
| Post title, date, excerpt |
| (every post in the category, newest first) |
+--------------------------------------------------+
| Page 1, 2, 3 |
+--------------------------------------------------+
That is useful in specific situations: for a returning reader who wants what is new, for a subject where recency is the point, such as product news, and as a complete index when nothing has been left out. Its weakness is the mirror image. The oldest and most basic article is on the last page, the excerpts are whatever the system cut from the first paragraph, and the page says nothing about how the posts relate.
| Responsibility | Topic hub | Category archive |
|---|---|---|
| Who decides what appears | An editor | The category assigned to each post |
| Order | By reader need | By date |
| Text describing each item | Written summary | Automatic excerpt |
| Introductory content | Written overview | Label name, sometimes a short description |
| Changes when | An editor revises it | Any post is published |
| Completeness | Selective | Exhaustive |
| Maintenance | Scheduled review | None required |
Internal link design
The two pages sit differently in the site’s link structure.
A hub links down to each article with anchor text that says what the article covers, and each article links back up to the hub. Google’s link guidance says anchor text “tells people and Google something about the page you’re linking to”, and suggests reading the anchor text alone to check that it makes sense (Google’s guidance on crawlable links and anchor text). A hub is where that advice is easiest to follow, because each link is written by hand.
An archive links with post titles, which may or may not describe the content, and its links move down the list and onto later pages as new posts arrive. An article that sat one click from the category page when published can be several pages deep a year later.
Where both exist, point the article’s return link at the hub, since the hub is the page that explains the subject.
When both should coexist
| Situation | Evidence | Outcome |
|---|---|---|
| A subject has enough articles that a newcomer needs a path | Count of articles; reader questions about where to start | Build a hub |
| Posts are time-sensitive and readers want the latest | Nature of the content | Keep the archive as the main listing |
| A subject has both lasting guides and frequent news | Mix of content types | Both: the hub for guides, the archive for chronology, each linking to the other |
| A category holds three posts | Count | Leave it; an archive is adequate |
| The hub and the archive would list the same items in nearly the same order | Side-by-side comparison | Keep one; they are duplicates in practice |
| No one can commit to reviewing a hub | Staffing | Do not build one; an unmaintained hub misleads |
The last row deserves weight. A hub makes a promise that its selection is current. An archive makes no such promise and has none to break.
A note on evidence: the layouts above are illustrative patterns, not a format documented by Google. The case for a hub rests on what it does for a reader arriving at a subject, and on the internal links it creates deliberately.
Whether the automatically generated archives a blog produces, tag archives in particular, should be open to indexing is a narrower question, taken up in the guide to when blog tag archives should be indexable.
The criterion for choosing: if a person must decide what a newcomer reads first, it is a hub. If the system can list everything by date and that serves the reader, it is an archive.
Add your comment to this answer