PeakKR
🚚

Website Migration SEO Checklist

Most ranking disasters aren't penalties β€” they're migrations nobody checked. This is the checklist for redesigns, domain moves and replatforms. The rule: snapshot before, verify after, fix within the week.

βœ“ 3 phases Β· 16 tasks βœ“ Covers two weeks before launch through two weeks after βœ“ The complete template β€” no email wall

Built for: Anyone shipping a redesign, replatform or domain move on a site with traffic worth keeping

1

Pre-launch (1–2 weeks out)

6 tasks Β· phase 1 of 3

  • Full crawl of the current site saved (URLs, titles, metas, status)
  • Rankings + Search Console data exported as baseline
  • Redirect map written: every old URL β†’ its new home (no chains)
  • New site crawled on staging: metas, headings, schema present
  • Analytics & Search Console verified for the new setup
  • Robots.txt and sitemap ready for the new structure
2

Launch day

5 tasks Β· phase 2 of 3

  • Redirects live and spot-checked on the top 50 URLs
  • Staging noindex REMOVED (the classic disaster)
  • New sitemap submitted in Search Console
  • Analytics firing verified on the live site
  • Site search & forms tested end-to-end
3

Post-launch (days 1–14)

5 tasks Β· phase 3 of 3

  • Full crawl vs. the pre-launch snapshot: vanished pages, changed metas, broken redirects
  • 404 report in Search Console monitored daily for the first week
  • Rankings tracked daily on target keywords; investigate drops >3 positions
  • Internal links updated to final URLs (kill redirect hops)
  • Page speed re-checked β€” new templates often regress it
Make it run itself

A template on a page is a start. A template that assigns itself is a system.

Copy this into any tool you like β€” it's yours. But the failure mode of every checklist is the same: it lives in a doc nobody opens on the day the work happens. In PeakKR this template is a phased project: phases unlock in order, each task lands on a real person with a due date, and your client watches the phases complete on their own hub link instead of emailing "where are we?"

  1. Create a project from the template β€” the phases and tasks above appear on the board, in order.
  2. Assign the phase owners once. New tasks default to the project's PM; recurring ones respawn on schedule.
  3. Share the client hub link. Progress, wins and reports at the same URL all engagement β€” no status meetings required.
FAQ

Using this template well

How much traffic does a botched migration lose?

Unchecked migrations routinely drop 20–60% of organic traffic, and recovery takes months because every day of broken redirects compounds. Nearly all of it is preventable with the pre-launch snapshot and a redirect map β€” the two items teams skip when the deadline slips.

What is the single most common migration mistake?

Shipping the staging site's noindex tag to production. It's one line, it deindexes the entire site, and it's on launch day of this checklist for a reason. The second most common: redirect chains, because the new redirects stack on top of old ones.

Do I need this for a redesign that keeps all the URLs?

Yes β€” a lighter version. URLs surviving doesn't protect titles, metas, headings, schema and internal links, all of which redesigns quietly rewrite. The crawl-vs-snapshot diff catches what the new templates changed without anyone deciding to change it.

Every seat, every client, one flat price. PeakKR is the agency workspace behind these templates β€” projects, timesheets, retainers, client reporting and SEO tooling for $100/month flat, with a 14-day free trial.

Start free See what's inside $100/mo