Content debt is the future work an organisation creates when it publishes without planning to maintain, reuse or retire what it publishes. Outdated pages, duplicated facts, inaccessible PDFs, unclear ownership and pages written for one channel that now have to serve several all count. None of it stops a website working today, but each makes the next change slower, riskier and more expensive.
The term borrows from technical debt, Ward Cunningham’s 1992 metaphor for the cost of shipping software quickly and not going back to rework it. The comparison holds up well. Some debt is a sensible choice: launching a service page before the content model is perfect may be the right call. Like a loan, though, it charges interest, paid in repeated work, confused readers and lost trust. Trouble begins when nobody records the shortcut, understands the interest or decides whether to pay it back.
Content debt is a broader idea than content decay, the gradual loss of accuracy as the world moves on. Decay is one source of debt. Other debt is created on the day of publication: a second page that duplicates an approved source, a PDF nobody can read with a screen reader, a campaign microsite with no owner and no end date.
Why it matters for content
Content debt usually shows up as repeated work, often in other parts of the organisation. Readers find the wrong version, support teams explain confusing guidance and editors make the same change in twenty places. Each problem looks small, while the combined effect damages trust and makes change expensive. Robert Rose puts it well: every published asset carries a maintenance obligation, a small recurring promise that it will stay true, current and findable.
A debt register turns that invisible irritation into manageable work. Each entry records the item, its consequence, an owner, the risk and the likely effort. One might read: “Opening hours are typed into 40 branch pages instead of pulled from the branch database. Consequence: every change takes two days and pages disagree. Owner: digital team. Fix: move the field into the content model.”
Some debt should be repaid quickly, some accepted for now and some cleared altogether by deleting content nobody needs. When GOV.UK content designers audited 7,396 transport pages with the Department for Transport, they concluded that “do we need to remove this page?” should be the first question, because a yes makes the others unnecessary.
The opening hours example also shows where content debt meets technical debt. The problem sits in the pages, but the fix sits in the content model. A register that covers both saves an argument about whose problem it is before anyone fixes it.
Prevention matters too. Clear ownership, structured reuse, review dates and retirement plans reduce avoidable debt, and they work best as part of everyday publishing rather than an annual clean-up.
How AI changes the picture
AI can find content debt at a scale no team could manage by hand. A well-instructed model can read an entire estate in hours, picking out duplicates, outdated references, contradictory claims and inconsistent terminology, and it can show which problems turn up most often in user questions or generated answers. It can draft the routine fixes too. People still decide what’s true now, which version is authoritative and what can go.
AI can also increase debt by making production cheap. More generated pages, summaries and variants mean more material to review, each with its own maintenance obligation. Weak source content becomes especially costly when assistants reuse it, because one outdated fact can surface in thousands of answers to people who never see the page it came from. Prompts, system instructions and retrieval sources are content too, and they belong in the same register as pages and documents.
Questions people ask
- Is all old content debt?
No. Age alone doesn’t make content debt. A stable reference can stay useful for years, while a newly published page creates debt immediately if it duplicates an approved source that will now need two updates.
- Should we fix the oldest items first?
Prioritise by consequence, frequency and future work. A small error in critical guidance may matter more than a large archive nobody uses.
- Is content debt the same as content decay?
No. Decay is the loss of usefulness over time. Debt also includes deliberate shortcuts, structural problems and neglected maintenance that create future cost. Decay that nobody deals with becomes debt.
- Can AI clear the backlog?
It can find most of it and handle a good share of the routine fixes. Someone still needs to be accountable for what’s authoritative, what’s safe to change and what’s no longer needed.
Learn more
- How To Face Your Content Debt and Get Buy-In for Fixing It – Robert Rose’s 2026 column on the maintenance obligation every asset carries, with a blunt “default-dead” rule for teams whose debt is too large to audit: treat anything older than two years as wrong until a named owner reverifies it.
- What we learned from a large scale content audit – Mark Green and Steph Wilson’s first-hand account of auditing 7,396 transport pages on GOV.UK, including what they’d do differently next time.