How to retire outdated website pages without losing customers

Start with pages that are likely to expire: services, offers, events, staff profiles, locations, recruitment posts, downloadable menus and dated articles. Add URLs found in the sitemap, website navigation, analytics and Search Console. Also ask the people answering calls which obsolete pages customers still mention. A spreadsheet is enough.

For each address, record the page owner, current accuracy, last meaningful update, customer task, enquiries or visits if available, internal links, known external links and an equivalent current page. Traffic alone is not the decision. A low-traffic warranty page may still be essential after a purchase, while a visited promotion may now contain a price the business cannot honour.

Keep a page when it remains accurate and serves a distinct need. Update it when the same service, place or question continues but facts have changed. Merge two or more thin, overlapping pages when one stronger page can answer the full need. Redirect an old address when a genuinely equivalent page has replaced it. Remove it when the subject has ended and there is no honest substitute.

A simple test is to read the old title, then open the proposed destination. Would the same visitor feel helped, or tricked? A discontinued winter tour may redirect to a current tour page only if the offer is meaningfully similar. Sending it to a generic homepage makes the customer start again. Google also treats permanent redirects as a signal that the destination should become the canonical address, so relevance matters.

When updating, correct the visible facts, title, description, images, structured data, contact path and translated versions. Do not merely change the year in the heading. If the page covers a recurring event, explain the current date and booking status. If a service is paused, say what is available and when the next update will be made.

For a merge, move only useful material into the chosen page, remove repetition and update links across the site. Then permanently redirect each retired address to that specific destination. Google recommends server-side permanent redirects, such as 301 or 308, when a move will not be reversed. Keep a redirect register so a future redesign does not accidentally delete the rules.

If the information is gone and no similar page exists, the old URL should return a real 404 Not Found or 410 Gone response. Google explicitly recommends these responses in that situation. A useful custom 404 page can offer navigation, search, contact details and a few popular services, but the server still needs to return the correct status rather than displaying an error message with a successful 200 response.

Avoid redirecting every deleted address to the homepage. It hides what happened, creates confusing journeys and can be interpreted as a soft 404. Remove the old URL from menus, internal links, hreflang groups and the XML sitemap. Google says a sitemap should contain the canonical URLs you want in search results, not retired or redirected addresses.

If confidential, harmful or seriously wrong information must disappear from Google quickly, first remove or protect it on the website. Search Console's Removals tool can temporarily block a result, but Google says the request alone is not permanent and does not remove the content from the internet. Do not use robots.txt as the permanent removal method because it can prevent the crawler from seeing the final instruction.

Ordinary housekeeping rarely needs an urgent removal request. Once an obsolete page correctly returns 404 or 410 and links and sitemaps are cleaned up, search engines can process the change during normal crawling. Record urgent cases separately, with the person responsible and the permanent action taken.

Test every old URL directly, not only the new page. Confirm that a kept page returns normally, a redirect reaches one relevant destination without a chain, and a removed page gives the intended status. Open the journey on a phone, check forms and bookings, and inspect all language versions independently. Equivalent translations may share a decision, but one market may have a different offer or replacement.

Finish by checking navigation, internal links, canonicals, hreflang references and the generated sitemap. Review Search Console after search engines have had time to recrawl; a temporary fluctuation is not proof of success or failure. Repeat this small audit quarterly and before a redesign. The goal is a website where every old address either helps the visitor or clearly explains that the page is gone.