Topical Authority Case Study: Page 5 to Top 3 in 9 Months

Topical authority is the trust a site earns by covering one subject completely — and it can be engineered. Over a 9-month engagement, we took a niche B2B SaaS site from page 5 to the top 3 for its target-cluster queries, moving its average ranking position from 23 to 6.8 across the board.

The method was structure, not volume. We reorganized ~120 ad-hoc blog posts into clusters, wrote a pillar for each priority topic, merged or deleted what diluted the site, and linked everything deliberately.

This is the full case study: the starting state, the diagnosis, the plan, the month-by-month execution, the results, the things that broke — including one we did not expect — and a transparent note on why you should extrapolate carefully. Here is exactly what we did.

Key takeaways

• A 9-month cluster rebuild moved average position from 23 to 6.8, organic sessions up 340%, conversions up 180%, and domain rating from 32 to 41 — on a site that already had ~120 posts.
• The problem was structure, not content volume. Mapping exposed 8 clear clusters, 3 orphaned topics, and 24 thin or duplicate posts. The site was trying to be an authority on 8 things and succeeding at none.
• The plan was six moves: pick the top 5 clusters by commercial intent, write a 4,000-word pillar for each, audit every post, link pillar to spokes, publish 2 spokes per week, decay-manage quarterly.
• The first 60 days felt like nothing was happening. The 90-day mark was the inflection point. By month 9, the compounding was obvious.
• Deletions with 301s worked — and consolidation had a cost. The homepage dropped its own long-tail rankings as signals moved to the new pillars.

What topical authority actually means

Topical authority is the degree to which a site demonstrates it can answer every question around a subject — the main one, the follow-ups, and the edge cases. Search systems use it to decide whom to trust when a query in that topic appears.

It is not a metric any tool exposes directly. You infer it from coverage: does the site answer the whole cluster of related queries, or only isolated keywords? That distinction is why this case study is about reorganization first and writing second. If you want the model in abstract form, our pillar and cluster architecture post covers the design we applied here.

The starting state

The site entered the engagement looking healthy on paper and failing in practice:

• ~120 blog posts, written ad-hoc over 3 years by three different freelancers with no brief connecting them.
• No topical structure. Random keywords, no internal linking strategy. Posts targeted whatever tool suggested on the day.
• Domain rating: 32. Respectable for niche B2B, not respectable enough to explain the results.
• Average ranking position: 23. Page 5 territory — the place where content exists and traffic does not.

Every conventional “content audit” would have said: write more. We said: stop writing and look at what you already have.

The diagnosis

We mapped every post to a topic cluster — one row per URL, one column per cluster, sorted by commercial intent. The spreadsheet told the whole story in an afternoon:

• 8 clear clusters with enough posts to justify a hub.
• 3 orphaned topics that did not fit any cluster.
• 24 posts that were thin or duplicate — rewordings of the same query, or 300-word stubs with no answer inside.

The pattern was a site trying to be an authority on 8 things — and succeeding on none. Each cluster had three to six scattered posts and no hub, so Google had no reason to treat any of them as a destination. The full cluster analysis is what we now run before touching a single headline.

The site was trying to be an authority on 8 things — and succeeding on none.

That diagnosis reframed the budget too. The client’s instinct was 40 new posts. We spent the first phase on consolidation instead, because new spokes hung off a structure that did not exist would have compounded the mess.

The plan

Six moves, sequenced deliberately:

1. Pick the top 5 clusters by commercial intent. Revenue proximity beat traffic volume — clusters closest to “buy” got the pillars first, even though two of them had smaller search demand.
2. Write a 4,000-word pillar for each. One comprehensive hub per cluster, scoped to cover the entire topic, not one keyword.
3. Audit every existing post — keep, merge, or rewrite. Every URL had to earn its place against its cluster.
4. Build internal links: pillar to spoke, spoke to spoke where relevant. The link graph is where topical authority becomes visible to crawlers — the mechanics are covered in our deep dive on internal linking algorithms.
5. Publish 2 new spokes per week. Small, steady, cluster-scoped additions — never off-topic.
6. Decay-manage quarterly. A standing review of positions that slipped, refreshed or relinked before they sank.

The execution: month by month

Months 1–2: pillars and consolidation

Wrote the 5 pillars. Audited and merged 60 existing posts into the cluster structure — overlapping articles combined into single, stronger spokes rather than competing with each other in the same SERP. Deleted 24 thin posts with 301s to the most relevant pillar.

The 301 map was treated as engineering, not clerical work: every redirect pointed to the closest topical destination, checked for chains and orphans before shipping. Redirect mistakes quietly eat the authority you just consolidated — our redirect chain audit guide is the checklist we ran.

Months 3–6: spokes and links

Published 2 new spokes per week — roughly 26 new posts across the 5 priority clusters. Built internal links on the same cadence: each spoke linked up to its pillar and sideways to two or three siblings. Updated Search Console submission for every URL change so consolidation signals propagated instead of waiting on recrawl.

Months 7–9: refinement

Decay-managed underperformers: spokes that lost positions got refreshed, relinked, or folded. Added sections to top performers based on Search Console queries — the report surfacing impressions for queries the page never addressed. That query-mining loop is the whole game after month six, and hidden Search Console reports covers exactly where we looked.

The results

Measured across the full 9 months against the pre-engagement baseline:

• Average ranking position: 23 → 6.8 across the mapped set — the blended improvement behind the headline “page 5 to top 3” on the priority clusters themselves.
• Organic sessions: +340%.
• Conversions: +180% - the number that paid for the engagement.

The trajectory as logged in the engagement report, month by month on the inverted-rank axis (higher on the curve means better rank):

