A site I work on had a hosting section. Twelve pages, ten languages, 120 URLs. It had been live for two to three years. Zero organic sessions. Zero revenue. Google buried it, and the data said Google was right.
A note on what is missing here. This was client work with a team, which is why it reads as “we” and why the domain stays unnamed. The raw traffic numbers are not mine to publish. The method and the structure are, and those are the parts that transfer. It is the same trade the research pillar makes whenever the records carry client detail: name what was withheld, publish what can be checked.
The content was single-provider advertorials dressed up as guides. No methodology. No comparative data. No reason for this site to be the authority on hosting. The parent domain had strong sections elsewhere, but authority doesn’t trickle down. Each section either earns its own credibility or it doesn’t rank.
Clean Doesn’t Mean Ready
We cut eight of twelve pages and rewrote the survivors. Fixed contradictory ratings (one provider scored 5/5 in the summary, then was called “unsuitable for enterprise” three paragraphs later). Removed redundant providers owned by the same parent company. Interlinked the cluster. Tightened the SEO.
It read well. It looked right. An independent AI review scored it 4-6 out of 10. The verdict: commodity. The structure was clean, the SEO was better, but the content said nothing a competitor couldn’t say. There was no moat.
What a Moat Looks Like
Other sections of the same site had moats and ranked for them:
| Section | What it can say that competitors can’t |
|---|---|
| Leg 1 | Real testing infrastructure, API access, lab data with published methodology |
| Leg 2 | An origin story no competitor can replicate. Evergreen by nature. |
| Leg 3 (before) | Nothing. Same stale research anyone could compile. |
| Leg 3 (after) | Security posture scans across 12 providers, with scores no one else publishes |
Leg 3 had inherited nothing from the parent domain. It needed its own angle.
Building the Gap
We researched what already ranks. Every competitor evaluates hosting by speed and uptime. That’s commoditized. Nobody evaluates providers by security posture. Not TLS configuration, not security headers, not server-level defaults.
So we ran SecurityHeaders.com scans on twelve provider domains. The results were genuinely surprising: one of the most popular hosts scored F with zero security headers. Only one provider earned an A. We cited speed benchmarks from two independent monitoring sources with dates and methodology links. Every number on the page now has a public, reproducible source.
The same independent review scored the rewritten pages 7-8 out of 10. The gap closed because the content now had something competitors would have to do real work to replicate.
The Rule
Every child section of a product needs its own moat. You can’t inherit authority from the parent domain. You can’t borrow credibility from a sibling section. If you can’t name the one thing your page says that a competitor’s page can’t, the page isn’t ready.
Clean structure, good links, and solid SEO are table stakes. The moat is what earns the rank.
Related:
- I Built 4 SaaS Products With AI. Total Revenue: $279.: the same no-moat problem, costed out across a year of products
- AI Trusts Your Docs. That’s the Problem.: Clean on paper is not the same as correct
- 5 Structural Patterns That Survive Every Code Review: What looks good file-by-file can miss the aggregate picture
- Audit Before You Spread the Mess: debt you can’t see until you audit