Retiring a Service Page: Redirect, or Let It Go?
Start with one question
When a business stops offering a service, the old page still has visitors, bookmarks and inbound links. The decision is not "redirect or delete". It is: does a page exist today that gives the visitor what the old page promised?
If yes, a permanent redirect fits. If no, sending people to the homepage or a loosely related page tends to confuse them, and a removed-page response is the more honest choice. That second point is an engineering recommendation, not something the Google documentation spells out.
A hypothetical example
Imagine a small print shop, Harbor Lane Print Studio, that retires two pages.
The first is "Wedding Invitation Printing". The shop now covers the same work on a new "Event Stationery" page, with the same ordering steps. A visitor arriving from an old link gets what they wanted. This is a genuine equivalent.
The second is "Same-Day Poster Rush". The shop no longer offers it, and nothing on the site replaces it. Redirecting it to the general posters page would suggest a rush option still exists.
What the documentation says
Google's redirect guidance describes server-side redirects as the preferred method: 301 and 308 are permanent, 302, 303 and 307 are temporary. Permanent redirects signal that the target should appear in search results, while temporary ones keep the source page in view.
It also says an instant meta refresh is read as permanent and a delayed one as temporary. JavaScript redirects are a last resort, because rendering can fail and the redirect might never be seen. The same page notes that old URLs may occasionally still show in results after a move, which is described as normal.
The operational decision
For the print shop, the rule is simple:
- Equivalent replacement exists: one server-side permanent redirect, straight to the final URL.
- No equivalent: serve a removed-page response (404, or 410 if you want to state it was deliberate). Give the error page a short message and links to nearby services.
- Partly related page only: do not redirect. Link to it from the error page instead.
Keep a small redirect map
A spreadsheet with four columns is enough: old URL, new URL, date added, reason. Add a fifth column, "last checked". Keep the map short by reviewing it each quarter and deleting rows whose old URLs no longer receive traffic. Do not delete the redirect itself while real links still point at it.
Before adding a row, check that the target does not itself redirect. If the Event Stationery page is later renamed, update the old wedding row to point at the newest URL, so visitors never pass through two hops.
Failure handling
- A chain appears (old, then renamed, then final): edit the first rule to point at the final URL.
- A loop appears: remove the most recent rule and re-test the starting URL.
- The redirect target returns an error: pause the redirect and serve the removed-page response until the target is repaired.
- The page was retired by mistake: restore it and delete its map row, noting the reversal.
- Someone suggests a delayed meta refresh for convenience: avoid it, since Google reads a delayed refresh as temporary.
Proposed acceptance checklist (not performed)
This list is a proposal. None of these checks has been run.
- Every row in the map has an equivalence note written in plain words.
- Each old URL answers with one hop and a permanent status code.
- No target URL redirects again.
- Removed pages return an error status, not a 200 page that says "not found".
- The error page links to at least two relevant live pages.
- Internal links, sitemap entries and navigation no longer point to retired URLs.
- The map has an owner and a quarterly review date.
Scope
This covers retiring a single page on an existing site. Moving an entire domain involves further steps that are outside this article.