First, separate fewer people seeing the profile from fewer people acting on it
Open the performance section of the Business Profile (GBPLocal listing on Google Search and Maps.). As the Business Profile optimisation tutorial describes it, the section shows how people found the listing, including the searches they used, what they did with it, such as calls, direction requests, website clicks, messages and bookings, and the trend over time. Business Profile Help is the reference for the exact metrics and their definitions; this page does not quote them.
Read the two halves separately. If the searches and views that bring people to the profile have fallen along with the actions, the profile is being seen less, and the cause is visibility: status, category, distance, prominence or a duplicate. Go to the not-showing diagnosis, which tests those in order. If the searches and views have held roughly steady and the actions have fallen, the profile is being seen and passed over, or the actions are happening somewhere the count does not reach. Stay on this page.
Before deciding either way, put the current weeks beside the same weeks last year, aligned by weekday and by any holidays that moved, as the guide to comparing periods sets out, and beside the profile's own BaselineAn estimate of what a metric would have done without a given change, campaign or promotion, against which the effect is measured. from the months before the drop. A single location's weekly actions are small counts, and small counts swing; the guide to reading small numbers explains how to tell a run of noise from a real change. Then list everything that changed around the date the drop began: edits applied to the profile by anyone, new reviews, a new phone number or phone system, a website change, a new listing. The five whys is a useful discipline here, because the first plausible answer is often not the cause.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Searches and views fell along with calls and directions | The profile's discovery figures against the same weeks last year | Fewer people seeing the profile at all | Work the not-showing diagnosis; do not change details on this page's account |
| Views held, actions fell soon after an edit nobody on the team made | Edit history for hours, phone, address and links; the values now shown | Details that send people away: wrong hours, phone or links | Correct the field and the source that fed it |
| Views held, actions fell as recent reviews turned critical | Recent reviews, ratings and replies against the months before | Reviews that read worse than before | Fix the operational cause and reply to each review |
| Actions fell, but the same weeks last year fell as well | The weekly series for two or more years, aligned by weekday and holidays | Demand that moved with the season or the calendar | No fix needed; report against the aligned period |
| Calls fell in the profile's count after a phone or tracking change | Which number is primary, which is additional, and where calls are recorded | A number change that moved the calls or the count | Restore the main number as additional and agree one count of record |
| Actions fell and a second listing for the same place appears in search | Searches by name, phone and address for other listings | A second listing taking the actions | Resolve the duplicate, keeping the listing with the reviews |
Fix, verify and prevent each cause
Fewer people seeing the profile at all
When discovery has fallen as well as actions, the drop in calls is a symptom of visibility, and the help centre's local ranking page names relevance, distance and prominence as the main factors in where a profile appears. That is the territory of the not-showing diagnosis, which checks status, category, distance, prominence, duplicates and service-area settings with searches made from where customers are.
Fix: follow that page rather than editing hours or the phone number here, because changing several things at once makes the cause impossible to identify.
Verify: searches and views recover towards the same weeks last year, and actions follow.
Prevent: keep the monthly reading described below, which shows a fall in discovery before it shows in the phone log.
Details that send people away: wrong hours, phone or links
A searcher who sees the business as closed does not call. A phone number that rings out, or a website link that opens a missing page, loses the action even though the profile was seen. The public can suggest edits to a profile and Google may apply them, so hours, a phone number or a link can change without anyone on the team touching them; the information-changed diagnosis explains where such edits come from and why they return.
Fix: correct the field on the profile, then find and correct the source that matches the wrong value, whether a directory, an aggregator or the business's own website, using that page and the citations and NAP guide to keep the name, address and phone (NAPA business's name, address and phone number as they appear across the web.) consistent. Test the phone number and every link from a phone.
Verify: the profile shows the right value in a private search, the number connects, the links open, and actions recover over the following weeks against last year.
Prevent: check the edit history every week and keep one master record of hours, numbers and links.
Reviews that read worse than before
People read recent reviews before they call. A run of critical reviews, or replies that read as defensive, can turn viewers away while discovery holds steady; the local ranking page also lists reviews among the inputs to prominence.
Fix: read the recent reviews for a shared complaint, treat a repeated complaint as an operational signal and fix the operation first, then reply to each review calmly for the next reader, as the reviews and reputation guide describes. If reviews went missing rather than turning negative, use the reviews disappearing diagnosis.
Verify: new reviews stop repeating the complaint and actions recover against the aligned period.
Prevent: read every new review the day it arrives and log recurring themes.
Demand that moved with the season or the calendar
Many local businesses are seasonal, and SeasonalityPredictable, repeating changes in demand tied to the calendar, such as months, holidays, weekdays or hours. moves calls and visits whatever the profile does. A month against the month before mostly measures the calendar, and a holiday that falls in a different week this year can make one period look much weaker than another.
Fix: compare the weeks of the drop with the same weeks last year, aligned by weekday and by moving holidays, as the guide to comparing periods recommends, and keep a calendar of local events, closures and weather that affected trade. If last year fell in the same way, there is nothing to fix.
Verify: the aligned comparison shows the profile tracking its own history.
Prevent: report actions against the aligned period every month, never against the previous month alone.
A number change that moved the calls or the count
A new phone system, a new mobile number or a Call TrackingAttributing phone calls to the marketing source that produced them, usually by showing different tracking numbers per source or visitor. number placed on the profile can change where calls go and where they are counted. The profile tutorial allows a tracking number as the primary number with the main number kept as an additional number, so that the listing still matches the rest of the web; a tracking number that replaces the main number everywhere, or a main number that disappears from the profile, breaks that match. Calls can also simply be recorded in a different place: the profile's own count, the tracking system and the phone log measure different things.
Fix: restore the main number as additional if it was removed, and agree one count of record for the profile's calls, as the guide to measuring calls and chats and the tutorial on measuring Business Profile results set out. Record the change and its date in a measurement change log.
Verify: the count of record shows the same calls the phone log does, and the series before and after the change can be read with the break marked.
Prevent: agree any number change with whoever owns the listings before it is made.
A second listing taking the actions
Two listings for one place split reviews and clicks, so calls and direction requests can go to a listing the business does not watch. A listing at an old address, one made by a member of staff or one recreated from outside data can all appear in search beside the real one.
Fix: search by name, phone number and address, record every listing and who controls it, and resolve the duplicate as the duplicate listings diagnosis describes, keeping the listing with the reviews.
Verify: a single listing appears for each search, and its actions recover.
Prevent: keep a listing register and search for stray listings after any move, rebrand or staff change.
Prevention: a monthly read of the performance data with an edit log
Falling actions are easier to explain when the business has been watching. Once a month, read the profile's performance data in two parts, discovery first and actions second, beside the same month last year and the profile's baseline, and write down anything that moved. Keep an edit log alongside it: every change to hours, phone numbers, links, categories and photos, who made it and when, and every edit applied by Google or the public. Note new reviews, local events and closures in the same place. When actions fall, the log usually shows what changed on the day, and the five whys can work from a fact rather than a guess.
Tag the profile's website and booking links so their visits reach analytics as a source of their own, decide where calls from the profile are counted, and check the phone number and every link from a phone after any change. The tutorial on measuring Business Profile results builds that monthly table end to end. If none of the causes fits, the troubleshooting collection lists the other local diagnoses.
Worked example
Ruddagrel Phone Repairs and the shortened Saturday
Ruddagrel Phone Repairs, an invented phone and tablet repair counter, notices that calls from its profile have fallen over six weeks, from about 40 a week to about 26, and direction requests from about 30 to about 19. Searches and views over the same weeks are within a few per cent of the same weeks last year, so the profile is being seen; people are not acting. The edit log shows no change by the team, but the profile's edit history shows a public suggestion, applied by Google seven weeks earlier, that changed Saturday closing from 5pm to 1pm. Saturday is the counter's busiest day. A search for the wrong hours finds them on one directory that the owner had never updated after a change some years before. The owner corrects the directory first, then the profile, and asks a colleague to check both from a phone. Over the next five weeks calls return to 37 a week and direction requests to 28, close to the same weeks of the previous year, and the owner adds a weekly check of the edit history to the Monday routine.
Common mistakes
Treating fewer calls as a ranking problem without reading discovery first. Comparing with last month in a seasonal business. Changing hours, categories and the phone number in one go. Correcting the profile but not the directory that fed the wrong value. Replacing the main number with a tracking number everywhere. Counting calls in a new place and reading the difference as fewer callers. Ignoring a second listing that shows in search.
