Categories vs tags on a news website: organising content

The structure behind a news site decides how readers navigate it, how editors file stories and how easily the archive can be maintained years later. Most CMSs give you the same four building blocks: sections or categories, tags, authors and the article itself. The skill lies in deciding what each one is for. This guide is about that design work. For the mechanics of section archive pages and pagination, see our thread on section pages.

What is the difference between sections, categories and tags?

Sections and categories are the same idea under different names. Both are a hierarchy that places each article in one primary location. Products use different vocabulary, but the principle is shared: a story belongs somewhere.

WordPress documentation says each category may be assigned a parent to set up a hierarchy, and that clicking a parent category displays all posts in it and all its sub-categories. That behaviour is what makes a parent section page useful. A story filed under “Local” appears on the “News” front without anyone filing it twice.

Tags work differently. WordPress documentation says tags have no hierarchy, so there is no parent-child relationship, and that clicking a tag shows a tag archive with every post that carries it. Use them for threads that run across sections, such as an election, a named project or a recurring event.

How should you design the main hierarchy?

Start with how readers talk about your coverage, not how the newsroom is organised. Desks change, reader interests change more slowly.

1. List the top-level topics. Keep them to the number your navigation can show without a second menu.
2. Give each one a single owner. Someone should decide what belongs in “Business” and approve changes.
3. Add subsections only for real volume. An empty or near-empty subsection looks neglected and dilutes the parent page.
4. File each story in one primary section. Allow extra categories sparingly, or you rebuild a tag system with less control.
5. Write definitions. One sentence per section, kept where editors can see it. It prevents “Lifestyle” turning into a dumping ground.

Name sections in plain words. WordPress documentation says category names and slugs must be unique and that the slug is used in the URL, so a category called “Animals” with the slug “animals” gives an address like example.com/category/animals/. The name you choose appears in the address for as long as the section exists.

What are tags for, and how do you keep them under control?

Tags grow fast. Without rules a site collects hundreds of near-duplicates: “Climate”, “climate change”, “Climate crisis”. Each one produces a thin archive page that helps nobody.

A workable policy is short:

• Maintain an approved list, and let only editors create new tags.
• Pick one form for each concept and merge variants.
• Use a tag only if you expect at least several stories to carry it.
• Review tags quarterly and merge or retire the weak ones.
• Do not use tags as a substitute for sections.

If your CMS lets you keep workflow labels out of public view, use that option. A label like “needs legal check” should never become a public archive page.

How should authors be represented?

A byline is a promise to readers about who stands behind a story. Treat it as data, not decoration.

Google’s Article structured data documentation recommends including the author’s name and a link to a web page that uniquely identifies the author, and listing each author separately instead of merging several names into one field. In CMS terms, that argues for an author record with its own page, linked from every article, rather than a typed name.

An author page should carry a short biography, the person’s role, and a list of their stories. For contributors, the same record can show affiliations and, where relevant, disclosure. Our guide to contributor submissions covers how external writers fit into roles and review.

Decide early what happens when a writer leaves. You usually want the byline and page to stay, with a note on their status, instead of reassigning their stories to a generic “Staff” account.

What dates and metadata belong on every article?

Structure is not only about labels. Each article should also carry consistent metadata that your templates and feeds can rely on.

Google’s documentation defines datePublished as the date and time the article was first published, and dateModified as the date and time it was most recently modified, both in ISO 8601 format. Give editors a clear rule for when an update counts as a modification, and make sure your CMS stores both values separately instead of overwriting the first.

Other fields worth defining for every article are headline, standfirst or summary, primary section, lead image with alt text, and article type. Fewer, well-enforced required fields beat a long optional form that nobody completes.

What happens when you restructure?

Moving or renaming a section is the most disruptive thing you can do to a content structure. URLs change, internal links break and archive pages vanish.

Know what your CMS does when something is removed. WordPress documentation says deleting a category does not delete its posts, and that posts assigned to the deleted category are moved to the Default Category, which cannot be deleted. That protects the articles but can leave hundreds of stories in a catch-all bucket if nobody reassigns them first.

Before restructuring:

1. Export the list of articles with their current section, tag and URL.
2. Map each old URL to a new one and prepare redirects.
3. Check your templates. WordPress documentation notes that a template named for a parent category will not match posts in a child category, so a design that relied on the old structure may need updating. Our guide to how themes work explains the template side.
4. Move content in batches and check the section pages afterwards.

How does structure connect to the rest of your CMS?

Your structure should be a decision you make, then configure, rather than whatever the default install gives you. Before choosing a system, check how it models categories, tags, authors and custom article types. Our feature checklist includes these questions. If you add extra fields or content types through add-ons, read how plugins work first, because structure that depends on a plugin is only as stable as that plugin.

For the wider picture of what a CMS does, see What is a CMS?.