Jeremy Ashburn

Click-to-Call: The Mobile Conversion Fixes Most Contractor Sites Miss

Where the call button has to be on a contractor site, thumb-zone placement, sticky bars that don't cover content, and how to track taps as key events.

TL;DR: Most visitors to a home service website are on a phone and most of them want to call you, not fill in a form. The fixes are small, cheap, and almost never done: a tappable number in the header, a sticky call bar in the thumb zone, phone numbers that are actual links, and tap tracking so you can see it working.

Why this matters more than your form
Make the number an actual link
Where the call button has to be
Thumb-zone placement
Sticky bars that don’t cover content
Tracking taps as key events
Testing on a real phone

Why This Matters More Than Your Form

For home services, mobile is the majority of traffic and calling is the preferred action. A homeowner with a problem wants to describe it to a person, get a rough answer, and know when someone can come out. A form makes them write that out and then wait.

That doesn’t mean remove the form — some people prefer it, and after-hours visitors need it. It means the call action should be the more prominent of the two on mobile, and on most contractor sites it isn’t. The number sits in an image in the header, or as plain text nobody can tap, or below a hero section that takes two scrolls to clear.

The fixes below take an afternoon and they don’t require rebuilding anything.

Want more customers from Google & AI search?

Get a free SEO audit of your site — see exactly what to fix first.

Get My Free Audit Book a Call

Make the Number an Actual Link

The most common defect, and the easiest fix.

A phone number typed as plain text does nothing when tapped. It needs to be a tel: link:

html <a href="tel:+18285550142">(828) 555-0142</a>

Three related mistakes worth checking:

The number is an image. Common on older sites and in headers built by page builders. Images aren’t tappable and search engines can’t read them. Replace with real text.

The link has formatting inside the href. tel:(828) 555-0142 is less reliable than tel:+18285550142. Put the clean E.164 format in the href and the pretty version in the visible text.

Only one instance is linked. Every appearance of your number — header, footer, contact section, mid-page CTAs — should be tappable. Visitors tap wherever they happen to be.

Check your own site right now on your phone. Tap every phone number you can find. It takes two minutes and it’s frequently the highest-return two minutes available.

Where the Call Button Has to Be

Four locations, in priority order:

1. Header, visible without scrolling. Not in a hamburger menu. A visitor who arrived with an urgent problem should see how to reach you in the first screen.

2. A sticky element that stays as they scroll. Covered below.

3. Inside the content, after the point where you’ve answered their question. Someone reading your water damage page hits the moment where they’ve decided — put a call action there, not only at the bottom.

4. Footer. Table stakes, and the least valuable of the four.

What doesn’t work: a single call-to-action at the very bottom of a long page, or a number that only appears on the contact page. Both assume a patience that urgent visitors don’t have — the same urgency that shapes how a great contractor estimate builds trust quickly rather than making the homeowner wait for clarity.

Thumb-Zone Placement

On a phone held one-handed, the comfortable reach area is the lower portion of the screen — roughly the bottom third, biased toward the side of the dominant thumb. The top corners are the hardest to reach.

Practical implications:

Sticky call bars belong at the bottom, not the top. Bottom-anchored is both easier to reach and less likely to obscure content.
Make the tap target big enough. Around 44–48 pixels of height minimum. A thin text link is a missed tap, and a missed tap on a call button is a lost lead.
Give it breathing room. Adjacent tappable elements cause mis-taps. Spacing matters as much as size.
High contrast. The call button should be the most visually obvious thing on the screen. This is not the place for subtle.

Sticky Bars That Don’t Cover Content

Sticky call bars work, and done badly they’re worse than nothing.

Do:
– Anchor to the bottom
– Keep it short — one line, one or two actions (“Call Now” and optionally “Text Us”)
– Add bottom padding to your page content equal to the bar height, so the bar never covers the last paragraph or the form submit button
– Make sure it doesn’t overlap a cookie notice, chat widget, or back-to-top button

Don’t:
– Stack a sticky header, sticky bar, chat bubble, and popup on the same screen. On a small phone that can consume most of the viewport and it makes the site feel like a trap.
– Animate it repeatedly or make it pulse
– Cover the form fields on your contact page

Test on a small phone, not just a large one. A layout that’s fine on a 6.7-inch screen can bury the content on a 5.4-inch one.

Tracking Taps as Key Events

If you don’t measure it, you’ll never know whether the changes worked.

In GA4, a tap on a tel: link can be tracked as an event and then marked as a key event. Configure it so you can see call taps by page, which tells you which service pages generate phone calls — genuinely useful for deciding where to invest content effort.

Three things to get right:

Mark it as a key event. Otherwise it’s buried and won’t appear in the reports anyone looks at.

Track by page. Aggregate tap counts are much less useful than knowing your water damage page drives four times the calls of your general services page.

Reconcile against actual calls. Taps aren’t calls — people tap and cancel. Compare tap counts against your call tracking data to learn your own ratio, then use taps as a leading indicator.

Pair this with call tracking and you can finally answer which pages produce phone calls that become jobs.

Testing on a Real Phone

Browser device emulators are useful for layout and useless for this. Tap targets, thumb reach, and whether tel: links actually dial can only be verified on hardware.

A five-minute checklist, done on your own phone:

Load your homepage. Is a tappable number visible without scrolling?
Tap it. Does the dialer open with the right number?
Scroll to the middle of a service page. Can you reach a call action with your thumb?
Scroll to the very bottom. Is anything covered by the sticky bar?
Open your contact page. Can you see and tap the submit button with the bar present?
Repeat on a second phone with a smaller screen, ideally someone else’s.

Do this after any theme update or redesign. These break silently, and nobody notices until leads drop.

Quick Recap

Mobile visitors to home service sites prefer calling; make the call action more prominent than the form.
Phone numbers must be real tel: links with clean E.164 formatting in the href — check every instance.
Put a tappable number in the header without scrolling, plus a bottom-anchored sticky bar.
Bottom third of the screen is the reachable zone; 44–48px minimum tap height with real spacing.
Add page padding so the sticky bar never covers content or a submit button.
Track taps as GA4 key events, segmented by page, and reconcile against real call data.

Frequently Asked Questions

Should I remove my contact form and only use calls?
No. Keep both. Some people won’t call, and after-hours visitors need a form. Just make the call action the more prominent one on mobile.

Does a sticky call bar hurt SEO?
No, provided it doesn’t obscure content or behave like an intrusive interstitial. Keep it small, keep it dismissible if it’s large, and add page padding.

What about text messaging as a second option?
Increasingly worth offering, especially for younger homeowners and non-urgent inquiries. Add it alongside the call button, not instead of it.

Do tap events equal phone calls?
No. Some taps get cancelled. Treat taps as a leading indicator and reconcile against call tracking to establish your real ratio.

Where should the number appear on a desktop site?
Top right of the header is conventional and works. Desktop matters less for this — most of the value is on mobile.