What each input and output means

Every number in the calculator is explicit: you choose the assumptions. Names below match the form fields; How this calculator works summarizes the same math in one place.

Inputs you enter

Monthly SEO spend

Total cost of the SEO motion for the month: tools, contractors or agency, content production, and any in-house time you allocate. This spend is the base for ROI: modeled revenue is compared to it.

Organic sessions / month

Count of organic sessions in your reporting window, usually from Google Analytics(GA4) or equivalent. The embed does not read GA4; only the value you type counts. If you want Direct or other channels in the “organic story,” merge them yourself before entering this field.

Total AI brand mentions / month

Your estimate of how many times your brand (or entity) is cited or surfaced in AI answers in total for the period, across ChatGPT-class assistants, Perplexity-style engines, Copilot, Gemini, and any other surfaces your data or vendors cover. This is not website traffic, and analytics will not tell you cleanly how many of those mentions produced visits (click now vs. later as Direct or brand). AI visibility tools such as Savannabay exist precisely to see whether and how your brand shows up in AI outputs; use them (and any other defensible sources) to build the count you enter here. Tools that only reflect prompts a user ran inside one product measure a narrow slice; reconcile or combine sources so the number matches the total visibility story you are defending.

Value per organic session ($)

Your average economic value for one organic visit: often “organic-attributed revenue (or pipeline) ÷ organic sessions” for a recent month, or “conversion rate × value per conversion” if you lack full attribution. It is a modeling input, not a GA4-built-in metric.

e.g. If a conversion (order, signup, or qualified lead) is worth $500 to you and you expect about one conversion every 200 organic visits, a simple expected value is $500 ÷ 200 = $2.50 per session (the same math as 0.5% conversion × $500).

Value per AI mention ($)

Your average economic value for one monitored mention. The AI line is separate from organic: you are not counting mentions as organic sessions, and someone can see your brand in an answer and only later visit as Direct or branded search.

A mention sits one step earlier in the funnel than a site session: the person must notice your brand in the answer, decide whether to engage, and click through or navigate later before they count as a visit on your site. That extra gap is a real filter, so the fair value per mention is usually smaller than value per organic session for the same underlying economics.

There is no universal GA4 line for this. A practical starting point is about five times smaller than value per organic session, then adjust. The advanced defaults use $0.35 per session and $0.07 per mention (that 5× spread). Go lower for a more conservative AI line or to fold in extra skepticism; raise it only when you have a reason. Teams also calibrate from experiments, branded lift, or rules of thumb.

Outputs after you click Calculate

Classic (organic-only) monthly attributed revenue

Organic sessions × value per organic session. Revenue (or value) implied by organic traffic alone, given the value-per-session you assumed.

AI attributed revenue (monthly)

Total AI brand mentions × value per AI mention, using the full mention count you entered (all monitored mentions in the period, not a subset labeled “dark” in analytics). Lower the mention count or value per mention if you want to approximate only incremental or hard-to-see impact. The separate organic-only story drops this entire line if you ignore AI mentions in the model.

Blended monthly attributed revenue

Classic organic revenue plus AI attributed revenue. Your org can later decide whether to merge, cap, or de-duplicate for official reporting. The calculator keeps the two lines visible side by side.

ROI classic

(Classic organic revenue − monthly SEO spend) ÷ monthly SEO spend, expressed as a percentage. Return on spend if only the organic attributed revenue counts.

ROI blended

(Blended revenue − monthly SEO spend) ÷ monthly SEO spend, as a percentage. Return on spend when the AI line is included in attributed revenue.

ROI lift from counting AI

Shown as a percentage in the same style as the two ROI rows: ROI blended minus ROI classic. If monthly SEO spend is held fixed, this equals AI attributed revenue ÷ monthly SEO spend (the AI line’s contribution to the ROI ratio relative to spend).

What is enterprise SEO ROI?

Return on investment (ROI) for enterprise SEO answers whether the business gets more value back than it spends on content, technical SEO, tools, and agency or in-house time. Teams often approximate “value” using organic traffic and a revenue proxy, for example attributed revenue per organic session, or conversion rate × customer value. That works well for reporting, but it usually reflects what shows up in analytics, not every place buyers learn about you.

Why organic-only ROI can mislead

Organic sessions remain the backbone of many SEO dashboards. At enterprise scale, the gap is this: buyers increasingly get recommendations from AI surfaces (ChatGPT, Perplexity, Microsoft Copilot, Gemini, and embedded assistants). Some of those journeys produce sessions you can see in GA4; many others influence revenue through direct visits and branded search without a clean “AI” channel label.

A classic ROI model can be internally consistent and still understate total impact if you only count what analytics attributes neatly to organic search, while ignoring AI-mediated discovery and “dark” attribution.

When influence does not show up as “AI” in Analytics

Many high-value interactions never produce a trackable click from the AI surface to your site. Typical pattern:

• The user reads your brand in an AI answer (recommendation, comparison, citation).
• Later they open a browser and type your URL, click a bookmark, or search your brand name.

