We scanned 5,034 data claims across 961 SaaS blog posts on 46 domains. 31% cited no source at all. Among the claims borrowed from other people's research, 70% carried no external link a reader could follow to the source. That's the condition of these posts on publication day, before a single source has had time to move.
Content debt is the accumulated liability of unverifiable claims in published content. Every statistic your posts contain is a promise that a reader who checks the number will find it true. Content debt is the distance between that promise and what the source says today, and it grows without anyone deciding anything.
A 50-post blog averaging five data claims per post is carrying 250 separate promises. The unit of content debt is the claim, and each claim ages on a schedule nobody set.
Defining Content Debt at the Claim Level
The common content debt definition treats it as a volume problem: too many old posts, too few writers refreshing them. Teams that accept that framing respond with more of the same medicine. More review cycles. A refresh contractor. A quarterly slot on the calendar.
The framing fails at the unit. One post can hold five data claims, each tied to a different source, each drifting at its own speed. Read the post top to bottom and you'll know whether the prose still holds up. You still won't know which of the five numbers inside it has moved.
Ward Cunningham coined technical debt for the cost of shipping code you know you'll have to revisit. Engineering teams write that cost down; the shortcut goes on a backlog with a name attached. Content debt has no ledger anywhere. Every post carrying a benchmark, a market share figure, or an attributed finding adds to the balance, and nobody keeps the inventory. The hidden cost of outdated charts is one line item on that missing ledger.
Content Decay vs Content Debt
When a post bleeds traffic over 12 months, content decay names the outcome you see in Search Console. Content debt names the cause: the claims inside the post drifted from their sources and nothing flagged the drift. Fixing broken links treats one symptom. Rewriting tired paragraphs treats another. The claims stay unwatched either way.
The instinct in content marketing teams is to blame process. Writers should double-check. Audits should run more often. Someone should own the maintenance calendar.
A team of five managing 200 posts at five claims each is answering for 1,000 separate assertions about the world. Discipline doesn't scale to 1,000 promises. I've never seen it scale past a few hundred. Beyond that point, infrastructure has to carry part of the load.
How Content Debt Accrues
A post starts accruing content debt the day it goes live. The liability is on the books before the first source changes.
Our SaaS blog claim attribution study put numbers on that starting balance: of 5,034 claims across 961 posts, 31% cited no source at all, and no publishing dashboard flagged a single one. That condition has a name, freshness theater. Every metric green, every claim unverifiable.
The blog source verification study traced the borrowed claims specifically. Of 3,299 third-party claims, 70% carried no external link a reader could follow to the source, checked against the claim's own paragraph rather than whatever link happened to sit elsewhere on the page. Among the 30% that did link out, about 20% of those links were already dead, gated, or broken. The pages load fine. The verification trail was never there.
None of the 46 domains in the scan had stood up a living content infrastructure to watch its claims, so all of them accrue on the same terms: automatically, whether or not anyone is looking.
Claims Nobody Owns
Claims age at different speeds. A statistic stamped with a publication year expires on a schedule you can predict. Market share moves quarterly. Pricing changes overnight with no announcement. The hardest case is the methodology-dependent benchmark, where the number keeps its face value while the study underneath it gets revised.
We found a 2023 Gartner adoption benchmark cited in 12 posts across six domains. Gartner updated the methodology in 2024 and the headline number moved by 11 points. All 12 posts still show the old figure.
When a source URL redirects to a vendor homepage, the claim becomes orphaned data: still published, still ranking, cut off from any origin a reader could verify. Stale content that gives no visual sign of being stale.
Content Velocity and Content Debt
Publishing velocity sets the accrual rate. A team shipping four posts per week at five claims each adds 1,040 new promises a year, and none of them ships with a monitoring plan. No line in the operating budget carries that balance. It compounds out of sight until someone runs the numbers.
Content Debt Audits Are Debt Service
The standard answer to all of this is the audit. Quarterly reviews, an annual deep dive, a spreadsheet naming which posts need refreshes and who owns each one.
No CFO would accept a quarterly glance at the balance sheet as a substitute for a general ledger.
A quarterly content debt audit reviews posts that have been drifting for 13 weeks. Whatever it catches, it catches late. Whatever it misses stays in print until the next cycle. That's debt service. It pays down some of the accrued balance, on a schedule, while the principal keeps growing.
There's a pattern worth sitting with: the teams running the most audits tend to carry the most content debt. A quarterly calendar is also a confession of a 13-week detection gap, 13 weeks where sources change without triggering anything and readers meet numbers that may have drifted since the last pass. The rigor of the schedule advertises the missing detection layer.
Audits also work at the wrong unit. A post-level pass asks whether the post is still accurate, which treats 200 words of prose and five separate data claims as one object. A claim-level pass asks whether this specific statistic, from this specific source, is still current. Post-level review scales with your post count. The liability scales with your claim count. Every post you publish widens the gap between those two numbers, and no audit cadence closes it.
How to Measure Content Debt
Content debt comes down to three variables: how many claims you've published, how likely each one is to have gone stale, and what it costs to verify or fix one. Multiply the three and you get a dollar figure content teams have never had a way to compute.
Claim count is the base. 100 posts at five data claims each is 500 promises. Stale probability tracks age and review history: an 18-month-old post nobody has touched carries more risk than a six-month-old post refreshed last quarter. Cost per claim tracks complexity. Checking a plain statistic against a live source takes minutes; re-sourcing an orphaned benchmark whose study got retracted takes hours. Run that across 500 claims and the content maintenance cost of a mid-sized blog turns into a budget line nobody planned for.
The formula is arithmetic. The reason nobody runs it is the input. Teams count posts, words, and sessions, and they have never once counted their claims.
How your team answers the next question says more than any content debt audit you've run.
Most content teams have a process for reviewing posts. Few have a system for counting the claims inside them. That distinction is the gap between knowing you have a content library and knowing what it owes. The formula only works when the input exists, and the input is an inventory most teams have never built.
The spread above sorts teams into two groups: those who have counted their claims and those who have not. The calculator below takes your claim count and returns the dollar figure.
I've watched teams fall silent at that number. It appeared in no planning document. The balance was already there; the formula just made it visible.
Getting Out of Content Debt
There is an exit, and it starts with changing the unit of management.
The teams that retire content debt track the claims inside their posts. Every data point has a source on record. Every source stays under watch. When a source moves, the claims tied to it surface on their own, in the window where an audit calendar is silent.
LiquiChart is claims monitoring infrastructure: it watches individual data points against their sources between audit dates.
Living content describes the full architecture. The short version: claims become monitored entities, and when a source updates, every post referencing it surfaces for review. The claims layer detects when published data goes stale and routes the affected posts into review.
The Content Health Scanner reads any URL and returns a claim count plus a staleness risk for every data point on the page, in seconds.
Run the audit quarterly, diligently, on time, and every claim still sits unwatched for the 13 weeks between passes.
Teams that measure their content debt find a larger number than they expected. Teams that skip the measurement carry the same balance, unmeasured.
Right now, your highest-traffic post is making claims nobody on your team has verified since the quarter it shipped.