SEO-safe WordPress website migration checklist
A practical migration checklist covering URL inventory, redirects, metadata, content and post-launch verification.
No agency can honestly guarantee that rankings will never fluctuate after a platform change. The risk can, however, be managed systematically. Most migration failures are caused not by the new technology but by lost URLs, content and internal links.
Create a complete URL inventory
Before development, export every indexable URL from the sitemap, CMS, analytics and Search Console. Every old URL needs one decision: preserve, redirect, merge or intentionally remove.
Preserve search intent and important content
If a page receives organic clicks or backlinks, moving the headline is not enough. Preserve the topic, important sections, title, description and contextual internal links.
Migration is a good time to improve stale content, but changing the platform, URL and content simultaneously makes results harder to diagnose.
Build direct 301 redirects
An old URL should point to the closest relevant new page, not every address to the homepage. Avoid redirect chains: the legacy URL should go directly to the final canonical URL.
Verify the technical signal set
Before launch, check canonical links, hreflang, robots, sitemap, structured data, status codes and HTML language. Multilingual sites need a correct alternative pair for each page.
- one indexable canonical URL;
- one H1 and a logical heading sequence;
- 200 responses for new pages;
- 301 redirects from legacy URLs;
- no staging noindex directive left in production.
Verify reality after launch
Run a complete crawl, test the priority forms and submit the sitemap in Search Console. Monitor 404s, indexing and query changes in the following weeks.
A migration is not finished when the homepage works. It is finished when legacy URLs, the new sitemap and the real Google report have been checked.