SEO

Website Redesign Redirect Map: A Practical Handoff Checklist

By WaveINO Editorial Team • Oct 6, 2026
Website Redesign Redirect Map: A Practical Handoff Checklist

A website redesign redirect map records what should happen when someone opens an old URL after launch. For each address, identify whether it stays, moves, merges with another page or is deliberately removed. Add the approved destination, reason, owner and test result so the implementation team can act without guessing.

Prepare this document while planning the new pages. Waiting until launch creates avoidable questions: which service replaced an older offer, whether a brochure is still valid, or who approved removing a useful guide.

This checklist is a proposed handoff process for a small business redesign. For the choice of status code, read our 301 vs 302 redirect guide. Here, the focus is the decision record and acceptance evidence.

Illustration of old webpage cards mapped to redesigned pages with arrows and a verification checklist
Original AI-generated illustration for WaveINO.

Record a decision before requesting a redirect

Start with the URLs already used by customers and staff. Ask the team for the website inventory, sales materials, campaign landing pages and downloadable documents. Record the source of each address so someone can investigate a questionable entry later.

For each row, review the old content alongside the proposed replacement. Similar wording in two URLs is not sufficient evidence that the pages serve the same purpose. A visitor looking for annual maintenance should arrive at information about that service, rather than an unrelated product catalogue.

Google’s site-move guidance recommends mapping old URLs to appropriate destinations, avoiding unnecessary redirect chains and updating links and sitemaps. It warns against sending many unrelated pages to one destination such as the homepage. Keep redirects for as long as practical, generally at least a year.

Give the working map enough detail for approval

Use one controlled version of the map, with one row for each old URL. Keep proposed decisions separate from approved ones, and record changes made after approval. A developer should be able to tell which rows are ready for implementation.

Field What to record Who resolves uncertainty
Old URL Complete address, including meaningful parameters Inventory owner
Decision Keep, move, merge or retire Business and content owner
Destination Approved final URL, or no destination for a retirement Content owner
Reason Why the new page satisfies the original visitor need Business owner
Implementation Expected response and any special matching rule Developer
Verification Actual result, test date, reviewer and outstanding issue QA reviewer

Add a priority field when the inventory is large. Explain that priority through actual business use, such as a link on an active quotation template or a frequently used support document. An unsupported “high value” label gives the reviewer little help.

Work through a hypothetical mapping example

Imagine a service business reorganising its website. These paths and decisions are fictional examples, not changes to WaveINO’s website. The real handoff should use complete URLs; paths are shortened here for readability.

Old path Decision Destination Approval question
/company Keep /company Will this address still show company information?
/services/annual-support Move /services/maintenance Does the new page explain the same support offer?
/support-plans Merge /services/maintenance Does the combined page retain support-plan details?
/maintenance-options Merge /services/maintenance Does the combined page retain maintenance choices?
/downloads/service-brochure.pdf Move /resources/service-brochure.pdf Is the replacement current and suitable for existing customers?
/offers/expired-event-package Retire No replacement Has the owner confirmed there is no relevant successor?

A Keep decision means the page stays at its existing address; it should not redirect to itself. The merge decision deserves a content review. If one old page explained an emergency response option, a replacement that only mentions routine maintenance may leave that visitor’s question unanswered.

For documents, include the team that distributes them. A brochure address may appear in a saved proposal long after the website navigation changes. Agree which document the recipient should receive before implementing the move.

Choose the expected response deliberately

A permanent move and a temporary diversion communicate different intentions. Google recommends a permanent server-side redirect where possible for a lasting URL change; 301 and 308 are permanent options. Review its redirect documentation with the person responsible for implementation.

A retired page does not always need a substitute. When content is gone without a useful replacement, agree on the removal and verify the actual response. Google’s HTTP status documentation explains that 404 and 410 responses represent missing content. A page returning 200 is not automatically indexed, and an error message displayed with that status may be treated as a soft 404.

Ask the business owner to approve retirements separately. This makes it easier to distinguish an intentional removal from a page that disappeared accidentally during the rebuild.

Write down the exceptions a simple path list misses

Check whether a parameter selects meaningful content. An old address containing a service identifier may need different handling from one containing only campaign information. Record the intended behaviour and have the developer test it rather than stripping every parameter by assumption.

Also review existing redirects. If an earlier address already sends visitors to a page that is moving again, include that earlier entry in the discussion. Record the expected final destination so the tester can recognise an unintended detour.

Give each pattern-based rule an example that should match and one that should not. For instance, a rule for an old service folder should not capture an unrelated document whose name happens to contain the same word. This turns a vague rule description into a reviewable requirement.

Test the map as a customer journey

Agree on acceptance criteria before release. Check all approved entries with a suitable URL-testing process, then manually review representative destinations and important enquiry journeys. Keep observed results beside the decisions.

Check Passing evidence Reason to investigate
Open a permanently moved URL Agreed 301 or 308 reaches the approved page, returning 200 Wrong destination, loop or unexpected intermediate page
Review destination content Original customer question is answered Relevant service details disappeared
Open a retained URL Intended page returns 200 without redirecting to itself A broad rule captures it accidentally
Open a retired URL Approved 404 or 410 response Homepage redirect or misleading success response
Follow the main next step Relevant enquiry or download action works Arrival succeeds but customer cannot continue

Review the destination’s canonical URL, indexing settings and internal links as part of release checks. A redirect can work while the new page has a separate discoverability problem. Keep these results distinguishable in the acceptance record.

Hand over ownership after launch

The final handover should include the approved map, test evidence, unresolved exceptions and a named person who can correct a rule. Record where the implementation is maintained and who must approve a later destination change.

Schedule a review after launch using real visitor issues, relevant search reports and available server evidence. Investigate unexpected missing pages against the approved map. Search reports can lag, so retain immediate technical test results too; neither alone explains every performance change.

WaveINO’s web development service can help scope a redesign, while its SEO services cover search and technical review. To discuss a migration handoff, contact WaveINO with your current site, proposed structure and URL decisions your team has not yet resolved.