The win: make the number callable, not just readable.
Here's the whole tactic in one sentence: every place your phone number appears, wrap it so a tap on mobile starts the call. In HTML that's a tel: link — <a href="tel:+19542812190">(954) 281-2190</a> — and the browser does the rest, popping the dialer with your number already filled in. No copying. No app-switching. No fat-fingering a digit and reaching a stranger.
It sounds too small to matter, and that's exactly why it gets skipped. But think about who's actually reading a local business site on their phone: someone with a clogged drain, a dead AC, a tooth that started throbbing an hour ago. They found you, they're sold, and they want to call now. If your number is plain grey text, you just handed them a five-step errand. If it's tappable, you handed them a phone call.
Pull up your own site on your phone before you read another word. Tap the number in the header. Tap the one in the footer. If either one just sits there, you found this week's win.
Why it works better than it should.
The reason this punches above its weight is friction. Every extra step between "I want to call" and "the phone is ringing" leaks intent. Highlight the number, copy it, leave the browser, open the dialer, paste, hit call — that's five deliberate actions, and each one is a chance for the customer to get distracted, second-guess, or bounce to the competitor whose number did tap. Collapsing five steps into one tap doesn't just feel nicer; it catches people at the exact second their intent is highest, before it cools off.
It also disproportionately helps the customers worth the most. Emergency and urgent-need searches — the burst pipe, the locked-out tenant, the same-day haircut before an event — skew heavily toward phone calls over forms, and they skew toward mobile. Those are your highest-intent, highest-margin leads, and they're precisely the ones a dead phone number turns away. You're not optimizing for tire-kickers here; you're optimizing for the person ready to pay today.
And unlike most growth moves, this one costs nothing and risks nothing. You're not spending on ads, redesigning a page, or asking the customer to do anything new. You're removing friction from traffic you already earned — the calls were always there; you were just making them harder to place.
Where to put it (all of these, not one).
The mistake I see most is treating the phone number as a footer item — one link, buried at the bottom, done. On mobile, nobody scrolls to your footer with a burst pipe. Put a tappable number everywhere a decision gets made. The header is non-negotiable: it should ride along at the top of every page so the call is one tap away no matter where someone landed. Your hero, right under the headline, is the next spot — the moment they've confirmed they're in the right place is the moment to offer the call.
Then hit the contact page (obviously), the bottom of every service page (they just read what you do — give them the next step), and any "call for a quote" or "emergency service" line in your copy. Wherever the words invite a call, the number beside them should be tappable. Consistency matters too: use the exact same number, formatted the same way, everywhere — it's the same string of digits your Google Business Profile and directory listings should show, and matching them is a small local-SEO trust signal on top of the conversion win.
A sticky "Call Now" bar on mobile.
Add a slim bar pinned to the bottom of the screen on phones — a single "Call Now" button that's always visible as they scroll. It turns "where was that number again?" into a permanent, one-tap answer. For phone-driven businesses (plumbers, HVAC, towing, urgent dental), it's often the single highest-leverage change on the whole site.
The traps that quietly break it.
A tappable number can still fail in ways you won't notice from your desk. The first trap is the phone-as-an-image number — a lot of older sites bake the number into a logo graphic or a banner, which means it can't be tapped, can't be read by Google, and can't be copied even if someone tries. If your number lives inside a picture, it's decoration, not a call button.
The second is formatting that confuses the dialer. The visible text can be pretty — (954) 281-2190 — but the tel: link itself should carry clean digits with the country code, like tel:+19542812190. Skip that and some phones drop a digit or refuse to dial. The third is the desktop mismatch: on a laptop with no calling app, a raw tel: link can do nothing when clicked, so make sure the number is also plainly visible as text — you want it to dial on a phone and simply read on a desktop, never leave someone staring at a dead link.
Last one, and it's the quiet killer: test the actual call. Tap your own number from your own phone and confirm it rings the line you answer — not an old cell, not a disconnected tracking number, not a voicemail nobody checks. A button that dials the wrong phone is worse than no button, because now you're losing the call and you think the problem is solved.
Do this before Saturday's over.
This is a genuine ten-minute job on most sites. Open your site on your phone, find every place the number shows up, and make each one a clean tel: link with the country code. Add it to your header and hero if it's missing. Then place one real call from your phone to make sure it rings the right line. That's the whole win.
If your site runs on a builder where you can't easily reach the header, the theme fights you, or you want the sticky mobile call bar done right and tracked, that's the point where a small fix turns into fiddly platform work — and it's exactly the kind of thing we handle for clients so the calls just start landing. But you don't need us to try it. Tap your own number this weekend. If nothing happens, you just found ten minutes of pure upside.
We make sure the easy calls actually connect.
Tap-to-call, a sticky mobile call bar, a number that matches everywhere and rings the right line — EpikReach builds and maintains the small conversion details that turn your existing traffic into booked work.
Talk to EpikReach →