Check that existing customer tasks survive the redesign
Accept the redesign through preserved product destinations, variant selection, support content and correctly collected synthetic purchases. Give each row an owner and a release condition. The checklist protects the tasks customers already use and separates a visual refresh from the evidence required to approve a migration.
Worked example — illustrative data.
| Before | After requirement | Evidence |
|---|---|---|
| Product URL receives useful visits | Same item or approved equivalent remains reachable | URL disposition and response check |
| Buyer chooses a finish | Variant and image stay aligned in cart | Staging walkthrough |
| Manual downloaded by owners | Manual remains linked and accessible | Support task test |
| Purchase event collected | One intended event per synthetic order | Browser-to-report reconciliation |
Assign a responsible owner to each acceptance row and decide what blocks release. Use current page and catalog inventories rather than assuming every old page is represented in the new navigation. Keep changes to content, routing and measurement separately identifiable so failures can be traced. Compare the important journeys on mobile and desktop using the same test data. Record exceptions before anyone treats the checklist as complete.
Make preservation an explicit redesign acceptance column
For each existing URL, record the buyer or support task it serves and the approved destination after the redesign. Include low-traffic manuals, order-help pages and saved campaign links in the review. Test a selected variant and an existing-owner support task as well as the new homepage. Hold any unmatched essential destination for a decision before cutover.
Low-traffic pages can still carry essential support content
A page with low recent visits may still be essential for warranties, product instructions or linked customer emails. Combine analytics with operational knowledge before proposing its retirement.
Hold the redesign release when a critical purchase or support path fails. Cosmetic feedback can remain in a follow-up list only when the buyer task and required access still work.
Should a low-traffic page be removed automatically?
Check its operational purpose and evidence first. A manual, return instruction or saved customer link can matter without large search traffic. Route retirement is a separate decision that needs an approved destination or removal plan.
Continue with Guides for stores, software teams and local businesses, Website redesign services and How to migrate a store without losing its useful URLs.