Website redesign redirects should be planned before the new site goes live, not after old links start breaking. When a redesign changes page URLs, the safest approach is to map each important old URL to the most relevant new destination, use a direct permanent redirect, update internal links to point to the final URL, and test the result after launch. That protects visitors from dead ends and gives search systems a clearer path from the old structure to the new one.
Why redirects belong in the redesign plan
A redesign often changes more than colors and layouts. Service pages may be renamed, location pages may move into a new structure, old content may be consolidated, and navigation may be reorganized. If those URL changes are handled casually, existing bookmarks, internal links, search listings, and outside links can keep pointing to addresses that no longer work.
The redirect plan is the bridge between the old site and the new one. It should be treated as part of the launch work, alongside content review, forms, mobile testing, analytics, backups, and final quality checks.
Build an old-to-new URL map before launch
Start with a list of the URLs that exist on the current site. Then decide what should happen to each one after the redesign. The important part is not simply creating a redirect for everything. The important part is choosing the destination that best matches what the old page was actually about.
- Page still exists with a new URL: Redirect the old address to the new version.
- Several pages were intentionally combined: Redirect each old page to the consolidated page only when it truly covers the same subject.
- Page was removed with no meaningful replacement: Let it return a proper not-found response rather than forcing visitors to an unrelated destination.
- URL did not change: No redirect is needed just because the page was redesigned.
For example, if a location page is being reorganized but the business still wants a final canonical page such as Website Design Kasson MN, the old address should point directly to that final page rather than to a temporary or intermediate URL.
Choose the final destination, not the closest-looking page
A redirect is most useful when the new destination answers the same basic need as the old page. Sending every retired page to the homepage may seem convenient, but it can create a confusing experience when someone expected a specific service, article, or location page.
Think about the old page’s purpose. What was the visitor trying to learn or do? The new destination should preserve that intent as closely as possible. If no page provides a reasonable replacement, a real not-found response can be clearer than a redirect that lands somewhere unrelated.
Use direct permanent redirects and avoid chains
When a URL has permanently moved, a permanent server-side redirect such as a 301 or 308 is generally the right type. The redirect should go straight from the old URL to the final destination whenever possible.
Redirect chains add unnecessary steps. A visitor should not have to travel from an old URL to an intermediate URL and then to the real page. The same applies to crawlers. If the final page is known, point to it directly.
Suppose an older page eventually belongs at Website Design Waseca MN. The clean setup is one permanent redirect to that final page, not a sequence of older replacements that happen to end there.
Update internal links instead of relying on redirects
Redirects are useful for old links that you do not fully control, but the redesigned site should not keep linking to its own old URLs. Update navigation, buttons, footer links, article links, location links, image links, and other internal references so they point directly to the final canonical addresses.
This reduces unnecessary redirect hops for visitors and makes the site’s current structure easier to understand. It also prevents old URL patterns from living indefinitely inside new content.
If a page should now link to a final location page such as Website Design Faribault MN, use that final address directly in the new site instead of depending on a legacy redirect to get there.
Know when not to redirect
Not every removed URL deserves a replacement. A redirect should represent a meaningful move or consolidation, not simply hide the fact that a page no longer exists.
Avoid forcing unrelated retired pages into one general destination. If an old event page, outdated announcement, discontinued service, or duplicate page has no useful successor, a proper 404 or 410 response may be more accurate. The key question is whether the destination genuinely satisfies the reason someone followed the old URL.
This is especially important during large redesigns because broad redirect rules can create accidental matches. A wildcard may save time, but it can also send unrelated pages to the wrong place if the pattern is not reviewed carefully.
Test redirects before and after launch
A redirect plan is not finished when the rules are entered. Test the important old URLs and confirm the complete result.
- Start with the old URL.
- Confirm that it returns the intended permanent redirect.
- Check that it lands directly on the final URL.
- Confirm that the destination loads successfully.
- Verify that the destination has the expected canonical URL.
- Check that the new site’s internal links point directly to the destination instead of the old address.
- Repeat the test after launch, when the live server, caching, plugins, and CDN rules are all in effect.
For a larger redesign, a focused website audit can help identify redirect chains, broken destinations, old internal links, canonical conflicts, and other migration issues that are easy to miss when pages are checked one at a time.
Keep redirects in place while users and search systems catch up
Do not remove permanent redirects immediately after a redesign appears stable. Old addresses may still exist in search results, bookmarks, email messages, social posts, directories, and links from other websites. Search systems also need time to revisit old and new URLs and process the move.
Google’s current site-move guidance recommends keeping redirects in place for at least a year, and from a user perspective it can make sense to keep useful permanent redirects even longer. The better long-term cleanup is to update links you control so they point directly to the new URLs while the redirects continue protecting older references.
A simple website redesign redirect checklist
- Create a complete list of important current URLs before launch.
- Decide which URLs are staying, moving, merging, or being removed.
- Map each moved URL to the most relevant final destination.
- Use permanent redirects for permanent moves.
- Point directly to final destinations instead of building chains.
- Do not redirect unrelated removed pages to a generic page just to avoid a 404.
- Update internal links, menus, buttons, and sitemaps to the new URLs.
- Verify canonicals and indexability on the new pages.
- Test old URLs before launch and again after the live change.
- Keep the redirects in place long enough for old references to be replaced naturally.
Protect the parts of the old site that still matter
A redesign should improve the website without breaking useful paths that already exist. The strongest redirect plan preserves the intent of important old pages, points directly to the right new destinations, and removes avoidable chains from the site’s own links.
If you are planning a redesign and want help reviewing old URLs, new page destinations, internal links, and post-launch checks, contact 507 Web Design before the redirect map becomes an emergency repair job.