Your Intranet Is Lying: Fixing Content Rot That Still Ranks First

A policy page sits at the top of internal search like it owns the place, even though the contact is gone, the phone extension is dead, and the “procedure” it describes has been replaced by an automated workflow.

The page is not just outdated. It is actively persuasive. It looks official, it sounds confident, and it is exactly wrong in the most operational way possible.

Stop ROT Today, Make Search Tell The Truth

Export a list of high traffic pages and flag anything without a named owner
Make owner and review-by mandatory fields at publish time for every policy and procedure page
Ship a deprecation banner template plus a brief screen walkthrough showing how to apply it
Redirect replaced procedures to the automated workflow and log the redirect as a change record
Turn on automated review reminders and escalate non-response to the content area lead
At the next governance checkpoint, the named owner confirms status, review-by is set, and search success is checked

If nobody is accountable for a page, the Intranet will eventually weaponize it.

ROT Content Turns Your Intranet Search Into a Time Machine

When a stale policy page ranks first, you are not dealing with a minor editorial defect. You are watching a knowledge system fail at its basic contract: help people do the right thing without needing a side channel.

The brutal part is that this failure mode is statistically ordinary. The vendor-led Veritas Global Databerg Report argues that a large share of organizational information is redundant, obsolete, or trivial, and it ties the mess to a predictable pattern: fear of deletion plus weak retention discipline. Treat the numbers as directional rather than independent truth, and the operational takeaway still holds: creating is cheap, deleting feels risky, and the cost shows up later as wasted time, wrong decisions, and quiet mistrust.

Here is the structural irony: the Intranet is often sold as the single source of truth, but it becomes a single source of plausible misinformation when ROT is allowed to accumulate in high-visibility locations like search results.

Consider a typical organization where a team replaced a manual process with an automated workflow, but the old policy page stayed untouched because “someone might still need it.” Months later, the workflow works fine, but support tickets rise because people keep following the obsolete instructions they find first.

Information Quality Is the Hidden Adoption Metric

Most Intranet programs talk about adoption as clicks, visits, and engagement. Those are easy to count, and they look great on slides. They also miss the thing that actually decides whether people will come back: information quality under time pressure.

In information systems research, quality is not a decorative concept. Models of system success treat information quality as a driver of user satisfaction, continued use, and perceived benefit. The validated DeLone and McLean Information Systems Success Model explicitly frames information quality in terms of characteristics like timeliness and accuracy, which is a polite academic way of saying: when the system lies, people stop listening.

This is why content rot is an adoption problem even when your usage charts look stable. People can keep visiting the Intranet while quietly refusing to trust it. They open it, skim it, and then verify elsewhere. That is not adoption. That is risk management.

The primary behavioral barrier is time poverty. When people are rushed, they will not cross-check a procedure against three other pages or hunt for the “latest version.” They will follow the first thing that looks official. If your system rewards that behavior with wrong instructions, you are training distrust at scale.

Why the Old Policy Still Ranks First

It feels unfair when the wrong page wins. It is not unfair. It is math.

Enterprise search typically ranks results using multiple signals: content match, metadata, authority, and user interaction. If the wrong page has been clicked for years, linked from many places, and treated as “authoritative” by legacy navigation, it can outcompete newer, correct content that has less history. Microsoft’s description of ranking in SharePoint search result ranking makes the underlying logic explicit: ranking models combine signals from indexed content, metadata, and interaction data like clicks. Search learns from behavior. If behavior is shaped by outdated prominence, search will faithfully reinforce the mistake.

This is the part governance teams love to underfund because it is annoyingly unglamorous. Search relevance tuning, result promotion rules, and deprecation banners are not shiny launches. They are the maintenance layer that keeps yesterday’s habits from hijacking today’s operating model.

There is also a psychological trap: once a page is “known,” employees stop evaluating it. Familiarity becomes a proxy for correctness. The top search result is not just a retrieval mechanism. It is an authority signal. If that authority signal is wrong, your Intranet does not merely fail to help. It actively misleads.

Content Lifecycle Management Needs Defaults, Not Reminders

Most content rot exists because organizations treat publication as the end of work. It is the start of work. The moment something goes live, it enters a lifecycle that needs ownership, monitoring, and eventual disposition.

This is not a quirky editorial opinion. It is the logic of records management. ISO 15489-1:2016 frames records management around principles that include assigned responsibilities, monitoring, training, and recurrent analysis of business context. Translate that into Intranet terms and the message is blunt: if you cannot name who owns the page and how review happens, you do not have content management. You have content drift.

Reminders are not a lifecycle. Reminders are a guilt mechanism. A lifecycle is a default that makes the right thing easier than the wrong thing. Mandatory ownership fields. Expiration metadata. Review workflows that do not depend on someone “remembering.” Clear outcomes when a review is ignored: update, redirect, archive, or delete.

And yes, this collides with incentive reality. Creating content is visible work. Maintaining content is invisible work. Many teams reward publishing and treat deletion like vandalism. The system is doing exactly what it is incentivized to do.

What if your CMS treated “no expiry” as an exception that required justification, the same way security teams treat “no MFA” as an exception that requires justification?

Automate Retention and Disposition Where You Can

Some content must be retained for legal or historical reasons. Some content should disappear the moment it stops being operationally true. The failure is treating both types the same.

Microsoft 365 gives many organizations the mechanics to automate parts of this decision, even if governance rarely keeps up. Microsoft Purview retention policies and labels describe how retention can be applied broadly at the container level or precisely at the item level, and how retention labels can travel with content when it moves. The point is not that Purview magically fixes your Intranet. The point is that you can stop relying on human memory for lifecycle enforcement.

Use automation for what automation is good at: enforcing defined outcomes consistently. Use humans for what humans are good at: deciding what “current and operationally true” means in a changing business context. When you reverse that, you get the classic failure pattern: people are asked to remember reviews, while the system is allowed to keep everything forever.

Be careful with the temptation to treat retention tooling as a governance substitute. It is enforcement, not judgment. It can archive or delete on schedule, but it cannot tell you that a policy is technically still “retained” while being practically dangerous when shown in search.

Audit Triage for Intranet Content Governance

You do not fix content rot by launching another content campaign. You fix it by running a triage process that produces irreversible outcomes.

Records guidance frames lifecycle as creation, maintenance and use, and disposition. The U.S. National Archives summarizes this lifecycle and its terms in Records Basics. Intranet content is not federal records, but the lifecycle logic applies cleanly: you create content, you maintain it while it is useful, and you decide what happens when it is no longer operational.

Update when the page is still the right destination but the details are wrong
Redirect when the page is the wrong destination but search and links keep sending people there
Deprecate when the page must remain for traceability but must stop presenting itself as current guidance
Archive when the content has historical value but no longer belongs in active navigation or default search results
Delete when the content is redundant, obsolete, or trivial and cannot justify the risk of being followed
Assign ownership when the content is valid but abandoned, because “valid but ownerless” is a countdown timer

This is also where you stop pretending that “we cannot delete anything” is a compliance stance. It is an avoidance stance. Compliance requires defensible retention and defensible disposition. Keeping everything in active view is neither.

Fix the one page that ranks first, then fix the mechanism that allowed it, or you will be back here again with a different dead extension and a different confident policy that no longer matches reality.