Why a migration changes the calculator's inputs
On the default page the estimator answers a forward-looking question: what might a page earn if it reached a given position? A migration asks a defensive one: what could the site lose if pages that already rank drop for a while? The inputs describe pages that exist, with known volume and conversion rate, so the estimator is working from evidence rather than ambition for two of its three inputs.
The third input, position, is used differently. Instead of a single target, it takes two values per page: today's average positionMean ranking of a site's topmost result across the impressions it received. from Search Console, and a slipped position that represents the risk being planned for. The estimator does not know how likely the slip is; that judgement comes from the scale of the change. Moving to new templates, a new platform and a new domain at once carries more risk than a move that only changes hosting. The site migrations guide explains what drives that risk; the estimator translates it into clicks and conversions so that it can be weighed against the cost of mitigation.
The inputs for a site migration
| Calculator input | On the default page | For a site migration | Where to find it |
|---|---|---|---|
| Monthly search volume | Volume of a target keyword | Volume of the queries a key page or cluster ranks for today, excluding brand queries | Search Console queries for the page |
| Ranking position | One target position | Run twice: today's average position, then the position it could slip to during the migration | Search Console now; a stated risk assumption for the slip |
| Conversion rate | A general rate | The page's own conversion rate from organic visits | Analytics landing-page conversions |
For volume, take the non-brand queries each key page ranks for in Search Console and use their impressions as a guide to monthly volume. Exclude brand queries because they tend to survive a migration well; including them inflates the risk on the pages that carry the brand. For conversion rate, use the page's own figure from organic landing-page reports, since migration risk is concentrated on particular pages and a site average would blur the ranking.
Entering the migration inputs step by step
List the pages that carry organic value
Export Search Console's pages report sorted by clicks and join it with organic conversions by landing page. Keep the pages that together account for most of the value, plus any with unusually high conversions.
Run each page at today's position
For each page, enter its non-brand query volume, its current average position and its organic conversion rate. Record the estimated clicks and conversions as the before run.
State the slip and run it again
Decide how far positions could fall given the scope of the migration, and write that assumption down. Change only the position to the slipped value and record the outputs as the risk run.
Rank pages by conversions at risk
Subtract the risk run from the before run for each page and sort the list by conversions at risk. Use that order for redirect checks, pre-launch testing and post-launch monitoring.
A worked migration with illustrative inputs
An outdoor-furniture shop sizes the risk of replatforming
Terrace & Thorn, an invented outdoor-furniture shop, is moving to a new e-commerce platform with new URL patterns. Its main garden-furniture category ranks third on average for non-brand queries totalling 27,000 searches a month, and the page converts organic visitors at about 2%. At position three the estimator assumes an 11% click-through rate, giving about 2,970 clicks and 59 conversions a month. The team assumes, as its stated risk case, that the page could slip to sixth while the new URLs are processed. At that position the assumed rate is 5%, giving about 1,350 clicks and 27 conversions. The difference — about 1,620 clicks and 32 conversions a month — is the traffic at risk on that one page, which puts it at the top of the redirect and testing list.
SEO Traffic Estimator
Open the SEO Traffic Estimator →Prefilled with the example's inputs: Monthly search volume 27,000 · Ranking position 6 · Conversion rate 2% → Assumed CTR 5% · Estimated monthly clicks 1,350 · Estimated conversions 27.
The embedded estimator shows the risk run for the invented shop. Change the position to three to see the before run, and the gap between the two outputs is the figure the team plans around.
Interpreting traffic at risk before a migration
Read the difference between the two runs first, not either run on its own. Clicks and conversions at risk per month are the measure of what is at stake for each page, and multiplying by the number of months a slip might last gives a rough cost to compare with the effort of prevention.
Then rank pages by conversions at risk rather than by traffic. A product category with modest clicks but a high conversion rate can carry more commercial risk than a popular guide. That ranking sets the order of work: checking redirects map each high-risk URL to its true equivalent, confirming each new page's Canonical TagTells search engines the preferred URL. points to itself, testing templates on staging and preparing extra monitoring. The website migration checklist lists those tasks; the ranking tells you which pages deserve them first.
Next, keep the slip visible as an assumption. The risk run is a scenario, not a prediction, and the estimator's click-through curve is illustrative. State the slip beside every figure in the plan, for example as a note in the risk table, so no one mistakes the planning case for a forecast. For the most valuable pages, running a milder and a harsher slip shows how sensitive the estimate is.
Finally, set up monitoring against the before run. After launch, compare each key page's clicks and average position in Search Console with the before run and with the same weeks before the move. Comparing with the risk run can make a real drop look acceptable because it is smaller than the planning case. The guide to diagnosing a traffic drop after a migration explains what to check when a page falls short, from redirect chains to changes on the SERPThe page of results a search engine shows.. Track organic CVRShare of visits or clicks that convert. per page too, since template changes can lower conversion even when rankings hold.
Pitfalls when migration numbers go into the estimator
- Running the estimate only for the home page. The home page is mostly brand traffic and usually survives a move. The risk sits in category, product and guide pages that rank for non-brand queries.
- Assuming no slip because redirects are planned. Redirects reduce the risk but do not remove it; search engines still have to process the change. Plan for a slip and treat a smooth migration as a bonus.
- Mixing brand queries into the volume. Brand demand tends to follow the site wherever it moves. Including it overstates the pages that carry the brand name and understates the rest.
- Monitoring site-wide clicks instead of the key pages. Site totals can hide a sharp fall on one valuable page behind gains elsewhere. Track the ranked list page by page for several weeks after launch.
