Good local rankings but no calls? Follow the enquiry path

Editorial illustration

Define what has actually stopped

“We rank well, but the phone is quiet” contains several possible problems. The business may rank for searches with little buying intent, appear mainly close to its base, receive enquiries through forms instead of calls, miss incoming calls or have a tracking fault. The first useful action is to separate those possibilities.

Write down the period, the services affected, the target area and what “no calls” means. Is the claim based on a phone log, a receptionist's impression, the Business Profile report or an analytics event? Check whether the business was open, whether a number changed and whether staff availability differed. A holiday closure is not a ranking diagnosis.

Build a small evidence sheet with four stages: visibility, visits or profile actions, enquiries received, and enquiries that fit the business. Keep each source beside the figure. The purpose is to find the stage where the customer journey stops.

Check which searches and places rank well

A branded search and an unbranded service search answer different questions. Someone entering the company name may already know whom to contact. Someone searching for a repair is choosing among suppliers. Keep those groups separate, then look at the specific service and the location represented in the ranking report.

Google's local results consider relevance, distance and prominence. A result checked beside the business is not a measurement of the entire city. Use the official ranking explanation to frame that limitation, then inspect a consistent set of places that matter to the business.

Also inspect intent. A guide about repairing an appliance yourself can attract readers who do not want a technician. A product supplier may rank for a term mostly used by people seeking installation. Look at the results and the landing page together before treating a good position as proof of commercial demand.

Read Business Profile interactions correctly

In the profile report, check the selected dates and the definitions of the available metrics. Google's performance documentation defines a call as a click on the call button. It also notes that reported performance can include organic results and Google Ads. A report label is not evidence that a call was answered or came solely from unpaid search.

Compare the available interactions with the phone system and enquiry log. If call-button clicks exist but no calls are received, test the number and routing. If website clicks exist but no enquiries follow, continue onto the landing page. If profile visibility exists without meaningful actions, examine intent, the offer and the information a customer sees before acting.

Record missing data as missing. An unavailable metric is not zero. Customers can also contact a business through routes the chosen report does not capture, so avoid forcing different systems into an exact numerical match.

Verify website attribution and lead events

Use consistent campaign parameters on the Business Profile's website link when a separate website traffic segment is needed. A practical convention might use utm_source=google, utm_medium=organic and utm_campaign=business_profile. These are an editorial naming example, not a Google-mandated campaign name. Google's campaign URL guide explains how the parameters populate attribution information.

Confirm what each event measures. A telephone-link click indicates intent to call; it does not prove a connected conversation. A submit-button click can occur before validation or a server error. Google's recommended generate_lead event is intended for a submitted form or information request. Implement it around the confirmed outcome, then test the event and the actual inbox. See recommended events.

Mark important, tested events as key events where appropriate. Google's key-event guidance explains that marking step; it does not validate the quality of an incorrectly implemented event. Keep test submissions and duplicate firing out of the business interpretation.

Test the page as a prospective customer

Open the exact profile destination on a phone using an ordinary connection. Can someone immediately tell which service is available, where it is offered and how to enquire? Look for vague headlines, unsupported claims, old business names and a contact button that appears only after substantial scrolling. Make the page answer the question that brought the visitor there.

Follow the route to completion. Test phone links, form validation, mandatory fields, file uploads and confirmation messages. Check whether the form works without an account and whether an error is explained in useful language. A form that requests a complete project specification before allowing an initial question can create avoidable friction.

Clear expectations also help. Tell visitors what information is useful, which projects the business handles and what the team will do next. Do not advertise instant answers if the inbox is reviewed once each day. An honest contact process is easier to operate consistently.

Inspect what happens after the click

Test the published number during the hours displayed on the profile. Confirm the correct business answers, voicemail identifies it clearly and any forwarding arrangement reaches the intended team. Check the experience outside hours as well. A caller should understand whether to leave a message, submit a request or try again later.

Review missed calls and response handling with the person who answers them. A busy owner may see the same unknown number several times without knowing whether it was a customer, a supplier or spam. A simple disposition log makes that distinction possible: answered, missed and returned, spam, wrong service, outside area, appointment arranged.

Keep the intake questions short and relevant. Ask enough to understand the service, area and next step. If recording calls or retaining personal details, establish an appropriate privacy and access process before doing so. Useful measurement does not require publishing customer information or filling a spreadsheet with unnecessary detail.

Match the next action to the evidence

These are investigation paths, not automatic diagnoses. Several faults can coexist, and a small sample can move sharply from one period to another. Read the underlying enquiry notes before choosing a remedy. Rewriting the profile description cannot repair a disconnected telephone number, while changing a form cannot create demand for an unsuitable service.

Measure the repair at the stage it should affect

Choose the most clearly evidenced fault, assign a repair and define a completion check. A routing repair is verified with a successful test call. A form repair is verified with a received submission and one correctly recorded event. A service-clarity change is assessed through the relevance of subsequent enquiries, alongside the volume.

Keep dates and notes about other changes, promotions, closures and seasonal factors. Compare matching periods where possible and avoid declaring success from a brief burst of activity. The business needs to know whether the enquiry path works consistently.

Positions remain useful diagnostic evidence. They become more valuable when connected to the customer's next action and the team's response. A quieter phone can be investigated systematically once those stages are visible.

Open this guide’s interactive checklist