Calling an article evergreen describes an editorial intention, not a promise that its facts will remain true indefinitely. A guide to planning a gallery visit may offer lasting reasoning while linking to a venue that changes its entrance. An article about exhibition media may retain its central argument while referring to an unavailable player. Maintenance begins by separating those changing dependencies from the useful core.
An update routine should make the publication more dependable rather than merely make old pages appear new. It needs a way to discover a problem, assess its consequence, assign work, verify the result and explain a meaningful revision. A small publication can do this without pretending to re-report every article on a fixed calendar or treating every minor edit as a fresh publication.
Inventory changeable claims within each article
Look below the page title and identify the statements that rely on current arrangements. These can include opening windows, entry procedures, software features, named contact routes and the availability of external resources. A broad label such as practical guide conceals substantial differences in how quickly those details may change.
Separate the claim from its supporting link. A working link does not prove that the article still describes the destination accurately. The external page may have changed while retaining its address. Conversely, a moved page may leave the underlying claim sound. The editor needs to inspect the relationship, not simply count successful responses.
Record the useful basis of important claims: an official source, a dated observation, an interview or the publication's own explanatory reasoning. This makes later review more efficient. An editor can see whether the task is to recheck a practical arrangement, obtain a new explanation or assess whether the article's argument still follows from its evidence.
Keep the inventory proportionate. A short article does not need every ordinary sentence entered into a database. Focus on details whose change would mislead a reader, prevent a task or weaken the central conclusion. The inventory is a working map of vulnerability rather than a second copy of the whole article.
Use events as well as calendar reminders
A reader correction, a programme change, a moved institution or a withdrawn source can trigger an immediate review. These events may matter more than the date scheduled for a routine check. Give incoming reports a place in the editorial workflow so that they do not remain in a private inbox until an unrelated archive audit occurs.
Calendar reminders can still help organise lower-change material. Choose intervals according to likely change, reader consequence and actual maintenance capacity rather than a universal rule for all pages. A source-dependent technical guide may need a different approach from an essay about a historical object. The publication should be able to explain that difference.
Distinguish a trigger from a completed review. Receiving a reminder does not make a page verified. An automated link check does not establish factual accuracy. Record what work occurred and which uncertainties remain. This prevents a dashboard full of reassuring dates from concealing articles that nobody has meaningfully examined.
Make responsibility explicit. A topic editor may decide whether the argument needs revision, while another colleague checks practical links. If the work is shared, define the handover and the final sign-off. An article should not fall between roles because each person assumes the other has completed the substantive part.
Rank the queue by consequence rather than page age alone
Ask what happens if the current statement is wrong. An inaccurate arrival instruction can disrupt a visit. A broken optional reading link may be inconvenient but less consequential. A doubtful central claim can undermine the whole article. Use those distinctions to decide which task should be done first, especially when the backlog exceeds available editorial time.
Consider exposure without treating popularity as the only measure. A frequently used practical guide deserves attention, but a less visited page can still contain a serious rights or factual problem. The queue should combine reader consequence, evidence of an issue and the chance that the detail has changed. It should not simply promote whichever article promises the most traffic.
Group related checks where useful. Several articles may rely on one institution's visitor information or a shared technical resource. Reviewing that dependency once can inform several pages, provided each article's wording is still examined. Do not mark the whole group complete because one destination loaded successfully.
Allow a temporary qualification or removal when full verification is not immediately possible. If a consequential detail cannot be supported, leaving it confidently in place is not the only option. Narrow the statement, direct readers to the responsible official source or withhold the affected claim while reporting continues.
| Issue | Likely first action | What completes the task |
|---|---|---|
| Incorrect practical instruction | Check and correct the affected statement | Verified wording and related references updated |
| Uncertain central argument | Assess supporting evidence | Revised claim or further reporting |
| Moved background resource | Find the appropriate new destination | Check the source still supports the paragraph |
| Cosmetic wording preference | Place behind consequential issues | A proportionate edit without a false freshness claim |
Review the argument and the practical details in separate passes
The practical pass checks current names, links, service arrangements, dates and contact routes. It asks whether a reader can carry out the task the article describes. The substantive pass asks whether the article still answers a useful question and whether its conclusions remain supported. Both matter, but they are different kinds of editorial work.
During the substantive pass, look for scope drift. A later introduction or new headline may have enlarged the promise while the body still covers a narrow example. An added paragraph may contradict an earlier qualification. Read the article as one account rather than treating each update as an isolated patch.
Check examples and visual context. A hypothetical scenario should remain identifiable as hypothetical. An image chosen for a general guide should not become apparent documentary evidence after the article is reframed around a named venue. Updated captions and alternative text need the same factual care as the prose.
Use the appropriate source for each detail. Official current arrangements are usually the direct route for a venue's practical information; an old interview may remain valuable for a person's view at the time. Do not erase historical context merely because a current source uses different language. Identify whether the article is describing the present or preserving an earlier account.
Make modification dates correspond to meaningful work
A displayed update date should help readers understand the article's current state. Changing it after fixing punctuation can create an impression of substantive verification that did not occur. Establish a publication convention for minor edits, factual corrections and significant revisions, then apply it consistently.
Record the scope of a review internally even when a public note is unnecessary. An editor might verify current practical links without revisiting the article's entire argument. That is useful work, but its record should say what was checked. A broad label such as fully updated is appropriate only when the actual work justifies it.
For material factual corrections, consider a clear public explanation. A corrected event date, misidentified object or changed attribution affects meaning differently from a smoother sentence. The correction should identify the relevant change without turning the page into a complete history of every typographic adjustment.
Preserve the original publication context where it matters. A review of a particular exhibition should not become a current assessment of a later programme because the headline was revised. A dated interview should not imply that a contributor has reconfirmed their view today. Updating should improve accuracy without rewriting the history of the reporting.
Respond thoughtfully when a source disappears
A withdrawn or missing source requires a decision about the claim it supported. Search for an official replacement where appropriate, but inspect whether the replacement actually says the same thing. A homepage is not necessarily a satisfactory substitute for a specific document. The goal is traceable support, not merely a destination that avoids an error screen.
If the article concerns a historical source, an appropriately identified archived record may be useful. Make its date and role clear. Do not use an old archived page as evidence of current opening arrangements. Historical preservation and practical verification answer different questions, even when both involve the same institution.
If support cannot be recovered, assess the importance of the claim. An optional example may be removable. A central factual assertion may require further reporting or a substantial revision. Do not keep a confident sentence solely because it has been published for a long time or because deleting it would make the article shorter.
Keep a note of the decision and the evidence considered. A later editor should be able to understand why a reference changed or a passage was removed. This avoids repeatedly reopening the same uncertainty and prevents an unsupported claim from returning through an old draft that somebody mistakes for a complete version.
A hypothetical audit of a durable visitor guide
Imagine a cultural publication with a guide about planning a short museum visit. Its central advice concerns choosing one priority and allowing time for arrival. A reader reports that a linked entrance description is out of date. The team initially considers changing only the link and refreshing the page date, but the claim inventory shows that the old entrance appears in two paragraphs and one caption.
The practical review confirms the current official visitor-information route and removes the obsolete description. The editor checks whether the example still makes sense without it. The substantive review finds that the short-visit reasoning remains useful, while a newly added headline had begun promising a complete destination guide. The title is narrowed to match the actual content.
The internal update record identifies the corrected arrival information, the revised caption and the title adjustment. It does not claim that the publication re-tested every route or revisited the venue. A public correction explains the material practical change where appropriate. The article now presents a clearer and more accurate promise.
This hypothetical audit demonstrates why maintenance is more than replacing a broken URL. One issue can affect the article's wording, visual context and scope. The useful routine follows the relationship between those elements while keeping the claims about the review itself proportionate.
Retire pages that no longer have a defensible purpose
Some articles cannot be repaired economically because their central question has become obsolete or their evidence cannot be supported. Retirement can be a responsible editorial choice. Before removing a page, identify incoming links and decide whether a genuinely relevant replacement exists. Do not redirect readers to unrelated material simply to conceal the disappearance.
Consolidation can help when several pages answer nearly the same question with small variations. Build a stronger account with a clear purpose rather than preserving every fragment to maintain a page count. Keep the distinction between useful consolidation and stitching together passages without adding a coherent argument.
A retired archive record may remain appropriate when the historical context is valuable. Give it an honest status and remove current calls to action. A publication should be able to preserve the fact that a programme existed without suggesting that it still offers the same opportunity today.
At the end of a maintenance cycle, review the pattern of work. Repeatedly stale practical details may suggest linking to official current information more directly. Repeated scope problems may suggest better commissioning. The update routine should improve future articles as well as repair the existing archive.
Questions specific to this guide
Should every article be updated on the same schedule?
No. Prioritise by the likelihood of change, reader consequence and the evidence of a problem. A general calendar can organise work, but it should not replace responding to a material correction or changed dependency.
Does fixing a link justify a new publication date?
Not automatically. Record the work accurately and follow a clear convention for minor edits, corrections and substantive revisions. Avoid implying that a whole article was re-reported when only one destination changed.
Is removing an outdated article an admission of failure?
It can be a responsible maintenance decision. Assess whether the page still has a useful, supportable purpose and whether a relevant replacement exists. Keeping unsupported material indefinitely is not the only way to preserve an archive.
Further reading
Authoritative background on related planning and access questions. These resources provide context; they do not endorse this guide or replace the current requirements for your specific setting.



