Decide between a real 404 and a redirect for a retired service page

Clarify the business decision before the status code

Ask the service owner whether the work has ended, been renamed, moved to another page, or paused temporarily. These situations need different visitor explanations. Record the effective date and the person who approves public wording. A developer cannot choose an accurate replacement if the business has not decided what existing customers should do.

Source checks: Google Crawling Infrastructure: HTTP status codes · Google Search Central: Redirects and Search

Inspect real routes into the retired page

List internal links, profile destinations, ads, directories, and any known bookmarked links. Check whether visitors arrive expecting a specific service or general contact information. You do not need a complete inventory of the entire internet to begin, but you should fix the important links you control. Pause or revise active promotions that still advertise work you no longer offer.

Evaluate whether the replacement really fits

Compare the retired page's promise with the proposed destination. A renamed appointment with the same scope is usually a stronger replacement than a homepage. A broader service may be suitable if it clearly explains the relevant change. If no page answers the old need, do not imply that an unrelated service is equivalent simply to retain the URL.

Implement the chosen response and visitor guidance

Prepare a small decision record.

• For a genuine permanent replacement, map the old URL to that page with the appropriate permanent redirect.
• For a removed resource without a replacement, return a real 404 or 410 rather than a successful empty shell.
• Make the missing-page design helpful with working navigation and an accurate contact route.
• Remove retired URLs from current navigation and preferred sitemap entries.
• Test the exact old path and the proposed final page.

Avoid hiding errors with attractive templates

A branded page saying service unavailable can still return a success response. That is a different technical result from an actual missing-page response. Likewise, redirecting every missing URL to the homepage makes visitors hunt for a service that may no longer exist. Visual appearance and HTTP behavior need to agree with the business decision.

Track the remaining links, not a zero-error target

Record where the old URL is still used and update owned links directly. Expect search and other systems to discover the change over time. A 404 report is not automatically a problem when the page was intentionally removed. Investigate errors on useful current services separately from expected retirement responses, and keep the decision log for future redesigns.

Illustrative discontinued service with no replacement

An illustrative maintenance company stops offering pool repairs. Its /pool-repair page has no equivalent current service. The owner removes current promotions and internal links, implements a genuine missing-page response with a clear service-directory link, and retains the decision in the content inventory. An unrelated garden-maintenance page is not presented as a replacement.

The retirement sheet marks pool repair as discontinued and names no replacement. Garden maintenance remains a separate currently offered service. This protects the next editor from adding a homepage redirect merely to make an error count disappear and preserves the difference between an intentional retirement and a broken active page.

Questions about this task