Website migration — moving to a new platform, redesigning your URL structure, or switching domains — is one of the highest-risk activities in SEO. Done carelessly, it can wipe out years of accumulated rankings in days. Done carefully, with a clear SEO migration plan, most sites come through with minimal disruption. This checklist walks through what to do before, during, and after launch, in plain terms any business owner or marketing manager can follow.

Before You Touch Anything: Inventory and Benchmarking

The most common migration mistake is starting on the new site before properly documenting the old one. If you do not know exactly what URLs exist and how they perform, you cannot protect them.

Crawl every URL

Use a crawler such as Screaming Frog, Sitebulb, or Ahrefs Site Audit to spider your entire current site. Export every URL, its <title> tag, meta description, H1, word count, inbound internal links, and HTTP status code. Save this as your source-of-truth spreadsheet — you will return to it throughout the project.

For a typical small-business site this might be 200–400 URLs. A Sydney accounting firm migrating from Squarespace to a custom Next.js build might find they have 60 blog posts, 12 service pages, and 30 tag/category pages they had completely forgotten about. All of them need a decision: redirect, recreate, or retire.

Benchmark your analytics and Search Console

Before launch, export at least 12 months of Google Search Console data: top queries, impressions, clicks, and average position for every URL. Do the same in GA4 — sessions, conversions, and landing page performance. Store it somewhere permanent. This is your baseline; without it you cannot tell whether a post-launch dip is a migration issue or a normal seasonal fluctuation.

  • Export Search Console performance report filtered by page (last 12 months)
  • Export GA4 landing page report with sessions and conversions
  • Screenshot your current Core Web Vitals scores from Search Console's Core Web Vitals report
  • Record your current domain authority and backlink count in Ahrefs or Moz — useful context, not a ranking signal itself
  • Note any structured data types currently active (FAQPage, LocalBusiness, Article)

Build Your Redirect Map Before Writing a Single Line of New Code

A redirect map is a spreadsheet that pairs every old URL with its new destination and the redirect type (301 permanent, in almost every case). It is the foundation of a safe replatforming SEO project, and it needs to be complete before development starts — not patched in at the end.

The goal is a true 1:1 map: every crawled URL gets a row. For pages you are retiring with no logical replacement, the destination should be the most relevant parent page or the homepage — not a blanket redirect of everything to the homepage, which Google treats as a soft 404.

If you are moving from WordPress to a headless Sanity setup, your URL structure may change significantly — for example from /category/post-slug/ to /blog/post-slug/. Every one of those old paths needs a 301 pointing to the new canonical URL. We cover the full technical implementation in our WordPress to Sanity migration guide.

JSON · redirect-map-sample.json
[  { "from": "/services/web-design-sydney/", "to": "/services/web-design", "status": 301 },  { "from": "/blog/category/seo/",          "to": "/blog/seo",           "status": 301 },  { "from": "/old-contact-page/",           "to": "/contact",            "status": 301 }]

Keep the spreadsheet version as your master record and derive the JSON or .htaccess rules from it programmatically. Never manage redirects by hand across two separate sources — they will diverge.

During Build: Staging, Content Parity, and Noindex

Staging must be blocked from indexing

Every new site should be developed on a staging URL — something like staging.yourdomain.com.au or a Vercel preview URL. That environment must return a noindex meta tag on every page and ideally block crawlers in robots.txt as well. Googlebot is fast; a staging site left open can get indexed before launch, creating duplicate content problems that take months to untangle.

BASH · robots.txt (staging only — remove before launch)
User-agent: *Disallow: /

Removing noindex and updating robots.txt on launch day is a checklist item, not something you will remember to do at 11 pm after a stressful cutover. Write it down.

Content and metadata parity

For every page you are keeping, the new version should match or improve on the original's <title>, meta description, H1, and body content. Rewriting content at the same time as migrating is fine — just do not accidentally delete text that Google has ranked. A common slip is migrating a service page and forgetting the 400-word body copy that lived below the fold on the old design.

  • Title tags match or improve on the originals
  • Meta descriptions carried across (not left blank)
  • Canonical tags present and pointing to the correct URL
  • Structured data (JSON-LD) recreated for pages that had it
  • Internal link structure preserved — check with a crawl of the staging site
  • Images have descriptive alt text and are not accidentally served at 3× their display size

Validate your sitemap and redirects before go-live

Run the staging site through our sitemap validator to confirm every URL in sitemap.xml returns a 200 status and has a canonical tag that matches its sitemap entry. Then run the redirect map through our broken link checker to verify each 301 resolves correctly and there are no redirect chains (A → B → C) that add unnecessary latency.

Launch Day: The Go-Live Checklist

Migration day is not the time for surprises. Run through this list in order, ideally during business hours when you can respond quickly to anything unexpected.

  1. Point DNS to the new server and confirm propagation (use dnschecker.org for a multi-region view)
  2. Remove noindex from all public pages and confirm with a curl -I check on a sample page
  3. Update robots.txt to allow all crawlers (unless specific paths should remain blocked)
  4. Submit the new sitemap.xml to Google Search Console
  5. Confirm all 301 redirects are live with a spot-check of 10–20 high-priority URLs
  6. Test structured data on key pages with Google's Rich Results Test
  7. Verify GA4 and any other analytics tags are firing on the new domain
  8. If it is a domain migration, add the new property in Search Console and use the Change of Address tool
  9. Update your Google Business Profile URL if applicable
  10. Check that the SSL certificate is valid and all pages load over https

After Launch: 30 Days of Monitoring

The work is not finished at go-live. Google re-crawls at its own pace — some sites are fully re-indexed within a week, others take three to four weeks. During that window, monitor closely.

Watch 404 errors daily for the first two weeks

Search Console's Coverage report (now under Indexing → Pages) will surface any URLs Google is hitting that return a 404. Each one is a redirect that was missed or implemented incorrectly. Fix them promptly — the longer a backlinked URL returns a 404, the more link equity bleeds away.

Track Core Web Vitals

A new platform often means a different performance profile. A Cronulla retailer moving from a heavily-customised WooCommerce store to a headless storefront might see Core Web Vitals improve dramatically. Conversely, a migration to a theme-heavy page-builder setup could make them worse. Check Search Console's Core Web Vitals report at the two-week and four-week marks and compare against your pre-migration screenshots.

Compare rankings and traffic at 30 days

Pull the same Search Console and GA4 reports you exported before the migration. Compare page by page, not just at the aggregate level — a site-wide traffic number can mask individual pages recovering at different rates. Some fluctuation in the first two to three weeks is normal. Sustained drops on specific URLs after 30 days warrant investigation: check whether the redirect fired, whether content parity was maintained, and whether the page has acquired any new crawl errors.

One important note: a careful migration minimises risk, but nobody can guarantee your rankings will hold. Any agency or freelancer promising zero ranking impact is overstating what is within anyone's control. What careful process does is give you the best possible chance and a clear audit trail to diagnose problems if they arise.

Frequently asked questions