Internal links and site structure guide
Build a Useful Topic Hub in WordPress
Write a hub page around one reader task, give each supporting article a stated role, and link them in the order readers need, instead of relying on a date-sorted archive.
On this page
A useful topic hub is a page written for one reader task. It explains the task briefly, introduces each supporting article in the order a reader needs it, and says in a sentence what each one covers. A category archive is not the same thing: it usually lists posts by date, whatever they answer. Build the hub as an ordinary WordPress page that you write and maintain, and let archives do the browsing job they are good at.
Google’s link guidance, checked September 27, 2026, asks that every page you care about has a link from at least one other page, and that anchor text describes the destination. A hub can meet both for a whole group of articles at once, as long as its links are ordinary <a href> links in the page content and each anchor names the article it points to.
Define the task and its boundary
Write one sentence that states the reader’s task, then two short lists: what the hub covers and what it does not. For garden.example, a fictional garden design business, an illustrative hub might be:
- Task: plan and build a small vegetable garden in the first year.
- Covers: choosing the site, soil, bed layout, first plantings, early maintenance.
- Does not cover: lawn care, trees, commercial growing, design services beyond a single link.
The boundary is what keeps a hub useful. Without it, every loosely related post gets added, the page turns into a second archive, and readers can no longer tell where to start.
Choose between a hub page and an archive
WordPress gives you several ways to list content. They do different jobs.
| Option | What it shows | Good for | Limit |
|---|---|---|---|
| Hand-written hub page | The links you choose, with your explanation of each | A route through one task | You maintain it by hand |
| Category or tag archive | Every post in the term, usually newest first | Browsing everything on a subject | No order by task, no explanation of each post |
| Page List block | Published pages, optionally only the children of one parent | Listing child pages under a parent | Titles only, no context |
| Query Loop block | Posts or pages matching filters such as category, tag or parent page | Recent or filtered lists inside a page | Ordered by date or alphabet, not by reading order |
Archives use WordPress’s main post query, which the WP_Query reference, checked September 27, 2026, orders by post date, newest first, unless a theme or plugin changes it. The Page List block documentation, checked September 27, 2026, describes a Parent setting that limits the list to the child pages of one page. That is handy for a hub built from pages, but it lists titles only, so write the hub’s explanatory text around it rather than letting it stand alone. The Query Loop block documentation, checked the same day, lists newest, oldest and alphabetical ordering, and notes that titles and featured images inside the loop do not link to their posts in every layout; to make them clickable, you turn on each block’s link setting. If you use one on a hub, check that setting before you publish.
A hub and an archive can both exist. The archive lets someone see everything; the hub tells someone where to start. For decisions about whether an archive should be indexed at all, see the site structure chapter of the WordPress SEO field guide.
Give every supporting page a role
List the articles you might include and assign each a role in the task. If you cannot name its role in a few words, it probably does not belong in this hub.
| Stage | Article | Role | Why it belongs |
|---|---|---|---|
| Start | Choosing a site for vegetable beds | Decide where | Every later step depends on the location |
| Start | Soil testing at home | Check the ground | Determines what to amend before planting |
| Plan | Raised bed materials compared | Choose how | A one-time decision with cost and lifespan tradeoffs |
| Plan | Bed layout for small spaces | Arrange | Spacing and paths for the chosen site |
| Do | First plantings month by month | Plant | The calendar for year one |
| Maintain | Watering and mulching basics | Keep it going | The most common first-year problems |
The table is illustrative, but the method is not. Look for two articles with the same role. That usually means overlap: merge them or give each a narrower job. Look for a stage with no article. That is a content gap, which you record rather than fill with a thin page written only to complete the hub.
Build the hub and its links
Write the hub page in this order:
- A short opening that states the task and who it is for.
- One section per stage, each with a sentence or two of guidance and links to the articles for that stage. Every link gets a line saying what the reader will find: “Soil testing at home explains the kit test, what the pH reading means, and when to send a sample to a lab.”
- A short note on what the hub does not cover, with links elsewhere if useful.
Then edit each supporting article:
- Add a link back to the hub near the top or where the article mentions the wider task. Readers who arrive from search on one article need a way to find the rest.
- Add a link to the next stage where it naturally follows. The site selection article can point to soil testing at the point where it mentions soil.
- Keep links between siblings for real dependencies only. Linking every article to every other one hides the order the hub was built to show.
If the hub and its articles are pages, you can also make the hub their parent page with the Parent Page setting. WordPress’s Create pages guide, checked September 27, 2026, notes that page permalinks reflect this hierarchy. With any permalink setting other than Plain (checked September 27, 2026), the address then shows the grouping, and a breadcrumb trail built from page parents shows it too. WP Visibility’s breadcrumb trail, for example, lists a page’s parent pages, as described in Add a visible breadcrumb trail. An SEO plugin can print the trail and the metadata; it does not decide which articles belong or in what order. That is the editorial work above.
Changing a parent can change existing addresses, so check redirects before you move published pages.
Test the links and look for uncovered questions
Once the hub is published:
- Open it signed out and follow every link. Each one should land on a page that returns successfully and matches the line describing it.
- From each supporting article, follow the link back to the hub.
- Run a crawl, such as the one in the small-site link audit, and confirm that every supporting article is reached.
- Collect the questions readers actually ask on this task: search queries in Search Console’s Performance report (checked September 27, 2026), support emails, questions from consultations. Mark each one as answered by a named article or not answered.
The unanswered questions are your hub’s backlog. Some deserve a new article. Some are a paragraph in an existing article. Some are outside the boundary you set and should stay out.
Hub checklist
- One sentence stating the task, and a written boundary.
- Every supporting article has a role; no two share one without a reason.
- Each link on the hub has a line saying what the reader will find.
- Every supporting article links back to the hub.
- All links followed signed out, and a crawl reaches every article.
- Uncovered questions recorded with a decision for each.