What is a redirect plan for a domain change, and how do you execute one? It is the ordered sequence that moves every important address from your old domain to the correct page on the new one, without losing visitors or rankings. Who needs it? Anyone renaming a business, merging sites, or moving to a cleaner domain.
Why does order matter? Because each step depends on the one before it: you cannot test redirects you have not implemented, and you cannot implement redirects you have not mapped. When does each part happen? Inventory first, mapping second, implementation third, monitoring last, with no stage skipped.
This guide is the hands-on sequence. It walks chronologically from building your URL inventory through launching redirects to verifying the move in analytics, so you can work down the steps in order.
Begin before you touch any settings. Open a spreadsheet with columns for old URL, new URL, redirect type, status, and notes. This document is your plan, and every later step updates it.
Work down the list and fill the new URL column with the closest matching page on the new domain. Match by topic and intent, not convenience. Where no equivalent exists, choose the nearest category page, and flag true dead ends for a genuine not found response.
While you map, confirm the new domain itself resolves correctly. Check its DNS and hosting are live before you build anything on top of them.
With the map complete, prepare the new site fully before any redirect goes live. Destination pages must exist, load correctly, and carry their final addresses. Redirecting to pages still changing creates rework and errors.
Now implement the plan exactly as mapped. Add permanent redirects for each old URL to its single new destination. Avoid redirecting everything to the homepage, and avoid chains where an old URL hops through an intermediate address.
Implementation varies by platform, from server files to hosting panels to plugins, but the checking habit is universal. Keep the spreadsheet open and mark each rule as added, group by group, so nothing is silently missed.
Background on how search engines interpret site moves is covered in related guides on the Seovaro blog, which pairs well with this execution sequence.
Testing is a separate step, not a hope. Before launch, work through the plan with fresh eyes, because errors found now cost minutes and errors found by customers cost trust.
At launch, activate all redirects together rather than in slow batches, submit the new sitemap, and use the change of address process in Search Console if your setup qualifies. Then update your own properties: social profiles, email signatures, directory listings, and adverts pointing at the old domain.
Tell real people too. A short note to customers and partners explaining the new address prevents confusion and reduces support questions after the change.
The plan ends with verification, not launch. Set up monitoring on day one, following the principles in Google guidance on getting started with Analytics, so old and new traffic can be compared honestly.
Watch three things daily for the first two weeks. First, traffic and conversions on the new domain against the old baseline. Second, crawl and index coverage in Search Console, including any spike in not found errors. Third, your top pages individually, confirming each recovered its visits at the new address.
Keep the old domain and its redirects in place long term. Links across the web will point at the old address for years, and the plan only works while those redirects remain live.
Starting your own domain move this week? Work through step one today, and use the domain into IP tool to verify your new domain resolves correctly before you map a single URL onto it.
Keep them indefinitely if you can, and for at least a full year as a minimum. External links and bookmarks point at old addresses for years, and removing redirects breaks every one of them at once.
No. Redirect each URL to its closest matching page. Homepage redirects waste relevance, frustrate visitors who expected specific content, and are often treated as soft errors.
Expect weeks, not days, with some fluctuation normal during the transition. Correct one-to-one permanent redirects, consistent internal links, and steady monitoring give the cleanest transfer.
Launching before testing. Untested plans hide loops, chains, and missed top pages, each found by a visitor or crawler instead of by you. Testing catches them while they are cheap to fix.