Recover the promise of the old page
Before changing a server rule, write down what the old URL offered. Use a saved copy, its page title and the links that still point to it. Record the visitor's task: requesting a particular service, reading an explanation or downloading a document. An address containing an old campaign name does not tell you enough on its own.
Create a decision row with the old URL, former purpose, reason for retirement, proposed destination, responsible owner and decision date. Ask the service owner whether the offering has moved, changed or ended. This avoids a technical fix that silently sends visitors to something the business no longer provides.
Evaluate the replacement before selecting a status
Open the candidate destination as a visitor. Check whether it answers the old page's main question and provides the expected next step. Record one sentence explaining the match. Shared branding or a broad category is not enough to prove that two pages serve the same purpose.
Google distinguishes permanent redirects such as 301 and 308 from temporary redirects such as 302 and 307. Its guidance recommends a permanent redirect when a move is permanent. If there is no appropriate replacement and the content is gone, a genuine 404 or 410 response communicates its absence. Do not retain an empty page merely to produce a successful response.
Example: a service renamed, another discontinued
Illustrative scenario: /website-care/ has been replaced by /website-maintenance/, which describes the same maintenance service and contact route. The reviewer records this relationship and approves a permanent move. A second URL, /weekend-training-2022/, described a one-off workshop that is no longer offered. The maintenance page is not a substitute for that workshop.
For the retired workshop, the team can show a helpful not-found page with navigation while returning the correct missing-resource status. For the renamed service, it updates links to the new destination. These are different decisions because the visitor's expectations differ; this example does not claim a measured ranking outcome.
Test the rule and its boundaries
Save the existing configuration before applying a change. Test the exact old address, the final destination and an unrelated page. Record the initial response, Location header when present, final URL and final response. A successful browser load alone can conceal an unexpected intermediate destination.
Check common variants that actually exist in your link inventory, including a trailing slash or a documented query parameter. Avoid broad matching rules unless their full scope has been reviewed. Check that the target does not send visitors back to the old address and that a language-specific URL reaches content in the expected language.
Close the migration task with observable evidence
Update relevant navigation and editorial links to point directly to the chosen destination. Review the sitemap so it represents the pages you intend to maintain. Keep the decision record and a timestamped test result together, including the configuration backup location and the person responsible for rollback.
Separate deployment acceptance from search observations. A passing redirect test establishes that the website behaves as intended at that time; it does not establish how Google has processed the move. Review later Search Console evidence in its own record instead of declaring an immediate visibility gain or changing the destination repeatedly without new evidence.