Topical authority is the third pillar of Search Quality Assurance (SQA-200)™ and carries a budget of forty points across fourteen checkpoints. It asks whether the content covers its subject as a deliberate map with one owning page per intent, or as a backlog of articles that happen to share a category.
Hub and spoke: why a map beats a publishing backlog
A hub and spoke architecture designates one page as the destination for a topic and surrounds it with supporting pages that answer narrower questions and link inward. The alternative, which most sites arrive at without choosing it, is a chronological backlog where every article is peer to every other and relevance is inferred by an engine from whatever the internal links happen to say.
The difference shows up in how the two structures fail. A map fails visibly: a missing spoke is an intent with no page, and the gap is in the map. A backlog fails invisibly: coverage looks complete because many articles exist, while the intent that converts has three partial answers spread across three posts and no page that owns it.
Intent mapping across the decision ladder
Checkpoint P3.06 requires every URL to be categorized by the stage of the decision it serves, and the framework maps those stages onto the five rungs of Decision Ladder Navigation: Orientation, Comparison, Proof, Price and Action. Categorizing a URL means committing to one rung, not noting that a page touches several.
The commitment is what makes the category useful. A page assigned to Comparison is then held to what a comparison-stage reader needs, and its internal links are expected to hand the reader upward rather than sideways. A page that claims three rungs is a page whose next step cannot be designed, which is precisely the failure the fifth pillar has to clean up later.
Cannibalization: the failure that looks like productivity
Cannibalization is two or more pages competing for the same intent, and checkpoint P3.13 exists because it is the one content failure that looks like success from the inside. The team published more, the archive grew, and the reporting shows activity. The engine, meanwhile, has to choose between near-identical candidates and distributes the signal across them instead of concentrating it.
Auditing for cannibalization means grouping URLs by the intent they target rather than by the keyword they mention, then consolidating each group to one owning page and redirecting the rest. The consolidation is the uncomfortable half, because it deletes work that took effort to produce. Keeping both pages is the option that preserves the effort and the problem together.
The fourteen content hub checkpoints
Below are the fourteen itemized checkpoints of pillar three. Six architectural items carry three points each, seven page-level items carry two, and the quarterly refresh item carries three, reflecting that a map left unmaintained stops describing the site within a year.
| Item | Checkpoint | Weight | Verification and execution standard |
|---|---|---|---|
| P3.01 | Topical Map Blueprint | 3.0 pt | Architect complete topical map mapping all core entities, sub-topics, and user intents. |
| P3.02 | Pillar Money Page Role | 3.0 pt | Designate high-converting pillar pages as destination hubs for cluster traffic. |
| P3.03 | Supporting Cluster Content | 3.0 pt | Publish comprehensive supporting cluster posts covering specific MOFU/TOFU questions. |
| P3.04 | Internal Link Silo Rigor | 3.0 pt | Restrict internal linking within topical silos, preventing cross-silo link equity leakage. |
| P3.05 | Contextual Anchor Precision | 3.0 pt | Use exact-match entity anchor text for internal links, banning 'click here' or generic phrases. |
| P3.06 | Intent-Funnel Mapping | 3.0 pt | Categorize every URL into TOFU (problem), MOFU (compare), or BOFU (action) intent. |
| P3.07 | Heading Hierarchy Logic | 2.0 pt | Maintain strict single H1 per page followed by logical nested H2/H3 sub-sections. |
| P3.08 | Intro Answer Placement | 2.0 pt | Deliver direct answer in first 50 words under H1 before detailed topic breakdown. |
| P3.09 | Experience Proof Stacking | 2.0 pt | Embed original data, case study metrics, or video proof inside technical guides. |
| P3.10 | Fact-Checking Citation | 2.0 pt | Cite authoritative primary sources (studies, standards) for all factual claims. |
| P3.11 | Scannable Typography | 2.0 pt | Format long-form text with short paragraphs, bold key terms, and bulleted lists. |
| P3.12 | CTR Asset Optimization | 2.0 pt | Craft compelling Title tags (< 60 char) and Meta Descriptions (< 155 char) with clear value. |
| P3.13 | Cannibalization Audit | 2.0 pt | Audit site for duplicate target intents, consolidating competing URLs into primary hub. |
| P3.14 | Quarterly Content Refresh | 3.0 pt | Maintain quarterly schedule to update outdated stats, broken links, and search intents. |
How to score the topical authority pillar
Scoring the topical authority pillar means summing the weights of the checkpoints that pass, and the weighting is deliberately uneven: the six architectural items carry three points each while the page-level craft items carry two. An auditor who passes every craft item and fails the architecture scores badly on purpose, because that is the state the pillar exists to catch.
Two items resist a quick verdict and should be scored last. The topical map is judged against the intents the business actually serves rather than against its own internal tidiness, and cannibalization is judged by grouping URLs by target intent rather than by the keyword each one mentions. Both take longer than the other twelve combined, and both are where the pillar's real findings come from.
What topical authority hands to AI-ready extraction
Topical authority hands the next pillar a page per intent, which is what makes extraction formatting worth doing. Answer-first structure applied to a page that does not own its question improves a candidate that was never going to be selected, so the fourth pillar's thirty points are contingent on the third pillar's map being real.
Continue to pillar four, AI-Ready GEO and AEO Optimization, which formats those owning pages so a generative engine can lift the answer out of them.
Frequently asked questions about the topical authority pillar
These are the questions readers ask most often about the topical authority pillar of SQA-200. Each one is answered directly from the deposited specification, in a few sentences, so that the answer can be read, quoted and cited on its own without the rest of this page.
Where should the direct answer appear on an SQA-200 page?
The direct answer should appear in the first 50 words under the H1, before the detailed breakdown of the topic. Checkpoint P3.08 audits this placement, because a reader and a parser both decide early whether the page answers their question.
How often should content be refreshed under SQA-200?
Content should be refreshed every quarter under SQA-200. Checkpoint P3.14 sets a quarterly schedule for updating outdated figures, broken links and search intents, and it carries 3 points, more than most items in the pillar.
How long should title tags and meta descriptions be?
Checkpoint P3.12 sets targets of under 60 characters for a title and under 155 for a meta description, each with a clear value. Google truncates snippets to fit the device, so the targets keep the key words inside the visible part.
How to score the SQA-200 topical authority pillar
These steps let you score the topical authority pillar of SQA-200 in the intended order, checking quick craft items first and leaving the topical map and cannibalization audit for last.
- List the fourteen checkpoints and weightsWrite out items P3.01 to P3.14 with their weights, six architectural items at three points, seven page-level items at two, and the quarterly refresh at three.
- Check the page-level craft itemsVerify heading hierarchy, intro answer placement, experience proof, fact-checking citations, scannable typography and title and meta description targets, and give each passing item its two points.
- Test the internal link siloConfirm that internal links stay within their topical silo and that anchors use exact-match entity text, with no 'click here' or generic phrases.
- Categorize every URL by intentAssign each URL to one rung of the decision ladder, Orientation, Comparison, Proof, Price or Action, and fail any page that claims several rungs at once.
- Judge the topical map against real intentsScore the topical map late, comparing it with the intents the business actually serves, and treat each missing spoke as an intent with no page.
- Audit cannibalization by target intentGroup URLs by the intent each one targets, then consolidate each group into one owning page and redirect the competing URLs to it.
- Sum the weights of passing checkpointsAdd the weights of every checkpoint that passes toward the budget of forty points, expecting a low score wherever the craft passes and the architecture fails.
FAQ about Topical authority
Why does a site with many articles still lack topical authority?
A large archive often hides gaps. In a chronological backlog every article is peer to every other, so coverage looks complete while the intent that converts has three partial answers spread across three posts and no page that owns it. A hub and spoke map makes that gap visible as a missing spoke.
Why is cannibalization so hard to notice from inside a team?
Cannibalization looks like success from the inside. The team publishes more, the archive grows and the reporting shows activity. Meanwhile the engine has to choose between near-identical candidates competing for the same intent and spreads the signal across them, so no single page concentrates it.
Is it a mistake to keep both pages when two URLs target one intent?
Yes, keeping both pages preserves the effort and the problem together. The cannibalization audit groups URLs by target intent, consolidates each group to one owning page and redirects the rest. Consolidation feels uncomfortable because it deletes work that took effort to produce, yet it is the half of the audit that fixes the competition.
What goes wrong when a single page tries to serve several decision stages?
A page that claims several rungs of the decision ladder has a next step that cannot be designed. Checkpoint P3.06 asks you to commit each URL to one rung, so the page is held to what that stage's reader needs and its internal links hand the reader upward. Otherwise the fifth pillar has to clean up later.
How many points and checkpoints does the topical authority pillar carry?
The topical authority pillar carries a budget of 40 points across 14 checkpoints, items P3.01 to P3.14. Architectural items carry three points each, page-level craft items carry two, and the quarterly content refresh carries three. It is the third of six pillars in SQA-200.
Why do architectural checkpoints weigh more than page-level craft items?
Architectural decisions determine whether page-level work compounds or cancels out. Building the topical map, designating the pillar pages and enforcing the link silo are worth more than tightening a title tag. A well-written article inside a silo that competes with itself is still a well-written article, and it still loses.
What is the difference between a hub and spoke map and a publishing backlog?
A hub and spoke map designates one page as the destination for a topic, with supporting pages that answer narrower questions and link inward. A publishing backlog is chronological, every article is peer to every other, and an engine infers relevance from whatever the internal links happen to say. A map fails visibly, a backlog fails invisibly.
Which checkpoints should an auditor score last in the topical authority pillar?
Score the topical map and the cannibalization audit last. The topical map is judged against the intents the business actually serves, and cannibalization is judged by grouping URLs by target intent. Both take longer than the other twelve checkpoints combined, and both are where the real findings of the pillar come from.
What is topical authority in the SQA-200 framework?
Topical authority is the third pillar of the Search Quality Assurance framework, SQA-200, with a budget of 40 points across 14 checkpoints. Topical authority asks whether content covers its subject as a deliberate map with one owning page per intent, or as a backlog of articles that happen to share a category.
What is content cannibalization and how do you fix it?
Content cannibalization is two or more pages competing for the same intent, which forces a search engine to split the signal across near-identical candidates. To fix cannibalization, group URLs by the intent they target, consolidate each group into one owning page and redirect the rest. In SQA-200, checkpoint P3.13 audits for cannibalization.
Does a site need topical authority before optimizing for AI answers?
Yes, in SQA-200 topical authority comes before AI-ready extraction. Answer-first formatting applied to a page that does not own its question improves a candidate that was never going to be selected. The thirty points of the fourth pillar, AI-Ready GEO and AEO Optimization, are contingent on the topical map of the third pillar being real.
Where should I start when building topical authority for a site?
Start building topical authority with a topical map that covers every core entity, sub-topic and user intent the business serves. Then designate pillar pages as destination hubs, publish supporting cluster posts for narrower questions, and keep internal links inside each topical silo. Each intent should end up with exactly one owning page.