Website redesign: preserve the routes customers already use

Build the inventory before changing URLs

Combine the published sitemaps with a crawl of internal links. Add landing pages from Search Console and any known advertising, email or social campaigns. For each URL, record its language, title, purpose, status and canonical address. Keep a dated export so the team can compare the release against an actual baseline.

Decide whether a page stays, moves, merges into a close equivalent or is deliberately retired. A useful redirect leads to the replacement answer. Sending every removed page to the home page loses context for the visitor. Keep stable URLs when the topic and purpose have not changed; a visual redesign alone does not require renaming them.

Treat language pairs as a relationship

An English route and its Spanish counterpart may use different slugs. Keep an explicit pairing instead of assuming a language-prefix replacement always works. Both pages should identify their own canonical URL and the corresponding published translations. A draft, private lesson or noindex archive entry should not be advertised as an indexable translation.

When repeated campaign publications contain exactly the same article, preserve the original post links and publication assets while choosing a primary text version for indexing. Distinct articles should keep their own identity. Shared titles alone are not enough evidence to merge pages: compare the actual content, purpose and sources.

Test complete customer actions

A successful page load does not prove the website works. Follow a contact form from input to its confirmation, open product downloads, verify payment destinations and try the language switch from deeper pages. Check mobile menus, visible focus and interaction with media. Keep production credentials and private customer information out of public previews.

For pages with 3D demonstrations, preserve the readable content before the model loads. Measure the actual assets delivered, not only the number of requests. A model that looks small in a thumbnail can still include large textures. Test a phone-sized viewport and the fallback when the user never opens the viewer.

Verify the public release and monitor evidence

After deployment, revisit representative URLs and all changed route mappings. Confirm the public sitemap, final canonical addresses and indexing directives. Keep the previous release recoverable. Compare search impressions, clicks and inquiry completions over a consistent period, accounting for seasonal demand and measurement consent. A technically clean redesign improves the foundation; it does not guarantee a particular Google position.

Before your next step

• An old-to-new URL map with an owner for every exception.
• Equivalent language pages and indexable canonical destinations.
• Verified forms, downloads and primary business actions.
• A recoverable release and a dated post-launch comparison.