Website Not Getting Phone Calls? Fixes for Local Service Firms

A website not getting phone calls is usually a site that makes calling harder than it should be on a mobile screen. The number is buried or cannot be tapped, opening hours and service area are missing, or the page loads too slowly for someone in a hurry, so visitors ring a competitor instead.

• A tel: link lets a mobile phone dial a number with 1 tap, and needs the full number with its country code (MDN Web Docs).
• WCAG 2.2 sets a minimum target size of 24 by 24 CSS pixels for things people tap (W3C).
• A good page shows its main content within 2.5 seconds of starting to load (web.dev).
• PageSpeed Insights rates a performance score of 90 or above as good and below 50 as poor (Google for Developers).

Why do visitors read your site but never call?

Visitors who do not call have usually hit a small obstacle at the moment they were ready. A hidden number, unclear hours or a slow page is enough to send them back to the search results.

Someone searching for an emergency plumber or a locksmith is rarely browsing for fun. They want to ring somebody now, and the first site that makes that easy and feels trustworthy usually gets the job. If your site has visitors but the phone stays quiet, the fault is more likely to be on the page than in your traffic. Paying for more visitors without fixing the page simply brings more people who leave without ringing. This guide looks only at phone calls; the wider question of a website not getting leads, including forms and visibility, has its own guide.

Many service sites look fine on a desktop screen and fail on a phone, which is where most urgent calls start. The owner checks the site at a desk, sees the number in the footer and assumes all is well. A customer standing in a flooded kitchen sees a long page, a menu that hides the number and a button too small to hit. The elements that prompt a call are few and predictable: a visible number that dials, clear hours, a stated service area and enough proof to trust a stranger. When any of these is missing, the call goes elsewhere.

Can customers tap your number to call?

A phone number on a mobile site should dial with a single tap. If it is plain text, an image or tucked into the footer, many visitors will not bother copying it.

Turning a number into a tap to call link is a small technical change with a direct effect. The link uses the tel: scheme, and MDN's documentation notes that on mobile devices such a link dials the number automatically. Write the number in full international form in the link, with the country code, so it works for a visitor who is travelling or using a foreign SIM. Never place the number inside an image, because it cannot be tapped, copied or read aloud by a screen reader. Check every page, not just the contact page, because people land on service pages from search.

The size and position of the call button matter as much as the link itself. W3C accessibility guidance sets 24 by 24 CSS pixels as the minimum size for a target, and a main call button should be comfortably larger than that. Put the number at the top of every page, and consider a call button that stays in view at the bottom of the screen as the visitor scrolls. That way the number is always within reach at the moment someone decides to ring. A visitor ready to call should never have to scroll back to find it.

Do your opening hours tell people when to ring?

Opening hours next to the number tell a caller whether anyone will answer now. Without them, a cautious visitor may decide not to try.

Hours answer the question every urgent caller has, which is whether ringing now is worth it. If you take emergency calls out of hours, say so next to the number; if you do not, say when you will call back. Keep the hours on your site identical to those on your Google Business Profile, where Google's Business Profile guidelines ask for your regular customer facing hours and let you add special hours for holidays. A visitor who sees different hours in two places loses confidence in both. Update both on the same day whenever your hours change.

Missed calls need an answer too. If you cannot pick up while you work, record a voicemail greeting that says when you will ring back, and keep that promise. A full voicemail box or a number that rings out tells the caller the business is not really there. State a reply promise on the site that you can keep, such as the same working day. The speed of your call back is part of how well the site performs, even though it happens away from the page.

Does your site say where you work and what you fix?

Callers need to see their area and their exact problem on the page before they ring. Vague copy leaves them unsure whether you can help.

A customer searching for a fence installer in Cedar Park wants to see Cedar Park on the page straight away. If your homepage opens with a generic line such as quality work at honest prices, they have no proof that you serve their street. Put your service area in the headline, the line below it or at least the first paragraph, and list the towns or districts you actually cover. Google's guidelines for service area businesses suggest an area no farther than about 2 hours' drive from your base, which is a sensible limit to show on the site too. A clear area also saves you calls from people you cannot serve.

Service descriptions should name the problem, the result and the place. Generic copy about handling all your plumbing needs speaks to nobody in particular. A homeowner whose water heater failed late at night wants to read about emergency water heater replacement in their county, with same day visits if you offer them. When someone recognises their exact situation, calling you feels like the obvious next step. Give each main service its own page so that each one can do this properly.

Is a slow page costing you calls?

A slow page loses callers before they see your number. On a weak mobile signal, heavy images and extra scripts make the delay worse.

Local service searches often happen on phones away from home, where the connection is unreliable. Google's web.dev guidance treats a page as good when its largest piece of content appears within 2.5 seconds, measured at the 75th percentile of page loads. Oversized photos, unused add ons and third party scripts all push that time up. Visitors who wait on a blank screen do not usually call you anyway; they go back and tap the next result. Speed is invisible when it works and costly when it does not.

PageSpeed Insights gives you a quick reading of any page. It reports a lab score, where 90 or above is good, 50 to 89 needs improvement and below 50 is poor, and it shows real visitor data from the previous 28 days where enough exists. The report lists the specific issues holding the page back, usually starting with images. Compress or resize the largest photos first, then remove scripts you no longer use. Test the homepage and your busiest service page, because those are where most callers arrive.

What should you check in a quick audit of your site?

Pick up your own phone and work through five checks on your homepage and your main service page. Each one takes moments and points to a specific fix.

First, count how many taps it takes to find your phone number; if it is more than one, fix that before anything else. Second, tap the number and confirm that the phone offers to dial the right number with the right country code. Third, look for your opening hours and your service area without scrolling, and compare the hours with your Google Business Profile. Fourth, check whether any real reviews or photos of your work are visible near the top, because a stranger needs some proof before ringing. Fifth, run the page through PageSpeed Insights and note the mobile score and the first issue it lists.

Once you have the results, fix the biggest gap first and leave the rest for later. Change one thing at a time and keep a simple count of calls each week, so you can tell whether the change helped. If you have no record of calls, start one now, with the date, the caller's need and how they found you. That record soon shows whether calls come from the site, the map listing or word of mouth. It also stops you crediting a change for calls that would have come anyway.

Questions service businesses ask about phone calls from their website

Should the phone number be on every page?

Yes, the number should appear at the top of every page and work as a tap to call link. People often land on a service page from search, not on your homepage. A number only on the contact page makes them hunt for it.

Is a contact form better than a phone number?

Offer both, but put the phone number first for urgent services. People with an emergency want to speak to someone, while others prefer to write at night. Test the form regularly so messages reach a person who replies.

What should I do about calls I miss while working?

Record a voicemail greeting that says when you will ring back, and then do it. State the same promise on your website so callers know what to expect. A clear promise you keep loses far fewer callers than a phone that rings out.

Can AI Web Maker help me rebuild a site that gets no calls?

Yes, you describe your business and AI Web Maker builds a complete site with pages, sections, text and photos that you then edit, including your number, hours and service area. Building and previewing costs nothing, and going live is $119 a year of hosting with the domain paid separately. Our AI SEO Tools can then check the pages for problems that keep them out of search.

Make calling the easiest thing on the page

The calls you are missing are going to competitors whose sites make ringing quicker and safer.

Start with the five point audit, fix the number and the tap to call link, and then work on hours, service area and speed. Most of these changes can be made in an afternoon without rebuilding the site. If you do decide to start again, AI Web Maker lets you preview a new site before paying anything. Whichever route you take, keep counting calls each week, because that count is the only honest measure of whether the site is working.