Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

Website migration · 17 Nov 2026 · 7 min read

Redirect plan for a website redesign or domain move

A redirect plan maps every old address to its new home so visitors and search engines are not sent to error pages. Here is how to build and test one.

The short answer

A redirect plan is a list of every old website address and the new page each should lead to. Build it from your sitemap, a crawl, analytics and Search Console, redirect each page to its closest match with a permanent redirect, then test the old list after launch and watch for errors.

What a redirect plan is

A redirect plan is a list that says, for every address on your old site, where a visitor and a search engine should be sent on the new one. It is the document that decides whether a redesign or a domain move keeps its traffic or quietly loses it.

The reason is simple. Other sites link to your old addresses, customers have bookmarked them, and search engines have stored them. When a page moves and nothing points from the old address to the new one, all of that leads to an error page. Visitors leave, and search engines gradually drop the old address without learning where the content went.

A redirect plan is most important when addresses change. That happens in a redesign that renames pages, a move to a new platform with a different address pattern, a change of domain name, or a switch from one secure or non-secure form of address to another. If every address stays exactly the same, you may need very little.

Why do redesigns need a redirect map?

New designs tend to rename and reorganise. A page called "services" becomes "what we do", a blog changes its folder, and old pages are merged or dropped. Each change breaks the old address. The map is the record of every one of those changes and its replacement.

It also forces useful decisions. Which old pages still deserve a home? Which have been merged into one? Which are gone for good? Answering these before launch is much cheaper than discovering them from a drop in enquiries a month later. If you are still deciding the new structure, our guide to website navigation and menu structure helps settle the pages before you map them.

A map also protects the work you have already paid for. Years of content and links are an asset, and a redirect plan carries part of that value across to the new site. Nobody can promise exactly how much; the aim is to avoid throwing it away.

How do I build a redirect map?

Build it in a spreadsheet with a few columns, before the new site goes live. Start with a complete list of old addresses, then match each to a new one.

Step 1: collect every old address

Do not trust memory. Combine several sources: the old site's XML sitemap, a crawl of the old site with a crawling tool, the pages that get visits in your analytics, the pages that appear in Search Console and any addresses that other sites link to. Add images, downloadable files and old landing pages that may sit outside the main menu. Save a copy of this list; you will need it for testing.

Step 2: decide what happens to each

For each old address, choose one of four outcomes:

  • Same address on the new site, so no redirect is needed.
  • A new address with the closest matching content, so it redirects there.
  • Merged into another page, so it redirects to the page that now covers the topic.
  • Removed with no replacement, so it returns a "gone" or "not found" response, and you offer a helpful error page.

Match by meaning, not by convenience. Sending every old page to the home page looks tidy but tells search engines and visitors that the specific content has gone. Search engines may treat such redirects as errors. Redirect each page to the closest relevant new page.

Step 3: choose the type

Use a permanent redirect when an address has moved for good, which is the case in most redesigns. Use a temporary one only when the move is genuinely short term. Our guide to 301 and 302 redirects explains the difference and the status codes.

Step 4: write the rules

Convert the map into rules for the server or the platform. Small sites can list each pair. Larger sites can use patterns, such as moving a whole folder, but patterns need careful testing because one wrong pattern can break many pages. A developer should do this part.

Step 5: keep the map

Store it with the site documents. A redirect rule should stay in place for a long time, because links and bookmarks do not disappear on a schedule. Check the current documentation from search engines on how long to keep redirects, and when in doubt keep them.

Domain moves need extra care

When the domain name changes, every address changes at once, so the plan must cover the whole site. Redirect each old address to its exact new equivalent on the new domain, and keep the old domain registered and pointing at the redirects for as long as you can. Let search engines know about the move using the tools they provide. Our checklist for changing your domain name lists the steps in order, and the guide to moving to a new host covers the hosting side.

Also think about everything that uses the old domain: email addresses, social media profiles, business listings, printed material, adverts, links in newsletters and documents. Update each one. A redirect catches the old links, but it is better for the links to be correct.

Agree in advance who is responsible for the redirects and for checking them. This is the sort of thing that belongs in the website development contract, with a clear statement of what the developer will deliver at launch and what the owner supplies.

How do I check redirects after launch?

Test on the day and again a few weeks later. Do not rely on the developer's word alone. A short routine finds most problems.

  1. Take your saved list of old addresses and run it through a tool that follows redirects and records the final address and status code. Many crawling tools can do this in bulk from a list.
  2. Check that each old address returns a permanent redirect and lands on the page you planned, in a single step.
  3. Look for chains and loops, where one redirect leads to another, or back to itself. They slow the page and may be dropped. Our guide to redirect chains and loops shows how to fix them.
  4. Click through your most important old pages by hand, especially those with the most visits and the most links.
  5. Check that the final pages load properly, return a normal success response and are not blocked from search engines.
  6. Open Search Console and watch for rising "not found" or redirect errors over the next weeks.
  7. Check your analytics for a sudden loss of visits to key pages.

Fix what you find, and add any missed addresses to the map. Speed is worth checking at the same time, because a redesign can change page weight; see how to check and improve website speed.

Mistakes that cost traffic

  • Redirecting everything to the home page.
  • Forgetting images, PDFs and old campaign pages.
  • Using temporary redirects for permanent moves.
  • Building long chains because earlier redirects were never updated.
  • Removing the rules after a few weeks.
  • Leaving internal links pointing at old addresses, so every click goes through a redirect.
  • Letting the new site go live with its search block still on from the test stage.
  • Skipping the map because the new site "has the same content".

Treat the plan as part of the project, with an owner and a deadline before launch. Legal and policy pages, such as the accessibility statement, also need their addresses carried across. Forms need care too, because a changed address can break the action behind them; see website contact forms for what to test.

If you want a team to prepare and test the redirect map during a rebuild, our website development service page describes the work. Search results can take time to settle, and we cannot say how long yours will take, so keep checking for several weeks after launch.

Related guides

Questions and answers

Why do redesigns need a redirect map?

Redesigns usually rename, merge or remove pages, which breaks old addresses that other sites, bookmarks and search engines still use. A redirect map records where each old address should go, so visitors and search engines reach the right new page.

How do I build a redirect map?

List every old address from the sitemap, a site crawl, analytics and Search Console. Decide for each whether it stays, redirects to the closest new page, is merged or is removed. Choose permanent redirects for lasting moves and have a developer write and test the rules.

How do I check redirects after launch?

Run the saved list of old addresses through a tool that follows redirects. Check each returns a permanent redirect to the planned page in one step, look for chains and loops, click key pages by hand, and watch Search Console and analytics for errors and traffic drops.

Should I redirect every old page to the home page?

No. Redirect each old page to the closest relevant new page. Sending everything to the home page can look like an error to search engines and does not help visitors find the content they wanted.

How long should I keep redirects in place?

Keep them for as long as you reasonably can, since links and bookmarks do not expire on a schedule. Check the search engines' current documentation for guidance, and avoid removing rules after only a few weeks.

Do I need a redirect plan if only the design changes?

If every address stays the same, you need very little, but check anyway. Many redesigns change menus, folders or page names without anyone noticing, so compare a list of old and new addresses before launch.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote