Topics API
Stable IDs, useful JSON, and a vocabulary built to evolve.
A field guide to content intelligence
Practical guides to topic APIs, structured AI output, and editorial taxonomies. Give unstructured content a vocabulary your application can understand.
For developers, publishers, and curious builders.

Start with a clearer vocabulary.
Build a more useful content experience.
01 / Explore the topic atlas
Start with the fundamentals, then find the vocabulary, fields, and review decisions that fit your domain.
Stable IDs, useful JSON, and a vocabulary built to evolve.
Label content with evidence, representative tests, and review.
Connect stories to subjects without losing the event context.
Turn language into structured, validated topic records.
Write clear instructions for consistent topic assignments.
Organize model tasks, versions, and capability evidence.
Keep subjects, horizons, and uncertainty in the record.
Separate financial subjects from entities and reporting periods.
Map research concepts and keep capability claims in scope.
Preserve place roles, local language, and geographic context.
Understand sampling, repetition, and the limits of a trend.
Classify policy subjects with attribution and context.
02 / A little structure goes a long way
A topic record connects a document to a defined concept. Explore three illustrative examples, then see how to design the contract behind them.
Give the vocabulary clear boundaries and stable identifiers.
Make it possible to inspect why a label fits the content.
Represent uncertainty before a label reaches a reader.
A publisher evaluates an LLM for its article archive.
{
"topics": [
{
"id": "ai.language-models",
"label": "Language models"
},
{
"id": "publishing.archives",
"label": "Digital archives"
}
],
"taxonomy_version": "demo-v1",
"review_status": "needs_review"
}Illustrative data for learning topic design. No live request is made.
03 / Find your reading path
FOR DEVELOPERS
Work through identifiers, schema validation, topic assignment, and predictable handling of unknown content.
Explore structured topic outputFOR PUBLISHERS
Build subject archives with useful editorial boundaries, source context, and a clear place for corrections.
Explore news taxonomiesFOR RESEARCHERS
Keep model claims, uncertainty, sampling limits, and evaluation conditions attached to the concepts you organize.
Explore model context04 / Ideas from the Lab
Ten practical reads on the decisions behind useful topic systems. From the first JSON contract to the context that a label can miss.

Build a topics API contract that readers, editors, and developers can understand. Explore stable identifiers, evidence, uncertainty, document revisions, and vocabulary changes through practical examples for content classification.
Read the article : Topics API design: IDs, labels, and useful JSON contracts
A useful evaluation starts with the decisions a label will drive. Build a representative review set, calculate topic-level metrics, inspect disagreements, and compare revisions without hiding costly mistakes in a single average.
Read the article : Evaluate AI topic classification before you trust the labels
News changes quickly, but a useful subject vocabulary needs continuity. Learn how to separate topics from sections and entities, handle evolving stories, map external vocabularies, and give editors clear rules for everyday classification.
Read the article : Build a news topic taxonomy that survives the next news cycle
Valid JSON is the first check in a longer workflow. Design topic extraction around an allowed vocabulary, verifiable evidence, explicit outcomes, document revisions, and validation that connects a generated label to its source.
Read the article : LLM topic extraction: a JSON contract you can actually validate
A strong labeling prompt describes a decision that another editor could follow. Learn to separate instructions from source text, choose examples that reveal topic boundaries, handle uncertainty, and evaluate changes against a stable review set.
Read the article : Prompt design for topic labels: definitions, evidence, and edge cases
Organize model coverage by task, modality, and evidence. This practical taxonomy separates the model being discussed from the system using it, while keeping broad capability claims attached to their sources and evaluation scope.
Read the article : Build an AI Model Taxonomy That Keeps Claims in Context
Prediction coverage needs careful boundaries between the subject, the statement, and its time horizon. Build a document contract that preserves uncertainty and provenance without presenting extracted labels as forecasts or probabilities.
Read the article : Design Prediction Topic Contracts Without Inventing Forecasts
Financial document labels need more than company names. Separate the document type, entities, reporting periods, and evidence so readers can find relevant material without confusing topic classification with a financial conclusion.
Read the article : Classify Financial Documents Without Losing Entity and Time Context
A place name, an institution, and a political subject play different roles in a document. Preserve those distinctions with sourced entity relationships, multilingual evidence, and review rules that make geographic context inspectable.
Read the article : Preserve Country and Political Context in Topic Data
Repeated posts can make one story look like many independent signals. Learn how to separate activities, content objects, and story clusters, then report observed topic patterns with clear sampling limits and evidence.
Read the article : Separate Social Topic Signals from Repeated Posts05 / Good questions
The vocabulary is only useful when everyone understands what it means.
Read the foundationsA topic API represents subjects and their relationship to content through a defined data contract. Depending on the design, it can expose a vocabulary, record topic assignments, or help an application retrieve documents by subject.
Twelve topic guides and ten long-form Lab articles covering API design, AI classification, news taxonomies, prompts, model metadata, and domain-specific context. Start with the Topics API foundations to choose a reading path.
TopicsAPI.com is an independent resource focused on content classification and topic-data design. Google’s browser advertising Topics API is a separate technology. See the distinction in our topic contract guide.
Not every workflow needs one. A carefully defined rule, a trained classifier, or an editorial process may suit the task. Compare approaches on representative documents and review the errors that matter to your readers.
A topic identifies the subject of content. Keep any prediction, capability claim, evaluation result, or political statement separately attributed, with the context needed to interpret it.
Developers can begin with the JSON contract guide. Publishers can start with the news topic guide. For automated labeling, continue to AI classification and evaluation.
Have a taxonomy question or an idea for the Lab? Get in touch.