SQL-to-closed-won conversion rate is the percentage of sales-qualified leads that become closed-won customers within a defined window. It can help backsolve the qualified demand SEO must contribute, but only after SQL, won, cohort and value definitions are stable.
The rate should not be applied blindly to traffic. Search journeys pass through landing, lead, MQL and SQL stages, each with its own conversion and delay.
Use this cohort contract before calculating or forecasting. It is original SEO Companies Hub analysis that prevents stage definitions, maturity and value from changing between numerator, denominator and plan.
| Contract field | Required decision | QA evidence | Forecast consequence if missing |
|---|---|---|---|
| Reporting unit | Person, account or opportunity | CRM object and deduplication rules | Duplicate people inflate the denominator |
| SQL entry | Acceptance criteria, timestamp and rule version | Sampled accepted records | Weak qualification makes win rate look artificially low |
| Closed-won event | Enforceable commercial milestone and exclusions | Stage history, order or finance record | Administrative closes distort the numerator |
| Cohort maturity | Maximum allowed sales-cycle age and cutoff | Distribution of time to close | Open deals are misclassified as losses |
| Value basis | Contract, recognized revenue, net revenue or gross profit | Finance-approved field | Revenue target is backsolved from incompatible value |
| Source continuity | Search cohort, landing session and governed CRM source | Joined IDs plus known loss points | Organic contribution is inferred from unjoined aggregates |
| Capacity | Sales coverage and opportunity load | Rep capacity and service-level evidence | The forecast assumes SQLs can be worked at unchanged quality |
Define the SQL denominator
An SQL should represent an eligible person or account that sales has accepted under documented criteria. Record:
- confirmed need or use case;
- customer and market fit;
- buying role or process;
- plausible value;
- timing;
- successful contact;
- required next step;
- duplicate-opportunity treatment;
- SQL entry timestamp;
- rule version and owner.
Decide whether the reporting unit is person, account or opportunity. For complex B2B sales, account or opportunity is usually more meaningful than raw lead records.
Do not include untouched MQLs or records marked SQL merely because a representative opened them.
Define closed won
Specify the event that qualifies:
- signed contract;
- accepted order;
- payment received;
- implementation booked;
- account activated;
- another enforceable commercial milestone.
Record whether renewals, expansions, reactivations and partner deals are included. Separate gross contract value, recognized revenue, net revenue and gross profit.
A deal can be closed won and later cancel or refund. Add a retained or net-value view where that risk is material.
Calculate from mature cohorts
For SQLs entering in a defined period:
SQL-to-closed-won rate = cohort SQLs closed won within the window ÷ eligible cohort SQLs × 100
Use an observation window based on historical sales-cycle distribution. Report:
- cohort size;
- percentage with resolved outcomes;
- open opportunities;
- median and percentile days to close;
- wins after the primary window;
- final restatement date.
Do not divide wins this month by SQLs this month when sales cycles span several months. That flow ratio mixes cohorts.
Distinguish win rate from conversion rate
Teams use “win rate” for different denominators:
- wins ÷ all SQLs;
- wins ÷ opportunities created;
- wins ÷ closed decisions only;
- won value ÷ closed value.
Name the formula. SQL-to-won includes SQLs that never become formal opportunities; opportunity win rate begins later. Closed-decision win rate excludes open and perhaps no-decision records.
Report multiple views when they answer different questions.
Audit stage and close data
Check:
- every SQL has an entry timestamp;
- stage changes are not backdated silently;
- duplicate opportunities are merged consistently;
- closed-lost and no-decision reasons are complete;
- reopened deals follow a stated rule;
- wins have contract or payment evidence;
- currency and value fields are valid;
- tests and internal accounts are excluded;
- owners and territories are current;
- definition changes are versioned.
Sample records manually. A clean dashboard can sit on inconsistent CRM behavior.
Segment the rate
Use meaningful cohorts:
- product or service;
- market and language;
- company size or segment;
- industry;
- new business versus expansion;
- contract-value band;
- sales motion;
- source and landing intent;
- sales team or territory;
- SQL qualification band;
- time to first response.
Keep counts visible and suppress small groups. Do not rank individual representatives from tiny, unequal books of business.
Preserve organic-search source carefully
Google's Search Console and Analytics guide separates search visibility and clicks from collected landing and site behavior. CRM records SQL and won stages, so preserve the chain rather than treating a search click as a CRM outcome.
Use the GA4 landing-page report for session-entry cohorts and key events for governed business-important interactions. Neither replaces CRM stage history or finance validation.
Use lawful fields for:
- first observable source;
- converting session source;
- landing page;
- campaign parameters;
- content or tool assists;
- self-reported source;
- product and market;
- attribution model.
The GA4 landing-page report can support landing cohorts. It cannot observe every offline, cross-device or prior interaction.
Backsolve from customer and revenue goals
Suppose the business needs C new customers. With a mature SQL-to-won rate r_sql:
Required SQLs = C ÷ r_sql
If MQL-to-SQL rate is r_mql:
Required MQLs = Required SQLs ÷ r_mql
If valid-lead-to-MQL rate is r_lead:
Required valid leads = Required MQLs ÷ r_lead
If eligible organic-landing-to-valid-lead rate is r_visit:
Required organic landing sessions = Required valid leads ÷ r_visit
Continue to clicks and impressions only with relevant cohort rates. Use decimals in calculations.
Use ranges and scenarios
Every input is uncertain. Build conservative, base and upside scenarios using historical cohort ranges.
Vary:
- sales win rate;
- lead-stage conversion;
- deal value and margin;
- sales-cycle time;
- organic conversion rate;
- addressable search demand;
- implementation timing;
- attribution share;
- churn or cancellation.
Do not hide the sensitivity. A small change in several funnel rates can produce a large difference in required traffic.
Test sales capacity
Backsolved SQL volume must fit operational capacity. Model:
- representatives and ramp status;
- active opportunities per representative;
- response service level;
- discovery and proposal capacity;
- implementation or fulfillment limits;
- market coverage;
- seasonality;
- current backlog.
If SEO generates more SQLs than sales can handle, slower response can lower conversion and invalidate the forecast.
Set throttling, routing or hiring decisions before scale.
Validate customer economics
Use net value:
- average or median won contract value;
- collected revenue;
- gross margin;
- implementation cost;
- refund, cancellation or bad-debt rate;
- retention and expansion;
- time to cash.
Backsolve from gross profit when margins differ by product or segment. A high win-rate low-margin cohort may be less attractive than a lower-rate enterprise cohort.
Keep forecast, pipeline and actual value separate.
Diagnose low SQL-to-won conversion
Possible causes include:
- SQL criteria too broad;
- slow follow-up;
- weak discovery;
- product or price mismatch;
- missing decision-maker access;
- content creates an inaccurate expectation;
- competitive disadvantage;
- long procurement or no-decision;
- territory or capacity constraint;
- stage hygiene problems.
Review loss reasons, recorded calls, time in stage and source cohorts. Do not assume SEO attracted bad leads until qualification and sales execution are examined.
Diagnose a high rate
High conversion may reflect strong fit. It can also indicate:
- SQL stage set very late;
- only near-certain deals included;
- lost or no-decision records missing;
- small sample;
- expansions mixed with new business;
- selective stage updates;
- discounts or low-margin deals;
- survival bias from excluding old open SQLs.
Validate volume, value and stage timing.
Turn the forecast into SEO cohorts
Allocate required acquisition across page and query roles:
- high-intent service and product pages;
- pricing and comparison pages;
- directories and tools;
- early content that assists later conversion;
- branded validation;
- market and location pages.
Estimate each cohort from its own conversion and demand evidence. Do not assign the sitewide organic rate to every page type.
Include implementation, indexing and maturation time. A forecast should show milestones before revenue.
Build a forecast QA checklist
- SQL and won definitions are documented.
- Cohorts are mature.
- Counts and windows are visible.
- Source fields pass through correctly.
- Funnel rates come from comparable cohorts.
- scenarios expose uncertainty.
- sales and fulfillment capacity are included.
- net value and margin are used.
- attribution limitations are stated.
- stop and review dates are defined.
An exact traffic target without these controls is false precision.
A practical standard
Calculate SQL-to-closed-won rate from versioned, mature cohorts and verified outcomes. Use it with the preceding funnel rates to backsolve a range of qualified organic demand, then test the result against addressable search volume, sales capacity and customer economics.
The rate helps plan SEO only when it represents the same customers and process the SEO program intends to acquire.
Related decisions
- Lead-to-MQL Conversion Rate: Definitions, Formula and QA Checks — the adjacent revenue operations decision.
- Sales Pipeline Velocity: Connecting SEO Leads to Revenue Timing — the adjacent revenue operations decision.
- MQL-to-SQL Conversion Rate: How Marketing and Sales Should Agree on It — the adjacent revenue operations decision.