Website traffic feels like progress. The chart rises, more people show up in Google Analytics, and then the phone does not ring and the quote requests stay flat.

The usual reactions are to buy more traffic, redesign the whole site, or blame search rankings. None should be the first move. Traffic only proves that people arrived. It does not prove they were the right people, that the form works, or that the inquiries you did receive were counted.

This guide is five checks to run in order. The first two are quick and rule out the plain causes, a broken form or an uncounted phone call, before you spend money on the harder ones.

It uses the terms from our Google Analytics guide for small businesses: sessions, engagement rate, landing pages, and key events. If those are new to you, read that first. You will also need to sign in to Google Analytics and Google Search Console. If someone else set them up and you cannot get in, start with our account ownership checklist.

Before you start: decide what counts as an inquiry

For a local service business, an inquiry is usually one of these:

  • A completed estimate or contact form
  • A phone call from a prospect
  • A booked consultation
  • A text or chat conversation that someone answers

A newsletter signup is not a sales inquiry, and a click on a button is not a completed form. Pick the two or three actions that represent real progress and count only those.

Skip the “average website conversion rate” figures quoted around the web. They rarely come with a method you can inspect, and a same-day plumbing repair has little in common with a six-month commercial project. Compare against yourself: this month against the same month last year, one service page against another, one traffic source against another.

Check 1: Does the inquiry path work?

Where to look: your own website, on your own phone, using cellular data instead of the office Wi-Fi, and not signed in as an administrator.

  1. Submit every form with a message that looks real.
  2. Confirm the page tells you plainly that the message was sent.
  3. Confirm the message arrives where someone will read it. Check the spam folder too.
  4. Tap the phone number. It should open the dialer with the correct number already filled in.
  5. Test the booking, text, chat, and email links the same way.

Healthy: every form shows a clear confirmation, the message reaches a monitored inbox within a few minutes, and the phone number dials on a tap.

Likely fix: the usual failures are dull ones. The notification goes to a former employee or an old address. The message lands in spam. The phone number is plain text or part of an image, so it cannot be tapped. Google’s guidance is to mark phone numbers as links using the tel: scheme so that a tap starts the call.

A form that worked at launch can stop delivering after a change of email provider, a software update, or an expired account, and nothing on the site will tell you. Repeat this test after any change to the website, the domain, or the business email. If it fails, fix it before going further.

Check 2: Are inquiries being counted?

Where to look: in Google Analytics, open Reports > Engagement > Landing page and find the Key events column. Then open Reports > Realtime, submit your form again, and watch the cards that list events and key events by name. The Realtime report covers the last 30 minutes, so your test should appear there if it is being recorded.

If the Key events column shows zeros while your inbox holds real inquiries, the site may be doing its job and only the measurement is missing.

Three limits on what Analytics can see:

  • Forms. With enhanced measurement turned on, Analytics can record form_start the first time a visitor interacts with a form and form_submit when the visitor submits it. That records the submission, not whether the message reached you, and whether it fires depends on how your form is built. Test it.
  • Phone taps. A tap on a phone link is not among the events Google lists for enhanced measurement. Assume taps are uncounted until you see an event for them. A tap is also not a call, and a visitor who reads the number and dials by hand leaves no trace.
  • Calls that never touch the website. Taps on the call button of your Google Business Profile are counted there, under Performance, alongside website clicks and direction requests. They do not appear in your website’s Analytics.

So do the count by hand once. Add up a month of real form inquiries from the inbox, with the spam removed, and put that next to the key events Analytics reports for the same month. Note the phone calls and Business Profile numbers separately.

Healthy: the form totals are in the same neighborhood. They will not match exactly, because consent choices and blocked scripts leave gaps in Analytics.

Likely fix: if the inbox has more than Analytics, have the completed form marked as a key event and an event added for phone taps. If Analytics has more than the inbox, either the count includes spam and your own tests, or submissions are being recorded that nobody receives, which sends you back to Check 1. Either way, ask new customers how they found you and write it down.

Check 3: Are the right people arriving?

Where to look:

  • Search Console > Performance. The Queries tab shows the Google searches your site appeared for and how many clicks each one produced. The Pages tab shows where those visitors landed. The default view covers the past three months. Google omits some queries to protect privacy, so the list is incomplete.
  • Analytics > Reports > Acquisition > Traffic acquisition. Compare sessions, engagement rate, and key events by channel.
  • Analytics > Reports > Engagement > Landing page. The pages visitors entered on.
  • Analytics > Reports > User attributes > Demographic details, set to City. Analytics derives location from the visitor’s IP address, so treat the city as an estimate.

Healthy: the queries name your service, often with your area. Most sessions land on the home page or a service page. The top cities are places you work.

Not healthy: imagine a plumbing company whose most-visited page explains how to relight a water heater. That article may draw thousands of do-it-yourself readers from other states. They were never going to request an estimate, and counting them makes the whole site look as if it fails. Job seekers, existing customers looking for support, and national visitors to a local business have the same effect.

Be skeptical of sudden spikes too. Analytics automatically excludes traffic from known bots and spiders, but it does not show how much it excluded, and it can only exclude the bots it knows about. A burst of sessions with almost no engagement from a place you do not serve is probably not a wave of customers.

