Audit your app
Why Isn't My Website Converting? Check Audience, Tracking, Then Page
Website not converting? Rule out the wrong audience and broken tracking before you touch the page. Here is the order we would check.
A website not converting is a diagnosis problem before it's a design problem. Check 3 things in this order: who is arriving, whether your numbers are true, and only then what the page does to the people who do arrive. Skipping ahead is how builders end up redesigning a page that was never the problem.
You know something's off. People visit, but few of them sign up, buy, or book. In this guide we go deep on the first 2 stages, audience and tracking, and keep the page checks short.
What does "not converting" actually mean?
A conversion is a visitor doing the one thing your site exists for. That might be buying, signing up, booking a call, or joining a list. Your conversion rate is the number of people who did it divided by the number of people who visited.
That number only means something if you picked one action first. If you can't name it in a single sentence, that's your first finding.
Why check the audience and the tracking before the page?
Because both can make a good page look bad, and a redesign fixes neither. If the wrong people arrive, no headline will rescue your rate. If the counter is broken, you're fixing a problem that exists only in your reports.
The table maps what you see to the first place to look. Each row is a starting point, not a verdict.
| What you see | Likely cause | Look first |
|---|---|---|
| Very few visitors | A traffic problem, not a conversion problem | Audience |
| Plenty of visitors, almost no clicks on the main button | Wrong audience, or the page does not match what they were told | Audience, then the first screen |
| One source converts, the others do not | Audience quality differs by source | Audience |
| Your reports say 0, but real sign-ups or emails exist | Missing or broken tracking | Tracking |
| Visitors click the main button, then nothing is recorded | Broken tracking, or a broken path | Tracking, then the path |
| Mostly phone visitors, and nobody finishes | Layout, a pop-up, or slow loading on mobile | Page: mobile |
| People start the form or checkout, then leave | Friction, a surprise cost, or doubt | Page: flow, trust, the ask |
Is the right audience arriving?
Open your analytics and find where visitors come from: search, social posts, ads, email, or people typing your address directly. Then compare how each source converts. For every source, ask 3 plain questions:
- Would this person want what I offer today?
- Did the post, ad, or search result promise something my page doesn't?
- Do I have enough visitors to say anything yet?
That last question matters most. With a handful of visitors, one extra sign-up swings your rate wildly, so small numbers are mostly noise. If you have very few visitors, the honest fix is more of the right visitors, and a new design won't supply them.
Then check the match between the click and the page. Pull up the exact words that earned the click, and open your page right after. If they don't line up, visitors have to work out whether they're in the right place.
Last, tag your links, or you can't tell which post sent whom. Google's page on campaign URLs says to set all the relevant ones if you set one, especially utm_source, utm_medium, and utm_campaign, because missing ones result in "(not set)" values in your reports. For one campaign page, our landing page audit guide follows that single journey.
Is your tracking telling the truth?
Tracking means your site records actions as they happen. In Google's analytics tool, each recorded action is called an event. If the event for your goal never fires, or fires twice, every rate you calculate is wrong.
Test it in 3 steps:
- Do the goal action yourself, once on your phone and once on a computer.
- Watch it arrive. Google's DebugView page explains how to see events in real time as the tool collects them. It also says it's important to filter out traffic while debug mode is on, so that your test data doesn't negatively impact the data in your reports.
- Compare with a record you trust, such as your sign-up list, your payment dashboard, or your inbox. If the record and the dashboard disagree, believe the record and fix the counter.
Test with your consent notice the way a visitor sees it, too. The same Google page says events aren't visible in debug mode when consent mode is in use and the visitor hasn't agreed to analytics cookies. So a notice can change what your reports contain, and it's worth checking both after accepting and after declining.
If an AI tool built your site, a page that looks finished doesn't prove that the goal event fires. Only a test does. Our guide on adding payments, email, and analytics covers the setup.
Say a founder launches an app that sends appointment reminders (a made-up one). After 2 weeks the dashboard shows 300 visitors and 0 sign-ups, and they start sketching a new homepage. First they check sources. Most visitors came from one post in a community of other builders, so the audience deserves a second look. Then they sign up themselves on a phone. The account is created and the welcome email arrives, yet the dashboard still says 0, because the thank-you page never sent the goal event. Meanwhile the app's own user list holds real accounts nobody had counted. The problem sat in the counter, and the page had been taking the blame for it.
What should you check on the page itself?
Only now, with the audience understood and the numbers trusted, do you look at the page. There are 5 short pointers, each with a place to go deeper:
- The first screen. Does it say what this is and who it's for, and does it match the words that earned the click? Our landing page audit guide covers message match.
- Trust. Would a first-time visitor feel safe giving you an email address or a card? Check the signals close to the button.
- The phone. Speed matters on a phone too. Google's web.dev Core Web Vitals page says the Largest Contentful Paint, the time the biggest item on screen takes to appear, should happen within 2.5 seconds of the page starting to load. It also says lab tests can't replace field data from real visitors.
- The path. In Flow and Usability terms, walk from the first click to the confirmation, and check that the email you promised arrives. Our website UX audit guide goes deeper on friction, and a CRO audit maps that one path click by click.
- The ask. Is the price clear before you request a commitment, and does the button name a specific action? Our call to action examples show what a specific label looks like.
How can a report tell a broken path from a broken counter?
This is the one thing our audit adds to the order above. The report keeps 2 lists apart. Under Recorded evidence, a block headed "What we clicked" shows what the audit actually did on your public pages, with counts of pages, links, and buttons, plus a Recorded submissions list for any form it tested. Under that sits a separate "Not confirmed" list, holding anything it tried but couldn't verify. The report says so rather than guessing.
Use that split on a symptom like "clicks happen, nothing is recorded." If the evidence shows the main path working end to end, suspect your counter. If the path breaks in the evidence, fix the path before you trust any number.
What the report can't do is see your tracking. It reads public pages only, meaning what a customer sees at your link, so your analytics, your ad accounts, and the source of each visitor are all outside it. The 3 tracking steps above stay your job.
How do you change things without fooling yourself?
Change one thing at a time. Write down the date and the change. Compare like with like, such as the same traffic source over a similar period. And give each change enough visitors to mean something before you judge it.
No one can promise a conversion rate or a sales result, and we can't either. What you can do is quit guessing and look in the right order: audience, tracking, then page.
Sources, all read 5 October 2026: Google's Analytics help on campaign URLs (no update date shown) and on DebugView (no update date shown), and web.dev on Core Web Vitals (updated 31 October 2024).
