Build a news topic taxonomy that survives the next news cycle

A newsroom taxonomy should help people find related reporting even when the latest headline has disappeared from the homepage. That requires concepts with enough continuity to connect stories over time, plus enough flexibility to describe subjects that editors are only beginning to cover. A growing list of tags can satisfy neither goal if nobody agrees on what each tag means.

Start with the editorial jobs the vocabulary will support: routing copy, building subject pages, suggesting related reading, or comparing coverage. The News Topics API guide introduces those workflows. This article develops a practical taxonomy for them, using a hypothetical local newsroom that covers transport, education, housing, and public policy.

Separate subjects from the other ways news is organized

A section answers where a newsroom publishes a story. A subject describes what the story substantially concerns. A location identifies a place with a defined relationship to the reporting. A genre describes the editorial form, such as analysis or an interview. A named entity identifies a person or organization. Keep these dimensions distinct even when the same words appear in several of them.

Imagine an analysis of a city's decision to buy electric buses. It might appear in a local section, concern public transport and procurement, mention the city government and a vehicle manufacturer, and focus on a particular municipality. Combining all those values into an undifferentiated tag list makes it harder to build predictable filters or explain related-story recommendations.

The distinction also prevents misleading assumptions. The location of a publisher does not establish where an event occurred. A politician's name does not prove that electoral politics is the main subject. A business desk may publish a story primarily about workplace safety. Define the relationship behind each metadata field, and let editors inspect it.

Begin with a compact set of useful concepts

Inventory a representative sample of articles and ask editors which recurring subjects readers would reasonably want to follow. Begin with the concepts that serve those reading needs. A small vocabulary with clear boundaries is easier to apply consistently than a large collection of impressive labels that overlap or rarely receive a meaningful assignment.

Give each concept a preferred label, a stable identifier, a definition, and a short note on exclusions. For public transport, the definition could include planning, provision, and operation of shared passenger services. An exclusion might distinguish private vehicle sales. These are proposed editorial choices for the hypothetical newsroom; another publisher may draw the boundary differently.

Add examples that test the boundary. A bus timetable change clearly fits public transport. A manufacturer's quarterly results may fit business finance, even if buses are its main product. An article about a government bus purchase may support several topics. The purpose of examples is to make the rule usable, not to exhaust every story an editor will encounter.

Use hierarchy to support navigation

A hierarchy can connect broad subjects to narrower concepts. A reader following transport may want to discover public transport, cycling infrastructure, and road planning. Decide whether assigning a child topic automatically makes a story eligible for its parent page. Then document the rule so that archive behavior does not depend on the particular editor who handled the article.

Allow depth where it serves coverage. A specialist climate publication may need several distinct energy-policy concepts, while a small general newsroom may prefer a broader energy category. Avoid forcing every branch to the same number of levels. A tidy diagram is less important than clear distinctions and enough relevant reporting to support each destination.

Keep temporary story collections separate

A named summit, court proceeding, or municipal election can deserve a dedicated collection without becoming a permanent subject category. Give event collections their own identifiers and relationships to enduring topics. A transport funding vote can belong to both a time-bound election collection and a lasting public transport subject page without making either structure carry the other's job.

Consider an external vocabulary carefully

IPTC Media Topics provides a subject taxonomy focused on categorizing text, with a hierarchy and machine-readable distribution formats. It offers a useful reference when a newsroom wants shared concepts or a vocabulary to compare with its own. The existence of a standard does not decide which concepts your readers need or how your editors should apply them.

Build a mapping table between local concepts and the external vocabulary. Mark whether each relationship is equivalent, broader, narrower, or only related. Do not label a mapping exact merely because two names look similar. Read the definitions, compare example articles, and preserve notes explaining where the boundaries differ.

Record the vocabulary release used for the mapping. When either side changes, review affected relationships instead of assuming the old mapping remains valid. The same principle applies to an internal reorganization: a stable concept identifier and a recorded version make archive interpretation much clearer than a display label alone. See the JSON contract guide for the underlying data model.

Handle evolving stories without losing history

News articles change as reporting develops. An early brief may focus on a transport delay; a later revision may establish that a procurement dispute caused it. Associate topic assignments with a document revision and record whether an editor accepted, removed, or replaced them. That history explains why a story appeared in one collection yesterday and another today.

Keep a distinction between adding a supported secondary topic and changing the primary subject. An update with a paragraph of background does not necessarily change the article's main purpose. Ask reviewers to consider the headline, opening, substantive evidence, and editorial intent together. Where they disagree, preserve the reason so that the taxonomy rules can improve.

Repeated updates also need a collection policy. A topic page flooded by minor versions of the same story may be technically complete but unhelpful to readers. Decide when to show the latest version, link a developing story thread, or display separate articles. The deduplication guide explores related decisions about repeated and overlapping content.

Make language and geography explicit

Use a shared concept identifier with language-specific display labels when the definition is intended to remain equivalent. Ask someone with relevant language and subject knowledge to review the translation. A literal translation can be grammatical while carrying a different institutional meaning, especially for public bodies, education systems, or government offices.

Store the original article language separately from the label language shown to a reader. A Spanish-language interface can display a translated topic label while the article remains in English. If a classifier works from a translated article, keep that processing choice visible because reviewers may need to inspect the source wording.

For location, define roles such as event location, subject jurisdiction, and places mentioned. A story about a national regulation discussed at a local meeting can legitimately contain all three. Avoid deriving political affiliation or a person's identity from a place label. The country topic guide develops ways to preserve useful geographic context.

Give changes an editorial owner

Choose who can propose a topic, who approves its definition, and who reviews effects on existing content. A lightweight change record can include the problem, proposed concept, example stories, overlapping concepts, and expected use. This keeps a one-off naming request from quietly becoming a permanent archive commitment.

Use actual confusion as a signal for improvement. If editors repeatedly disagree between two topics, review the definitions and the examples before adding another category. If a label stays unused, ask whether the newsroom lacks coverage, the wording is unclear, or the concept is too narrow. Each explanation suggests a different response.

Try a revision on a small archive sample before applying it broadly. Inspect the subject pages it would produce, including empty or very sparse destinations. Preserve old assignments when they remain meaningful, and mark cases requiring fresh review. A migration should make editorial behavior clearer, with enough context to reverse a mistaken change.

Conclusion: treat the taxonomy as an editorial product

A useful news taxonomy joins stable concepts to the newsroom's everyday decisions. Keep subjects distinct from people, places, sections, and temporary collections. Write definitions that editors can apply, version the important changes, and review the resulting reading experience. The vocabulary earns its place when it helps a reader follow a subject and helps an editor explain why a story belongs.