Topical authority: how to plan, build and measure it

Topical authority is what a site earns when it covers a subject so completely and coherently that search engines treat it as a dependable source for the whole subject rather than a single keyword. You build it with three things: a coverage map of everything your audience searches for on the topic, a cluster structure of pillar and supporting pages that reflects that map, and a measurement routine that tells you whether Google is rewarding the work. This guide walks through all three, using a coffee brand writing about cold brew as the running example.

What is topical authority?

Think of it as the difference between a site with one good cold brew recipe and a site that answers every cold brew question a reader could have: ratios, grind size, steeping time, concentrate versus ready-to-drink, caffeine, storage, nitro, equipment and troubleshooting. The second site gives Google many consistent signals that it understands the topic. It ranks for more long-tail queries, its new pages tend to get tested in results sooner, and its pillar page has a stronger chance at the head term.

Topical authority is a property of a group of pages. A single 6,000-word guide can’t earn it alone, because one URL can only target a limited set of intents before it turns into a wall of text that serves nobody well.

Does Google use topical authority as a ranking factor?

Be precise about this with stakeholders. Google has publicly discussed a “topic authority” system in the context of news publishers. For other sites, topical authority is industry shorthand for an outcome rather than a documented metric. Google’s Search Central documentation describes creating helpful, reliable, people-first content, and that guidance lines up with the cluster approach: answer the real questions, show first-hand experience, and make related content easy to find.

What you can observe directly is the effect. Sites with deep coverage rank for a wider spread of queries in their niche, and you can measure that spread. That is why the last section of this guide matters more than any definition.

How topic clusters and pillar pages work

A topic cluster is a set of pages that together cover one subject: a pillar page for the broad topic and several spoke pages, each targeting one specific subtopic or intent.

For the coffee brand, it looks like this:

• Pillar: “Cold brew coffee: the complete guide” targets “cold brew coffee” and summarizes every subtopic in a few paragraphs each.
• Spokes: “Cold brew ratio,” “How long to steep cold brew,” “Best coffee beans for cold brew,” “Cold brew vs iced coffee,” “How much caffeine is in cold brew,” “How to make cold brew concentrate.”

Three linking rules hold the structure together:

1. Every spoke links to the pillar with descriptive anchor text, usually early in the article.
2. The pillar links to every spoke from the section that summarizes that subtopic.
3. Spokes link to each other only where a reader genuinely needs the next step, for example from “cold brew ratio” to “how to make cold brew concentrate.”

The internal linking strategy guide covers anchor text and link placement in more detail.

Decide which keywords belong together using SERP overlap rather than word similarity. If Google shows mostly the same URLs for “cold brew ratio” and “cold brew coffee to water ratio,” those two queries belong on one page. If the results for “cold brew concentrate” and “cold brew ratio” barely overlap, they need separate spokes. Keyword clustering by SERP overlap explains the method.

How to map topical coverage, step by step

A coverage map is a table that lists every subtopic you need to cover, the queries behind it, and the single URL responsible for it. Build it before you write anything.

Step 1: Collect the query universe. Pull keywords from your research tool, Search Console queries you already get impressions for, People Also Ask boxes, related searches, and your sales or support inbox. For cold brew, support emails asking “why does my cold brew taste bitter” are as useful as any tool export.

Step 2: Cluster by SERP overlap. Group queries that share ranking URLs. Each group becomes one page.

Step 3: Label intent and page type. Informational guide, comparison, recipe, product or category page. A query like “cold brew maker” probably wants a product or category page, not a blog post, so it may belong to your shop.

Step 4: Assign one URL per group. Mark each row as existing (with its URL), missing, or needs merging. If two existing URLs serve the same group, you have a cannibalization problem to fix first; see how to find and fix keyword cannibalization.

Step 5: Mark the gaps that matter most. Prioritize subtopics that the top-ranking competitors all cover and you don’t, then subtopics nobody covers well.

Step 6: Decide what to leave out. Not every query deserves a page. “Cold brew stock price” has nothing to do with a coffee brand. Scope keeps the cluster coherent.

Here is what a slice of the cold brew map might look like:

In SupaDraft, the Terrain map shows this as a live topographic map: keywords grouped into clusters by SERP overlap, volume as elevation, difficulty as hatching, and your current Search Console rankings as pins. You can lasso keywords into a new cluster or drag a keyword to a different one when your judgement disagrees with the grouping, then switch to the table view to work through it row by row.

