Start with the visitor’s question
Old content often accumulates quietly on a small website. A past event announcement remains in the news section, an earlier service description appears in search results, or a guide refers to a process that has changed. Before deciding where a page should live, ask what someone arriving on it today would need to know. Could they still complete a task, learn something useful, or understand why the page exists?
Age alone is a poor reason to delete a page. A ten-year-old explanation may still be useful, while a recent announcement may already be misleading. Review each page for accuracy, purpose and audience. Note whether it appears in site navigation, is linked from other pages, or answers a question that a current page now answers better. This gives you a reason for the decision beyond “it looks old.”
Know what “archive” means on your site
Archiving can mean two different things. A public archive keeps a page available to visitors but moves it out of prominent navigation and identifies it as a record of the past. An internal archive saves a copy for the organization while removing the public page. Agree on which meaning you intend before making changes; otherwise, a request to “archive this” can result in an important page disappearing unexpectedly.
A public archive suits material with lasting historical value, such as a completed project summary or an account of a past community event. Give the page enough context to prevent confusion: state that the event has ended or the information is no longer current, and link to the current equivalent if one exists. Keep archived pages readable and accessible. A label that appears only in a menu or a color change may be missed by someone who lands directly on the page.
Choose between updating, archiving, consolidating and deleting
Update a page when its core purpose is still relevant and you can make it accurate without obscuring its meaning. For example, a guide to requesting a service may need revised steps and contact details rather than a replacement. Consolidate pages when several short or overlapping articles answer the same question; choose a clear home for the useful information and remove duplication. Both approaches can reduce the number of pages you must maintain.
Archive publicly when the original record matters but should not be mistaken for current guidance. Delete a public page when it serves no continuing visitor need, is obsolete without historical value, or contains information you should no longer publish. Before deleting, check whether you need to retain a private copy under your organization’s own record-keeping practices. If you cannot verify an old claim, avoid preserving it on a public page simply because it has been there for years.
Some pages need more than one action. You might move the useful instructions from an old campaign page into a current guide, retain a brief public summary of the campaign, and remove the obsolete sign-up form. Decide based on the parts of the page, not just its title.
Handle links and navigation deliberately
Removing a page without checking its links can leave visitors at a dead end. Look for links to it in menus, related-content lists, documents and other pages you control. If a new page answers substantially the same need, redirect the old address to that page. A redirect to the home page is usually less helpful: visitors may have followed a link expecting a specific answer.
If there is no meaningful replacement, make sure the site provides a clear way to recover, such as helpful navigation or a useful not-found page. For a publicly archived page, decide whether it belongs in an archive index rather than the main menu. After changing it, open the old address yourself and follow its important links. This small test often catches mistakes that are easy to miss in a content management system.
Make the decision repeatable
For a manageable review, start with one section of the site rather than every page. Record each page’s address, owner, purpose, decision and next review point in a simple content inventory. Give uncertain pages to someone who knows the subject; a website editor should not have to guess whether an instruction is still valid. Where possible, assign one person to approve the final change.
Use consistent rules, but allow exceptions. A brief event notice and a detailed project history do not need the same treatment. The goal is a site where visitors can tell what is current, find what they need, and understand older material when it remains available. Reviewing content in small batches makes those decisions easier to make and easier to maintain.
