Blog · Board and management reporting
SEO conversion rates connect organic landing sessions to defined leads and orders. This guide shows which rows to export, how to calculate page-level and total rates, and how to check that business outcomes match the underlying records.
SEO conversion rates show the share of organic-search sessions that produce a defined business outcome. Divide organic sessions with an accepted lead submission or order by eligible organic sessions, then compare landing pages using consistent dates and outcome rules. More traffic does not necessarily mean more qualified demand, and more recorded actions do not necessarily mean more converting sessions.
Start with a question the business can act on: which organic landing pages produce accepted leads, which produce orders, and which attract visits that rarely reach either outcome? Keep those measures separate before creating a combined rate.
For this report, organic search means visits classified as organic-search traffic in the supplied analytics export. Google's channel definitions describe Organic Search as arrival through non-ad links in organic-search results. Use the session's channel classification, not an unrelated first-user source field.
A landing page is the page where the session began. Google's reporting definitions define landing page using the first pageview in a session and session key event rate using sessions with a key event. That distinction matters: a page seen halfway through a visit is not automatically the landing page credited in this report.
Your business outcome can be narrower than every configured key event. A file may count a newsletter signup as a key event, while sales only accepts requests meeting its lead criteria. Document which recorded action becomes a qualifying lead outcome and which order statuses count. The stage conversion glossary explains the general denominator rule; here the denominator is organic sessions.
Organic lead conversion rate = Organic sessions with a qualifying lead submission / Organic sessions
Organic order conversion rate = Organic sessions with an eligible order / Organic sessions
Combined organic conversion rate = Organic sessions with either outcome / Organic sessions
Multiply by 100 when displaying the ratios as percentages. An accepted lead count divided by unique visitors is a different measure and needs its own label.
Prepare one session-summary row per organic session, with a session identifier, session start, landing page, and outcome flags. Use lead and order exports to validate the linked business records. A lead export needs the originating session identifier, submission date, lead identifier, and acceptance status. An order export needs the originating session identifier, order identifier, order date, and eligible status.
If those identifiers are absent, say the exports cannot establish the match. Matching page totals by approximate date does not prove that the leads came from the organic sessions in the denominator. Exclude identifiable internal or test traffic consistently, and retain the excluded-row counts for review.
For the example below, each eligible session can have a same-session lead submission, a same-session order, or neither. Lead acceptance is checked through a common follow-up cutoff. Leads accepted after that cutoff remain outside this particular numerator until the cohort is refreshed. This is an explicitly defined business-outcome rate, not a claim that every analytics platform will display the same default metric.
A US commercial-equipment company reviews organic sessions beginning September 1 through September 30, 2026. It checks acceptance of submitted leads through October 15, 2026, and compares the same completed cohort across pages.
In this illustration, no session has both outcomes, and each outcome session links to exactly one accepted lead or eligible order. Those are verified properties of this example, not assumptions to apply to every export.
| Landing page | Organic sessions | Sessions with accepted lead | Sessions with order | Sessions with either |
|---|---|---|---|---|
| Category page | 4,000 | 100 | 20 | 120 |
| Buying guide | 6,000 | 54 | 6 | 60 |
| Product page | 2,000 | 70 | 30 | 100 |
| Total | 12,000 | 224 | 56 | 280 |
With that table in A1:E5, the lead rate, order rate, and combined rate for row 2 are:
=IF(B2=0,"",C2/B2)
=IF(B2=0,"",D2/B2)
=IF(B2=0,"",E2/B2)
Fill down and format the cells as percentages. Keep the exact ratios for calculations; the table below rounds to two decimal places.
| Landing page | Lead rate | Order rate | Combined rate |
|---|---|---|---|
| Category page | 2.50% | 0.50% | 3.00% |
| Buying guide | 0.90% | 0.10% | 1.00% |
| Product page | 3.50% | 1.50% | 5.00% |
| Total | 1.87% | 0.47% | 2.33% |
The total combined rate is 280 / 12,000 = 2.33%. The simple average of the page rates is (3% + 1% + 5%) / 3 = 3.00%, which gives the smallest page the same weight as the largest. Calculate the total from counts instead:
=SUM(E2:E4)/SUM(B2:B4)
First tie the 12,000 session rows to the analytics export with the identical date range and session channel filter. Every session must appear under exactly one landing page. Document whether query strings are preserved or grouped, so a page is not split differently next month.
Next tie the 224 qualifying lead sessions to their accepted lead records and the 56 order sessions to eligible order IDs. In this example, the two groups do not overlap, so 224 + 56 = 280 converting sessions. The remaining sessions are 12,000 - 280 = 11,720; 280 + 11,720 must return the full denominator.
When a real session can contain both outcomes, make the combined flag on each session row. With lead and order flags in F2 and G2, use:
=IF(OR(F2=1,G2=1),1,0)
Sum that flag by landing page. Adding the separate lead and order session counts would double-count the overlap. The total should also reconcile as lead sessions plus order sessions minus sessions with both.
The product page has the strongest direct conversion in this cohort. The guide has the largest session volume and the weakest same-session conversion. Those facts support a review of visitor intent, the next-step offer, and tracking coverage; they do not prove that removing the guide would improve sales.
Educational visits can precede later commercial visits. If the business wants later outcomes, create a separate matched cohort with an explicit follow-up window and attribution rule. Do not attach all later CRM wins to these sessions without a defensible match. Win rate versus conversion rate explains why later opportunity measures use different denominators.
For another acquisition route, webinar sales conversion rates follow event registrants through a fixed later outcome window. Once organic leads become opportunities, pipeline coverage answers a separate question about the value of the sales pipeline.
Covirage is not affiliated with Google.
Bring a sample of your own organic landing-page session summary and matched lead or order exports. Covirage maps the columns; its tools compute and check the counts and conversion rates, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, then set up your business and bring your file.
See Covirage for sales insights for the supporting workflow.
A useful comparison uses your own pages with similar intent, audiences, and outcome definitions. An educational page and a product page do different jobs. Compare a page with its prior mature cohorts before using an outside average whose session and conversion rules may differ.
You can calculate a leads-per-click measure if the exports support that comparison, but it is not a session conversion rate. Search clicks, website sessions, and identified people count different things. Label the denominator explicitly and avoid switching it between pages or reporting periods.
Count each action for an action-volume report, but count the session once for a session conversion rate. Keep separate flags for lead and order outcomes. For a combined rate, a session with both outcomes still contributes only once to the numerator.