How do you protect SEO during a redesign?

Inventory URLs before design files

List existing category, product and content URLs. Which stay, change or disappear? Without this map, a visual redesign can accidentally remove useful content.

Redirect to the relevant destination

Map changed content to its new location. Instead of redirecting every old page to the homepage, use the closest relevant destination. Check permanent redirects and redirect chains before release.

Discovery in the new interface

Category navigation, internal links and search results should remain understandable. A clean layout does not require hiding descriptions or necessary technical information. Test access to filters and product links on mobile separately.

Release checks

Review canonical URLs, indexing controls, sitemaps and server response codes together. Do not accidentally carry a staging noindex setting into production. Conversely, keep unfinished previews out of search.

Compare after launch

Retest forms, orders and content journeys after release. Compare indexing and search traffic with the earlier site over time. Build a measurement plan without assuming a visual redesign guarantees better rankings.

Consider one product address

Suppose /product/abc-123 becomes /catalog/abc-123. Our proposed migration table has separate columns for the old address, new equivalent, publication state and verification result. Prepare it before design starts rather than trying to reconstruct thousands of addresses at release time.

Even when URLs stay unchanged, content and navigation may change. Is the product name clear? Is its technical description retained? Is there a category link? Was useful text moved entirely into an image? A visitor arriving through an old link should still find an answer to the same need. That is a separate objective alongside visual improvement.

What belongs in the release record?

Leave the team verified address examples, not just screenshots. Test the homepage, category, product, editorial article and a missing page separately. Forms, product filters and internal navigation belong in the same review. Preview indexing restrictions must be handled deliberately when preparing production.

Plan a report that compares equivalent periods and page groups before and after release. If traffic declines, separate technical access, redirects, content and changing demand instead of automatically blaming design. A rollback plan should identify both the software and data that can be restored. A redesign cannot guarantee unchanged rankings; the objective is to make the transition observable and manageable.