Decide whether the content moved, merged or ended
Use a URL map with one deliberate disposition for every page in scope. The examples below are hypothetical editorial decisions, not instructions already applied to your website.
Read each row with its scope and evidence.
| Situation | Destination decision | What to check |
|---|---|---|
| The same guide has a new address | Redirect the old URL to the new guide. | The destination still answers the linked topic; the redirect reaches it directly. |
| Several overlapping pages became one substantive guide | Map each old URL to the relevant consolidated page. | The new page covers the material a visitor following each old link would expect. |
| A product or claim has changed, but the page still serves a useful purpose | Consider retaining the URL with a clear correction or dated update. | The page states what is current and does not present a withdrawn claim as valid. |
| The page is gone and no relevant replacement exists | Return an appropriate not-found or gone response rather than an unrelated destination. | The server returns the intended status, and the error page helps people navigate without pretending the old content exists. |
Google warns against sending unrelated retired URLs to the homepage. It supports relevant consolidations and documents 404/410 responses for content that is removed. Google’s site-move guidance
An old citation is not a reason to preserve inaccurate content indefinitely. Keep the evidence of what was observed; correct what the public page says now.
A redirect and a canonical solve different parts of the problem
A permanent redirect sends the request for the old URL to a new destination. Google documents server-side 301 and 308 redirects for permanent moves. Temporary redirects communicate a different intention. Choose the behavior that matches the move rather than using a temporary rule indefinitely by accident. Redirects and Google Search
A canonical annotation indicates a preferred URL among duplicate or very similar pages. It does not send a person clicking the old link to the new page. Google treats redirects and canonical annotations as strong canonicalization signals, and sitemap inclusion as a weaker signal; none is an instruction that guarantees which URL Google will choose. Canonicalization guidance
For the person following a saved citation, the practical difference is visible: a redirect can take them to the replacement; a canonical tag alone leaves them on the page they requested. Do not substitute one for the other without deciding which behavior you need.
Check the complete route, not just the new page
Before a release, make the intended path reviewable:
Saved citation → old URL → intended redirect → relevant destination → supporting passage.
This is an explanatory route, not a diagram of an AI system’s retrieval process. A working path lets someone inspect the source today; it does not prove that the current page supplied the wording in a past answer.
For each mapped URL, have the site owner check these four things in a controlled preview and again after the approved release:
- The old URL responds as intended. Verify the status and final destination for the exact cited address.
- The new page contains the expected information. A successful response that serves a login wall, a generic homepage or an error message is not the same as a usable replacement guide.
- The site points consistently to the new URL. Check internal links, sitemap entries and canonical annotations against the intended destination.
- Publication controls match the intended access. Verify that the replacement is available to its intended readers. Preserve deliberate privacy and indexing restrictions.
For a site move, Google recommends a direct route to the final page and keeping redirects as long as possible, generally at least a year. Assign a maintenance owner. Google’s migration checklist
HTTP success is only one check. Google explicitly says a 2xx response does not guarantee indexing; an error message returned with a successful status can become a soft 404. That is why the destination’s content belongs in the acceptance check. Google’s HTTP-status documentation
Keep the original citation in your research history
A reporting system may resolve or normalize an old URL to its new destination. Keep that convenience separate from the evidence you captured.
Read each row with its scope and evidence.
| Preserve from the original observation | Record separately after the move |
|---|---|
| Exact question, answer text, service and collection time | Date the route was checked |
| URL as it appeared in the answer’s citation | Redirect status, intermediate hops and current destination |
| Relevant cited passage or retained source version, when available | Current supporting passage and its update date |
| Whether the link was an inline citation or only in a broader source list | Whether the current page supports the claim, contradicts it or cannot settle it |
Do not rewrite a historical citation to make it look as though the answer originally named the new URL. Likewise, today’s corrected page cannot by itself prove that an older answer misread the page that existed then. An unavailable historical version should stay an evidence gap.
If the source’s substance changed, add an explicit note to the analysis. “The link now resolves to the replacement guide” and “the replacement supports the saved claim” are separate findings.
Verify search eligibility without promising an AI update
For Google AI Overviews and AI Mode, Google says a supporting page must be indexed and eligible to appear in Search with a snippet. It also states that meeting the requirements does not guarantee crawling, indexing or serving. A clean migration supports eligibility; it does not reserve a place in an AI answer. Google’s AI-feature guidance
Keep the post-release checks separate: the old link reaches the right page; the available indexing and canonical reports are checked for the intended URL; and any later authorized observation shows what an AI answer actually cites. These can occur on different schedules. A sitemap submission or a working redirect is not evidence that an assistant has fetched the new version.
The source-preservation work is complete when the route works, the destination is accurate and the history remains explainable. Whether future answers select the new page is a later observation—not a guarantee you can obtain by changing the URL.