
Checklist Website Migration
A website migration is won or lost in the hours and weeks after launch. This checklist covers the go/no-go decision, an hour-by-hour launch runbook, the first 24 hours, the first 30 days, a rollback plan and how to diagnose a traffic drop.
Maimoona
Content Writer
This checklist for website migration starts where most planning documents stop: the moment you press the button. It covers the go/no-go decision, the launch-day runbook, the first 24 hours, the first 30 days, a rollback plan and, if things go wrong, how to find the cause of a traffic drop. Use it as your website relaunch checklist on the day, alongside the planning work in our website migration checklist.
Need this done right?
Hoop builds the strategy, design and development behind sites like this one, talk to us about yours.
What This Checklist for Website Migration Covers
This checklist covers six moments: the go/no-go check before launch, launch day, the first 24 hours, the first 30 days, the rollback decision and recovery from a traffic drop. It assumes the planning is done: the URL inventory, the redirect map and the staging tests. If they are not, stop and do those first; no launch checklist can rescue a migration that was not prepared.
The Go/No-Go Check Before Launch
The go/no-go check is a short meeting, the day before or the morning of launch, where each owner confirms their area is ready. If any item is a “no”, the launch moves. A website relaunch checklist that allows “we will fix it after launch” for core items is not a checklist.
- Redirect map tested: loaded and checked against staging, with no chains or temporary redirects.
- Staging crawl clean: no broken links, correct canonicals, titles and content in place on the important pages.
- Tracking verified: analytics and conversion tags fire on every template, and test conversions are recorded.
- Forms, checkout and emails tested end to end; our migration website checklist lists what to test.
- Backups taken of the old site, its database and its server configuration.
- Rollback owner named: one person who can decide to roll back, and a tested way to do it.
- The team is available for the next 48 hours, including someone who can change server configuration.
- Benchmark saved: traffic, rankings and Search Console data from before the move.
Launch Day: The Website Launch Checklist, Hour by Hour
On the day, work through this website launch checklist in order. Timings are a guide; the order matters more than the clock.
Hour 0: Go live
- Put up the new site and switch DNS or routing as planned.
- Remove every staging block: password protection, noindex tags and disallow rules in robots.txt.
- Deploy the redirect rules.
Hour 1: Verify the essentials
- Test redirects in bulk with a crawler or script: every old URL should return one 301 to the right page.
- Check the top 50 URLs by traffic: status code, title, content, canonical and meta robots tag.
- Read robots.txt on the live site and open the XML sitemap.
- Submit the new sitemap in Google Search Console (and Bing Webmaster Tools).
- Submit every form and run a test purchase or booking, if you have them.
- Check analytics real-time reports for visits and test conversions.
Hours 2 to 8: Watch
- Watch server logs and monitoring for spikes in 404 and 5xx errors.
- Check page speed on the main templates on a phone.
- Confirm ad landing pages work, since paid campaigns keep sending traffic to them.
- Keep a shared log of every issue found, who owns it and when it was fixed.
Hours 8 to 24: Tell the people who depend on the site
- Brief customer service and sales on what changed, so they can help customers who cannot find a page or log in.
- Update links you control: email signatures, social profiles, your Google Business Profile, directory listings and email templates.
- Check paid campaigns: ads pointing at old URLs work through redirects, but update them to the new URLs so tracking parameters and landing page quality are not affected.
- If the site has accounts, send any planned password-reset or welcome emails, and watch for replies.
This is the same SEO launch checklist whether you call it go-live, relaunch or cut-over; what matters is that someone owns each line and ticks it with evidence.
End launch day with a short written status: what was checked, what passed, what is still open and who owns each open item. It keeps the next morning focused and gives stakeholders an honest picture from the start.
The First 24 Hours: Website Launch SEO Checklist
By the next day, search engines will have started crawling the new site. This website launch SEO checklist confirms they are seeing what you intended.
- URL Inspection in Search Console on a handful of important new URLs: can Google fetch them, is the page indexable, and which canonical does Google see?
- Old URLs inspected to confirm Google sees the redirect.
- robots.txt and meta robots checked again, in case a deployment restored a staging setting.
- Canonicals point to the live URLs on the right domain and protocol.
- 404 and 5xx logs reviewed: add redirects for any old URLs you missed, starting with those receiving visits.
- Analytics compared with the same weekday last week: similar traffic, similar conversions.
The First 30 Days: A Post Migration Checklist
For the first month, run this post migration checklist weekly (daily in the first week if the site is large or important to revenue):
| Check | Where | What good looks like |
|---|---|---|
| Indexing of new URLs | Search Console page indexing report | New URLs being indexed, old ones dropping out |
| Errors | Search Console, server logs, crawler | No rise in not found, server or redirect errors |
| Rankings vs benchmark | Rank tracker, Search Console queries | Stable or recovering, by page group |
| Organic traffic and conversions | Analytics | Close to the benchmark for the same period |
| Links to old URLs | Backlink tool | Top linking sites asked to update links |
| Internal links | Crawler | Pointing straight to new URLs, not through redirects |
| Speed | PageSpeed Insights, Core Web Vitals report | No worse than before |
Two things often get forgotten in this period. First, keep the old redirects and the old domain (if it changed) indefinitely; Google's guidance is to keep redirects in place for at least a year, and links and bookmarks keep using them for far longer. Second, do not start a second round of big changes, such as a new navigation, more URL changes or a content purge, until the site has settled. Stacking changes makes it impossible to tell which one caused a movement in traffic.
Report the results weekly to stakeholders in plain terms, so everyone knows whether a dip is expected or needs action.
A Website Migration Rollback Plan
A rollback plan answers three questions before launch: when do we roll back, who decides, and how exactly do we do it?
Roll back when a core function is broken and cannot be fixed within hours: checkout or lead forms failing, the whole site accidentally blocked from search engines and the setting cannot be changed quickly, redirects failing across the site, or serious errors on most pages. In these cases, every hour on the broken site costs more than switching back.
Fix forward for everything else: individual missing redirects, a broken template, slow pages, tracking gaps. Switching back and forth confuses search engines and users, so it should be rare.
How: keep the old site and its server configuration intact and ready to restore, know exactly which DNS or routing change reverses the launch, and test the rollback on staging if you can. Name one person who makes the call, so the decision is not debated in a group chat while customers wait.
Three launch problems and the right response
| What you find | Roll back or fix forward? | Why |
|---|---|---|
| Checkout fails for every customer and the fix is unclear | Roll back | Every hour costs orders; restore the old site while the cause is found |
| A few hundred old URLs return 404s | Fix forward | Add the missing redirects today; rolling back would confuse search engines more |
| The whole site carries a noindex tag from staging | Fix forward immediately; roll back only if the setting cannot be changed within hours | A quick fix limits the damage; a long-running noindex can remove pages from search |
Agree examples like these with the rollback owner before launch, so the decision on the day is quick and calm.
Traffic Drop After a Website Migration: How to Find the Cause
First, check whether the drop is real. Compare analytics with Search Console clicks. If Search Console clicks are steady but analytics sessions fell, the problem is probably tracking, not traffic. If both fell, work through these causes in order, because they are listed from most to least common:
- Redirects. Old URLs returning 404s, redirecting to the homepage, using 302s or chaining through several hops. Check the old URLs that had the most traffic first.
- Indexing blocks. A leftover noindex tag, a disallow rule, a canonical pointing to the wrong place, or pages that only render content with JavaScript Google cannot process.
- Lost content. Pages that ranked lost sections, headings or whole topics in the redesign. Compare old and new versions of the pages that dropped.
- Internal links. Navigation or in-content links changed, so important pages now receive fewer internal links than before.
- Speed and usability. New templates are heavier or harder to use on phones.
- Tracking error. Revisit this if the first five look clean.
What a normal dip looks like: Google's documentation on site moves with URL changes says fluctuations are expected while a site move is processed, and that a medium-sized site can take a few weeks for most pages to move. A dip spread evenly across the site that starts to recover within that period is usually normal. A drop concentrated in one section, or one that keeps deepening, usually has one of the causes above. For a full technical review, use our technical SEO audit checklist or our technical SEO audit service.
When to bring in a second opinion
If you have worked through every cause above and the drop continues, or if the drop is large and revenue depends on organic search, get an independent review quickly. A fresh crawl of old and new URLs, a comparison with the benchmark and a look at server logs often find what a team close to the project has stopped seeing. The cost of a few days' review is small next to weeks of lost traffic.
Copy This Launch Checklist
Copy this checklist website migration table into your project tool and fill in an owner and time for each row.
| Check | Owner | When | Pass / fail |
|---|---|---|---|
| Go/no-go: redirects, staging crawl, tracking, backups, rollback owner | Project lead | Before launch | |
| Staging blocks removed (password, noindex, robots.txt) | Developer | Hour 0 | |
| Redirects deployed and bulk-tested | Developer + SEO | Hour 0-1 | |
| Top 50 URLs checked | SEO | Hour 1 | |
| Sitemap submitted | SEO | Hour 1 | |
| Forms, checkout and emails tested live | Marketing / sales | Hour 1 | |
| Analytics and conversions recording | Analytics | Hour 1 | |
| 404 and 5xx monitoring | Developer | Hours 2-8 | |
| URL Inspection on key new and old URLs | SEO | Day 1 | |
| Weekly post-migration review | SEO | Weeks 1-4 |
Traffic fell after a migration? Get a free SEO audit. Our SEO migration team runs recovery audits that compare old and new URLs against your data and fix the causes in order of the traffic they cost.
“Most migration problems are visible in the first hour, if someone is looking.”
Key takeaways
- 01Do not launch until redirects, the staging crawl, tracking, backups and a rollback owner are all confirmed
- 02In the first hour: remove staging blocks, deploy redirects, test the top URLs, forms and checkout
- 03For 30 days, compare indexing, rankings, errors and conversions with your benchmark every week
- 04If traffic drops, check redirects, indexing blocks, lost content, internal links, speed and tracking, in that order
Written by
Maimoona
Content Writer
Frequently Asked
Questions
Everything you need to know before booking a strategy call. Can't find your answer? Contact us directly.
Ask hoop
Usually replies in minutes
How long does traffic take to recover after a migration?
It depends on the size of the site and how cleanly the migration ran. Google's documentation says a medium-sized site can take a few weeks for most pages to move in its index, and larger sites take longer. A migration with complete redirects and unchanged content often sees only a short dip; one with missing redirects or removed content can take much longer, and may not recover until the faults are fixed.
PEOPLE ALSO ASK
Swipe for 3 more questions →
Can't find your answer? Contact us directly.


