Every legal news desk loves the thrill of a fresh story. A new judgment lands, a notification appears in the Gazette, and the whole team rushes to explain it. Meanwhile the explainers you published last year sit quietly in the archive, and nobody asks whether they still say anything true. This piece compares the three things you can do with an old legal explainer, and argues that the least glamorous one usually deserves your next free hour. It is general information about publishing practice, not legal advice for any particular matter.

The question matters more for legal content than for most subjects. A recipe that is a little dated still makes dinner. A page about a procedure, a limitation period or a filing route that has since changed can mislead a reader who has no way to tell. That reader may be a student, a small business owner or a family member trying to understand a notice. They trust the page because it looks settled.

Option one: leave it alone

Doing nothing is the default, and it is not as harmless as it feels. An untouched page keeps collecting visitors from search, and each visit is a small bet that the content is still current. The bet pays off for evergreen topics such as the structure of the courts or the meaning of a basic term. It fails quietly for anything tied to a rule that Parliament, a regulator or the Supreme Court may have revisited.

The appeal of leaving things alone is speed. You spend nothing today. The cost arrives later, usually as a reader email, a correction request or a screenshot passed around by someone who spotted the mismatch. At that point you are fixing the page in public, under pressure, and your reputation for care takes the hit rather than the page.

Option two: refresh it in place

Refreshing means opening the old article, checking each claim against the current position, and editing what has changed. You keep the address, keep the history, and keep whatever trust the page has earned. For a news site this is the strongest option for explainers that still answer a question people really ask.

A sensible refresh has a few parts. Reread the opening claim first, because that is what most readers will take away. Check any named provision, authority or deadline against its official source. Add a visible note showing when the page was last reviewed, so a reader can judge its age for themselves. Then look at what the page points to. Our own daily digest of Indian legal developments is a good example of content that is meant to be dated, and the way to treat it is to label it clearly rather than pretend it is timeless.

The weakness of refreshing is effort. Each page can take as long to verify as a new one takes to write, and a careful editor will sometimes discover that the whole premise has aged out. That is useful information, but it means a refresh is not always the cheap path it first appears to be.

Option three: retire it properly

Some pages should simply go. If the rule has been replaced, the topic no longer draws questions, or a newer article covers the same ground better, the honest move is to retire the old one. Retiring does not mean deleting and hoping. It means choosing where readers should land instead, and pointing the old address there so that bookmarks and shared links do not hit a dead end.

Retirement is the option editors resist most, because removing work feels like admitting it was wasted. It was not wasted. It served readers while it was accurate. A clean exit is a courtesy to everyone who comes later.

Side by side

• Effort: leaving costs nothing now, retiring costs a little, refreshing costs the most.
• Risk to readers: leaving carries the highest risk on fast-moving topics, while refreshing and retiring both remove it.
• Effect on search traffic: refreshing tends to preserve it, retiring with a proper redirect preserves most of it, and leaving lets it decay as the page ages.
• Effect on trust: a visible review date builds it, an unexplained stale page erodes it.

Put simply, refresh the pages that still answer a live question, retire the ones that do not, and leave alone only what is truly timeless. Most archives hold far fewer timeless pages than their owners believe.

The links you forgot you were holding

An old explainer is also a list of promises. Every outbound reference says to the reader that a useful source waits at the other end. Government portals reorganise their sites, tribunals move their notices, and a link that worked when you published can lead to an error page a year on. If your archive is large, checking these by hand is a chore that nobody finishes. A link-management platform such as URLSnow runs automatic health checks that flag links that stopped responding, which turns a vague worry into a short repair list.

That list is where the refresh work starts. A broken reference is often the first sign that the underlying rule or process also changed, so treat each one as a prompt to reread the surrounding paragraph, not just swap in a new address.

A routine that fits a busy desk

You do not need a grand audit. Pick the dozen explainers that draw the most readers and review them in a set order. For each one, decide among the three options above, write the decision down, and act on it that week. Revisit the next dozen later. The previous day’s legal roundup shows the opposite rhythm, a constant stream of new items, and the two habits complement each other. The stream keeps readers coming, while the review keeps them able to trust what they find.

If a topic keeps changing, consider whether an article is even the right format. A dated news item that makes no claim to be permanent is often safer than an explainer that implies it will stay true. Another useful trick is to link forward from an old page to the newest development, so that a reader landing on yesterday’s explanation can see today’s change in one click. When you read a related update such as a further digest covering courts and government notices, notice how much of its value depends on the date being plain to see.

What to take away

New coverage will always feel more exciting than old coverage, and that is fine. The point is to stop treating the archive as a finished warehouse. It is a set of promises you are still making to anyone who finds it. Before the next big story, spend an hour checking what you already published: does it still work, is it still needed, and does it point to the right place? Fixing a small error now is quiet and cheap. Fixing it after it has gone round the internet is neither.