A number-one ranking is not automatically an asset. If the page attracts people the business cannot serve, qualifies the offer badly or creates the wrong expectation, defending the position can protect the very problem marketing needs to fix. The ranking may be real. The commercial value may not be.
A position never earns a veto over inspection. It is evidence of visibility under stated conditions, not proof that the page is winning the customer decision the business needs.
That is the rule I apply before anybody is allowed to defend a graph.
TL;DR
- Keep search visibility and enquiry fit as two separate records; do not force a causal bridge the data cannot support.
- The form reveals the mismatch. It does not tell you which earlier signal caused it.
- Turn sales frustration into an Enquiry-Fit Ledger, and keep unknowns in the denominator.
- Resolve the ranking into one of five decisions: keep, qualify, reroute, rebuild or relinquish.
Separate visibility from commercial fit
Search Console can show that a page appeared in Google Search, received clicks and held an average position within a defined view. Google recommends treating position as a trend and explains that the metric varies across impressions rather than representing one permanent rank (Google: Search Console metric definitions). None of that identifies a suitable customer. Keep two records separate:
| Evidence lane | Record | Does not prove alone |
|---|---|---|
| Search visibility | Query, page, country, device, period, impressions, clicks and average position | That visitors fit the offer or became valuable opportunities |
| Enquiry fit | Requested service, customer type, territory, budget/timing where appropriate, disposition and reason | Which exact query or ranking caused the enquiry |
Do not force a causal bridge unless the records genuinely connect. A set of unsuitable enquiries during the same period does not prove one ranking caused them. It does justify inspecting the page rather than granting it immunity. I call this the Position-without-Fit Gap: the page has earned attention but has not yet earned a commercial defence.
The wrong enquiry begins before the form
A visitor forms an expectation from a chain of signals: query wording; search-result title and description; page title; opening proposition; imagery and examples; scope and exclusions; price or project-scale cues; and the call to action. The form is merely where the mismatch becomes visible.
Take a bounded sample of unsuitable enquiries and classify the problem:
| Mismatch | What to inspect |
|---|---|
| Wrong service | Query theme, page subject and service boundaries |
| Wrong location | Search-result wording, location statements and service-area clarity |
| Wrong customer type | Opening proposition, examples, imagery and eligibility |
| Wrong budget or scale | Price basis, minimum engagement and project cues |
| Wrong urgency | Availability, lead times and emergency language |
| Researcher rather than buyer | Search intent, information depth and CTA |
| Existing customer/support | Contact-route purpose and form labels |
The point is not to blame every poor lead on copy. It is to find where the public promise and the deliverable offer may have stopped matching. My distinction is mismatch location versus mismatch cause. The form reveals the mismatch. It does not automatically identify which earlier signal caused it.
A top ranking can conceal an over-broad promise
Ranking reports reward presence. Buyers respond to promises. A page may rank for a broad phrase because its title and copy stretch across several interpretations. That reach looks impressive while the sales team spends its week explaining what the company does not provide.
Read the search-result title, description and opening as a prospective customer. Do they identify the actual service or product, the intended buyer, the relevant geography, the minimum project scale or price basis where material, the decisive exclusion and the next suitable action? Or does the page maximise the chance of a click by postponing the disqualifying detail until halfway down?
Useful qualification is not conversion sabotage. It prevents the wrong person entering a journey designed for somebody else. I use a Promise-to-Offer Test: write the promise a reasonable visitor could infer from the result and opening, then compare it with what the business will actually quote and deliver. The gap is the diagnostic object.
Do not build the diagnosis from anecdotes
Sales complaints can be revealing and incomplete. “SEO leads are rubbish” is not a dataset. Neither is one strange call forwarded to marketing with seventeen exclamation marks. Create a bounded review:
- Choose a defined period.
- Use a consistent contact route or landing-page cohort where available.
- Record the requested service and relevant fit conditions.
- Preserve
unknownwhen information was not captured. - Separate spam, suppliers, recruitment and support contacts from prospective customers.
- Record why an apparently genuine opportunity did not progress.
- Keep the source join at the certainty the implementation supports.
Then compare the pattern with page and query evidence. Search Console supports grouping and filtering by dimensions including query, page, country, device and date, while some query data is withheld or limited (Google: Performance report; Google: Search Console data groupings). Those limits belong in the analysis. Do not attach an individual query to one CRM record merely because the landing page ranked for it during the week.
Use an Enquiry-Fit Ledger
I use an Enquiry-Fit Ledger to turn sales frustration into inspectable evidence.
| Field | Purpose |
|---|---|
| Enquiry record | Stable internal identifier |
| Receipt date and route | Bounds the observation |
| Landing context | Page or permitted page group, if known |
| Requested outcome | What the person actually wanted |
| Fit state | Qualified, disqualified, invalid, unknown or another approved state |
| Reason | Controlled service, territory, scale, timing or customer-type reason |
| Public promise checked | Result or page language relevant to the mismatch |
| Evidence limit | What cannot be attributed or concluded |
| Next investigation | Smallest check capable of reducing uncertainty |
The ledger does not create a magic quality score. It makes repeated mismatch visible without pretending that every record has complete attribution. My rule is to keep unknowns in the denominator. Removing them creates a cleaner report by deleting evidence of a broken handoff.
Sales says the leads are wrong and marketing says the rankings are right? We can build the ledger that lets both of you look at the same evidence.
Identify the decision before editing the page
Once the mismatch is understood, the ranking creates five broad choices.
Decision 1
Keep
Leave the page unchanged when enquiries are commercially suitable, the alleged problem is unsupported or the page serves another valuable purpose.
Decision 2
Qualify
Clarify audience, territory, exclusions, availability, price basis or project scale when the page reaches the right broad market but delays a decisive boundary.
Decision 3
Reroute
Provide a clearer path when the visitor's need is legitimate but belongs to another service, resource or contact route.
Decision 4
Rebuild
Change the page's proposition and decision support when the current promise attracts an incompatible interpretation.
Decision 5
Relinquish
Stop targeting the dominant intent when it is fundamentally incompatible with the offer. A strong position for the wrong decision does not become valuable through rank alone.
I call this the KQRRR decision: keep, qualify, reroute, rebuild or relinquish. The label matters less than refusing to jump from “wrong enquiries” directly to “rewrite everything”.
Qualification should travel into the result and opening
Do not bury the material boundary below the first CTA. If territory, buyer type, minimum scale or availability changes whether the service fits, the qualification should appear where the expectation forms. That may mean adjusting:
- title wording;
- meta description where useful;
- page opening;
- examples and imagery;
- service inclusions and exclusions;
- CTA language;
- form routing.
The objective is not to repel everybody. It is to make the right reader recognise the offer and the wrong reader find a more appropriate path before creating unnecessary sales work. My test is early enough to change the decision. A qualification that appears after the visitor has completed the form is operationally late.
Protect the business outcome, not the dashboard ornament
Teams can become sentimental about a successful-looking position. They tolerate confused visitors and sales friction because nobody wants to be responsible for moving a number-one graph. Use controlled change:
- Record the baseline
The current page, query view and bounded enquiry pattern.
- State the hypothesised mismatch
Which signal you believe is creating the wrong expectation.
- Define the intended change
The qualification or route change you expect to fix it.
- Change the smallest surface capable of testing it
Not the whole page.
- Monitor
Visibility, useful visits, conversion events and returned enquiry disposition.
- Preserve the limits of attribution
Record what the result cannot prove.
If position falls but remaining enquiries fit the business better, the commercial result may have improved. If visibility and qualified demand both fall, reconsider the change. If nothing changes, the original diagnosis may have been wrong. That is why the ranking should neither be destroyed casually nor defended automatically.
Ask what customer decision the page is winning
Before protecting a top position, answer: which customer decision does the page currently win; which offer does the visitor reasonably expect; which enquiries fit or fail the actual delivery model; where does the mismatch first become visible; what is the smallest defensible intervention; and which outcome will remain uncertain after the change?
If the first answer is unclear, the ranking is not a verdict. It is evidence waiting for commercial interpretation. My job is not to worship the position or punish it for bad leads. It is to connect visibility with a customer decision the business is willing and able to serve.
Good to know
FAQs
Not necessarily. Position is visibility under stated conditions. Keep the search record and the enquiry-fit record separate, sample the unsuitable enquiries, classify the mismatch and find where the public promise stopped matching the deliverable offer.
It may change it. If position falls but remaining enquiries fit better, the commercial result may have improved. Use controlled change on the smallest surface and monitor visibility, useful visits and enquiry disposition together.
Keep, qualify, reroute, rebuild or relinquish. It forces a named choice between leaving the page alone, clarifying its boundaries, routing legitimate but misplaced needs elsewhere, changing the proposition, or stopping targeting an incompatible intent.
Rarely with certainty. Search Console groups and limits query data, and a landing page ranking for a query during the week does not attach that query to one CRM record. Keep the source join at the certainty the implementation supports.
Next step
Is your best ranking winning the wrong decision?
We separate visibility from enquiry fit, build the ledger, and help you choose between keep, qualify, reroute, rebuild or relinquish with evidence rather than sentiment.