GA4 will often record that follow-up visit as Direct (or branded organic), even though discovery started in the AI experience. That is a form of dark attribution: the channel that shaped demand is invisible in default reports.

For ROI storytelling, the consequence is blunt: if you attribute value only to sessions with a tidy “organic” or “paid” label, you systematically under-credit anything that lifts direct and branded demand after AI exposure. That is one reason enterprise teams pair analytics with total AI visibility metrics (how the brand shows up in answers across the ecosystem), alongside classic SEO metrics.

Site analytics rarely report how many AI mentions actually drove traffic to your site (whether users arrived via a direct click from an answer or only later, as Direct or branded search, with no reliable “this session came from that mention” link). Because that bridge is usually missing, you need AI visibility tooling to check if your brand is being mentioned by AI and in what context (recommended, compared, cited, or missing). Products such as Savannabay are built for that layer of insight; the total AI brand mentions field in this calculator is the kind of input you ground in monitoring like that, not from GA4 alone.

What are AI mentions?

Here, AI mentions mean your brand (or tracked entity) appearing in AI-generated answers out in the wild: the aggregate picture across assistants and answer engines buyers actually use, not a single in-app prompt list. Volume shifts with models, the prompts people ask, citations, and competitive narratives. Because site analytics rarely tie sessions back to which mentions drove traffic (immediate click or delayed visit), Savannabay and similar tools focus on monitoring mentions and context in AI answers. The total AI brand mentions you enter in the calculator should align with the total mention narrative you want in the model (often by combining vendors, samples, or estimates), not only “mentions from questions I generated inside one application.”

This calculator does not prove causality from a mention to revenue. It gives a transparent way to stress-test how sensitive your ROI narrative is when you add a separate AI-attributed revenue line, using assumptions you can explain in a deck.

How this calculator works

Definitions match the numbers we show above:

• Monthly SEO spend: total program cost for the month.
• Organic sessions × value per organic session → organic attributed revenue (classic line). Value per organic session is the average dollar value you assign to one organic visit for modeling; it is not a built-in GA4 metric. It compresses attribution into one number so you can stress-test ROI; your finance team may use a different definition.
• Total AI brand mentions × value per AI mention → AI attributed revenue. This is a separate modeled line from organic. A mention is one step earlier than a session: notice in the answer, then maybe click or visit later. Many teams start with value per AI mention around five times lower than value per organic session (same ratio as the default 0.35 / 0.07) and refine from there.
• Blended revenue: sum of organic and AI lines (two explicit lines so you can discuss overlap or double-counting in your own methodology).
• ROI: (revenue − cost) ÷ cost for the classic view (organic only) and for the blended view.

AI attributed revenue multiplies every mention you included in total AI brand mentions by your value per AI mention. Discussion of dark attribution elsewhere explains why teams add this line next to organic; it does not mean this row isolates only unseen or Direct traffic. ROI lift from counting AI is the difference between blended ROI and classic ROI.

Dark traffic: The tool does not read your GA4 “Direct” bucket or auto-detect dark sessions. Whatever you type as organic sessions stays on that line only. The total AI mentions line applies total AI brand mentions × value per AI mention to the full count you entered (not a dark-only subset), while the copy on dark attribution explains why that full mention line still matters beside organic reporting.

Why this matters for enterprise teams

Benchmarking: Compare “ROI story A” (organic only) vs “ROI story B” (organic + AI visibility) on the same spend.
Planning: If total AI mention volume is a strategic metric, set targets and show how ROI moves under a conservative value per mention.
Alignment: Shift the conversation from whether AI visibility “counts” to which assumptions the org accepts.

FAQ

Is this financial advice?

No. Illustrative model for discussion and planning only.

How should I pick “value per organic session”?

It is your modeling assumption for “how much one organic session is worth on average.” Strongest approach: revenue (or pipeline) attributed to organic for a recent month ÷ organic sessions in GA4 for the same period (e.g. $175k ÷ 500k sessions ≈ $0.35 per session).

If you do not have revenue attribution yet, approximate with organic conversion rate × value per conversion (order value, lead value, or discounted LTV), e.g. 2% × $80 ≈ $1.60 per session. Another quick mental model: if a conversion is worth $X and you believe you need about Y organic visits per conversion on average, expect roughly $X ÷ Y per session (same idea as rate × value). If you are early, use a deliberately low default and treat the output as directional only.

How should I pick “value per AI mention”?

It is the dollar value you assign to one monitored mention on average, a separate line from organic. A mention is one step earlier in the journey: the user sees your brand in an AI answer first, then may click or come to your site later, often as Direct or branded search, so mention → visit rarely maps cleanly in analytics.

A simple approach: start around five times lower than your value per organic session (the calculator’s advanced defaults use 0.35 vs 0.07, that 5× gap) and adjust from there. If you would have used a separate “attribution %,” fold that into a lower value per AI mention instead. Scenario-test until the story is defensible for finance.