Protect Useful Links During a Website Redesign
Start with a complete URL inventory before you move a single page. Map every old URL to its closest equivalent, redirect only when the content truly moved, and remove pages that no longer serve a purpose. Then update internal links and verify language variants so users and search engines reach the right page.
Build a URL inventory before you touch the design
Export every URL from your current site, including pages that are not in the main navigation. Use a crawler, your server logs, and your content management system export. Combine them into one spreadsheet with columns for the full URL, page title, primary topic, and whether the page still serves a business or user need.
Mark each URL as keep, move, merge, or remove. Keep means the page stays at the same address. Move means the content goes to a new URL. Merge means two or more pages become one. Remove means the content is going away with no direct replacement. This decision drives everything that follows.
Map equivalent pages and choose redirects carefully
For every move or merge, identify the single best destination on the new site. A redirect should send users to a page that answers the same intent, not just to the homepage. If no equivalent exists, consider whether the old page should be kept or removed.
Use permanent redirects for content that has moved for good. Avoid redirect chains and loops. Test a sample of redirects with a simple request tool: enter the old URL and confirm that the response is a single redirect to the intended destination, not a chain or a 404. That is your pass or fail test for this step.
Remove pages honestly and update internal links
Some pages should disappear. A discontinued product, an outdated event, or a duplicate service page may no longer belong. When you remove a page, let it return a clear not found response rather than redirecting it to an unrelated page. Users and search engines both benefit from an honest signal.
After the new site is live, crawl it to find internal links that still point to old URLs. Update those links to the new destinations. This includes navigation, footer links, calls to action, and any hardcoded links in templates or content. Broken internal links waste user attention and weaken the browsing experience.
Verify language variants and hreflang
If your site has English and Arabic versions, each language should have its own URL. Do not canonicalize all translations to a single default language. Instead, set a self-canonical on each language page and add reciprocal hreflang tags that point to the equivalent page in the other language.
Suppose you run a bilingual consultancy site. The English services page lives at /en/services and the Arabic at /ar/services. Each page should canonicalize to itself and include hreflang links to the other. If the Arabic page canonicalizes to the English one, the Arabic version may not appear in search results for Arabic queries. Check this manually for a few key pages.
Test the migration with a concrete pass or fail check
Before you announce the redesign, run a focused test. Pick ten important old URLs that you moved or removed. For each, request the old URL and record the response. A pass means the response is either a single permanent redirect to a relevant new page or a clear not found for a genuine removal. A fail means a redirect chain, a redirect to an unrelated page, or a server error.
Also verify that the new site returns the correct language variant when you request a language-specific URL. If the Arabic URL serves English content or redirects to the English page, the language setup needs correction. Fix these issues before launch to avoid confusing users and losing the value of existing links.
Tradeoffs and ongoing maintenance
Keeping every old URL is not always possible or desirable. A clean URL structure may require moving pages, and some content should be retired. The tradeoff is between preserving link equity and maintaining a clear, logical site. Document your decisions so you can revisit them if needed.
After launch, monitor your server logs for frequent 404 errors. If a removed page still gets significant traffic, consider whether a redirect or a new page is warranted. Review your redirect map periodically and update it as content changes. A redesign is not a one-time event but the start of a new structure that needs care.
References and related reading
Continue reading
A practical next step
Explore the related Devign work, then discuss your requirements before committing to a project scope.