Your current website is showing its age. Performance is mediocre, the design feels dated, the technology stack is obsolete. You have decided to move to a modern platform. Good call — and if you are still weighing your options, our comparison of Next.js versus WordPress in 2026 can help you decide. But here is the danger: a poorly managed migration can wipe out, in a matter of days, the search rankings you spent years building. At Go To Agency, we have handled dozens of website migrations, and we know that the difference between a successful migration and an SEO disaster comes down to one thing: rigorous preparation. Here is the complete guide, step by step.
The pre-migration audit: the foundation of the entire project
Before you touch anything, you need a complete picture of the current state of your site. This audit is the foundation on which the whole migration strategy rests.
The full URL inventory: crawl your site with a tool like Screaming Frog, Sitebulb, or Ahrefs Site Audit. List every existing URL with its HTTP status, title tag, meta description, H1-H6 headings, and internal and external links. This file will be your bible for the duration of the project.
The organic traffic analysis: identify in Google Analytics and Google Search Console the pages that generate the most organic traffic. These are your strategic pages, and they must be migrated with particular care. Also record the keywords each page ranks for.
The backlink profile: export the list of every external link pointing to your site from Ahrefs, Majestic, or Moz. Those backlinks are your SEO capital. Every external link must resolve to a working URL after the migration, or you lose that authority. The mechanics here are the same ones that make inheriting domain authority through 301 redirects work: link equity follows redirects, but only if the redirects exist and are correct.
The technical elements: robots.txt, sitemap.xml, structured data, canonical tags, hreflang annotations (if the site is multilingual), Open Graph tags. Document everything. Every technical SEO element must be reproduced or improved on the new site.
The performance baseline: record your current metrics — rankings for your main keywords, monthly organic traffic, number of indexed pages, Core Web Vitals. These are the reference points you will use to measure the impact of the migration.
The redirect map: the single most critical element
If you remember only one thing from this article, make it this: 301 redirects are the most critical element of an SEO migration. A 301 redirect tells Google (and your visitors) that a page has permanently moved to a new address.
URL mapping: build a correspondence table between every old URL and its new URL. Old: /our-products/blue-widget.html → New: /products/blue-widget. Every page on the current site must have a destination. No URL should be left orphaned.
Redirect rules: for systematic structural changes, use regex rules. If all your old blog URLs move from /blog/2025/01/article-title to /blog/article-title, a single regex rule handles hundreds of redirects in one line. But test every rule against concrete examples before deployment.
Common traps: redirect chains (A redirects to B, which redirects to C) dilute the SEO signal and slow things down for users. Every redirect should go straight to its final destination. 302 (temporary) redirects do not pass link equity the way 301s do: always use 301s for a permanent migration.
Pages with no equivalent: some pages on the old site will have no direct counterpart on the new one. In that case, redirect them to the most thematically relevant page — the parent category page, or the section landing page. Never redirect everything to the homepage: Google detects these mass redirects and treats them as soft 404s.
Technical preparation of the new site
The new site must be technically flawless before migration day. Not after. Before.
On-page SEO: every page on the new site needs its title tag, meta description, H1, and structured data correctly configured. Ideally, carry over the optimized elements from the old site and improve on them. Do not throw away optimization work that has already been done.
Internal linking: rebuild your internal link structure using the new URLs. Verify that every internal link points to the correct destination. A crawl of the staging environment will surface broken links before launch.
Performance: the new site must be faster than the old one — that is often the primary motivation for migrating in the first place. Run your staging environment through PageSpeed Insights and check the Core Web Vitals (LCP, INP, CLS). Our guide to advanced technical SEO and Core Web Vitals explains how to optimize each metric.
Responsive design: test the new site on mobile, tablet, and desktop. Google uses mobile-first indexing: if your mobile experience is degraded, your SEO will suffer for it.
Sitemap and robots.txt: prepare the new sitemap.xml with every URL of the new site. Check that robots.txt does not block important pages. Both files get submitted to Google Search Console the moment the migration goes live.
Migration day: procedure and vigilance
Launch day is a critical moment that demands meticulous organization. Here is the procedure we follow at Go To Agency for every migration.
Timing: schedule the migration for a Tuesday or Wednesday, early in the day. Avoid Fridays (if something breaks, you do not want to spend the weekend firefighting) and high-traffic periods such as sales events or holidays.
The launch checklist:
| Step | What to verify |
|---|---|
| Activate 301 redirects | Spot-check the redirect map against live URLs |
| Switch DNS to the new server | Propagation complete, no mixed old/new responses |
| SSL certificate | Valid certificate, no mixed-content warnings |
| Test redirects | Use a tool like httpstatus.io on a sample of old URLs |
| robots.txt and meta robots | No stray noindex or disallow directives left over from staging |
| Submit the new sitemap | Uploaded and accepted in Google Search Console |
Immediate verifications: crawl the new site in production to catch 404 errors, broken redirects, and dead internal links. Manually test your 20-30 most strategic pages. Confirm that your analytics and tag management tools fire correctly on the new site.
Communication: inform your internal teams, your vendors, and possibly your customers if the change is significant. A transparent migration is a better-managed migration.
Post-migration monitoring: the critical 90 days
The migration does not end on launch day. The following 90 days are a period of intensive monitoring during which every anomaly must be caught and corrected quickly.
Google Search Console: monitor the coverage report daily. Google will progressively recrawl your site and flag URLs in error (404s, redirect issues, server problems). Address every error within 24-48 hours. Use the URL inspection tool to request indexing of your priority pages.
Rank tracking: watch your strategic keywords with a rank-tracking tool (Semrush, Ahrefs, SE Ranking). A temporary drop of 10-15% is normal in the first few weeks. If the drop exceeds 30% or persists beyond 4 weeks, there is a problem to identify.
Organic traffic: compare organic traffic week over week against the pre-migration period. Identify the pages that have lost traffic and verify that their redirects are working correctly.
404 errors: watch for 404s in Google Search Console and in your server logs. Every 404 is a URL that was not properly redirected. Fix it by adding the missing redirect. In the first few weeks you will probably find several dozen — that is normal; what matters is handling them fast.
Backlinks: verify that your most important backlinks point to pages that respond correctly, either directly or through a redirect. If a valuable external link points to a 404, contact the site owner and ask them to update the link.
Fatal mistakes to avoid at all costs
Over the years we have seen catastrophic migrations caused by mistakes that were entirely avoidable. These are the most dangerous ones.
No redirects at all: it sounds obvious, but we have seen agencies launch a new site on new URLs without a single redirect. The result: 100% of organic traffic lost within days. That traffic can take 6 to 12 months to come back — if it ever fully does.
Changing domain and structure at the same time: Google recommends changing only one thing at a time. If you change the domain (example.com → new-example.com) AND the URL structure AND the technology simultaneously, Google has a hard time connecting the old site to the new one. Where possible, migrate the technology first on the same domain, then change the domain in a second phase.
Ignoring HTTPS: if your old site was on HTTP and the new one is on HTTPS (as it should be), Google treats this as a domain change. HTTP → HTTPS redirects must be in place for every old URL.
Not updating internal links: if your new pages still contain links pointing to old URLs (which then redirect to the new ones), you are creating unnecessary redirect chains. Update every internal link to point directly to the new URLs.
Panicking too early: a traffic dip in the 2-4 weeks following a migration is normal. Google needs to recrawl and reindex your site, and fluctuations are expected. Panic leads to hasty changes that make things worse. Stay methodical and patient.
Protect your SEO capital
A website migration is a strategic project that deserves professional execution. At Go To Agency, we manage the entire process: pre-migration audit, redirect mapping, development of the new site, deployment, and post-migration monitoring. Tell us about your migration project — describe your current site and where you want to take it, and you will get a detailed written response within 48 hours, entirely by email, with no calls or meetings required. Your search rankings are a valuable asset: do not gamble them on an improvised migration.
