Ring fencing is the idea that some revenue is useful but dangerous, and dangerous revenue should be contained so that a problem in it cannot spread. Link revenue is the textbook case. It can be a healthy line, but it carries pattern risk that other income does not, and the worst outcome is a business that has quietly become dependent on it. Ring fencing link revenue means building containment in from the start, so the line stays a contributor and never becomes a load bearing wall.
Why link revenue specifically needs a fence
Most revenue streams fail gracefully. Display income dips with traffic. Affiliate income softens when a programme cuts rates. Link revenue can fail suddenly and take the underlying asset with it, because the same pattern that earns it can, if mismanaged, damage the organic visibility that the whole site rests on. A stream that can fail fast and damage the foundation is exactly the kind you isolate. You do not let it touch the structural parts of the business.
This is consistent with how we think about durability across the build thesis. We want every property to survive the loss of any single revenue line without drama. Link revenue is the line we are most deliberate about containing.
The three fences
Fence one, cap the share
The first and most important fence is a ceiling on how much of a site's income can come from link sales. Our directional guideline is the One Third Ceiling. Link revenue stays a minority of any single site's income, comfortably below the point where losing it would be a crisis. The exact figure matters less than the principle. If a site would be in trouble without its link income, the fence has already failed. Keeping the share modest is what makes the whole line safe to run, and it pairs naturally with diversification, which I cover in combining link revenue with other streams.
Fence two, isolate it from the core asset
The second fence is keeping the practice away from anything structural. Paid placements live on genuinely good content, stay relevant, and never involve interlinking your own properties or building a network that ties the site's fate to others. The core asset, the organic visibility, must never be entangled with the link programme in a way that lets a problem in one spread to the other. We never build reciprocal sitewide links between properties for exactly this reason.
Fence three, contain the practice to defensible pages
The third fence is operational. Keep paid placements on pages that would survive scrutiny on their own merits, keep volume far below what would form a footprint, and keep the whole programme small enough to manage by hand. A contained programme is one you can audit, explain, and unwind if needed. A sprawling one is not. The discipline here connects directly to the pattern thinking in the penalty risk of selling links.
What ring fencing buys you
The payoff is calm. When link revenue is capped, isolated, and contained, you can run it without anxiety, because the worst case is bounded. If the line had to stop tomorrow, the site would lose a minority of its income and keep everything that matters. That bounded downside is what lets you hold the relevance and volume discipline, because you are never desperate for the next placement. Desperation is what breaks the fences. A capped line removes the desperation.
The temptation to let the fence slip
Ring fencing is easy to design and hard to hold, because link revenue is often the highest margin income a site has. There are no production costs, no inventory, just a placement on a page that already exists. That margin makes it tempting to let the line grow past the ceiling, to take the off topic placement, to push the volume. Every one of those is a crack in a fence. The operators who keep the fences intact are the ones who treat the cap as a real constraint rather than a suggestion, and they are the ones still running healthy link income years later.
Ring fencing at the portfolio level
The same logic scales up. Across a portfolio, you never want the group's health tied to link revenue, and you never want the properties entangled in a way that lets a problem on one spread to the rest. Each site stands alone, each link programme is contained on its own site, and the group showcases the portfolio without ever wiring the properties together into a network. Containment at the site level and containment at the group level are the same instinct applied at two scales.
The principle to take away is simple. Treat link revenue as useful but dangerous, build the fences before you scale, and hold the cap even when the margin tempts you to breach it. A fenced link line is an asset. An unfenced one is a liability waiting to surface. For the wider context, the guest posts and link revenue pillar ties this together with pricing, relevance, and disclosure.
Kings Hospitality Group holds link revenue to a deliberately capped share of any single site's income with the One Third Ceiling guideline, a directional cap that keeps the line meaningful but never load bearing, so no site ever depends on a revenue source that carries pattern risk.
Common questions
What share of income should come from link revenue?
Keep it a minority. Our directional guideline holds it comfortably below a third of any single site's income, so losing the line would never be a crisis. The exact figure matters less than staying well clear of dependence.
Why not maximise link revenue if the margins are high?
Because it carries pattern risk that can damage the core organic asset. High margin does not justify load bearing dependence on a stream that can fail suddenly. Cap it, isolate it, and diversify around it.