Moving a WordPress site is rarely just a design or hosting task. A careful WordPress SEO migration checklist for redirects, canonicals and sitemaps helps you protect crawlability, preserve important URLs, and reduce the chance of technical issues after launch.
This matters whether you are changing permalinks, moving from one theme to another, switching SEO plugins, merging content, or redesigning a WooCommerce store. SEO results still depend on content quality, site structure, internal linking, page experience, and ongoing maintenance, so migration planning should cover more than just the visible pages.
What a WordPress SEO migration checklist should cover
A migration checklist is a structured way to compare the old site and the new one before changes go live. It usually includes URL mapping, redirects, canonical URLs, XML sitemaps, robots.txt, metadata, image handling, and post-launch monitoring in Google Search Console and Google Analytics 4.
WordPress itself provides the framework, but themes, plugins, hosting, and custom code all affect the final result. For example, a theme may output a canonical tag, an SEO plugin may generate titles and sitemaps, and the server may control redirects. If those layers disagree, search engines can receive mixed signals.
Before changing anything, crawl the existing site, export key URLs, and note which pages drive traffic, links, enquiries, or sales. If you need a wider review of current technical issues, a free website SEO audit can help you spot risks before a migration begins.
Redirects: map old URLs to the closest relevant new page
Redirects tell browsers and search engines that a page has moved. A permanent redirect, usually a 301, is commonly used when a URL change is lasting. A temporary redirect, such as a 302, is better when a move is short term and the old URL may return.
The safest approach is to map each important old URL to the closest equivalent new URL. Avoid sending every removed page to the homepage, because that gives users poor results and can confuse search engines. Keep redirect chains short, and check for loops where one URL points to another that points back again.
Redirects are especially important during HTTPS migrations, domain changes, permalink updates, and content consolidation. They also matter in WooCommerce when old product URLs are replaced by new product slugs or category structures. Do not forget internal links, menu items, breadcrumbs, and any hard-coded template links.
Common redirect mistakes to avoid
One common issue is letting a redirect plugin and server-level rules manage the same paths. Another is redirecting deleted content to unrelated pages. If an old page has no close replacement, consider whether it should be consolidated into a broader topic rather than pushed somewhere random.
After launch, test a sample of redirected URLs manually and check crawl reports for broken paths. If you are planning broader link maintenance as part of the move, the backlink building process guide is useful for understanding how clean link structures support long-term website growth.
Canonicals: help search engines identify the preferred version
A canonical URL is a signal that suggests which version of a page should be treated as the main one when similar URLs exist. This is useful on sites with duplicate content patterns such as product filters, printer-friendly views, UTM variants, archives, or category pages that overlap with posts.
Canonical tags do not force search engines to obey every time, so they should align with your site structure and internal linking. A self-referencing canonical is often appropriate on ordinary indexable pages. Avoid pointing canonicals to unrelated content, broken pages, redirecting URLs, or pages marked noindex unless you have a very specific reason and understand the implications.
During migration, compare the rendered page source on the old and new versions, rather than trusting only a plugin setting. Themes, SEO plugins such as Yoast SEO, Rank Math, All in One SEO, or SEOPress, and custom code can all affect canonical output. Most sites should use one primary SEO plugin, not several overlapping ones.
If you switch SEO plugins as part of a migration, review titles, meta descriptions, canonicals, robots settings, sitemaps, schema, and social metadata after the change. Plugin interfaces may change over time, so confirm current options in the official documentation before relying on any specific setting.
XML sitemaps and robots.txt: guide crawling without creating mixed signals
XML sitemaps help search engines discover preferred URLs, but they do not guarantee indexing. Include indexable pages that you genuinely want discovered, such as core service pages, key posts, product pages, and useful category pages. Exclude redirects, error pages, staging URLs, and low-value duplicates unless there is a clear technical reason to include them.
WordPress core or an SEO plugin may generate sitemaps, so check for duplication after a migration. If the site uses multilingual content, make sure each language version is handled consistently and that translated pages are represented correctly in the sitemap structure.
robots.txt controls crawler access, not search removal. Blocking a URL in robots.txt does not necessarily remove it from the index, and it can also stop crawlers from seeing a noindex directive on that page. Use it carefully, especially on sites with filters, search results, APIs, or ecommerce parameter URLs.
For official guidance on crawling and indexing, the Google Search crawling and indexing overview is a helpful reference when you are checking technical decisions against current best practice.
Pre-launch and post-launch checks for indexing, content and performance
Before launch, verify that important pages still have clear title tags, accurate meta descriptions, clean permalinks, descriptive headings, and helpful internal links. These elements support user understanding and help search engines interpret the page purpose. Avoid keyword stuffing, duplicated titles, or thin archive pages that add little value.
Image SEO also matters during migration. Keep descriptive file names where practical, use meaningful alternative text for informative images, compress files sensibly, and confirm that responsive image delivery still works. Decorative images may not need detailed alt text, but useful images should be described for accessibility and context.
Check Core Web Vitals and overall speed after major changes. Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift are influenced by hosting, theme code, scripts, images, and caching behaviour. A migration can accidentally make pages heavier, so test on staging first if possible and avoid stacking multiple optimisation plugins that do the same job.
Also review WordPress security basics. Unexpected redirects, injected pages, or hacked content can undermine trust and visibility. Keep backups, update core, themes and plugins, and use strong access controls. If a migration involves content pruning, review traffic, links, relevance, and replacement options before removing pages permanently.
Troubleshooting with Search Console, analytics and audits
After launch, monitor Google Search Console for discovery, crawl, and indexing trends, and use Google Analytics 4 to compare engagement and landing-page performance. These tools measure different things, so a drop in impressions is not the same as a drop in sessions or conversions.
Use the URL Inspection tool to understand how a specific page is seen, but do not treat it as a promise of inclusion in search results. A page may be crawlable and still not indexed if it is duplicated, weak, blocked elsewhere, or judged less useful than alternatives.
Watch for patterns such as redirected pages still appearing in internal links, canonicals pointing to removed URLs, XML sitemaps listing non-indexable pages, or robots rules left active from a staging site. If a large site move is involved, a structured review can save time later. For broader optimisation support, Backlink Works SEO education and website growth resources can be useful alongside your own audit process.
Conclusion
A WordPress SEO migration is safest when you treat redirects, canonicals and sitemaps as part of one connected system. The goal is not to chase a plugin score, but to keep the site understandable for users, crawlers and editors while preserving the strongest existing signals.
Plan carefully, back up the site, test changes before going live, and monitor the pages that matter most after launch. A tidy migration will not guarantee rankings or traffic, but it gives your content the best chance to be crawled, interpreted and maintained properly over time.
Frequently Asked Questions
Do I need redirects for every changed WordPress URL?
Yes, for important URLs that have moved permanently. Map them to the closest relevant replacement rather than sending them all to the homepage.
Should my sitemap include redirected or noindex pages?
Usually no. XML sitemaps are best used for canonical, indexable URLs that you actually want search engines to discover.
Can a canonical tag replace a redirect?
No. A canonical tag is a signal, not a substitute for a proper redirect when a page has permanently moved.
What should I check after changing SEO plugins during a migration?
Review titles, descriptions, canonicals, schema, sitemap output, robots settings, social metadata and any duplicate functionality from other plugins.
- Sponsored Ad -
