A familiar shape of SEO case study: take a single site, report “rankings up by N%” with one chart, attach a quote, and call it proof. The format flatters the agency and tells the reader almost nothing. The useful version reports leading indicators, time-to- visibility on cluster queries, and citation capture across AI engines — because those are the things topical authority work actually moves first, and they survive algorithm updates that flatter-format rankings often do not.
How to Read a Topical Authority Case Study
Three reading rules before the cases. Worth setting up so the patterns become legible.
- Read leading indicators first. Rankings are the lagging confirmation. A case study that only reports rankings is either very mature (the cluster is past the build phase) or hiding that the leading indicators never moved.
- Watch the time-to-visibility curve, not the endpoint. A site that reaches position #1 in nine months tells you nothing about why. A site whose coverage ratio passes 60% in week 4 and whose citation capture starts moving in week 6 is reproducible.
- Pay attention to the perimeter, not the head term. Most case studies celebrate head-term wins. The interesting story is usually in the long tail — how many cluster queries the site now ranks for, and how many AI engines cite it on cross-cluster questions.
Three Composite Patterns
Each pattern is a composite drawn from multiple customer engagements with similar profiles. Numbers are smoothed across cases and rounded; the shape of the curve is what reproduces. Where a single case diverged sharply from the composite, that divergence is called out separately.
Pattern A — Early-Stage SaaS, Narrow Niche
Profile: 6–18 months old, 8–20 existing pages, single product, DR 5–15, no established cluster.
- Before
- Eight to twelve scattered blog posts targeting head terms in the product's category. Median position 28 on the head term. Zero citations across ChatGPT, Perplexity, AI Overviews on cluster queries. Cluster coverage ratio approximately 15% against the topic graph.
- Intervention
- Twelve weeks. Mapped the topic, identified the canonical entity, wrote 12–15 perimeter pages keyed to coverage gaps rather than search volume, restructured the existing pages to share entity definitions, built two bridges into the adjacent topic. See the four-step playbook for the operational detail.
- After
- Week 4: coverage ratio at 50%, citation capture at 8% (vs 0% baseline). Week 8: long-tail rankings appear across 40–60 cluster queries, head term moves from 28 to 14. Week 12: citation capture at ~25% on the cluster's core query set, head term in the top 10 region on most-tracked cluster keywords.
- Takeaway
- Time to visibility for a coherent 12-page cluster on an under-saturated niche is roughly 8 weeks for AI citation, 12 weeks for Google long-tail consolidation, 4–6 months for the head term.
Pattern B — Established Consultancy, Saturated Head Terms
Profile: 3+ years old, 80–200 existing pages, mixed topics, DR 25–45, head terms ranked at positions 8–20 with no movement in 12+ months.
- Before
- Strong general SEO; weak cluster coherence. Head-term page on the target topic ranked at position 11 for 18 months with no progress despite continued publishing. Cluster coverage ratio at 35%; entity-definition coherence at ~60% (the same entity is defined three different ways across the site). Zero AI citations on the cluster's bridge queries.
- Intervention
- Sixteen weeks. Cluster audit first — identified the perimeter gaps and the definitional drift. Rewrote definitions across the existing 22 cluster pages to land on one canonical phrasing. Published 8 new perimeter pages on the highest- betweenness gaps. Restructured internal links so perimeter pages consistently point at the central article. Added 3 bridges. See the measurement guide for the indicators tracked through the build.
- After
- Week 6: coherence ratio at 92%, citation capture at 15% (vs 0% baseline). Week 10: long-tail rankings expand from ~120 to ~340 cluster queries. Week 14: head term moves from position 11 to position 4. Week 16: citation capture at 38% on the cluster's bridge queries — the canonization signal.
- Takeaway
- For established sites with saturated head terms, the highest-leverage intervention is usually definitional reconciliation across existing pages, not new publishing. The head term moves when the network around it becomes coherent.
Pattern C — B2B Technical, Long Decision Cycle
Profile: enterprise product, 50–80 pages, DR 20–35, decision cycles 3–6 months, perimeter queries dominated by Reddit, forums, and competitor docs.
- Before
- Strong commercial pages, weak educational coverage. Cluster coverage ratio at 25%, mostly on commercial intent terms. Customers find the brand through paid search or referrals, not organic discovery. Zero AI citations across all monitored cluster queries — competitor docs and Reddit threads dominate the citation surface.
- Intervention
- Twenty weeks. Built the cluster on the educational perimeter — concept pages, how-it-works pages, comparison pages, and a measurement framework page keyed to the perimeter queries that AI engines couldn’t cite cleanly. Made every page extractable: 40–60 word definitions in the first 100 words, entity-named headings, comparison tables on every bridge edge. Specifically targeted citation-capture queries first, head-term rankings second.
- After
- Week 6: 12 new pages published, citation capture moves from 0% to 18% on educational queries. Week 12: citation capture at 42% on educational queries; AI engines now cite the brand consistently on cross-cluster bridge questions. Week 20: 28% citation capture on commercial-adjacent queries (queries that ChatGPT routes through educational sources before naming brands). Long-tail rankings expand by ~5x; head-term consolidation lags as expected for long-cycle B2B.
- Takeaway
- For B2B with long decision cycles, AI citation precedes Google ranking and precedes pipeline impact by 1–2 quarters. Optimizing for citation directly is the more efficient strategy than chasing head-term rankings.
Time to Visibility: What's Typical
A reference table from across the documented patterns. Use as planning input, not as a guarantee — site age, niche maturity, and competitive density all shift the curves.
What These Cases Did Not Do
Three things worth naming explicitly because they correlate with most failed builds.
- No volume-first publishing. None of the three cases prioritized the highest-volume head terms. Coverage gaps in the topic graph dictated the calendar.
- No paid-link campaign during the build. The cluster builds first; external links arrive after. Cases that attempted to accelerate with bought links consistently produced flat or negative coherence signals.
- No rewriting of the head-term page to chase rankings. The head-term page mostly did not change. The cluster around it did. Rankings on the head term moved as a downstream effect of cluster consolidation.
Common Misconceptions
Submit Your Own Case
KeywordGraph runs ongoing customer case work and publishes anonymised results as new patterns consolidate. If you are running a topical authority build — on KeywordGraph or elsewhere — and want the diagnostic framework applied to your data, the team will audit the build and publish the pattern with your permission.