How do I calculate the revenue at risk from an unresolved SEO problem?
Short answer
Multiply affected sessions per week by conversion rate, close rate, average deal value, and weeks until the fix ships, then apply a decay probability between 0.5 and 0.95 depending on whether the loss is likely to reverse on its own. Present the result as a range, because a number like "$52,435" invites scrutiny you can't defend while "$40,000 to $65,000 depending on decay assumption" survives the meeting.
Why this reframe gets tickets prioritised
Engineering teams don't treat "SEO issues" as urgent because they read as maintenance. They treat revenue-at-risk numbers as urgent because those read as opportunity cost with a deadline attached.
The reframe also forces honesty in your own backlog. Some issues have almost no revenue impact and don't deserve engineering attention. Others are quietly compounding. Running the formula tells you which is which before you spend political capital asking for the fix.
The formula
Revenue at risk = Sessions lost per week
× Conversion rate to lead
× Close rate lead → customer
× Average deal value
× Weeks until resolved
× Decay probability
Pull sessions from GA4, conversion rate from your form tool, close rate and ACV from your CRM. Never use remembered numbers, because the first challenged input discredits the whole estimate.
Three worked examples
A high-value page drops from position 3 to 8
CTR falls from roughly 10% to 2%, an 80% sessions loss on that keyword cluster.
- Current sessions: 400/week → 320/week at risk
- Conversion to lead: 2% | Close rate: 18% | ACV: $10,000
- Weeks until fix: 4 | Decay probability: 0.9
320 × 0.02 × 0.18 × $10,000 × 4 × 0.9 = $41,472
That converts "we should fix this" into "this fix returns $41,000 in 30 days."
A canonicalisation bug hits a template
Template bugs scale across hundreds of URLs at once, which is why they usually top the list.
- 1,200 affected product pages × 22 sessions/week = 26,400 sessions/week
- Conversion: 0.8% | Close rate: 15% | ACV: $3,000
- Weeks until fix: 3 | Decay probability: 0.85
26,400 × 0.008 × 0.15 × $3,000 × 3 × 0.85 = $242,352
AI citation share drops in ChatGPT
Newer category, and your CFO won't have a mental model for it. Substitute citations for sessions and assisted revenue for direct.
Our own state of AI search research found that once a brand is mentioned in an AI answer for a prompt, next-observation mention probability is 83.2% on ChatGPT. Miss once, and it drops to 9.9%. Because that makes presence lumpy, researchers argue visibility should be measured as a distribution across runs, prompts, and time rather than as one snapshot, so size this loss from a four-week average rather than a single week's reading. Loss compounds fast here, which is why the decay probability sits higher than for a ranking dip.
- 15 tracked commercial prompts, 5 lost the citation this week
- Estimated influenced pipeline per prompt-month: $8,000
- Weeks until fix: 6 | Decay probability: 0.7
5 × $8,000 × (6/4) × 0.7 = $42,000
See How do I track prompts and competitors across many clients without tool costs exploding? for the tracking setup.
Choosing the decay probability honestly
This multiplier is what separates a credible estimate from an inflated one, and it's the input most reports skip entirely.
| Situation | Decay probability |
|---|---|
| Transient issue likely to self-correct (algorithm noise, brief indexation glitch) | 0.5 to 0.7 |
| Structural issue that persists until fixed (template bug, CWV regression) | 0.8 to 0.9 |
| AI-search citation loss, where mention consistency is path-dependent | 0.85 to 0.95 |
Skip the multiplier and your "$1M at risk" becomes $200,000 of actual impact, and nobody takes your next risk number seriously. Applying it honestly is what buys you credibility for the issue that really is a $1M problem.
Run it on your top three issues
1. List the three unresolved issues by suspected traffic impact. Not by team preference. The issues that feel important often aren't the ones losing money.
2. Pull affected sessions. GA4 plus GSC. For indexation problems, use the GSC Pages report to count affected URLs precisely.
3. Apply bucket-specific conversion and close rates. Blended rates produce misleading risk on both ends.
4. Get an engineering estimate and add 30%. Estimates slip, and the buffer keeps your number honest rather than optimistic.
5. Apply the decay probability and present a range.
Catch these automatically instead
Quarterly audits find problems after the revenue is gone. The alternative is a daily monitor that only speaks when something crosses a threshold.
Three recipes cover the detection surface. declining-pages catches traffic loss, visibility-losers catches AI-visibility loss, and citation-decay-alert catches the specific case of a page dropping out of citation sets, which most SEO monitoring misses entirely because it isn't visible in Search Console.
The daily agent:
Start (schedule, daily 6am) → GSC Page Performance Summary (day-over-day, all top pages) → GSC Indexing Status → declining-pages recipe → citation-decay-alert recipe → visibility-losers recipe → HubSpot Get CRM Objects (conversion and close rates per intent bucket) → Code (apply the revenue-at-risk formula per detected issue, using bucket-specific rates and a decay probability set by issue type) → Conditional (stay silent unless an issue exceeds $10,000 in weekly risk) → Prompt LLM (state the dollar range and the single next action) → Send Notification to the SEO channel.
Two design choices carry it. The Conditional threshold keeps the alerts credible, because a monitor that fires daily gets muted within a fortnight. And setting the decay probability by issue type inside the Code node means a transient ranking dip and a template-level indexation bug get scored differently without anyone having to remember to adjust it.
FAQ
Related answers
- How do I prove SEO is generating revenue and not just traffic?
- How do I keep track of which site changes caused which traffic changes?
Want to catch revenue-at-risk before it shows up in the quarterly review? Start a free Analyze AI trial and get daily alerts on citation decay and page-level visibility drops.