Build the cluster in the right order

The order you publish in affects how quickly the cluster starts working.

1. Fix overlaps first. Merge or retarget competing URLs so each subtopic has one owner.
2. Publish or upgrade the pillar early. Spokes need a destination to link to. The pillar can launch lean and grow as spokes go live.
3. Ship spokes with existing demand first. Start with subtopics where you already have impressions or “almost ranking” positions, because they show the fastest response.
4. Then fill the gaps. Move on to missing subtopics, highest value first.
5. Update the pillar each time a spoke ships, adding the summary paragraph and link.

Each spoke should start from a brief that names its one primary keyword, the questions it answers, and which pages it links to. The content brief template gives you a structure to reuse. To turn the order into dated work your team can actually ship, see how to build an SEO content calendar.

How do you measure topical authority in Search Console?

There is no single number, so track a small set of indicators monthly in a spreadsheet.

Set up the filters. In Search Console, open Performance, then Search results. Add a query filter, choose “Custom (regex)”, and enter a pattern that captures the topic, such as cold ?brew|cold-brew. Search Console uses RE2 regex syntax. If your cluster lives in a folder, add a page filter too, for example a regex on /cold-brew/.

Track these indicators:

1. Cluster impressions. Compare the last three months against the previous three. Rising impressions across the regex mean Google is showing you for more of the topic, more often.
2. Query breadth. Export the queries table and count distinct queries with impressions. This is often the earliest sign of growing authority, because Google tests you on long-tail queries before it ranks you well for them.
3. Top-10 share. Of those queries, what share has an average position of 10 or better? Track the percentage, not the raw count, so it isn’t skewed by breadth growth.
4. Almost-ranking queries. Count queries in positions 8 to 20. These are your next wins, usually through a section update or better internal links.
5. Time to first impressions for new spokes. Note the publish date of each new spoke and the date it first shows meaningful impressions in the Pages tab. If later spokes get picked up faster than early ones, the cluster is gaining trust.
6. Pillar position for the head term. Filter to the exact head query and watch the pillar’s average position. It usually moves last.

Read the data carefully. Average position blends every query a page appears for, so always filter to a single query before judging a page’s ranking. Search Console also omits some rare queries for privacy, so query counts are a floor, not a total. And compare like with like: equal-length windows, ideally the same months year on year if the topic is seasonal. Cold brew interest climbs in warm months, so a summer jump may be weather rather than authority.

Common mistakes that stall topical authority

• Publishing spokes with no pillar, leaving a pile of orphaned articles with no hub.
• Two pages for one intent. Writing both “cold brew ratio” and “cold brew coffee to water ratio” splits signals and confuses Google about which to rank.
• Thin spokes written to fill a map. A 400-word page that restates the pillar adds nothing. Each spoke must answer its question better than the pillar can.
• Never updating the pillar. If the pillar doesn’t link to new spokes, they rely on discovery alone.
• Drifting off topic. A coffee brand publishing general productivity tips dilutes the signal you are trying to build.
• Judging too early. New clusters take months to show in rankings. Watch breadth and impressions first.

Frequently asked questions

How many articles do you need for topical authority?

There is no fixed number. You need enough pages to answer the distinct intents in your coverage map well. For a narrow topic that might be eight pages, for a broad one many more. Coverage of real intents matters more than volume.

How long does it take to build topical authority?

Expect months rather than weeks. Query breadth and impressions usually move first, then top-10 share, then the pillar’s position for the head term. Track monthly and compare equal date ranges.

Is a pillar page the same as a long-form guide?

Not quite. A pillar is a broad overview that summarizes each subtopic and links to the spoke that covers it in depth. A long guide that tries to answer everything in one URL usually serves each intent less well.

Can a small site build topical authority?

Yes. Small sites often do it faster by choosing a narrow topic and covering it completely. A coffee brand that owns cold brew thoroughly can outrank larger generalist sites on cold brew queries.

Map your first cluster

Pick one topic you want to own, list every question your customers ask about it, and give each one a single URL. Then open the Terrain map in SupaDraft, connect Search Console, and map your first cluster to see where you already rank and where the gaps are.