Nov
22

How to Write a Redirect Plan for a Domain Change This Week

11/22/2026 08:00 PM door Seovaro Team in


How to Write a Redirect Plan for a Domain Change This Week

A domain change is happening this week, and you need a redirect plan that is ready before the switch, not after traffic starts to fall. A redirect plan for a domain change is simply a complete map that tells browsers and search engines where every old page now lives on the new domain.

Who needs this sprint? Site owners, marketers, and developers with a launch date they cannot move. Why does sequencing matter? Because a redirect written in a hurry and patched later is how chains, loops, and missing pages are born.

Work day by day: inventory first, map second, build third, and test before anyone touches DNS. Follow the order below and do not skip ahead.

Your 7-Day Redirect Plan for a Domain Change

Think of the week as a production line. Each day has one clear output and one owner. If a day slips, cut scope from the bottom of the priority list, never from testing.

Start by freezing content changes on the old site, so your crawl, analytics, and redirect list all describe the same website.

  • Day 1: Full inventory of the old domain
  • Day 2: URL-to-URL mapping decisions
  • Day 3: Writing the actual redirect rules
  • Day 4: Staging setup and internal link updates
  • Day 5: Testing every rule and fixing failures
  • Day 6: Launch preparation and rollback planning
  • Day 7: Go live, verify, and monitor

Day 1 and Day 2: Inventory, Then Mapping

On Day 1, crawl the old domain and export every indexable URL. Add pages from your sitemap, analytics, and search console data, because crawlers miss orphaned pages that still earn traffic. Record status codes and traffic in a shared spreadsheet.

On Day 2, give every old URL exactly one destination on the new domain. Match pages by intent first: a product page goes to the equivalent product page, a guide goes to the equivalent guide. Only send a page to the homepage when no relevant destination truly exists.

How to prioritise the mapping work

Work in value order. Map your highest-traffic and highest-revenue pages first, review them with a second person, and let low-traffic archive pages follow a simpler pattern.

Watch for traps. Do not create chains where an old URL points to a page that itself redirects, and do not map several different topics onto one generic page.

Day 3 and Day 4: Build the Rules and Prepare the New Site

On Day 3, turn the spreadsheet into server rules. Most teams use permanent 301 redirects for a domain move, because the change is not temporary. Keep the spreadsheet as the source of truth, and generate rules from it rather than typing addresses by hand.

Before launch, run every old and new address through the WWW Redirect Checker workflow in your plan mindset: check that host versions, protocol versions, and trailing slashes resolve consistently. A domain move is the worst moment to discover that www and non-www versions behave differently.

On Day 4, update the new site itself. Change internal links to point directly at the new URLs, and update the sitemap, canonical tags, and hard-coded links in templates and emails. Redirects are a safety net for outside links, not a crutch for your own navigation.

  1. Generate redirect rules from the approved mapping sheet.
  2. Deploy the rules to a staging copy of the new domain.
  3. Update internal links, sitemaps, and canonical tags.
  4. Prepare new analytics and search console properties.
  5. Write the rollback steps while everyone is still calm.

Day 5 and Day 6: Test Hard, Then Rehearse Launch

Day 5 is testing only. Crawl the staging site through the redirects and check that every old URL lands on a live page with a 200 status in one hop. Test top pages on mobile and desktop, plus journeys that make money, such as checkout and contact forms.

Keep a simple fix log: the old URL, what it did, what it should do, and who fixed it. Retest fixed rows the same day, because one rule can break a pattern covering fifty pages.

Day 6 launch rehearsal

On Day 6, rehearse the launch. Confirm who changes DNS, who deploys the rules, who watches analytics, and who can roll everything back. Lower DNS time-to-live in advance, so changes and any rollback propagate faster.

Good sequencing also protects your content quality. Teams under time pressure sometimes stuff every old keyword variant into new pages to compensate for a move, a habit as counterproductive as keyword stuffing itself. Keep pages focused on their real topic and let clean redirects do the transfer work.

Day 7: Go Live, Verify, and Keep Watching

Launch early in the day when the full team is available, never late on a Friday. Deploy the rules, switch the domain, then immediately test the top fifty URLs from your sheet by hand. Check that forms, logins, payments, and tracking all work on the new domain.

In the first forty-eight hours, watch crawl errors, traffic, and conversions. Small dips can be normal, but a sharp drop on one section usually points to a missing rule or wrong destination. Fix from the sheet, redeploy, and retest.

For more launch checklists, browse the guides on the Seovaro blog and add the useful ones to your runbook, so the next move will not need the same frantic week.

Ready to test your own move before launch day arrives? Try the WWW Redirect Checker on your old and new addresses, work through any chains or mismatched versions it reveals, and fix them on staging while you still have time to spare.

Frequently Asked Questions

How long should redirects stay in place after a domain change?

Keep them in place for at least a year, and ideally permanently. External sites, bookmarks, and printed materials can send visitors through old addresses for a very long time.

Should every old page redirect to the homepage?

No. Send each page to the closest matching page on the new domain. Homepage redirects for unrelated content look like soft errors and waste the value the old page had built.

What if I discover a missing redirect after launch?

Add it from your mapping sheet as soon as you spot it, then check crawl errors and server logs for similar gaps. A fast, documented fix prevents a small gap from becoming a pattern.

Can I write a redirect plan in less than seven days?

Yes, for a small site you can compress inventory and mapping into one day. Keep testing and rehearsal as separate steps, because those are the stages that prevent launch-day failures.