Google Ads leak audit: 7 reasons paid clicks fail to convert on service sites

When a service business tells us Google Ads "doesn't work", the account is usually not the problem. The click arrives. Then the page loses it.

We wanted numbers rather than anecdotes, so on 18 October 2026 we scanned the homepages of 100 Tallinn service businesses that rank in Google's top 10 for searches like "elektrik tallinn", "santehnik tallinn" and "kolimisteenus tallinn". Twelve of them had a Google Ads tag on the homepage, which means they are paying for clicks right now. Below are the seven leaks we saw most often, with the count across all 100 sites and across those 12.

1. The phone number is text, not a button

On a service site the phone is the conversion. 39 of the 100 homepages had no tel: link, so a visitor on a phone has to copy the number by hand or retype it. Four of the twelve sites running Google Ads were among them.

A paid click from someone with a leaking pipe lasts seconds. Every extra step in that moment is where the money goes.

2. No form for people who will not call

Some people will not phone a stranger, especially in a second language or at eleven at night. 41 homepages had no form at all. Five of the twelve advertisers were in that group, and two of the twelve had neither a phone link nor a form. Those two pay for each visit and give the visitor no one-tap way to become a lead.

3. Conversion tracking the account cannot see

32 of the 100 homepages had no Google tag or Tag Manager container in their HTML. Tracking can be loaded in other ways, so this is a flag rather than a verdict. But where it is genuinely missing, Google Ads has no idea which clicks turned into calls or forms. Automated bidding then optimises for clicks, not customers, and the owner judges the campaign by gut feeling.

Check it in the account itself: Goals, then Conversions. A conversion action that has recorded nothing for weeks while the phone keeps ringing is broken, not quiet.

4. The ad checker is locked out

Google checks landing pages with its own crawler, AdsBot. Google's documentation notes that AdsBot ignores the general User-agent: * rules in robots.txt and only obeys rules that name it directly. That trips people up in both directions: a blanket rule does not block it, and a rule written specifically for AdsBot-Google does.

One site in our sample had exactly that line in robots.txt, a Disallow for AdsBot-Google. Another answered 403 to every request that identified as AdsBot or Googlebot. Our requests did not come from Google's addresses and some firewalls reject fake bots deliberately, so that second case needs confirming from inside Google Ads or Search Console. Both are worth five minutes, because Google states that these crawler settings affect its ability to check ad quality on the page.

5. Redirects in front of the landing page

30 homepages went through a chain of redirects before the real page loaded: http to https, then to www, or the other way round. Three of the twelve advertisers did. Each hop costs a round trip on mobile data.

The bigger risk is the click ID. Google Ads adds a gclid parameter to the URL so the conversion can be tied to the click. A redirect that rebuilds the address without the query string throws it away. Point the ad at the final URL directly and check that the parameter survives.

6. No price anywhere

69 of the 100 homepages did not show a single euro amount in visible text. We understand why: prices depend on the job. But a visitor who cannot find even "from €X" has two options, call to ask or go back to the results. Paid traffic tends to choose the second, and the owner pays for the click either way.

A "from" price with a clear note that the final price depends on the job filters out people who would never buy and reassures the ones who would.

7. The page never confirms the visitor is in the right place

The first thing a paid visitor looks for is proof that this page is about the thing they searched for. 22 homepages had no H1 heading at all, and 17 had several competing ones. When an ad for "emergency locksmith" lands on a homepage whose top line is a slogan, the visitor has to work out the match on their own.

Send each ad group to the service page that matches it, with a heading that repeats the service and the area.

What was not the problem: speed

Speed gets blamed first, and in this sample it was mostly fine. The median server response was 355 ms, none of the 100 took longer than three seconds to answer, and only four homepages had unusually heavy HTML. Speed matters, but on these sites the money was leaking through the steps above, not through load time.

One more thing worth a calendar reminder: five sites had an SSL certificate expiring within 30 days. An expired certificate puts a full-page browser warning between the paid click and the site.

The check we run before touching bids

1. Open the landing page on a phone and try to call and to send the form, as a customer would.
2. In Google Ads, confirm that each conversion action has recorded something recently.
3. Click a live ad and confirm the gclid is still in the address bar on the final page.
4. Check robots.txt for any rule naming AdsBot, and the server for 403s.
5. Make sure every ad group lands on a page that names its service and shows at least a starting price.

Two of these leaks, a missing phone or email link and a redirect chain in front of the homepage, are among the checks in the free score below. It is a quick way to see where your own homepage stands before you change a single bid.

How we counted

The sample is the Google Estonia top 10 for 20 Tallinn service searches, collected on 18 October 2026, with directories, social networks and marketplaces removed: 100 independent business homepages. "Google Ads tag" means an AW- conversion ID in the homepage HTML. Each figure describes the homepage only; other pages on the same site may differ.

Common questions

Why does Google Ads bring clicks but no calls?

In most cases we see, the page loses the visitor: no tap-to-call button, no form, no price, or a heading that does not match the ad. Broken conversion tracking can also make a working campaign look like a failing one.

Does blocking AdsBot in robots.txt affect my ads?

Google says preferences for AdsBot affect its ability to check ad quality on your pages. AdsBot ignores the general User-agent: * rules, so it is only blocked by a rule that names it, which makes an accidental block easy to miss.

Should I send ads to the homepage?

Usually not. A service page that names the service and the area in its heading and shows a starting price matches the search better than a general homepage.

Is page speed the main reason ads do not convert?

Not in our sample. Median server response was 355 ms and no site took over three seconds to answer. Missing contact options and missing prices were far more common.