Free tool
SEO Traffic Loss Calculator
How much traffic did you lose, what is it worth, and which pages should you look at first? Compare two periods with the lengths normalised, then load a page level export to get the shortlist.
No signup. Your CSV is read in your browser and never uploaded.
1. What are you comparing?
This decides which money models are available below. Clicks and sessions are counted by different systems and are not interchangeable.
Periods are normalised before comparison
A 28 day window against a 31 day window is not a 10 percent drop. Everything below is measured against what the current period should have produced at the baseline rate.
Baseline period
Set a valid start and end date
Current period
Set a valid start and end date
The same period last year is the only comparison that controls for seasonality. It shifts back 364 days rather than a calendar year so the days of the week still line up.
2. The two totals
Total clicks across the whole baseline period.
Total clicks across the whole current period.
3. What is the traffic worth? (optional)
Three ways a traffic loss number goes wrong before you read it
Subtracting two totals is the easy part. Almost every mistake happens in the setup, and all three of these produce a confident number that is simply not true.
Unequal periods
February against January is three fewer days. At a flat 100 visits a day that reads as a 10 percent decline. Everything here is measured against what the current period should have produced at the baseline daily rate.
Gains quietly erased
Sum the absolute movement of every page and you get an alarming figure that includes the pages that grew. Movement here stays signed, losses and gains are counted separately, and both appear in the output.
Dividing by zero
A page with no baseline traffic has no rate to compare against. That is not an infinite percentage change, it is an undefined one, and it gets reported as not calculable and excluded from the loss total.
Clicks are not sessions, and this tool will not pretend otherwise
The most common way a traffic loss calculator produces a wrong revenue figure is by taking a Search Console click total and multiplying it by an analytics session conversion rate. Google documents the two products as measuring different things: clicks are counted on the search result, sessions are counted on your site, and the filtering, attribution and identity rules differ on both sides. The gap between them is real, it varies by site, and it is not a rounding error.
So the metric you pick at the top of the tool decides which money models you can reach. Choose Search Console clicks and the conversion rate models are locked. You can still report lost clicks, supply your own value per click, or price the loss as advertising replacement value. To unlock the session models you have to divide your organic sessions by your clicks over the same dates and enter that ratio, at which point the output says it used your measured mapping.
| Your metric | Money models available | Locked, and why |
|---|---|---|
| Search Console clicks | Value per click that you supply, or CPC as replacement value. | Conversion rate models, until you supply a measured sessions per click ratio. |
| Organic sessions | Ecommerce, lead generation, value per visit, CPC. | Page RPM, which is priced per pageview rather than per session. |
| Pageviews | Publisher RPM, value per view, CPC. | Session conversion models, because one session can be several pageviews. |
Every money figure here is a scenario
Take the worked example: 12,000 organic sessions in the baseline period and 8,000 in a current period of the same length is a loss of 4,000 sessions. At a 2 percent conversion rate and 100 dollars per order that is an 8,000 dollar scenario. What it does not show is that the lost traffic would have converted at the same rate as the traffic that stayed, that indexing caused any of it, or that fixing something recovers the 8,000 dollars. The only measured revenue figure is the one your payment system reports for the same dates.
From one number to a list of pages worth opening
A sitewide total tells you there is a problem. It does not tell you where to look, and the honest answer to that is almost never the pages with the biggest percentage drops. Load a page level export and the tool ranks every URL by absolute loss, gives each one as a share of the total, and reports how many URLs account for 80 percent of the damage. A loss concentrated in nine pages is a different investigation from the same loss spread across nine hundred.
What to export
In Search Console, open Performance, set the date filter to Compare, open the Pages tab and export. That single file already contains both periods. From analytics, export landing pages with sessions for each period separately and load the two files. The tool detects the delimiter, skips the comment lines analytics tools put above the header, guesses the columns, and lets you correct any of it. If one export uses full URLs and the other uses paths, it falls back to matching on path and tells you it did, because that fallback can merge two hostnames into one row.
What each evidence status means
None of these is a cause. They describe what the two numbers support saying about a URL, which is what decides the order you check things in.
| Status | What the data shows | Suggested next step |
|---|---|---|
| Traffic gone | Traffic in the baseline period, a measured zero in the current one. | Confirm index status and the response code before anything else. |
| Missing from current export | No row at all in the current file, which is not the same as a measured zero. | Unconfirmed. Check the URL directly before counting it as lost. |
| Declined | Fell by more than the difference in period length explains. | Compare the query set and average position across the two periods. |
| Minor decline | A small absolute change on low volume, where percentages mislead. | Look at the group total rather than the individual rows. |
| Gained | Grew against the normalised baseline. | No action. Kept visible so the sitewide total stays honest. |
| No baseline | Published after the baseline period, so there is nothing to compare. | Excluded from the loss total rather than counted as a gain. |
A calculator cannot tell you why traffic fell
Google groups the causes of a search traffic decline into technical problems, manual actions and security issues, movement in rankings, changes in what people are searching for, and seasonality. Every one of those produces the same shape in a two period comparison. Anything that reads two totals and announces a cause is guessing, and a confident guess is worse than no answer because it sends you to the wrong week of work.
What a comparison can honestly do is order the investigation. Index status goes first, not because it is the most likely cause but because it is the cheapest to eliminate and it rules out an entire branch: a page that is not in the index cannot rank, so if the pages are still indexed you are looking at a ranking or demand question and none of the technical fixes apply.
Start with the cheap checks
Take the biggest losses and check whether they are still in Google, then confirm nothing is blocking them with the indexability checker. Both take minutes and settle the technical branch.
Then narrow the cause
If pages really have left the index, the deindex cause diagnostic ranks the likely reasons against what actually happened on your site, with the Search Console step that confirms each one.
The expensive part of a traffic drop is the time before you notice
Every calculation on this page is retrospective. You are pricing a loss that already happened, and the size of it is mostly a function of how long it ran before anyone looked. SearchOptimo re-checks your URLs on a schedule, keeps an index history timeline per URL so you can see the exact date a page left, and alerts you when one drops out. A known date turns this whole investigation into a question about what you shipped that day.
Frequently asked questions
- How do you calculate lost organic traffic?
- Rescale the baseline to the length of the period you are measuring, then subtract. Expected current traffic is baseline traffic divided by baseline days, multiplied by current days. The signed change is actual current traffic minus that expected figure, and the loss is that change when it is negative. Subtracting two raw totals is only correct when both periods are exactly the same number of days, which is rarely true once you compare a month against a month or a quarter against the one before it. A 31 day period against a 28 day period looks like a 10 percent drop even when nothing changed at all.
- How much revenue did my traffic drop cost?
- Multiply the lost sessions by your organic session conversion rate and by revenue per conversion. Four thousand lost sessions at a 2 percent conversion rate and 100 dollars per order gives an 8,000 dollar scenario. Treat that as a scenario rather than a measurement: it assumes the traffic you lost would have converted at the same rate as the traffic that stayed, which is usually optimistic, because the queries that disappear first tend to be the informational ones. If you need the real figure, read it out of the systems that recorded the money over the same dates.
- Can I use Search Console clicks with my Google Analytics conversion rate?
- Not without measuring the relationship first. Search Console counts clicks on a search result. Analytics counts sessions that began on your site. They apply different filtering, different attribution and different identity rules, so the two totals never match and the gap is not a constant across sites. This calculator blocks that combination by default. If you want to use it, divide your organic sessions by your Search Console clicks over the same dates, enter that ratio, and the tool will convert clicks to sessions using your own measured number and say so in the output.
- What is the difference between a traffic drop and a seasonal dip?
- A seasonal dip repeats. The way to tell them apart is to compare against the same calendar window a year earlier rather than against the period immediately before, which is why this calculator has a same period last year button. If the current period is down against the preceding period but flat against the same period last year, you are looking at a season, not a problem. Shifting back 364 days rather than a calendar year keeps the days of the week aligned, which matters because search traffic is strongly weekly.
- Which pages should I investigate first after a traffic drop?
- The ones carrying the most absolute loss, not the largest percentage drops. A page falling from 8 clicks to 2 is a 75 percent drop and 6 clicks. A page falling from 4,000 to 3,000 is a 25 percent drop and a thousand clicks. Load a page level export into the CSV mode here and it ranks every URL by absolute loss, shows each one as a share of the total, and tells you how many URLs account for 80 percent of it. That last number is the useful one, because a handful of pages points at something specific and a long flat tail points at something sitewide.
- Why does a page show as missing rather than zero?
- Because those are different facts and collapsing them invents a loss. Search Console omits rows below its reporting threshold, so a URL absent from the current export might have dropped to zero, or it might have dropped to two clicks and fallen out of the report. This calculator counts a measured zero as traffic gone and flags an absent row separately as unconfirmed, so you check it directly before you count it as lost. Most calculators treat the two identically and overstate the loss.
- Does a traffic drop mean my pages were deindexed?
- Not on this evidence. Google lists technical problems, security or manual actions, ranking movement, changes in what people search for, and seasonality as separate causes of a decline, and two traffic totals cannot distinguish between them. Deindexing is worth eliminating first only because it is the cheapest to check: a page that is no longer in the index cannot rank, so confirming index status takes minutes and rules out an entire branch. If the pages are still indexed, the drop is a ranking or demand question and none of the indexing fixes apply.
- Should I use CPC to value lost organic traffic?
- Only as a replacement cost, and label it that way. Multiplying lost clicks by cost per click tells you what buying the same volume of traffic would cost, which is a legitimate budgeting figure. It is not revenue, and it is not what the traffic earned. Paid clicks on the same terms do not convert at the same rate as organic clicks, and the terms with the highest CPC are rarely the ones you lost. This tool reports that model under the label advertising replacement value and never calls it revenue.
You just priced the last drop. Catch the next one on day one.
A calculator measures what already happened. Monitoring tells you the day a page falls out, while you still remember what you shipped, and while the number on this page is still small. Free plan, no credit card, cancel anytime.