I think of topical authority as territory. A territory has borders (the topic map), it has ground you either hold or do not (the coverage map), it has places that matter more than others (depth tiers), it has roads connecting them (the linking pattern), it is taken in an order (the publishing sequence), and you need a way of knowing whether you actually hold it (measurement). That is the Territory Model: six moves, run in order, repeated per topic. It is the method behind my topical authority guide, written as something you can execute rather than read.
- Map
- Cover
- Tier
- Connect
- Sequence
- Measure
When to use this
Use the Territory Model when a site needs to rank for a subject rather than for a keyword. That describes most SaaS companies, most publishers, most education and finance sites, and any D2C brand whose category has a real information layer around it (skincare, nutrition, personal finance, home improvement). It is the right tool when you have the budget to publish a connected set of pages over months, not a single article.
It is the wrong tool for a one-off landing page, and it is the wrong tool if the plan is to publish more of everything. Volume without a map is the problem I describe in publishing more is not the answer. The model is also a poor fit if the business cannot say which topics it wants to be known for. Settle that first with a strategy framework, then come back.
The six moves
Move 1: Map. Define the territory's borders.
Inputs: the business's product or category, keyword research, competitor site structures, People Also Ask and related searches, support tickets and sales questions. Actions: build a topic map: a tree of the subject from the broadest concept down to the specific questions people ask, including Hindi and Hinglish phrasings where your audience searches that way. Group by meaning, not keyword string. Outputs: a topic map document with one row per node, its parent, and its estimated demand. Checks: a subject-matter expert agrees the map is complete; no node is just a synonym of another. My keyword mapping guide covers the mechanics.
Move 2: Cover. Mark what you hold and what you do not.
Inputs: the topic map, a crawl of your own site, your Search Console query data. Actions: assign every existing URL to a node on the map. Nodes with no URL are gaps. Nodes with several URLs are cannibalisation candidates. Nodes with a URL that ranks nowhere are weak coverage. Outputs: a coverage map: the topic map with a status per node (covered, weak, duplicated, missing). Checks: every URL on the site has a node, or has been marked as out of scope. If a large share of your content does not fit the map, either the map is wrong or the content is.
Move 3: Tier. Decide how deep each part of the territory needs to be.
Inputs: the coverage map, demand estimates, commercial value per node. Actions: assign each node to a depth tier. Tier 0 is the pillar: one comprehensive page per top-level topic. Tier 1 is the core subtopics that a pillar cannot do justice to in a section. Tier 2 is supporting pages: comparisons, how-tos, specific scenarios. Tier 3 is long-tail questions, often short pages or FAQ sections rather than full articles. Outputs: a tiered map with a page type per node. Checks: the number of Tier 0 pages is small, Tier 1 is the largest investment, and Tier 3 does not get full articles. The topic clusters guide explains why this shape works.
Move 4: Connect. Design the roads before building the towns.
Inputs: the tiered map. Actions: define the linking pattern as rules, not as a list of links. Every Tier 1 page links up to its pillar and across to its siblings. Every Tier 2 page links up to its Tier 1 parent and to at least two related Tier 2 pages. The pillar links down to every Tier 1 page and to the best-performing Tier 2 pages. Anchor text uses the node's name, varied naturally. Outputs: a linking rule sheet per tier and a target link count per page. Checks: no page in the cluster is more than one click from the pillar and three from the home page. The full method is in the internal linking framework.
Move 5: Sequence. Take the territory in an order that compounds.
Inputs: the tiered map, the coverage map, production capacity. Actions: publish in clusters, not in a stream. Ship the pillar and its Tier 1 pages together, or in quick succession, so the links exist from day one. Fix weak and duplicated nodes before writing new ones. Finish one cluster before opening another. Outputs: a publishing calendar grouped by cluster with explicit "cluster complete" dates. Checks: on any given date, the live content forms whole clusters rather than fragments of many.
Move 6: Measure. Find out whether you hold the ground.
Inputs: Search Console query and page data, rank tracking by cluster, the coverage map. Actions: measure at cluster level: number of queries the cluster ranks for, share of the cluster's queries where you appear, impressions and clicks per cluster, and whether Tier 2 pages start ranking faster than the first ones did. Outputs: a cluster scorecard updated monthly. Checks: cluster query count is rising, new pages in a mature cluster rank sooner than in a new one, and the pillar collects queries it was never written for, which is the clearest evidence of authority I know. I tested a version of this in the cluster test experiment.
Worked example (hypothetical)
Take an invented Indian SaaS company selling payroll software to small businesses that wants to own "payroll compliance in India" as a subject. This is an example, not a client.
Map. The territory includes statutory deductions (PF, ESI, professional tax, TDS on salary), payslip formats, payroll for contractors versus employees, state-wise rules, year-end processes, and the questions founders ask ("do I need to register for PF with five employees?"). The map ends up with around sixty nodes.
Cover. The site has forty blog posts. Twenty-two map onto nodes. Four nodes have two or three posts each competing with one another. Thirty nodes have nothing. Eighteen posts do not fit the map at all; they are generic "productivity tips" pieces.
Tier. One pillar: a complete guide to payroll compliance in India. Six Tier 1 pages, one per statutory component. Around twenty Tier 2 pages: state-specific professional tax, contractor payroll, first-hire checklist, and so on. The remaining nodes are Tier 3 questions, handled as FAQ blocks inside Tier 1 and Tier 2 pages rather than as separate articles.
Connect, Sequence, Measure. The linking rules are written before anything is drafted. The pillar and the six Tier 1 pages ship as one release, with the four duplicated nodes merged first. Tier 2 pages follow, cluster by cluster. Measurement tracks the cluster's query count monthly and watches for the pillar starting to pick up queries about topics it only mentions in passing.
Prioritisation: which territory first
When there are several topics competing for the same production budget, I score them. Demand (1 to 5) is search volume across the whole cluster, not the head term. Fit (1 to 5) is how directly the topic leads to the product. Winnability (1 to 5) is how beatable the current results are given the site's existing strength. Gap (1 to 5) is how much of the cluster is currently missing or weak. The score is Demand plus Fit plus Winnability plus Gap, with Fit counted twice, because authority in a topic that does not sell anything is a vanity project.
| Topic cluster (from the example) | Demand | Fit (x2) | Winnability | Gap | Score | Decision |
|---|---|---|---|---|---|---|
| Payroll compliance in India | 4 | 5 | 3 | 4 | 21 | Cluster 1 |
| Hiring your first employee | 4 | 4 | 4 | 5 | 21 | Cluster 2 |
| Employee benefits and leave policy | 3 | 3 | 3 | 4 | 16 | Cluster 3 |
| Small business accounting basics | 5 | 2 | 2 | 5 | 16 | Later |
| Productivity and remote work | 5 | 1 | 1 | 2 | 10 | Prune |
Two clusters tie at the top; the tie-break is Winnability, because an early win builds strength for the harder cluster. The bottom row is where the eighteen orphan posts came from, and the honest decision is to prune or consolidate them.
Common failure modes
Mapping by keyword tool export
A keyword list sorted by volume is not a topic map. It misses the questions nobody has typed in exactly that form yet, and it includes dozens of string variants of the same idea. Build the tree from meaning, then attach keywords to nodes.
Writing the pillar last
Teams publish twenty supporting articles and plan to "write the hub later". The links have nowhere to point, and the cluster looks like a pile. Pillar first, or pillar with the first batch.
Giving Tier 3 full articles
Four hundred thin pages answering one-line questions dilute the cluster and compete with each other. Fold them into FAQ sections on the page above them.
Measuring the head term only
If the only metric is the rank for "payroll software", you cannot see authority forming. Count the cluster's queries and watch the pillar's query spread.
Opening every cluster at once
Five half-built clusters are worth less than one complete one. Search engines are assessing completeness, and half-built never looks complete.
Run it yourself
- Pick one subject the business wants to be known for. One.
- Build the topic map as a tree of meanings; have an expert check it for gaps.
- Assign every existing URL to a node; mark each node covered, weak, duplicated or missing.
- Set depth tiers: one pillar, a handful of Tier 1, a longer list of Tier 2, Tier 3 as FAQ blocks.
- Write the linking rules per tier before any drafting begins.
- Merge duplicates and fix weak nodes first.
- Publish the pillar and Tier 1 pages together; then complete Tier 2 cluster by cluster.
- Track cluster query count, cluster query share, and pillar query spread monthly.
- Only open the next territory when the first one is complete and measured.
If you want this run as a programme with briefs, production and linking handled together, my content SEO service is built around it, and the SaaS SEO service applies it to the product-led version. The SaaS organic growth case study is structured around these six moves, with placeholders where verified figures belong.
FAQ
How many pages does it take to build topical authority?
As many as the topic map says, and no more. A narrow subject might be complete at fifteen pages; a broad one might need two hundred. The question to ask is whether the territory is covered, not whether a page count has been hit.
How long before authority shows up in results?
Content programmes take months, not weeks. In my experience the first visible signal is usually new pages in a cluster ranking faster than the first ones did, which tends to appear after the cluster is complete rather than while it is being built.
Does this work for e-commerce category pages?
Yes, with the category page as the pillar and buying guides, comparisons and care guides as the tiers beneath it. The linking pattern matters even more there, because category pages often have no editorial content of their own. See the e-commerce SEO guide.
How does this relate to semantic SEO?
Semantic SEO is about how a single page and its entities are understood; topical authority is about how a connected set of pages is understood together. The Territory Model works at the set level; the semantic SEO guide covers the page level.