Most teams start a migration and find out it was high-risk partway through. The redirect list is longer than expected. The platform doesn't support the URL structure they assumed it would. The domain change adds a variable nobody planned for. The risk was always there; nobody quantified it before kick-off.
The Migration Risk Quiz is three questions. It takes under a minute. The score it returns is based on the same three factors that determine migration risk in practice: what's changing, how many URLs are affected, and how much of the business depends on organic search.
This post explains what the quiz actually measures and how to use the result.
Why migration risk isn't one thing
A migration is any change to how a site is structured, accessed, or delivered. That covers everything from a hosting move with no URL changes to a simultaneous replatform, domain change, and redesign. The SEO exposure across those two scenarios is orders of magnitude apart.
The reason teams get this wrong is that they think of migration risk as a single dial. It isn't. It's three separate variables that interact:
- What's changing (and how many of those things are changing at once)
- How many URLs are involved
- What a traffic drop would actually cost the business
Misread any one of those and you either over-invest in a low-stakes move or, more commonly, under-invest in one where the stakes are high.
What the quiz measures
Factor 1: What's changing
The first question asks you to select every variable that's moving: domain, platform, URL structure, design and information architecture, or hosting only.
Risk compounds when several variables change at once. A platform switch on its own is medium-risk. Add a domain change and you've now given Google two things to relearn simultaneously. Add a URL restructure on top of that and the redirect mapping becomes a project in itself. Add a redesign and any Core Web Vitals gains you've made are now at risk from a heavier theme.
The quiz weights each combination, not each variable in isolation. That's the part most pre-migration checklists skip.
Factor 2: URL volume
The second question asks for the number of URLs affected, banded into four ranges: under 100, 100 to 1,000, 1,000 to 10,000, over 10,000.
Volume determines the scope of three specific work items: redirect mapping, pre-launch validation, and post-launch monitoring. At under 100 URLs you can map and validate manually in a spreadsheet. At 10,000 you need tooling, a structured workflow, and a way to catch the URLs that fall through.
The quiz also reflects something that's easy to underestimate: the chance of missing something doesn't scale linearly with URL count. At 200 URLs, a missed redirect is a problem. At 5,000 URLs, a systematic gap in your mapping can be invisible until Google surfaces it in Search Console weeks later.
Factor 3: Organic dependence
The third question asks what share of revenue or acquisition comes from organic search. The bands are under 20%, 20 to 50%, and over 50%.
Two migrations with identical technical profiles can have very different business risk. A site where organic drives 8% of revenue can absorb a three-week ranking disruption. A site where it drives 60% cannot. The quiz uses this factor to calibrate the recommendation: the same technical score at high organic dependence gets a different result than at low dependence, because the stakes are different.
How the score bands work
The quiz returns one of four bands.
Low. The variables in scope are few, the URL count is manageable, and organic dependence is not high. A solid checklist and a validated redirect map are sufficient. Expert involvement is optional.
Medium. One or two risk factors are elevated. The migration warrants a documented pre-launch checklist, a structured redirect mapping workflow, and post-launch monitoring in Search Console for at least 30 days.
High. Multiple variables are changing, URL volume is significant, or organic dependence is high enough that a traffic drop has real commercial consequences. This band is where gaps in planning cause the most damage because there's more to go wrong and more at stake when it does.
Highest. The combination of variables puts the migration in the pattern that loses rankings most reliably: multiple major changes happening simultaneously at scale with high organic dependence. This is not a situation to manage with a shared spreadsheet and good intentions.
A note on what the score doesn't cover
The quiz measures structural risk, not execution quality. A high-risk migration run by a team that has done it before, with the right tooling in place, is not the same as a high-risk migration being handled by a developer whose job is primarily frontend build work. The score is a starting point for planning, not a verdict.
It also doesn't account for factors that are hard to standardise: the quality of your current canonical setup, whether your internal links are already clean, whether your current platform has any non-standard redirect behaviour that will create chains on day one. Those show up in an audit, not a quiz.
What it does well is give a clear answer to a question that most teams don't ask until they're already committed to a timeline: is this migration straightforward or is it the kind that needs a plan before it has a go-live date?
Where to go after the quiz
Whichever band the quiz returns, the practical next steps are the same guides, all collected on the Migration hub:
- Website Migration SEO Checklist for the full pre/during/post workflow, platform-agnostic
- URL Redirects for Site Migrations for the redirect mapping and validation process specifically
- Traffic Drop After Migration if traffic has already fallen and you need the diagnostic and recovery playbook
If the quiz returns High or Highest, the migration risk review is worth booking before the build plan is finalised. The point of that conversation is to surface the failure points specific to your configuration before they become launch-day problems.