You migrate a WordPress site without losing search rankings by mapping each old URL to its closest new match with a direct, one-to-one permanent server-side 301 redirect and keeping page signals unchanged. You also update WordPress addresses, internal links, sitemaps, and Search Console so search engines find and credit the new location.
A migration here means moving WordPress to a new domain, subdomain, directory, or host. Rankings depend on whether search engines can follow that move cleanly. Small breaks in redirects, links, or page code cause most losses.
Table of Contents
- Map and redirect every old URL
- Update WordPress addresses and internal links
- Carry over titles, content, and code signals
- Publish a clean sitemap and file the address change
- Monitor the traffic shift and expect fluctuation
Map and redirect every old URL
List every live old URL from your sitemap, crawl, analytics, and server logs. Pair each one with the closest new equivalent, not the homepage. According to Google Search Central, permanent redirects transfer signals to the new location, as explained in permanent redirect guidance.
Avoid chains where one redirect points to another redirect. Chains slow crawling and weaken signal transfer. Fix image, file, feed, and paginated URLs too.
- Keep each redirect direct, one hop, old page to new page.
- Use the same method site-wide, usually server config or a redirect plugin.
- Test top pages by hand, then test the full map with a crawler.
Update WordPress addresses and internal links
Change the domain or directory in Settings > General under WordPress Address and Site Address. For moves managed in code, set WP_HOME and WP_SITEURL in wp-config.php instead. The WordPress Developer Handbook describes this address change and content replacement in migration instructions.
Replace old-domain strings throughout posts, pages, widgets, menus, and media links. Re-save permalinks to rebuild rewrite rules and .htaccess. Then click through navigation, search, forms, and checkout to confirm internal links resolve.
Carry over titles, content, and code signals
Keep titles, meta descriptions, H1s, body text, image alt text, canonical tags, internal links, hreflang, and structured data the same. Change them only to fix a clear problem. Consistent signals help new pages stay eligible for the same queries and rich results.
Watch common losses during theme or builder changes. Headings may shift levels, alt text may drop, and canonical tags may point to staging. Compare HTML from old and new versions for key templates. Keep URL style, pagination, and schema output steady.
Publish a clean sitemap and file the address change
Build a new XML sitemap with only the new canonical URLs. Remove staging, deleted, redirected, and non-canonical addresses. Reference the sitemap in robots.txt, allow crawling of new pages, and submit it in Search Console.
For a domain or subdomain change, verify both old and new properties in the same Search Console account. Then submit Change of Address on the old property. The tool supports the move but does not replace 301 redirects.
Monitor the traffic shift and expect fluctuation
Check Search Console Performance, Page Indexing, and Crawl Stats plus server logs after launch. Look for 404s, redirect errors, indexed old URLs, and missing new URLs. According to Google Search Central, old-site traffic should fall as new-site traffic rises, as described in site move processing guidance.
Expect rankings and crawl rate to fluctuate for a few weeks, longer for large sites, even with correct redirects. Keep old-site 301s live for many months. Keep extra server capacity because the new site is crawled more heavily at first.




