Migrating a WordPress site can feel risky—especially when search rankings and organic traffic are on the line. Follow this practical checklist to keep rankings steady, avoid traffic loss, and finish the move with confidence.
Before you begin: scope, backups, and a rollback plan
Start with a short planning session. Identify pages that drive most traffic and conversions (top landing pages, blog posts, product pages). Create a full backup and export your database and uploads. Document your current server and WordPress configuration: PHP version, permalink structure, active plugins, SSL certificate, and custom rules in your .htaccess or nginx config.
- Export content with the WordPress exporter and make a separate SQL dump.
- Copy /wp-content/uploads and any custom directories.
- Note current URLs, canonical tags, hreflang (if used), structured data, and robots.txt rules.
Run an SEO audit to capture baseline signals
Record essential metrics so you can compare after the migration. Use Google Search Console, Google Analytics (or GA4), and a crawl tool.
- List top 50 URLs by organic sessions and clicks.
- Download a sitemap.xml and a full crawl (Screaming Frog, Sitebulb, etc.).
- Note index coverage issues and any manual actions in Search Console.
Set up the destination environment
Prepare the new host or server to mirror the current environment as closely as possible.
- Create a staging URL (not indexed) like staging.example.com or use an IP-based preview.
- Install the same WordPress version and plugins, at least initially; update incrementally after testing.
- Provision SSL and ensure PHP settings (memory_limit, upload_max_filesize) are adequate.
Move files and database carefully
Migrate content and update site URLs in the database. Prefer tools designed for WordPress migrations (WP Migrate DB Pro, All-in-One WP Migration) or a controlled manual export/import.
- Replace old URLs in the database using a serialized-aware tool to prevent corrupting widgets and plugin settings.
- Copy uploads and check file permissions.
- Keep the old site live until you validate the new one.
Preserve URL structure, metadata, and technical SEO
Maintaining the same URL structure is the safest way to keep rankings. If you must change URLs, map every old URL to a new URL with 301 redirects.
- Keep permalinks identical unless there’s a strong reason to alter them.
- Ensure meta titles, descriptions, structured data, and rel=canonical tags are preserved.
- Transfer robots.txt and sitemap.xml; update any absolute URLs inside them.
Testing checklist on the staging site
Before switching DNS, verify the staging site behaves like production.
- Run a full crawl and compare HTTP status codes to your baseline.
- Check mobile and desktop render, structured data, hreflang (if applicable), and the sitemap.
- Test key forms, e-commerce flows, and redirects.
- Verify SSL and mixed-content warnings are resolved.
Schedule the migration and minimize downtime
Pick a low-traffic window and estimate DNS TTL timing. Lower TTL on the existing DNS a day in advance to speed the switch.
- Put the old site into maintenance mode only if necessary. Avoid full teardown until DNS propagation completes.
- Change DNS A records or update your hosting control panel as planned.
- Keep both sites writable? If not, freeze content updates or plan how to reapply post-migration changes.
Launch validation
Immediately after the switch, run targeted checks.
- Verify site loads on the live domain with HTTPS and correct canonical tags.
- Check the most important landing pages for 200 status and consistent content.
- Submit the updated sitemap to Google Search Console and request indexing for critical pages.
- Monitor Search Console for crawl errors and coverage issues over the next 72 hours.
Set up monitoring and post-launch tasks
Post-migration monitoring is where you catch issues early and protect rankings.
- Keep detailed traffic and ranking monitoring for two to four weeks. Watch organic sessions and impressions.
- Check server logs for 404 spikes and fix them with 301 redirects where needed.
- Re-enable any performance or security caching and verify cache headers and CDN settings.
- Update any third-party services (CDN, marketing tags, analytics, image CDN) with the new origin if required.
Common migration pitfalls and how to avoid them
- Broken internal links: run a site-wide crawl and repair internal link targets or site URLs rewritten incorrectly.
- Lost organic pages: ensure your sitemap lists all important URLs and that none are accidentally blocked by robots.txt or noindex tags.
- Performance regressions: compare Core Web Vitals and server response times; tune PHP, caching, and CDN configuration.
- Missing structured data: confirm schema markup carried over, especially for product, article, and local business schemas.
When to get professional help
If your site has high traffic, complex redirects, multi-language setups, or large e-commerce catalogs, consider partnering with a developer or an SEO specialist. A small business can avoid costly ranking drops by using experienced hands for the migration. If you want an expert who combines development and SEO, our web development service can plan and execute the move: Web Development.
Conclusion
A careful, documented migration keeps search rankings intact. Back up everything, mirror your environment, preserve URLs and metadata, validate thoroughly on staging, and monitor closely after launch. Follow this checklist, and you’ll minimize downtime and protect your organic traffic. Need help with a migration plan tailored to your small business? Reach out through our web development page to get a practical migration roadmap.