“The website sends bad leads” is a useful signal, but it is not yet a diagnosis. The same label can describe wrong audience, unclear offer, missing qualification, slow response, a CRM mapping error, or a service team that is rejecting a workable request. Collect evidence from the user’s decision, the website path, the record, and the mature business outcome before approving a redesign.
1. Define what “quality” means
Write the business decision the evidence must support: change audience, offer, page, form, routing, qualification, sales process, or service boundary. Define accepted lead, qualified lead, opportunity, won work, wrong fit, duplicate, spam, and unknown. Include the time window and sales-cycle maturity.
Do not collapse “high intent” into “closed revenue.” A person can have a clear need and still be outside geography, budget, timing, or capability. Keep fit, intent, readiness, and commercial outcome as separate fields.
2. Collect user-intent evidence
Interview or survey representative users about the question they were trying to answer, the promise they thought they were responding to, the information they expected after submitting, and what made them hesitate. Record role, situation, market, page, device, and date without inventing quotes.
Review search terms, referring context, page entry, internal search, scroll or interaction signals, and return visits as directional evidence. These signals describe behavior, not a person’s reason. Compare them with the actual form message and later sales record.
3. Build the page-to-record path
Create a sample ledger with URL, page version, query or source, device, CTA, form fields, consent state, timestamp, record ID, owner, response time, disposition, and mature outcome. Redact unnecessary personal data and limit access. Include phone, chat, booking, email, and partner routes, not only web forms.
For interaction definitions, GA4 event guidance can help document what was measured. An event means an interaction was recorded; it does not establish fit, acceptance, or revenue.
4. Inspect the page promise and qualification
Compare headline, audience, service boundary, proof, price condition, geography, response expectation, and CTA with what Sales actually accepts. Check whether a visitor can disqualify themselves before submitting. A generic “contact us” route often shifts qualification cost to Sales and makes the website look worse than the offer definition.
Test missing information, wrong location, unsupported service, urgent request, existing customer, procurement request, and partner inquiry. Capture which fields are necessary for a useful response and which merely create friction without improving routing.
5. Ask Sales for record-level evidence
Do not ask only whether leads are “good.” Ask Sales to label a controlled sample using the shared definitions: fit, problem, authority, timing, capability, source truth, first response, next action, and final disposition. Require a reason and evidence for “wrong fit” or “bad lead.”
Compare feedback by owner, market, page, campaign, day, and response delay. A high rejection rate concentrated in one queue may be a routing or capacity problem. A common objection across pages may be an offer or expectation problem. Preserve disagreements as unknown until the definition is resolved.
6. Reconcile CRM stages and business outcomes
Map form submit to contact, accepted lead, qualified lead, opportunity, proposal, won, lost, delivered, and paid. Record who changed each stage, when, and under what rule. Salesforce’s lead implementation guidance is a useful reminder to treat lead fields and process stages as governed data, not as an informal spreadsheet.
Check duplicates, reopened records, merged contacts, recycled opportunities, and deals that arrived through another channel. Report time-to-maturity so a recent cohort is not called low quality simply because it has not had time to progress.
7. Use Search Console and analytics without overclaiming
The Search Console Performance report can help segment queries, pages, devices, countries, clicks, impressions, CTR, and position within its reporting scope. Treat those as visibility observations. Join them to accepted quality only when the source key and date logic are trustworthy.
Separate assisted, direct, organic, paid, referral, and unknown paths. State attribution windows, consent limits, offline imports, and missing-source rates. A page with lower CTR may still serve a better-fit audience; a page with many clicks may be attracting the wrong problem.
8. Choose the smallest evidence-backed intervention
If the promise is unclear, repair copy and qualification. If the page attracts the right problem but routing fails, fix the handoff. If Sales definitions differ, repair the CRM contract before redesigning. If evidence shows a true audience or capability mismatch, change the offer or pause the page.
Run one bounded cohort with a preserved baseline. Change one variable, keep a control where safe, and review mature outcomes. Stop if the sample is too small, definitions are unstable, consent is unclear, or the service team cannot respond. Do not publish a conversion lift from an immature or hand-labelled sample.
9. Assemble the lead-quality gate
| Evidence layer | Required record | Hold if | | — | — | — | | user | question, role, expectation, hesitation | feedback is generic or invented | | page | version, promise, CTA, boundary, route | page job is unclear | | interaction | event, form/call/booking, consent, timestamp | event is called lead quality | | CRM | owner, stage, reason, response, duplicate state | labels are inconsistent | | sales | record-level fit and objection evidence | “bad lead” has no reason | | outcome | mature opportunity, delivery, payment or explicit loss | recent cohort is judged too early | | attribution | source key, window, unknown rate, limit | source is inferred from last click |
The evidence pack is ready when a neutral reviewer can follow a representative request from user intent to mature outcome and see where uncertainty remains. That is enough to choose a bounded website, routing, or offer intervention; it is not permission to claim that every form submission represents a valuable lead.
How did this article land?
Choose one reaction. You can change it anytime.
