First, record what changed, when, and what the web says
Write down the field that changed, the value now shown, the value it should have, and when the change was noticed. Open the profile manager and check whether the change is listed as an edit applied by Google or suggested by the public, and whether anyone with access edited the profile around that date. Then search for the wrong value itself: the wrong phone number, the old hours or the previous address, each in quotes. Wherever that value appears, on the business's website, a directory, an aggregator, a booking platform or a social profile, is a candidate source.
Finally, compare the location page on the website with the profile, both the visible text and the structured data behind it. The aim is to find which source Google may have trusted over the owner, not to audit every listing; the citations and NAP guide covers the full audit when one is needed. Correct nothing until the record is complete, because a correction made before the source is found tends not to last.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| A field changed and the profile manager shows it as a public or Google edit | Edit notices and the date of the change against the last owner check | Public suggested edits applied while nobody reviewed the profile | Correct the field and set a regular review of edits |
| The wrong value matches what a directory, aggregator or the website shows | Searches for the wrong value in quotes | Conflicting details on the website, citations or aggregators | Correct the source first, then the profile |
| The location page's markup carries old hours, phone or address | The page's structured data against its visible text and the profile | Missing or outdated LocalBusiness markup | Generate markup from the current details and match the page |
| Operations changed hours or numbers and the listings still show the old ones | Who changed what internally, and whether marketing was told | No change control between operations and marketing | Route every operational change through one owner and one record |
| Wrong hours appear on public holidays or during closures | Special hours set for upcoming dates | Special or holiday hours never set | Add special hours ahead of each holiday and closure |
Fix, verify and prevent each cause
Suggested edits nobody reviewed
The Business Profile tutorial notes that Google accepts suggested edits from users and may apply them, so hours, a phone number or even a category can change without the owner's action. An edit that goes unnoticed for weeks becomes the version customers rely on.
Fix: correct the field in the profile, and if the change was a real event the owner missed, such as a new phone line, update the internal record too; the routine at the end of the Business Profile optimisation tutorial includes re-checking for such edits.
Verify: the profile shows the corrected value in a private search and no further edit is pending.
Prevent: assign one person to open the profile at least weekly and handle any applied or suggested edits.
Conflicting details elsewhere on the web
Google compares sources, and a stale directory or aggregator record that keeps the old details is a standing argument for them. When a suggested edit arrives that matches those sources, it looks credible.
Fix: correct the source where the wrong value was found, starting with the aggregators that feed other directories and with the business's own website, then correct the profile; use the correction and claiming routes in the citations and NAP guide rather than working through every listing at once.
Verify: a search for the wrong value in quotes returns fewer results each week, and the profile keeps the correct value after the next check.
Prevent: keep one canonical record and change it before anything else whenever the business changes.
Markup that tells a different story
The location page's LocalBusiness structured data (Schema MarkupStructured data vocabulary.) is meant to describe the same business the page and profile show. Google's documentation for this markup covers properties such as the address, telephone number and opening hours. Markup copied from a template, or written once and never updated, can carry the old values long after the page text changed.
Fix: regenerate the markup from the current canonical details so it matches the visible page and the profile, as the website section of the citations guide recommends, and test it after publishing.
Verify: the markup, the page text and the profile show identical values.
Prevent: generate markup from the same record that feeds the page, never by hand.
No route from operations to marketing
Hours change because staffing changes, numbers change because the phone system changes, and the people who make those decisions are rarely the people who manage listings. When nobody tells marketing, the profile and the website lag behind reality, and customers or the public correct them in their own way.
Fix: name an owner for each field, route every operational change through a single master record, and give marketing a short procedure for pushing it to the profile, the website and the main listings, as the change control section of the location pages and listings at scale guide describes.
Verify: the next operational change appears everywhere within the agreed time.
Prevent: keep a change log against the master record, so a mismatch can be traced to the step that failed.
Holiday and special hours left blank
If the profile only holds regular hours, it shows the business as open on public holidays and during planned closures, and customers who arrive to a locked door may suggest new hours or leave a review.
Fix: add special hours for every upcoming holiday and known closure, as the hours step of the Business Profile tutorial describes, and do the same on the website.
Verify: checking the profile on the dates concerned shows the special hours.
Prevent: put the year's holidays into the calendar with a reminder to set special hours ahead of each one.
Prevention: a monthly profile check and change control
Wrong details are mostly a process failure, so the prevention is a process. Monthly, open the Business Profile (GBPLocal listing on Google Search and Maps.) and compare every field with the master record, handle any applied or suggested edits, and search for the old phone number and previous address in quotes to see whether stale copies are spreading. Before each holiday season, set special hours on the profile and the website together. Whenever operations change hours, phone numbers, services or addresses, the change goes into the master record first, then to the profile, the website and its markup, then to the main aggregators and directories, with a check some days later that every copy agrees. Keep the website's location pages as the most accurate copy of all, because local search engine optimisation (SEOImproving visibility in unpaid search results.) treats the business's own site as the source every other listing should match. When the owner's data is the most consistent version on the web, a stray suggestion has much less to stand on.
A café whose Sunday hours kept changing
A café that stopped opening on Sundays in March finds in May that its profile shows Sunday hours again, and two customers have left reviews about a locked door. The profile manager shows the hours were changed by a public edit on 28 April. A search for the old Sunday hours finds them on a restaurant directory, a delivery app and the café's own location page markup, which still lists Sunday opening although the page text was updated. The owner corrects the directory and the delivery app, regenerates the markup from the current hours, and resets the profile. A weekly check is assigned to the manager. Over the next three months no further edits to the hours are applied, and the old Sunday hours no longer appear in searches.
Common mistakes
Correcting the profile and nothing else. Fixing copies instead of the aggregator. Leaving markup written by hand. Changing hours in the booking system but not the listings. Forgetting holiday hours. Assuming suggested edits are always wrong when some reflect a change the owner missed.
