We ran RankForge on RankForge: a structural SEO case study (79 → 87)
We use our own tool on our own site — the same audit, fix, re-crawl loop we ask customers to run. This is the unedited before/after: rankforge.cc scored 79, one module was quietly holding the whole thing down, we acted on exactly what the audit told us, and the re-crawl came back at 87. No new content, no smoothing over the numbers that didn't move. Here is precisely what happened, module by module.
Run the Authority Flow Checker on your site — free, no account.
Why we audited our own site
The honest test of a structural SEO tool is whether its own recommendations, applied to its own site, move its own number. So we run RankForge on rankforge.cc the way we tell customers to: crawl the site, read the module scorecard, fix the single biggest constraint, re-crawl, and check that the module that was broken actually recovered. This case study is one full turn of that loop, with the real report numbers from both crawls.
What this is — and isn't: This is a before/after of the structural health score — the thing RankForge measures. It is not a rankings or traffic claim. The point is to show that fixing the structural problem the audit described made the structural problem smaller.
The starting point: 79, held back by one module
The overall health score is never a separate figure — it is the weighted composite of the individual module scores (see how authority distribution is scored). That matters here, because on paper the site looked healthy: on-page SEO, page speed, content visibility, and GEO readiness were all sitting at 99–100. But the composite was stuck at 79, and the scorecard made the reason obvious — one module was an outlier.
MODULE SCORE (/100) ────────────────────── ───────────── Authority Distribution 41 <- the outlier Pillar Strength 67 Anchor Gaps 74 Topical Clusters 77 Content Visibility 99 Internal Link Strategy 99 On-Page SEO 99 Page Speed 100 GEO Readiness 100 ────────────────────── ───────────── OVERALL HEALTH 79
The report named it directly: primary constraint, Authority Distribution, verdict “fragile authority flow.” When one module is thirty-plus points below the rest, you do not need to touch the other eight — you need to understand why that one is low.
The diagnosis: an authority cliff at depth 2
Internal authority flows along links like an internal PageRank: every page passes a share of its authority to the pages it links to. When you plot average internal authority by crawl depth, a healthy site decays gently. Ours fell off a cliff.
DEPTH AVG AUTHORITY ───────── ───────────────────────────── Depth 0 99 ████████████████████ (homepage) Depth 1 80 ████████████████ Depth 2 11 ██ <- the cliff
The knock-on effects were all in the report. Fifteen strategic pages sat below median authority — high-value pages our own internal linking was failing to reach. Only 27.9% of internal links were editorial (in-body); the rest were boilerplate nav and footer links, which carry weaker signals. And the audit's top two priority fixes were “reinforce weak pillars” and “strengthen links to deep pages.” The diagnosis was consistent from every angle: authority was pooling on the homepage and top-level pages and never reaching the deeper, more specific ones.
The fix: route authority, don't publish more
We did not write a single new page. We acted on the audit's authority-routing fixes by adding a handful of contextual, in-body links from our strongest shallow hubs into the exact under-supported pages the report named. The report's PageRank what-if simulation had already modeled which pages would gain the most equity, so the work was targeted rather than a spray of links.
- chevron_rightFrom the internal linking hub into the deepest guide the model flagged (its biggest projected gainer, +17 authority in the simulation).
- chevron_rightFrom two authority-flow explainers into the page that describes how authority flow is calculated — a depth-2 page with almost no inbound editorial links.
- chevron_rightA nudge to the weakest pillar (our WordPress audit hub), lifting its pillar-strength score from 48 to 55.
The lever is placement, not volume: Net internal links went from 5,494 to 5,499 — about five links. A handful of well-placed editorial links, aimed where the simulation said equity would flow, moved a module 38 points. Adding hundreds of nav or footer links would have done almost nothing.
The result: 79 → 87, driven by one module
On the re-crawl, Authority Distribution jumped from 41 to 79 and the overall structural health score rose from 79 to 87. The authority cliff was gone — the report went from “fragile authority flow” to “moderately healthy,” and the deep-page starvation that had been the #2 priority fix was resolved outright, dropping the priority list from three fixes to two.
MODULE BEFORE AFTER Δ ────────────────────── ────── ───── ──── Authority Distribution 41 79 +38 Pillar Strength 67 68 +1 Anchor Gaps 74 73 -1 Topical Clusters 77 77 0 Content Visibility 99 99 0 Internal Link Strategy 99 99 0 On-Page SEO 99 99 0 Page Speed 100 100 0 GEO Readiness 100 100 0 ────────────────────── ────── ───── ──── OVERALL HEALTH 79 87 +8
We are showing the whole scorecard, including the parts that didn't improve, on purpose. Anchor Gaps ticked down a point (74 → 73). The editorial-link ratio barely moved (27.9% → 28.0%) — five links can't reshape a site-wide ratio. And one median-relative count, “weak strategic pages,” actually rose from 15 to 22, because it is measured against the median and the median shifts as authority redistributes. None of that changes the headline: the specific structural problem the audit described — the depth-2 authority cliff — got smaller, and the score moved because of it, not because we gamed a number.
What this proves, and what it doesn't
Read this honestly: A structural health score is a measure of internal structure, not a guarantee of rankings or traffic. Structural fixes remove a ceiling; they don't manufacture demand. On a small site the absolute numbers are modest. What this case study demonstrates is narrower and more useful: the tool's recommendations, applied literally, moved the tool's own metric in the predicted direction.
That is the loop we hand every customer. Audit the site, find the one module that is dragging the composite, fix that constraint with a few deliberate internal links rather than a content sprint, and re-crawl to confirm the module recovered. It worked on our own site; the mechanism is the same on yours.
Run the same loop on your site
- Run a structural audit and read the module scorecard — find the single lowest module, not the average.
- If it's authority, look at average authority by depth for a cliff, and at which strategic pages sit below the median.
- Fix the constraint with a few contextual, in-body links from strong shallow pages into the starved deep ones — placement over volume.
- Re-crawl and confirm the low module recovered and the overall composite moved with it.
FAQ
Is this a real audit of RankForge's own site?expand_more
Yes. Both the 79 (before) and 87 (after) figures are from real RankForge crawls of rankforge.cc, taken before and after we applied the audit's own recommendations. Nothing is fabricated or illustrative.
Does a health score of 87 mean better rankings or more traffic?expand_more
No. The structural health score measures internal structure — crawl paths, authority flow, clusters — not rankings or traffic. Structural fixes remove a ceiling on what a page can achieve; they don't by themselves move rankings. We deliberately frame this as a structural before/after only.
How many links did it take to move the score 8 points?expand_more
About five. Net internal links went from 5,494 to 5,499. The gain came from placement, not volume — a few editorial, in-body links aimed at the specific deep pages the PageRank simulation flagged as the biggest gainers.
Why did the overall score move so much from one module?expand_more
Because the overall health score is a weighted composite of the module scores. Eight of nine modules were already strong (99–100), so the whole site was being held back by one outlier — Authority Distribution at 41. Fixing that one module lifted the composite from 79 to 87.
Put this into practice
Run the Authority Flow Checker to see this on your own site, or run the full structural audit for the complete picture — both free, no account required.