To migrate a WordPress website without losing important SEO settings, record your current pages, prepare redirects, test the new site and monitor it after launch. Missing URLs, unwanted noindex rules and broken redirects can affect search visibility. A WordPress migration may involve:
- new hosting;
- a domain change;
- different URLs;
- a website rebuild.
Each needs a different level of SEO work. This WordPress Migration SEO Checklist covers what to check before launch, on launch day and during the next 90 days.
Which Type of WordPress Migration Are You Planning?
Check what will change before starting. A hosting move with unchanged URLs does not normally need page redirects. A domain move usually does.
| Migration | Main risk | Priority check |
| New hosting, same URLs | Downtime or server errors | DNS, HTTPS and live page access |
| New domain | Old URLs stop working | URL mapping, redirects and Search Console |
| New URL structure | Broken links and lost pages | Old-to-new redirect map |
| New theme or site rebuild | Missing content or SEO tags | Page-by-page staging comparison |
| Move from another CMS to WordPress | Changed URLs and templates | Content, redirects, canonicals and schema |
Phase 1: WordPress Migration SEO Checklist Before Launch
1. Save Your Current Search Performance
Export important landing pages, queries, clicks and impressions from Google Search Console. Record organic traffic and enquiries in GA4 where tracking exists. A 12 to 16-month history can help identify seasonal changes, but use whatever reliable history is available. Also keep a list of pages that:
- generate leads;
- attract useful backlinks;
- support important services.
These pages deserve extra checks during the migration. Record the launch date so you can compare the same pages afterwards.
2. Crawl the Old Website and Save Its SEO Data
Use a crawler such as Screaming Frog SEO Spider to export:
- URLs;
- status codes;
- titles;
- canonicals;
- indexing rules;
- internal links.
Save the XML sitemap too. Compare important pages with staging before launch.
| SEO item | Old live site | New staging site |
| Main service page | Current URL and content | Intended live URL and matching content |
| SEO title | Existing title | Preserved or approved replacement |
| Canonical | Current preferred URL | Intended new preferred URL |
| Indexing | Current indexable status | Planned live indexing status |
| Redirect | Current URL | Relevant new destination, if changed |
Fill in the actual URLs and values for your project. This is a comparison template, not a completed Wixdek case study.
3. Map Every URL That Will Change
Create a spreadsheet showing each old URL and its best new destination. Include:
- service pages;
- articles;
- PDFs;
- URLs with backlinks.
Pages keeping the same URL do not need redirects simply because the hosting changes.
| Old URL | New URL or decision | Launch action |
| /roof-repair-london/ | /services/roof-repairs/ | Permanent 301 redirect |
| /contact-us/ | /contact/ | Permanent 301 redirect |
| /about/ | /about/ | Keep unchanged |
| /expired-offer/ | No suitable replacement | Return 404 or 410 after review |
Redirect users directly to the closest relevant page. Avoid:
- redirect chains;
- mass redirects to the homepage.
Test your mapping before launch.
4. Check the Staging Site Before It Goes Live
Build the new WordPress website in a separate staging environment. Protect it with a password or another access-control method. A noindex rule may provide extra protection, but robots.txt alone does not keep a URL out of Google. Compare staging pages with the live site. Check:
- page copy;
- images;
- mobile layouts;
- menus;
- enquiry forms.
If the migration includes a design change, see the planned article Changing a WordPress Theme Without Losing Rankings. At launch, remove access restrictions from the new live website. Keep staging private. Also remove unintended live noindex rules.
5. Review SEO Output and Back Up the Site
Check that the intended:
- titles;
- meta descriptions;
- canonicals;
- schema;
- XML sitemap
survive the migration. Watch for old-domain canonicals and duplicate tags created by the theme or SEO plugin. If two versions of a page remain accessible, review whether a canonical or redirect is needed. The planned guide How to Fix Duplicate Content in WordPress explains those options. Take a full backup of the website files and database. Test the restore process and confirm who will handle a failed launch.
For a domain change, retain access to the old domain and any hosting needed for redirects.
Phase 2: WordPress Migration SEO Checklist for Launch Day
6. Publish and Test Your Redirects
Activate the redirect map when the new URLs go live. Check that each old URL:
- returns a permanent redirect;
- reaches the correct destination;
- lands on a page returning HTTP 200.
Use direct redirects rather than chains. For a domain move, Google’s guidance is to keep redirects for at least one year, preferably longer. Update links you control to point directly to the new URLs.
7. Check DNS, HTTPS and Live Access
If hosting or domain settings changed, confirm DNS points to the correct server. Open the live site over HTTPS. Check for:
- certificate warnings;
- missing images;
- server errors;
- inaccessible pages.
Keep the old setup available until the new website works reliably.
8. Remove Live Indexing Blocks and Fix Internal Links
In WordPress, go to Settings > Reading. Check Discourage search engines from indexing this site. Make sure the live website is not unintentionally discouraged from indexing. Also check:
- page-level noindex;
- HTTP response headers;
- robots.txt;
- canonical tags.
Important pages should use the correct live-domain canonicals. Update:
- menus;
- buttons;
- internal links;
- stored domain references.
Use a WordPress-safe database replacement method when updating stored URLs.
9. Publish the Sitemap and Update Search Console
Open the live XML sitemap before submitting it. It should contain preferred, indexable URLs, not:
- staging URLs;
- retired pages;
- redirecting pages.
Submit it in Search Console. For a domain move, verify the new property and use Google’s Change of Address tool when the move meets its requirements. That tool is not needed for a normal hosting move or simple URL-path change. A sitemap helps discovery but does not guarantee indexing.
Phase 3: WordPress Migration SEO Checklist After Launch
10. Run a Live Crawl Within 48 Hours
Crawl the new website and compare it with your original URL inventory. Prioritise:
- missing service pages;
- redirect failures;
- unexpected noindex rules;
- incorrect canonicals.
Test enquiry forms and confirm GA4 events or other lead tracking still work. Fix broken high-value landing pages before minor metadata issues. Record each problem, owner and fix.
11. Watch Search Console and Organic Leads
During the first two weeks, check for:
- new crawl errors;
- blocked pages;
- unexpected canonical choices;
- missing URLs.
After a domain move, the old domain’s indexed URLs may fall as replacement URLs appear. Use your baseline to compare the same landing pages and enquiries, rather than only looking at total traffic. Search demand can also change, so investigate the pages and queries behind any decline.
12. Complete Your 30, 60 and 90-Day Reviews
| When | Main review | Response |
| Days 1–2 | Access, redirects, forms and index rules | Fix urgent failures |
| Days 3–14 | Crawl and indexing reports | Resolve missing URLs and wrong canonicals |
| Day 30 | Organic landing pages and conversions | Compare with pre-launch data |
| Day 60 | Remaining redirects and index gaps | Investigate pages not yet recovered |
| Day 90 | Traffic, enquiries and unresolved errors | Complete the migration audit |
Rankings may move while Google processes a migration. Do not rewrite working pages before identifying the actual cause. If the site also becomes slower, check hosting, themes and plugins. The planned guide How Plugin Bloat Hurts WordPress Speed and Security covers that issue. For harder problems, a technical SEO review can help identify crawl, canonical and redirect faults.
WordPress Migration SEO Checklist: Final Sign-Off
Use these checks after completing the detailed steps.
Before Launch
- Save Search Console, traffic and conversion baselines.
- Crawl the old website and compare key pages with staging.
- Map changed URLs and test redirects.
- Restrict staging and review SEO output.
- Verify a working backup.
Launch Day
- Activate redirects.
- Check DNS, HTTPS and live access.
- Remove live password protection and unwanted indexing restrictions.
- Check canonicals and internal links.
- Review the XML sitemap.
- Verify Search Console and domain-move settings where needed.
After Launch
- Crawl the new website within 48 hours.
- Test forms and tracking.
- Fix indexing and redirect problems during the first two weeks.
- Review organic landing pages and leads at 30, 60 and 90 days.
Frequently Asked Questions
What Is a WordPress Migration SEO Checklist?
A WordPress Migration SEO Checklist helps you protect important SEO settings, URLs and search visibility before, during and after a WordPress migration.
Can You Migrate WordPress Without Losing SEO?
You can reduce the risk with URL mapping, staging tests and careful launch checks. Google visibility may still fluctuate while the migration is processed.
Do I Need 301 Redirects for a WordPress Hosting Move?
Not when page URLs stay the same. Use permanent redirects when URLs change and relevant replacement pages exist.
How Long Does a WordPress Migration Take to Appear in Google?
There is no fixed timeframe. Google may take weeks or longer to recrawl and process moved URLs, depending on the website.
Should My WordPress Staging Site Be Indexed?
No. Keep staging private while making sure the new live website is accessible and uses the correct indexing rules.
How Often Should I Review a WordPress Migration SEO Checklist After Launch?
Check urgent technical issues during the first 48 hours, then review indexing and performance during the first two weeks. Complete deeper checks at 30, 60 and 90 days.
Need Help With Your WordPress Migration SEO Checklist?
A missed redirect or blocked service page can put valuable search traffic at risk. Wixdek helps UK businesses review WordPress migration plans and identify problems before launch. Explore our WordPress SEO services and request a WordPress SEO migration review.
By Wixdek