If most of the traffic was never going to hire you, the site is not failing to convert. Judge it on the visits that could have become customers: the rows for your service pages in the Landing page report, and the channels in Traffic acquisition that send local visitors. For those rows, watch Session key event rate, the percentage of sessions that included a key event, against your own earlier months.

Likely fix: adjust the targeting, not the page. Review the ad keywords and locations, the titles that appear in search results, and the subjects the site writes about.

Check 4: Does the page keep its promise and earn the next step?

Where to look: in the Landing page report, take your three busiest service pages and compare their key events and average engagement time against each other. Then open the weakest one the way a visitor does: from the search result or ad that sends people to it.

Healthy: without scrolling far, a stranger can tell what the business offers, who it is for, where it works, why it is a credible choice, and what to do next.

The wording should read like the next sentence of the search or ad that brought the visitor. Someone who searched for “commercial roof repair in Fort Worth” should not land on a home page that says only “Building excellence through innovation.” Google asks the same of its advertisers: an ad’s destination should be functional, useful, and easy to navigate.

Then look for proof. The amount a visitor needs rises with price and risk: a family choosing a foundation contractor needs more than someone ordering lunch. Useful proof includes real photographs of the team and the work, reviews with enough detail to be believable, licenses or insurance where they matter, examples of similar projects, and straight answers about pricing structure, timelines, and what happens after someone reaches out.

Put each piece of proof next to the claim it supports. If the page says projects move quickly, say what “quickly” means and what the customer has to provide.

Likely fix: rewrite the top of the page around the visitor’s question, then add the missing proof. Ask recent customers what they needed to know before they contacted you. This is often a content job, not a new website. Our guide to repairing or rebuilding a website covers how to tell the difference.

Check 5: Is the next step easy on a phone?

Where to look:

  • Analytics > Reports > Tech > Tech details, set to Device category. Compare engagement rate and key events for mobile against desktop. A large gap points to a phone problem.
  • PageSpeed Insights. Run your busiest landing page.
  • Search Console > Core Web Vitals. It labels groups of pages Good, Need improvement, or Poor, based on data from real visits.

Healthy: Google’s published targets for a good experience are a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint of 200 milliseconds or less, and a Cumulative Layout Shift of 0.1 or less, met for at least 75 percent of page loads. In plain terms, the main content appears quickly, the page responds when tapped, and nothing jumps around while it loads.

Two cautions. A small site may not have enough real-visitor data for these tools. PageSpeed Insights then falls back to site-wide data or to a simulated test, and Search Console may show no data at all. In that case your own phone on a cellular connection is a fair judge. Also, passing these targets does not produce inquiries. A page that misses them badly is asking visitors to wait, and some will not.

Then look at the action itself:

  • One primary next step, visible and clearly named
  • A form that asks only for what is needed at this stage
  • A visible label on every field
  • Error messages that say what is wrong and how to fix it, without clearing what was typed
  • Buttons and links large enough to tap. The accessibility standard WCAG 2.2 sets a minimum of 24 by 24 CSS pixels for most tap targets, and a primary button should be comfortably larger.
  • No pop-up covering the form or the phone number

In Analytics, many form_start events with few form_submit events suggests the form itself is the obstacle.

Likely fix: shorten the form, repair the error handling, and make the phone number and main button easy to hit. Match the request to the visitor’s readiness: “Buy now” suits a familiar product, while an expensive service may need “Request an estimate” or “Ask a question.” Some friction is appropriate. A contractor may need a project address before scheduling. Aim for the smallest request that lets both sides take the next step.

Read the pattern

  • The form or phone link fails: fix it before anything else.
  • The inbox has inquiries that Analytics does not: this is a tracking problem, not a marketing problem.
  • Most traffic is irrelevant: the site may be fine. Work on targeting and topics.
  • Relevant visitors leave quickly: check message match, speed, and the phone experience.
  • Engaged visitors do not act: strengthen the proof and the offer, and reduce the size of the request.
  • Forms are started but not finished: simplify the form and repair its errors.
  • Qualified inquiries do not become sales: look at response time, follow-up, and pricing. The website has done its job, and it cannot fix a slow callback.

Change one thing, then compare

Pick the earliest check that failed and fix that. If you rewrite the message, change the form, launch ads, and replace the tracking all at once, you will not know which change mattered.

Then compare a similar period. A small site may see only a handful of inquiries a month, so one month proves little either way. Give the change long enough to show more than two or three inquiries of difference, and if the business is seasonal, compare with the same months last year.

The aim is to replace “the website does not work” with something specific:

The right people reach this page, and the form works, but few of them start it. The service is clear. The page has no project examples and asks for a budget before explaining the process.

That statement can be acted on. A rising traffic chart cannot.

If you want a second opinion

If you have run the checks and are not sure what you are looking at, send us a note with the page address and the check that stopped you. We will tell you what we would look at next.

On the sites we build, Analytics is configured so that form submissions and the button clicks that matter are counted as leads. That is listed with the rest of what is included on our features page.

Sources and further reading