• Month 1: average position 22.8 (flat).
• Month 2: average position 22.0 (still flat — the gap before Google starts reweighting).
• Month 3: average position 18.2. The day-90 inflection begins.
• Month 4: average position 14.7. The first hire-rank cross.
• Month 5: average position 11.6. Cluster cross-linking compounds.
• Month 6: average position 9.6. Top-10 on the mapped clusters.
• Month 7: average position 8.4. Hub pages absorbing long-tail queries.
• Month 8: average position 7.2. Steady climb continues.
• Month 9: average position 6.8. Steady-state where the budget plateaued.

The shape matters more than the numbers — budgets that quit at week six never see the bend. The flat-first 60 days are the most dangerous part of the engagement, because the work looks unproductive right until it is not. The advice we give every client: commit to 90 days minimum before reading the curve.

• Domain rating: 32 → 41. Mostly earned, not bought: comprehensive hubs attract links that scattered posts never did.

Two interpretation notes, because raw percentages flatter. The +340% session figure is from a low base — page 5 is a discount bin, and climbing out of it produces steep percentage curves that look absurd next to absolute numbers. And the conversion lift tracks the intent-first cluster ordering: the traffic grew closest to revenue, which is the entire point of sorting clusters by commercial intent in step one.

What didn’t work

Honesty section, because case studies only show the green lines:

• The orphaned topics lost rankings. The 3 clusters we did not address decayed visibly as we consolidated around the priority five. We expected that. Coverage gaps get exploited by competitors and punished by algorithms.
• The homepage dropped — and we did not expect that. It had quietly ranked for long-tail queries over three years. As we consolidated signals into the new pillars, the homepage lost its own long-tail rankings. The lesson: homepages hoard incidental relevance. Before a restructure, export the homepage’s ranking queries and give each one a deliberate destination, or you will trade pillar gains for homepage losses.

Both failures were recoverable and were addressed in the month 7–9 phase. Neither belongs in a highlight reel.

Methodology and limitations

A case study is not a controlled experiment, so here is the fine print:

• Single site, single window. One niche B2B SaaS domain, 9 months, one market. No control group, no parallel site.
• Confounders exist. Seasonality, brand growth, and normal content aging all moved during the window. We cannot isolate their share of the lift from the restructure’s share.
• Third-party metrics. Domain rating is an external proxy, not a Google measurement, and average position is a blended number across clusters of very different sizes.
• Reproducibility is directional. The sequence and cadence should transfer to other content sites. The magnitudes — +340%, 23 → 6.8 — belong to this site.

We publish the limitation because the alternative is a testimonial with headings.

How to replicate this playbook

The condensed version for your own site:

1. Map before you write. Export all posts, assign each to a cluster, flag thin and duplicate pages and orphans. If you cannot name a post’s cluster, that is the finding.
2. Rank clusters by commercial intent, not volume. Five hubs done well beat fifteen done shallowly.
3. Write the pillar before more spokes. The hub is what turns a pile of posts into a topic.
4. Merge aggressively, redirect carefully. One strong page beats three competing ones; every 301 needs a topically close target and no chains.
5. Ship spokes on a fixed cadence — 2 per week is sustainable and steady beats sprints.
6. Instrument by cluster. Track average position, impressions, and conversions per cluster in Search Console, not site-wide. Site-wide averages hide exactly the decay that quarter-two reviews catch.

The full editorial cadence — briefing, decay checks, refresh triggers — lives in our content strategy guide.

The lesson

Topical authority is a long game. The first 60 days felt like nothing was happening. The 90-day mark was the inflection point. By month 9, the compounding was obvious.

That curve is the planning fact most teams miss. Budgets organized around monthly traffic reports kill this playbook in month two, right at the flat part of the curve. If you cannot hold a 90-day window — ideally two — before judging, do not start. Plan for the 90-day mark, instrument by cluster so the early movement is visible somewhere other than the homepage graph, and let the compounding arrive.

Frequently asked questions

How long does it take to build topical authority?

On a site with existing content, expect the first 60 days to look flat, an inflection near day 90, and clear compounding by month six to nine. On a new site, add the time it takes to publish the clusters at all. The reorganization here showed its shape in one quarter and its results in three.

How many posts do you need for topical authority?

Fewer than the checklists claim, mapped completely. We consolidated 120 scattered posts into 8 clusters and acted on 5 — the work was mostly merging and linking, not new writing. Coverage of a topic’s real question set beats raw volume every time.

Should I delete thin content or rewrite it?

Rewrite or merge when the underlying query has demand — combine overlapping posts into one strong page. Delete with a 301 to the most relevant pillar when the query is worthless or already covered. We deleted 24 posts and redirected every one. Leaving thin pages up dilutes the cluster you are trying to strengthen.

Is topical authority an official Google ranking factor?

No. It is an observed outcome of how relevance and trust systems work, not a switch Google documents. Practically, it behaves like a factor: sites that cover a subject completely win queries that isolated pages on the same subject lose. That is testable on your own cluster dashboards.

Did this site build links?

Not as the lever. DR rose 32 → 41 across the window, and the pillars earned links the scattered posts never attracted. But the inputs were structure, consolidation, and cadence — the authority score followed the content changes rather than the reverse.

Bottom line

Nine months, one niche B2B SaaS site, average position 23 → 6.8, sessions +340%, conversions +180%, DR 32 → 41 — produced by organizing what already existed before adding anything new.

Topical authority is won with structure and patience: map the clusters, pick five by intent, build the hubs, merge the mess, ship spokes on a cadence, and give the compounding its 90 days before your next budget review. Start the mapping pass this week — the two-column spreadsheet is the cheapest SEO diagnostic you will ever run. Then build it out with our pillar and cluster model and keep duplicates off the field with the rules in duplicate content penalties.