The basic arithmetic is (revenue reasonably attributed to organic search - SEO cost) divided by SEO cost, multiplied by 100. A previously published example for this page used a $3,000 monthly investment sustained for 12 months and $60,000 in attributed revenue, producing an illustrative ROI of about 67%. That example is arithmetic, not a forecast for another business.
The formula is simple; the inputs are where most disagreement begins. Before presenting a result, document three assumptions and one control:
- Attribution assumption. State which interactions receive credit for the sale or lead and whether organic search was the first interaction, an assisting interaction, or the final recorded interaction. A last-touch model can understate earlier discovery, while a broad multi-touch model can over-credit channels if its rules are not understood.
- Conversion-quality assumption. Confirm that the event being counted is a real business outcome or a clearly defined proxy. A previously published example on this page referenced a 1% organic conversion rate; treat that as illustration only. A recorded form submission is not automatically a qualified lead, and a checkout event is not useful if duplicate tagging inflates the total.
- Customer-value assumption. Decide whether the model uses immediate transaction value, expected gross revenue, contribution margin, or lifetime value. Use the value that finance can explain and defend rather than the largest possible figure.
- Measurement control. Validate important organic conversions in GA4 or the relevant analytics and CRM systems with test journeys before building the ROI model. Your measured rate should come from your own correctly configured data.
Include all relevant SEO costs: agency or internal labor, content production, technical implementation, specialist tools, and material third-party expenses that exist because of the program. If cost categories are omitted, the ROI appears stronger than the underlying economics.
A useful model therefore has two outputs: the calculated return and an assumptions note. The assumptions note should explain attribution, conversion definitions, customer value, included costs, and any known data gaps. That makes the result auditable and prevents a precise-looking percentage from hiding weak measurement.