Skip to content
Docs

Topics

What your market asks about, how much of it you already answer, and where the gaps are.

Open in ChatGPTOpen in Claude

App route: /topics

Topics: demand and coverage map
Topics: demand and coverage map

Topics, a tab in Strategy, is the map of what your market is asking about, and how much of it you currently answer. Agents (the automated workers that research, draft and score) build it as they research your market, so it isn't a taxonomy you author from scratch: it's a picture of demand you read. After the first map, you can rename, merge, move and delete its topics.

It's the bridge between research and production. Topics is where you see that a subject has real demand and thin coverage; Clusters, the groups of related opportunities worked as a set, is where you commit to doing something about it.

Doing this rather than looking it up? The Tutorial walks this screen step by step in 4.1 · Align on strategy.

Reference

ColumnWhat it means
TopicThe subject, as research named it
Search demandTraditional search volume for the topic
AI demandStrong, Moderate, Emerging, or a dash: see below for what it actually measures
QuestionsDistinct questions research found inside the topic
PagesLive pages mapped to it: which is why this won't reconcile with the Pages Portfolio, where archived pages still count
CoverageQuestions answered out of questions found (e.g. 2/9)

AI demand is a proxy, and worth understanding before you lean on it. Nobody can measure query volume inside AI assistants: no such API exists. So the grade is inferred from the Google SERP instead: how many People-Also-Ask questions the topic's prompts pull, with the presence of an AI Overview setting a floor. Both signals come from the same keyword data as search volume, read differently.

That makes it a genuine signal about how question-shaped and answer-engine-ready a topic is, but not a measurement of AI traffic. A topic with negligible search volume and Strong AI demand is one the SERP treats as a question rather than a destination.

Coverage counts questions, not pages. 22 pages against a topic with 0/4 coverage means you've published a lot about the subject without answering what people actually ask. The uncovered remainder is split further behind the scenes: a question already on an accepted opportunity or an in-progress brief (the plan a draft is written from) counts as neither covered nor a gap.

The Topic taxonomy is system-managed. You can't edit it the way you edit other taxonomies: topics are managed on Strategy, and the Topic taxonomy is hidden from the Taxonomy screen entirely. It does still appear as a built-in grouping in the Portfolio's Group by; what you can't do is build a new grouping on the Topic category. It's also the layer strategic territories are built on: a cluster owns topics, and a topic's questions are what its coverage is measured against.

Cluster is the word; you may still meet "Bet." The API and the MCP tools call the same object a Bet: a rename that landed in the backend vocabulary and not in the front end. Cluster is canonical, and these docs use it throughout. If you query the API or point an agent at the MCP server and get back bets, that is this same object under its older name.

Demand without coverage is the only signal that matters here. High demand with high coverage is a subject you already own. Low demand is a subject to skip. The whole screen is a way of finding the third case, and everything else on it is context for that read.

Why it works this way

On this page