Map individual destinations
Give every old URL an equivalent destination or an explained removal. Use CMS records, internal links and available server logs. Sending every old page to the homepage removes the answer the visitor expected. Record unresolved addresses rather than guessing a destination.
Check staging thoroughly
Test content, media, forms and indexing instructions. Staging restrictions must be removed from the public site at the correct moment. Compare canonicals and language alternatives against the intended public hostname rather than the test server.
Make the switch reversible
Save the files and routing configuration. Agree stopping conditions such as server errors, a broken purchase journey or missing important content. Someone should be able to initiate rollback using a written procedure instead of assembling one during an incident.
Review exceptions after launch
Run the URL inventory again. Investigate redirect chains, broken links and missing content. Compare trends over comparable periods; an unusual day does not establish that migration caused a traffic change.
- Map
- Test
- Switch
- Monitor
Worked example
Acceptance table: old URL / destination / expected status / canonical / functional check / owner. A relocated article should use one permanent redirect to its equivalent, followed by a 200 response.
Check before moving on
These checkboxes are not saved.
A migration handoff you can test before launch
A redirect spreadsheet becomes useful when another person can run it and explain every exception. Treat the handoff as a set of acceptance decisions, with an owner and evidence for each one. The local mapping checker below finds structural problems in a small CSV; it does not contact a server or verify that a redirect has been deployed.
Give one row a complete journey
For each old address, record its intended final destination, the expected redirect status, the expected final HTTP response and the person responsible. Add a content check: the heading, key media and task the visitor must still be able to complete. A destination returning 200 can still be the wrong article. A valid canonical cannot repair an unrelated redirect.
Our fictional example moves https://old.example.test/article-a/ directly to https://new.example.test/guide-a/. The reserved .test addresses are teaching examples. The acceptance note asks for one permanent server redirect, followed by the intended page. It also asks the reviewer to compare the text and download on that page. The CSV contains only old_url and new_url; the downloadable worksheet provides the remaining acceptance columns.
Look for conflicts before asking someone to deploy
Two rows assigning different destinations to the same old URL create a conflict. A row whose destination is another row's old URL can create a redirect chain. A self-map may describe an unchanged page, but should not become a redirect rule pointing to itself. A loop is a release blocker. Resolve these questions in the inventory rather than letting a routing script choose silently.
The checker accepts a two-column CSV, including quoted fields and doubled internal quotes. Quote any URL containing a comma. It reports duplicate sources, self-maps, chains and loops. It treats addresses exactly as entered after normalising them through the browser's URL parser. It cannot discover server-specific case handling, query-string rules, existing redirects, DNS failures or content equivalence. Review those separately on a controlled test environment.
A release note with a stopping condition
Write who will make the change, who will test it, where the saved version lives and which failures require rollback. For the example article, a broken download is enough to hold its release. For a commerce journey, the corresponding condition may be a failed form. Set these conditions before launch and use the site's actual priorities.
After deployment, request each old URL and follow the real response to the final page. Check status, canonical, language annotations and internal links. Include assets and important forms. Google's migration guidance recommends preparing URL mappings and testing the new site; the acceptance sheet is our way to make those checks assignable.
Record unresolved rows and their owners in the handoff. Compare search observations over comparable periods when data becomes available. A structurally clean CSV is useful preparation, not evidence of preserved traffic or completed indexing.
Steps: OLD / article-a. NEW / guide-a. CHECK / content + HTTP. One source → one intended final page → evidence.
Try the local worksheet
Inputs stay in this page and are not sent or stored. Use anonymised examples. No account is needed.
CSV format: two columns old_url,new_url, up to 500 records and 20,000 characters. Quote a URL containing a comma; double any quote inside a quoted field. A UTF-8 BOM is accepted. Do not paste credentials, private tokens or production secrets. The checker rejects literal whitespace, backslashes, embedded credentials and fragment-bearing rows for review. A chain report shows its mapped final destination; it does not make a live HTTP request.
Download the blank worksheet and worked example ↓
Primary context and limits
Sources & method
Sources reviewed on 1 October 2026. Worked calculations use explicitly hypothetical inputs.
Topic provenance: 5 points cruciaux pour une migration réussie (2008-03-14). Search Engine Feng Shui. Byline retained in the publication feed: François Houste.
This guide is newly written in 2026. It does not reproduce the earlier text and is not attributed to its historical author.
Test the redirect contract on a local fixture
The existing mapping worksheet can detect a loop in a list of URLs. It cannot tell you what a server actually returns. Add a local rehearsal that distinguishes the response code, the final destination and the content at that destination. A technically followed redirect can still lead to an unhelpful error page.
Three intentionally different routes
The downloadable fixture binds to 127.0.0.1 and serves only teaching responses. Route /old uses a permanent 301 redirect to /new; /new returns 200 and an identifiable marker. Route /missing is a 301 to /gone, whose response is 404. Route /loop points back to itself. The fixture does not change your site's redirects or request a public domain.
In our local run, following /old ended at /new with status 200 and the expected marker. Following /missing ended at /gone with status 404. Following /loop stopped at the explicit redirect limit. The raw commands and results are supplied with the fixture. These are test-fixture observations, not a claim that every live migration route has passed.
Rehearse the acceptance check
- Start the fixture with an unused local port and keep the terminal open.
- Request the old path without following redirects; record status and Location.
- Follow with a bounded number of redirects; record the effective URL and final status.
- Inspect the response marker rather than accepting 200 alone.
- Repeat the missing and looping cases so a failure is recognisable.
- Stop the local server after the rehearsal.
For a real route, substitute evidence of the actual page's purpose for the teaching marker. Compare language, topic and the user's next action. A product moved to a new address should not be treated as equivalent to a generic homepage merely because both return 200.
Google documents permanent redirects as signals for canonicalisation, not a guarantee of index selection or traffic. Preserve the real route list, content equivalence and rollback evidence. Do not submit all old URLs to one destination unless the destination genuinely fulfils their purpose.
This exercise complements the CSV validator. It does not inspect production DNS, protected accounts or search results, and it performs no deployment. The French and English exercises have the same routes, limits and result evidence; a translation of the heading alone would not be an equivalent guide.
Steps: 301 → /new → 200 + marker → 301 → /gone → 404 → Self-loop → explicit redirect limit
| Field | Completed example |
|---|---|
| Local fixture version and port | /old fixture, loopback only |
| First status and Location | 301; Location /new |
| Final URL and status | /new; 200 |
| Content evidence | Teaching marker found |
| Failure / limit | /missing:404; /loop:limit |
| Live equivalence not yet checked | No production redirect changed |
Blank worksheet and worked example ↓
Download the local Python fixture · Commands and raw results
Primary context: Google Search Central: redirects