Free checklist · Maintenance and Checklists
Website migration checklist and SEO risk assessment
This free website migration checklist covers the checks that have broken real migrations: redirect mapping, DNS cutover, email routing, analytics continuity and indexing. Work through it as a migration questionnaire before launch, give each item an owner and share the link with whoever is doing the move. It doubles as an SEO migration risk assessment.
Website migration risk checklist
0 of 20 done
Before you touch anything
0/4The state you need captured before a single DNS record changes.
Redirect mapping
0/4The single most common cause of a migration losing traffic.
DNS and go-live
0/4The window where things actually break, if they break.
Tracking and communication continuity
0/4The things that quietly stop working if nobody checks.
After launch
0/4The first two weeks, where most missed redirects surface.
Your ticks are saved in this browser and in the page address, so a copied link brings the same state back on another device. Nothing about your site is sent to us or to anyone else.
Check done
Want someone to fix what this found?
Finding a problem and fixing it are different jobs, and the second one is ours. Send the result over and you get back what it would take to put right — scoped and priced, from the person who would do the work, within one business day.
What can go wrong in a website migration?
Migrations fail in a small number of well-known ways, and almost all of them are avoidable with a list. Redirects that were never mapped, DNS changed before the new site was verified, email routing broken because it lived on the same domain record, analytics that stopped and took the comparison data with it.
This is the launch-day list, split into what to do before, during and after the cutover. It is deliberately ordered: several items are only safe once an earlier one is done, and the ordering is what most improvised migration plans get wrong.
Why the order matters
Redirect mapping comes before anything is switched, because it needs the old site to still be crawlable. Mapping redirects from memory after the old site is gone is how sites lose rankings they had for years.
Email routing is checked before DNS is touched, not after. Mail records live in the same place as the records you are changing, and the failure is silent: nothing bounces, mail simply stops arriving, and it is usually a customer who tells you.
Analytics continuity comes before launch too. If tracking breaks at cutover, you lose the before-and-after comparison that would have told you whether the migration worked, and there is no way to reconstruct it later.
How to use it on the day
Assign owners before you start. Turn on the owner fields, put a name against every item, and share the link with whoever else is on the call. A migration checklist that lives in one person's browser cannot do the job it exists for.
Work top to bottom and do not skip ahead when something is blocked. The blocked item is usually blocked because a dependency is not ready, and proceeding past it is exactly the shortcut that causes the incident.
Export the completed list afterwards. It is the record of what was checked and by whom, and it is the document that answers the question everyone asks a week later when something turns out to be wrong.
After the cutover
Watch indexing for a fortnight rather than a day. Search engines re-crawl gradually, so a drop on day two is normal and a drop still there on day fourteen is a problem. Knowing the difference prevents both panic and complacency.
Keep the old site reachable for at least a month if you can, on a subdomain or offline copy. It is the cheapest insurance available, and it is only cheap before you have deleted it.
Website migration: questions people ask
What should a website migration questionnaire ask?
Five things before anything else: every URL the old site has indexed and where each one will redirect, who controls DNS and when it will change, where email is routed and whether the MX records move, how analytics and conversion tracking carry over, and who checks Search Console in the week after launch.
How long should redirects stay in place?
At least a year, and permanently if the cost of keeping them is near zero, which it usually is. Old links keep sending people for far longer than anyone expects.
Will we lose rankings?
A short dip is normal while everything is re-crawled. A lasting drop almost always traces back to a specific mistake on this list, most often unmapped redirects or a page that changed URL and content at the same time.
Should the design change at the same time?
Ideally not, and it usually does anyway. If both change together and traffic moves, you cannot tell which caused it. When both must change, at least keep URLs and page structure stable so the redirect layer is simple.
When is the safest time to cut over?
Early in a working day, early in the week, when the people who can fix things are awake and available. Friday evening is popular because it feels low-traffic and it is the worst possible choice.
Fixed-price packages
Rather have us do it? Website care plans
Monthly maintenance for WordPress and Shopify sites, run against the same checklist this site publishes for free. Pick the plan by how much the site earns and how quickly a fault has to be fixed.
Essential Care
from USD 150/month
Brochure sites and small stores that need someone to keep them patched and backed up.
Includes: WordPress core, theme and plugin updates (or Shopify app reviews); Daily backups, with a restore tested every month; Uptime monitoring with alerts; Security patching; Monthly report of what was done.
Delivery: Monthly, starts within a week
Growth CareMost chosen
from USD 300/month
Sites that bring in leads or sales every week and change often.
Includes: Everything in Essential Care; 3 developer hours a month for changes and fixes; Speed and Core Web Vitals tuning; A staging copy for testing updates before they go live; Plugin and app audit, broken-link and 404 fixes.
Delivery: Monthly, starts within a week
Priority Care
from USD 600/month
Stores and lead-generation sites where an hour offline costs real money.
Includes: Everything in Growth Care; 8 developer hours a month; 4-hour response time on faults; Quarterly SEO health check; Migration support when you change host or platform.
Delivery: Monthly, starts within a week
Hosting, premium plugin or app licences and new features are not included. They are billed at cost or quoted separately, and we say so before any work starts. Prices are in USD and are starting prices for the scope listed; larger sites get a written quote first. Compare every package.
Where to go from here
- SEO Audit Checklist: run this on the new site once it is live, and on the old one before you plan redirects.
- Downtime Cost Calculator: what a botched cutover costs per hour, which is the case for doing it carefully.
- Hosting and Maintenance Plan Builder: who is watching after launch, and how fast they have to answer.
Guides behind this tool
Built by GoDesign FZE, who migrate and relaunch business websites.
Get in touch
Want someone to just do this part?
The tool is free and stays free. If you would rather hand the work over, tell us what you are dealing with and you get a straight answer on scope, cost and timeline.
- You own everythingRepository, hosting and domain credentials sit in your name from day one, not handed over at the end.
- A written timelineMilestone dates are agreed in writing before work starts, so you always know what ships next.
- One business dayEvery enquiry gets a reply from the person who would scope the work, not a sales sequence.
Media City, Dubai, UAE · DHA Phase 2, Islamabad, Pakistan
Would rather type than fill in a form?
Message on WhatsApp