Moving a WordPress site is one of the moments when small technical changes can have a large SEO impact. A careful WordPress Site Migration Checklist: SEO Steps to Protect Rankings helps you preserve crawlability, indexing signals, internal links, metadata, and page structure while you move to a new domain, hosting setup, theme, or permalink format.
The safest approach is to treat migration as both a technical project and an SEO project. That means planning redirects, checking canonical URLs, reviewing XML sitemaps, and monitoring Google Search Console and analytics after launch rather than assuming WordPress will handle everything automatically.
Start with a migration plan, not a plugin
Before changing URLs, themes, or servers, document what currently exists. Export your main page types, posts, product pages, categories, tags, and any custom post types. If you use a plugin such as Yoast SEO, Rank Math, All in One SEO, or SEOPress, note where it manages titles, meta descriptions, sitemaps, schema, and redirects so you can preserve the right settings or replicate them carefully on the new site.
WordPress SEO tools are useful, but they are not a replacement for planning. One site may need a simple setup, while another may depend on ecommerce product data, multilingual content, or local landing pages. The right approach depends on your content workflow, technical constraints, budget, and how much custom code or plugin logic supports the current site.
A practical first step is to crawl the old site and create a URL inventory. Keep a record of high-value pages, pages with backlinks, and pages that receive organic traffic. If you need a broader SEO baseline before the move, a free website SEO audit can help you identify issues that should be fixed before migration.
Protect on-page SEO elements during the move
On-page SEO refers to the visible and structural signals on each page, such as the title tag, meta description, headings, copy, internal links, image alt text, and URL. During a migration, these can change accidentally if templates are replaced or content is imported incorrectly.
Make sure each important page keeps a clear purpose and a unique title tag that matches search intent. Meta descriptions do not directly guarantee rankings, but they still support click-through by helping people understand the page. Avoid rewriting content simply to fit a plugin score. A readability or SEO suggestion is guidance, not a substitute for editorial judgement.
Permalinks deserve special attention. If you change the structure of post or product URLs, use 301 redirects for old addresses that should permanently move to new ones. A 301 redirect tells search engines and users that the page has a new home. Temporary redirects are better reserved for short-term changes. Avoid redirect chains, loops, and blanket redirects to the homepage.
Check crawlability, indexing, and canonical URLs
Crawling means search engines can discover a URL. Indexing means they decide to store it in search results. A page can be crawlable without being indexed, so do not assume that being accessible to Google automatically means it will appear in search. After migration, review robots.txt, robots meta tags, and any noindex settings to make sure important pages are not being blocked by mistake.
Canonical URLs are also important. A canonical tag is a signal that indicates the preferred version of a page when similar URLs exist. It does not force search engines to choose that URL, so the rest of the site must support the same preference through internal links, redirects, and sitemaps. Check the rendered page source, not just the plugin interface, because themes or custom code can introduce duplicate or conflicting canonicals.
XML sitemaps help search engines discover preferred URLs, but they do not guarantee indexing. Make sure the sitemap includes useful, indexable pages and excludes staging URLs, redirected pages, error pages, and other low-value or duplicate addresses. WordPress core or an SEO plugin may generate the sitemap, so avoid running multiple sitemap tools at the same time unless you have checked for overlap.
For official guidance on crawlability, sitemaps, robots, and indexing, Google’s SEO Starter Guide is a useful reference.
Redirects, internal links, and broken links after launch
Redirect mapping is one of the most important parts of a migration. Match each valuable old URL to the closest relevant new URL rather than sending everything to the homepage. If a page was removed and there is no useful replacement, decide whether it should return a proper 404 or be consolidated into a related page. The best choice depends on the page’s history, links, and user value.
After launch, update internal links in navigation menus, breadcrumbs, contextual links, category archives, and HTML sitemaps. Internal links help users and crawlers discover related content, and descriptive anchor text makes those links clearer. Automated internal-link plugins can create repetitive or irrelevant links, so review their output carefully.
Broken links deserve attention because they affect user experience and can waste crawl effort. Check not only internal links but also redirects, canonicals, and sitemap entries. If you use a redirect plugin, confirm it is not competing with server-level rules or custom rewrite logic. Conflicting redirect systems can create inconsistent behaviour.
Watch site speed, schema, and special content types
A migration often changes more than URLs. New themes, builders, scripts, or hosting settings can affect website speed and Core Web Vitals. Largest Contentful Paint measures when the main content becomes visible, Interaction to Next Paint reflects responsiveness, and Cumulative Layout Shift measures visual stability. These are experience signals, not the whole SEO picture, and results can vary between lab tools and real-user data.
Test the new site on a staging copy before launch where possible. Check image sizes, compression, responsive delivery, CSS, JavaScript, caching, fonts, and third-party scripts. Do not chase a perfect score if it means breaking features, accessibility, analytics, or security. WordPress performance depends on hosting, theme quality, plugin load, database health, and custom code, not just one optimisation plugin.
Schema markup can help search engines understand page content, but it should match what users can see on the page. Watch for duplicate schema if your theme, ecommerce plugin, and SEO plugin all generate structured data. This matters for product pages, article pages, local business information, and multilingual setups. For product-focused sites, review the WooCommerce documentation on WooCommerce SEO considerations alongside your own page templates.
If you rely on images, keep filenames descriptive, alt text meaningful, and dimensions appropriate. Decorative images do not need keyword-stuffed alt text. Image optimisation supports accessibility and speed as well as discovery.
Post-migration monitoring and SEO audit process
Once the new site is live, monitor the important signals rather than making assumptions. Check Google Search Console for crawl issues, indexing changes, sitemap status, and URL inspection details. The URL Inspection tool can be helpful, but it does not guarantee inclusion in search results. In Google Analytics 4, compare organic landing page performance, engagement, and conversions with a similar previous period, remembering that analytics and Search Console measure different things.
Look for unexpected noindex tags, blocked resources, canonical mismatches, missing metadata, broken redirects, and pages that lost internal links. If you run local SEO pages, product pages, or translated content, review each section separately. Local pages should contain genuinely useful location information, while multilingual pages should use consistent language targeting and careful canonical handling.
When you need a structured follow-up, a website audit helps separate technical issues from content issues. If you want a broader process for cleaning up a site after the move, the backlink building process page can also be useful context for understanding how internal and external authority signals fit into wider SEO work.
Conclusion
A WordPress migration is safest when you treat it as a controlled SEO change, not just a design or hosting switch. Preserve valuable URLs where possible, map redirects carefully, check crawlability and indexing settings, and verify that titles, canonicals, sitemaps, and internal links still make sense on the new site.
Results will depend on content quality, technical setup, site structure, authority, competition, and ongoing maintenance. A careful checklist reduces risk, but it does not remove the need for monitoring and gradual improvement after launch.
Frequently Asked Questions
What should I back up before migrating a WordPress site?
Back up the database, files, uploads, themes, plugins, and any custom code or configuration files. If possible, keep a separate copy of your URL list, redirects, sitemap exports, and analytics data for comparison after launch.
Do I need to keep old URLs working after a migration?
Yes, for pages that have value or external links. Use relevant 301 redirects so users and search engines can find the closest replacement page. Avoid sending important old URLs to the homepage unless there is no better option.
Will submitting a new sitemap make Google index everything faster?
No. A sitemap helps discovery, but indexing still depends on crawlability, canonical signals, noindex rules, internal links, page quality, and server responses. It is useful, but it is not a guarantee.
Should I use more than one WordPress SEO plugin after migration?
Usually no. Running multiple full SEO plugins can create duplicate titles, conflicting canonicals, sitemap duplication, or overlapping schema. Choose one primary SEO plugin and check that its features do not duplicate functionality already handled by your theme or custom code.
- Sponsored Ad -
