Traffic that does not convert, and the four reasons why
The traffic arrived and nothing happened, and you cannot tell which part is broken.
Short answer
There are four causes and they need different fixes: the queries carry the wrong intent, the page does not deliver what the result promised, the interface fails at the moment of action, or the offer is wrong. Diagnose in that order, because the first two are cheap to check and the last is the one everyone assumes first.
Cause one: intent mismatch
You rank for a query whose searcher wants something adjacent to what you sell. Informational queries convert badly by nature, and ranking well for one produces impressive traffic and no revenue. Check which queries actually drive the sessions before concluding the page is at fault.
Cause two: the promise and the page disagree
The title and description made a specific promise and the page delivers something broader or different. The visit is recorded, the person leaves in seconds, and the analytics call it a bounce rather than a broken promise. Read your own snippet next to your own page.
Cause three: the interface fails
People try and cannot. Buttons that do not respond, forms that fail silently, a step that breaks on mobile. This is invisible in a funnel because nothing errors server-side, and it is the cause teams check last despite being the cheapest to fix.
Cause four: the offer
Sometimes the traffic is right, the page is right, the interface works, and the thing on offer is not compelling at that price to that person. This is the expensive answer and it is also the one people jump to first, which wastes the cheap checks.
Diagnose in order of cost
Query intent takes ten minutes in Search Console. Promise mismatch takes ten minutes reading your own result. Interface failure takes an afternoon with behaviour analytics. Offer problems take a quarter. Working in that order means you rarely reach the fourth.
Segment before you conclude
A site-wide conversion rate averages your best page with your worst and describes neither. Look per page and per query cluster: usually a small number of pages carry the traffic and a different small number carry the conversions, and the gap between them is the finding.
The number that reframes it
Dead clicks. If a meaningful share of sessions contain a click that produced no response, you do not have a conversion problem, you have an interface defect that presents as one. That is a good outcome, because it is fixable this week.
Questions
- Is a high bounce rate always bad?
- No. On a page whose job is to answer one question, a visitor reading the answer and leaving satisfied is success. Bounce is only a problem where the page needed a next step.
- Should I fix conversion or get more traffic?
- Fix conversion first when you already have traffic, because the gain applies to every visitor you go on to acquire. Chasing volume on top of a leaking page multiplies the leak.
- How do I know if intent is the problem?
- List the top queries driving the page and ask whether someone typing each would want to buy today. If most of them are researching, the traffic is doing what it was always going to do.
Measured, not asserted
On ihatepdf.cv, 26.92% of 132,748 sessions completed the task, and 37.16% of sessions contained a dead click, on the way to 100,542 users. The second number is the actionable one: a third of visitors clicking something that did nothing is an interface finding, not a conversion-copy finding.
Free tool for this: Search Console Analyzer. No account, nothing uploaded.
Where this goes deeper
Every number on this page comes from one complete dataset: one product taken from zero to 100K+ users on search alone, with nothing spent on advertising. The full argument is Chapter 19 and Chapter 21 of the book. Five chapters are free to read.