Use this SEO website migration checklist before you change your domain, switch CMS or redesign your site. First, make a list of the pages that bring in business and decide what should happen to each one. Keep useful URLs where you can. Where a URL has to change, send people straight to the closest equivalent and test the route from the old link all the way to the enquiry form.
A new homepage can look fine while the pages you depend on are broken. Take a Dublin contractor whose Google Business Profile points to a roofing service page. If that old address leads to a generic homepage after a rebuild, the person clicking still has to work out whether the contractor does the job they need. A good migration starts with that old link, before the design is signed off.
The migration checklist at a glance
Use this summary to plan the work and assign owners. Each stage is explained in more detail below.
Before launch
If you need help with redirect mapping or pre-launch crawl checks, scope the work with a technical SEO specialist before launch.
- Export current URLs from the sitemap, Search Console and analytics, and mark the pages that bring in enquiries or sales.
- Record each priority page’s title, main heading, canonical URL, key content and how its form or call button works.
- Map every old URL that changes to its closest new equivalent, using a server-side 301 or 308 redirect.
- Decide which removed pages should return 404 or 410 because nothing replaces them.
- Keep staging behind a login, and list every noindex rule, robots.txt block and staging canonical to remove at launch.
- Verify the new site in Search Console and keep the existing verification method on the new build.
- Name the person who can roll back the launch, and pick a quieter trading day for the switch.
On launch day
- Turn on redirects and test priority old URLs. Each should reach the right page in one hop.
- Confirm new pages return HTTP 200, use a self-referencing canonical and carry no stray noindex.
- Check robots.txt and point internal links and navigation at final URLs.
- Submit the new XML sitemap, and use the Change of Address tool if the domain has changed.
- Send a test enquiry from a phone and confirm it arrives and is tracked.
In the weeks after launch
- Review the Page indexing and Performance reports for your priority pages.
- Crawl the site or check server logs for 404s, redirect loops and server errors.
- Update your Google Business Profile, directory listings and social profiles with the new URLs.
- Ask sites that send you useful visits to update their links.
- Keep the redirects in place for at least a year.
SEO website migration checklist by stage
Record the pages and enquiry paths you depend on
Build your list from the current sitemap, Search Console and your enquiry records. Add pages linked from trade directories, profiles, articles or customer emails. Start with pages that bring in relevant visits, answer questions before a quote, or give customers a way to call, book or buy.
For each page, save its address, title, main heading, canonical URL and the sections people use. On a service page that might mean coverage, hours and contact details. Capture how the enquiry form works as well. Record where it sends the submission, what the customer sees and whether the visit is recorded in analytics.
Give each priority page an owner. The business owner can confirm where the company works. A developer can check the redirect and form, while the person managing search can check indexability and the sitemap. Agree who makes the final call if one of those checks fails.
Map old URLs to the closest valid destinations
Keep an existing URL when the page still serves the same purpose. When the address has to change, use a direct permanent redirect to the page that best serves the original visitor. Google’s site move documentation lists server-side 301 and 308 redirects for permanent moves.
The paths below are illustrative. Put the full addresses and expected responses in your own redirect sheet.
| Old path | Expected result | Reason |
|---|---|---|
/emergency-plumber-dublin/ |
Redirect to /services/emergency-plumbing-dublin/ |
The new page covers the same service and area. |
/about/ |
Keep /about/ with HTTP 200 |
The page can keep its address on the new platform. |
/plumbing-help/ |
Redirect to /services/plumbing/#questions if that section answers the same questions |
The useful information moves with the visitor. The destination page keeps its own canonical URL. |
/expired-summer-offer/ |
Return HTTP 404 or 410 if there is no suitable replacement | The offer has ended and there’s nowhere useful to send the visitor. |
Run through the list from the old address, including URLs with external links. If one old URL redirects through two intermediate pages, change the first redirect to point straight to the final destination. Check that the final page works and matches the reason someone clicked.
Protect staging and prepare the launch checks
Keep unfinished work behind a login on staging. Before release, list the settings that belong there and need to come off the public version. A staging canonical or a noindex rule left in a shared template can affect a whole section of the live site.
Test one of each page type your site depends on. A service business might pick a service page, a location page, a contact form and a blog post. An online shop should also test a category and product page. See Digiwizard’s website redesign guide for decisions about the wider rebuild.
Write down who can roll back the launch and how. If every mobile quote form fails, it may be worth delaying the release while the developer fixes it. A small display issue on an old post can usually wait. Make those decisions before you’re trying to diagnose faults on a live site. Google’s migration guidance also recommends changing one thing at a time where you can. If you plan a new domain, a new platform and a new design, launching them separately makes any drop far easier to trace.
What goes in a 301 redirect map?
Give each changed URL a row with the old address, new canonical address, redirect status and test result. For example, if /roof-repairs-dublin/ becomes /services/roof-repairs/, verify that the old URL returns one permanent redirect and the new page returns HTTP 200. Then update your internal links to point straight to the new page and test the enquiry form there.
What to verify on launch day
Start with the old URLs customers already use. Open them on the public site, follow the redirect and test the call, form or booking path on the new page. That takes you through the same route a person would follow from a saved link, directory or search result.
| Check | What a pass looks like |
|---|---|
| Redirects | Priority old URLs reach the equivalent page in one hop. |
| Public pages | The final URL loads with HTTP 200, the intended canonical and no accidental noindex. |
| Navigation and sitemap | Internal links point directly to final URLs. The sitemap lists the pages you want indexed. |
| Enquiry flow | A mobile test submission reaches the correct inbox or system. The call button uses the intended number. |
| Tracking | Test enquiries show up in the agreed records, and the tracking fires where it should. |
| Business information | The site, profile and key directories still agree on contact details and where the business works. |
Submit the new sitemap in the relevant Search Console property. Use URL Inspection to check a few important pages. The live test tells you whether Google can currently access the page. Google’s stored index view may still show the old information until it crawls the site again.
When the domain changes, use Google’s migration documentation to check whether the Change of Address tool applies. If you’re only changing paths on the same domain, focus on the redirects, internal links and sitemap.
How long a migration takes to settle
Google processes a move one URL at a time, as it recrawls old and new addresses. Its documentation says most pages on a small or medium-sized site can take a few weeks to move across, and larger sites take longer. Rankings can fluctuate in that period, so compare priority pages week by week rather than reacting to a single day’s data.
Googlebot also crawls more heavily than usual straight after a move, because it follows redirects from the old site as well as crawling the new one. If your hosting is on a small plan, check with your provider that the server can handle the extra requests.
Planning a website migration or redesign?
We map every URL, redirect and tracking tag before launch so you keep the rankings and enquiries you already earn. See how our technical SEO service works, or browse our client case studies.
How to diagnose a visibility drop
Look at the pages that had a job to do before the move. Compare service and location pages individually in Search Console, then check what a visitor can do on those pages. Overall traffic can look healthy while one important service loses calls.
| What you notice | First place to look |
|---|---|
| Google still shows the old address | Check the old redirect, new canonical and both URLs in Search Console. |
| Several new pages lose impressions together | Look for a shared robots or canonical setting and confirm those pages appear in the sitemap. |
| Visits continue but enquiries fall | Submit a mobile form, try the call link and check whether your team received the enquiry. |
| A location page stops showing for town-specific searches | Compare old and new wording, the redirect target and the areas listed on the page. |
| ChatGPT still links to an old page | Open the cited URL, follow the redirect and check whether the destination still backs up the answer. |
Fix server errors, wrong redirects and broken forms as soon as you confirm them. For changes in impressions, look at the affected pages over comparable dates. A bank holiday or seasonal drop in demand can also change the number of calls a business receives.
Keep sources and business details connected
When a service page moves, preserve the facts people use to choose the business. If a contractor serves Tralee and Killarney, the replacement page should still explain what work the contractor does in those towns and how to request a visit. A redirect keeps an old link usable. The new page still has to answer the original question.
Update the website link on Google Business Profile and on the directories or trade listings you control. Where an association or publication links to an important old URL, ask it to update the link. Google recommends keeping permanent redirects for at least a year, and older links may keep sending customers long after that.
If you audit ChatGPT citations after a site move, save the exact question and open its source links after launch. A citation may point to an old address that redirects correctly, or to a page that no longer confirms the service or area. Record which you found so you know whether to fix the destination or ask a publisher to update a link.
Questions About SEO Website Migrations
Will moving from one WordPress host to another affect SEO?
If the public addresses stay the same, check that the new host serves the same pages with the same canonicals, robots rules and forms. Map redirects for addresses that actually change.
Should every old page go to the homepage?
Send each old URL to the closest page that answers the same need. If a page has been removed and there is no suitable replacement, return HTTP 404 or 410.
How long should permanent redirects stay in place?
Google recommends at least one year after a move. Keep useful redirects longer if people still reach the old addresses from saved links or directories.
Can we launch if the sitemap works but the forms fail?
Fix the enquiry route first if the site depends on leads. Submit a test on mobile and check the message, delivery and tracking.
What should I check if my website disappears from search after a redesign?
Inspect an affected URL in Search Console. Check its live response, canonical, robots rules and old redirect. If the problem appears on more than one page, check whether those pages share a template.
How long does it take to recover after a website migration?
For a small or medium-sized site, Google says most pages can take a few weeks to move across in its index. Larger sites take longer. If priority pages are still losing visibility after that, check their redirects, canonicals and content against the old versions.
Do I need the Change of Address tool?
Only when you move from one domain or subdomain to another. You don’t need it for an HTTP to HTTPS move, a switch between www and non-www, or path changes on the same domain.
Get the migration reviewed before launch
Bring your current sitemap, the proposed launch date and the pages you depend on for enquiries. Digiwizard’s technical SEO services cover crawl and indexing checks, redirects and migration risks. Book a free consultation if you’d like those checks reviewed before release. If you’re weighing up quotes for migration support, our guide to SEO cost in Ireland shows how to compare them.