Website Gets Traffic but No Leads? How to Find the Leak (2026)
Summarize this article with AI

Leads are the goal. If your analytics show real visitors and your inbox shows nothing, something between the click and the form submit is leaking. Most leaks fall into three places: the wrong visitors are arriving, the right visitors are not convinced, or the right visitors try to contact you and something breaks.
This is a diagnostic. You will use three free tools you probably already have (Google Search Console, Google Analytics 4, PageSpeed Insights) plus your own phone, and you can run the whole thing in an afternoon. Each step tells you what to look at and what "bad" looks like, so you are not guessing.
By the end you will know which of the three leaks you have, and what to fix first.
Key Takeaways
- Most leaks fall into three places: the wrong visitors show up, the right visitors are not convinced, or the right visitors try to contact you and fail.
- Google Search Console's Performance report shows which queries and pages bring traffic in, broken out by clicks, impressions, CTR, and average position, so you can see if the traffic matches what you sell.
- Core Web Vitals has three pass or fail thresholds: Largest Contentful Paint at or under 2,500 milliseconds, Interaction to Next Paint at or under 200 milliseconds, and Cumulative Layout Shift at or under 0.1. Anything worse counts as poor.
- The recommended minimum tap target on mobile is 48 device independent pixels. A phone number or button smaller than that is hard to tap accurately.
- In GA4, a form submit or phone click only counts as a lead if it is set up as a key event. A site that never marks one has every "lead" that already happened going uncounted.
- Run the audit in this order: check who is arriving (Search Console), check if they are convinced (your own read of the page), then check if they can actually convert (PageSpeed and your phone). Fixing step three before step one wastes the fix.
The Three Places a Lead Gets Lost
Every visit that does not become a lead failed at one of three points. Naming which one saves you from redesigning a site that was never the problem, or writing new headlines for traffic that was never going to buy.
- Leak 1, the wrong visitors: People are landing on your site, but they are not the people who hire or buy what you sell. Wrong search queries, wrong pages ranking, wrong ad targeting.
- Leak 2, unconvinced visitors: The right person lands on the right page and leaves anyway, because the message, the proof, or the price is not clear enough to act on.
- Leak 3, visitors who try and fail: The right person is convinced enough to try to contact you, and the form, the phone number, or the page itself gets in the way, or your tracking never counted the attempt in the first place.
The audit below checks each one in order, with a free tool for each.
Step 1: Check Who Is Actually Arriving (Search Console)
Open Google Search Console and go to the Performance report. Google's own help page describes what it shows: clicks ("the number of times a user clicked your site from Google Search results"), impressions ("how many times your site appeared in Search results"), CTR ("the click count divided by the impression count"), and average position ("the average position of the topmost result from your site"), and you can group all of it by query, page, country, device, or search appearance.
Do this in order:
- Sort queries by clicks. Read the top 20. If most of them describe a problem you do not solve, a product you do not sell, or a city you do not serve, your traffic is coming from the wrong intent. That is Leak 1, and no amount of homepage polish fixes it.
- Sort pages by clicks. Check which page is bringing the most visitors. If it is a blog post about a tangential topic and your main service page barely appears, your traffic is landing somewhere with no reason to convert.
- Filter by device. Compare clicks and average position on mobile versus desktop. A big gap tells you where to focus the rest of this audit.
What "bad" looks like here: your top queries are informational ("what is," "how does," "diy") instead of transactional ("near me," "cost," "quote," a service name plus a city), or your top-clicked page is not one that can generate a lead at all.
Then open GA4 and check Acquisition alongside it. If Search Console shows real clicks but GA4 shows almost no matching sessions, that points to a tracking gap. Check that your GA4 tag fires on every page and that consent settings are not blocking it before you look anywhere else. If the sessions are there but average engagement time on your main service pages is very short, visitors are landing and leaving fast, which points toward Leak 2.
Step 2: Check If the Right Visitors Are Convinced
If step 1 showed the right people are arriving on the right pages, and they still are not converting, the problem is what they see once they get there. Read your own page as a stranger would, on the device most of your traffic uses (Search Console's device filter tells you which one).
Check these in order:
- Message clarity: Can a visitor tell in the first screen what you do, who it is for, and what happens if they call or fill out the form? If the headline is a slogan instead of a description, that is a red flag.
- Proof: Is there anything a skeptical stranger would trust, reviews, photos of real work, a license number, years in business? A page with claims and no proof reads the same as every competitor's page.
- Price clarity: If price is normally a sticking point in your industry, does the page say anything about it (a starting price, a range, "free estimate," financing) or does it stay silent and hope the visitor calls anyway? Staying silent on price can cost you a visitor who was otherwise convinced.
- The ask: Is there one clear next step (call, text, fill out a short form) repeated near the top and again near the bottom, or does the visitor have to hunt for how to contact you?
A page that is otherwise fine on message and proof but sits on an old redesign or was never built with conversion in mind is worth a rebuild rather than a patch. Rankwyre's website redesign service and landing page service both start from this same read: what does a stranger actually see, and does it give them a reason to act.

Step 3: Check If Visitors Can Actually Convert (PageSpeed and Your Phone)
This leak is easy to miss, because the visitor wanted to contact you and something in the way stopped them, or stopped your tracking from seeing it.
Run PageSpeed Insights
Go to PageSpeed Insights and test your homepage and your main service page, separately, for mobile. Google's own documentation on Core Web Vitals gives three thresholds for a "good" score: Largest Contentful Paint at or under 2,500 milliseconds, Interaction to Next Paint at or under 200 milliseconds, and Cumulative Layout Shift at or under 0.1. Anything above those is rated "needs improvement" or "poor."
PageSpeed Insights reports two kinds of data, and the distinction matters: field data is "anonymized performance data from users in the real-world on a variety of devices and network conditions," while lab data is "based on a simulated load of a page on a single device and fixed set of network conditions," according to Google's own PageSpeed Insights documentation. Trust the field data first when your site has enough traffic to show it, since it reflects what real visitors actually experienced on their own devices.
What "bad" looks like: any metric in the red or yellow zone on mobile, especially LCP, since that measures how long a visitor waits before the main content of the page is even visible. A slow-loading service page loses visitors before they see your proof or your ask.
Test your own forms and phone number, on your own phone
Do this from your actual phone, on cellular data, not your office wifi:
- Tap the phone number. Does it dial? A phone number that is styled as plain text instead of a clickable "tel:" link makes a visitor copy and paste it manually, and many will not bother.
- Check the tap target size. Google's own accessibility guidance recommends a minimum touch target size of around 48 device independent pixels. Zoom in on your call button and form fields. If they look cramped next to other tappable elements, mis-taps and abandoned attempts are likely.
- Fill out the form yourself, start to finish. Count the fields. Time yourself. Note anywhere the keyboard covers the submit button, anywhere a required field is unclear, and anywhere the page does not tell you it submitted.
- Check what happens after you submit. Does a thank-you page load, or does the form just sit there? Does an email arrive? If nothing visibly confirms the submission, visitors who did successfully convert may believe they failed and give up, or worse, submit twice.
Check whether your leads are even being counted
Open your GA4 property and go to Admin, then Data display, then Events. According to Google's own help documentation, a conversion in GA4 has to be deliberately set up: you "create or identify an event that measures the action and then mark the event as a key event." If your form submit or phone click event exists but was never marked as a key event, GA4 will show traffic and zero conversions even on days when the phone rang. That is a measurement gap, and it is worth ruling out before you rebuild anything.
The Leak Map: Symptom, Likely Leak, First Fix
| Symptom | Likely leak | First fix |
|---|---|---|
| Top Search Console queries do not describe what you sell | Leak 1: wrong visitors | Rewrite page titles and headings around the specific service and city, not general topics |
| Traffic lands mostly on a blog post, not a service page | Leak 1: wrong visitors | Add a clear link and call to action from that post to the relevant service page |
| Visitors arrive on the right page but leave in seconds (short GA4 engagement time) | Leak 2: not convinced | Add specific proof (reviews, photos, credentials) above the fold |
| Page has no mention of price or next step | Leak 2: not convinced | State a starting price, range, or "free quote" and repeat one clear call to action |
| PageSpeed Insights shows LCP over 2,500 ms on mobile | Leak 3: page is too slow to reach | Compress hero images and defer anything below the fold |
| Phone number does not dial when tapped on a real phone | Leak 3: broken contact path | Wrap the number in a "tel:" link |
| Form has many required fields and no confirmation message | Leak 3: broken contact path | Cut the form to name, phone, and one detail field, and add a visible thank-you state |
| GA4 shows zero conversions despite known phone calls or emails coming in | Leak 3: measurement, not a real leak | Mark the form submit and phone click events as key events in GA4 |
Common Mistakes
- Redesigning the whole site before running the audit. A new design does nothing for Leak 1 (wrong visitors) or a broken phone link (Leak 3). The fix: run all three steps above first, then decide whether the fix is a redesign, a content change, or a technical one.
- Testing forms only on a desktop browser. A form that works fine with a mouse and a full keyboard can still fail on a phone screen. The fix: always test from your own phone on cellular data, the way most visitors will actually use it.
- Assuming GA4 shows zero conversions because the funnel is broken. Often the funnel worked and nothing was ever marked as a key event. The fix: check Admin, then Data display, then Events in GA4 before you touch the page itself.
- Chasing more traffic to compensate for a low conversion rate. More of the wrong visitors, or more visitors into a broken form, just wastes a bigger ad budget. The fix: fix the leak first, then scale the traffic that already exists.
- Reading Search Console on desktop numbers only. If most of your real visitors are on mobile, a desktop-only read can hide the exact problem. The fix: filter the Performance report and PageSpeed test by device and read mobile first.
FAQs
It means the leak is somewhere between the click and the form submit rather than in how many people find your site. The three places to check are whether the wrong visitors are arriving, whether the right visitors are not convinced by the page, or whether the right visitors try to contact you and something (a broken form, an unclickable phone number, slow load, or missing tracking) gets in the way.
Run the same three checks. For an ecommerce or service business, also test the actual purchase or booking path on your own phone, since a slow checkout page or a form with too many required fields loses buyers the same way it loses leads. Start with Google Search Console to confirm the traffic matches what you sell, then test the path to purchase yourself.
Open GA4, go to Admin, then Data display, then Events. If your form submit or phone click event is not listed there, or exists but was never marked as a key event, GA4 will report zero conversions even when real leads are coming in. Mark the relevant events as key events to start counting them going forward.
Google's Core Web Vitals set the bar at a Largest Contentful Paint of 2,500 milliseconds or under, an Interaction to Next Paint of 200 milliseconds or under, and a Cumulative Layout Shift of 0.1 or under, all rated as "good." Test your site's actual field data in PageSpeed Insights rather than guessing, since a page that feels fast on your office wifi can still fail these thresholds on a visitor's phone.
Only after you have ruled out the other two leaks. A redesign fixes an unconvincing page (unclear message, missing proof, no price clarity), but it does nothing for the wrong traffic arriving in the first place or a phone number that will not dial. Run the full audit first, then decide whether the fix is a redesign, a content change, or a technical one.
Check Search Console and GA4 monthly, since the queries and pages bringing traffic change as your rankings shift. Re-test your forms and phone number any time you change your website, your phone system, or your CRM, since any of those can silently break the contact path without changing how the page looks.
Conclusion
Traffic without leads means a leak, and it is usually in one of three places: the wrong visitors, an unconvinced visitor, or a visitor who tried and failed. Search Console tells you who is arriving. Your own read of the page tells you if they are convinced. PageSpeed Insights and your own phone tell you if they can actually get through.
Run all three before you spend on a redesign or more ads. If you want a second set of eyes on where your leak is, run Rankwyre's free website audit for an instant read on your SEO, Core Web Vitals, and conversion setup, or get started with Rankwyre to have a team fix it. Rankwyre is a digital technology company based in Miami, Florida. It builds custom websites, ecommerce stores, web apps, CRM systems, and dashboards, then runs the SEO and ads that bring in customers, including full business website builds when the fix is bigger than one page.
About the author:
Rankwyre Team
Digital technology company, Miami, Florida
Rankwyre is a digital technology company based in Miami, Florida. It builds custom websites, ecommerce stores, web apps, CRM systems, and dashboards, then runs the SEO and ads that bring in customers.














