Research Guides
Before the URLs Move: Build a Migration Acceptance Ledger
A redirect spreadsheet can look complete while leaving the important question unanswered: will someone following an old link reach the information they expected?
Before changing a site's URLs, create an acceptance ledger. It combines the proposed destination, the reason that destination is appropriate, and the evidence required before anyone marks the move complete. The deliverable is not another SEO score. It is a set of reviewable decisions.
This guide describes a manual research workflow. It does not require or imply an automated migration feature in Colquhoun.shop.
Start with the move you actually intend
Write one sentence defining the change: “Existing articles will move to a new domain with their content preserved.” Separate that from unrelated work such as rewriting those articles or changing navigation. Google recommends separating major changes rather than combining a domain move, platform change and redesign. Its site-move guidance also calls for a mapping between old and new URLs, testing, and monitoring both sets of URLs. Google Search Central: site moves.
Then add your own explicit exclusions. For example: “Account pages and billing routes are outside this content move.” An exclusion is a boundary to preserve, not permission to ignore whether the release accidentally affects it.
Make each row a decision, not just a pair of URLs
Use these columns in a spreadsheet:
| Field | What to record |
|---|---|
| Old address | The exact URL someone may still follow |
| Existing purpose | What that visitor expects to find |
| Proposed destination | The exact replacement, or an explicit retirement decision |
| Match rationale | Why the replacement satisfies the same need |
| Expected behavior | The agreed response and final page |
| Observed behavior | Actual response, final address and content check |
| Evidence | Test date, environment and saved result |
| Owner and decision | Who can approve, fix or reject the row |
Keep proposed and observed values separate. Otherwise a spreadsheet can quietly turn an intention into supposed proof.
Here is a fictional editorial example:
| Old page | Proposal | Review decision |
|---|---|---|
/guides/export-csv |
/help/export-csv |
Accept only if the destination still explains CSV export |
/guides/export-pdf |
/help/export-csv |
Hold: similar names do not establish equivalent instructions |
/reports/2022-summary.pdf |
/reports/2022-summary.pdf on the new host |
Check that the historical document remains the intended version |
The second row is the useful failure. Finding it before release is better than reporting a perfect redirect count afterward.
Test the route and the destination separately
For permanent URL changes, Google recommends permanent server-side redirects when possible; 301 and 308 are permanent status codes. Temporary redirects serve a different purpose. Choose behavior to match the actual decision, not a blanket rule that every redirect is interchangeable. Google Search Central: redirects.
Record two outcomes for every reviewed row:
- Transport check: did the old address lead to the agreed final address?
- Meaning check: does the final page actually satisfy the old page's purpose?
A correct address with the wrong document fails the second check. A useful document behind a failed redirect fails the first. Neither should receive a combined “passed” label.
Test in a controlled environment before release, then repeat the agreed public checks afterward. Label the environment in every result. A staging success is not a production observation.
Do not use a notification tool as a substitute for the move
Search Console's Change of Address tool applies to eligible domain or subdomain moves after the site has moved and redirects are in place. It is not for an HTTP-to-HTTPS change, an internal path change, or a hosting change that leaves visible URLs unchanged. The owner must meet the tool's property-ownership requirements. Search Console Help: Change of Address.
Add a ledger-level field: “Applicable notification: yes, no, or unresolved, with reason.” That prevents a team from treating a familiar button as a universal migration checklist.
Agree on what “done” means
Before release, assign a person to unresolved mappings and define which failures block the move. Save the reviewed ledger alongside the release identifier so later edits do not erase what was approved.
Afterward, report three separate facts: the changes deployed, the routes checked, and the search outcomes observed. Do not label deployment success as ranking recovery. Google warns that rankings can fluctuate while a move is processed. Google Search Central: site moves.
A useful handoff ends with the exceptions, not a celebratory percentage: “These rows passed both checks; these remain unresolved; these are intentionally retired; here is who owns the next decision.” That is evidence another person can use.