A redirect map is a decision about where a visitor arriving at an old address should go. When a company moves its website or changes URL paths, commission an approved source-to-destination table and tests proving that the destination is relevant and the important task still works. A functioning new homepage does not establish a successful migration.
This scope concerns business-website pages, addresses and downloads. Store-data transfers and application rebuilds are different projects. If all URLs stay unchanged and only hosting changes, do not assume that extensive redirect mapping is required. Identify the actual change first.
Define the move before changing the site
Record old and new domains, changing paths, included languages, important downloads and the proposed content freeze. Name who can approve content retirement, implement redirects and authorize rollback. Missing domain or hosting access must become visible before the cutover window.
Establish a baseline of available pages, known defects, enquiry journeys and commonly used downloads. That prevents existing defects from being blamed on the move and new problems from being dismissed without evidence. Preserve the approved mapping version rather than relying on an undocumented, constantly changing file.
Make the mapping executable
| Field | What it establishes |
|---|---|
| Complete old URL | The exact source, including its language |
| Item type | Page, download, important asset or campaign route |
| Disposition | Retain, move, merge or retire |
| Approved destination | A specific address meeting the same need |
| Relevance rationale | Same service or consolidated coverage |
| Decision and implementation owners | Who approves meaning and who implements it |
| Expected and observed result | Evidence before and after release |
Do not finish the table with “everything else to the homepage.” Google recommends server-side permanent redirects where possible and warns against redirecting many pages to an irrelevant generic destination. Search visibility can fluctuate while a move is processed. Google's migration guidance.
Relevance requires content judgment. Similar words in two addresses do not establish an appropriate replacement. SEO and AI Search Readiness connects editorial decisions with technical signals, but cannot guarantee retained traffic or a particular ranking.
Hypothetical example: consolidating two maintenance services
Imagine a company with separate periodic-maintenance and preventive-maintenance pages. Its commercial offer has become one maintenance service that explains both activities and their boundaries. This is illustrative, not a LAB client project. The service owner approves a shared destination because it answers the original questions, not because its URL is shorter.
The company also has a PDF describing a discontinued service. Redirecting it to a new document that implies the old offer continues would mislead readers. The owner decides to retire it, and the implementation team defines the appropriate technical response and user experience.
An old maintenance-request page moves to a new enquiry route. Testing must verify receipt of the submission, not merely that the destination opens. Content relevance, URL behavior and functional completion are separate decisions: two can succeed while the third fails. CMS Development therefore needs an explicit route and behavior scope, not just a copy-transfer instruction.
Test before and after cutover
Before release, test the map in an appropriate environment and record anything that can only be verified on the live domain. Look for missing destinations, loops, unintended chains and Arabic links landing on English content. Include a download reached outside the navigation: a customer may still use a link from an old email.
After launch, repeat checks on public addresses. Follow a complete journey from an old link to the service description and an authorized test enquiry. Check internal links too. New navigation should not keep pointing at old routes simply because redirects conceal the mistake.
Quality Assurance should record the source, time, relevant device, expected result and actual result for important failures. Separate automated coverage of the URL list from manual review of relevance and business tasks. A small successful sample does not prove that every mapping was tested.
Record the environment and release version. A test from yesterday's staging build is not evidence that today's production rule is working. Conversely, a transient result from one browser should be reproduced before the team changes multiple configurations in response.
Give monitoring an owner
Agree who reviews migration errors, which failures need urgent attention and how newly discovered legacy links enter the map. Authorized logs or sales correspondence may reveal an address missing from the original inventory. Add it with a reason and an approved disposition instead of applying an undocumented server change.
If a core journey breaks, the appropriate response might be a bounded Website Repair and Improvement task or rollback of part of the release. Tie the choice to an agreed criterion and authorized decision-maker. Avoid changing several systems simultaneously without knowing which change addresses the fault.
Required handover evidence
- A dated mapping with exceptions and decision owners.
- The location and ownership of redirect configuration.
- Pre- and post-release results with coverage limits.
- Open issues, their consequences and assigned actions.
- A monitoring and rollback plan executable with available access.
Frequently asked questions
Is it enough that every old link opens a page?
No. It may open irrelevant content or the wrong language. Acceptance includes relevance, route behavior and completion of the intended task.
Can we remove the old domain immediately?
Do not decide independently of incoming links, redirects and domain ownership. Agree retention, renewal and responsibility with the specialist handling the actual move.
Does a passing redirect test guarantee retained rankings?
No. Implementation can be verified, but search performance depends on other factors and cannot be guaranteed from a redirect test.
Who approves merging two pages?
The content owner confirms that the destination meets the original needs. The technical team demonstrates implementation. Technical approval alone cannot validate a commercial offer.
Next step
Bring LAB the migration scope and your most-used service and document links. Ask for mapping, implementation, testing and monitoring to be distinguished before agreeing a launch date.
Sources
- Google Search Central: site moves with URL changes, reviewed 26 October 2026; used for the stated technical behavior, not a search-performance promise.
