Google updates
Google gathers information from sources such as user reports and licensed data, and may update a profile when those sources indicate it is wrong or outdated. Sometimes that is right; sometimes it overwrites correct data.
Location Operations
Monitoring
Know what Google actually shows for every location
What you publish to a Business Profile is not always what customers see. Google can update profile information from other sources — user reports, suggested edits and licensed data — and anyone with access can change a profile directly. Monitoring compares the live state of every location with your source of truth, flags each difference and turns it into a decision: accept, correct or escalate, with a record of who decided what.
Monitoring starts with Google Business Profile, where Google exposes its own updates; Apple Maps, Bing and TomTom are added where they are in scope.
Drift
Six ways live data moves away from your source
Drift is rarely one large error. It is many small differences that accumulate until customers notice them first.
Suggested edits
People on Google Maps can suggest changes to a place’s name, category, address, hours or phone number. Google notifies the business about certain suggested edits and gives it 4 days to accept or reject them. Suggestions without a notification, or without an answer in time, can go live without anyone in your organization deciding.
Direct edits
Local managers, agencies and former partners with access change profiles outside the agreed process — often with good intentions, and without a record.
Competing publishers
Two systems writing the same field overwrite each other. The live value depends on which one ran last.
Source errors
The master data itself is wrong or out of date — a closure never entered, a phone number changed at the branch but not in the system.
Platform differences
Apple Maps, Bing and TomTom receive and display data through their own channels, so a correction on Google does not automatically appear everywhere else.
What is checked
Field by field, not profile by profile
A profile is correct only if every customer-facing field matches the source of truth. These are the fields where differences matter most.
| Field | What can change it | Why it matters | Typical decision |
|---|---|---|---|
| Name | Google updates, suggested edits, local edits | Names with added details can breach Google’s guidelines; unapproved names break brand consistency. | Restore the approved name and find out where the change came from. |
| Address and map pin | Suggested edits, address formatting, relocations | A misplaced pin sends customers to the wrong entrance or street. | Correct the pin or address; check directions from the main approach. |
| Phone and website | Suggested edits, local edits, tracking changes | Calls and visits go to the wrong place; campaign tracking breaks. | Restore the agreed number and URL, including tracking parameters. |
| Regular and special hours | Google updates, suggested edits, missed holiday plans | The error customers notice first — a closed door during listed hours. | Correct immediately; trace whether the source or the process failed. |
| Categories and attributes | Google updates, local edits | Categories shape the searches a location appears in; inconsistent categories fragment a network. | Hold to the network’s category rules for each location type. |
| Status and duplicates | Google updates, duplicate detection, closures | A location shown as closed, or a duplicate competing with the real profile. | Correct the status; resolve duplicates as cases. |
How Google exposes it
Google shows its own changes — if you look
Google’s Business Profile APIs separate what the business submitted from what customers currently see.
For each location, Google can return the version that is live on Maps and Search. Google’s documentation describes this consumer-facing view as one that “may have been updated by Google or user-generated content and may differ from the merchant’s version”, and marks which fields differ from the business’s own information.
A Google update is accepted by confirming the value, or rejected by submitting the preferred value. Accounts can also receive notifications when Google has updates for a location, when a location’s duplicate status changes, and when its standing changes.
Edits the business submitted can also sit in review before they appear. A difference between your source and the live view is therefore one of three things: a Google update, your own edit still pending, or an error in your data — and each needs a different response.
Reconciliation
Every difference ends in a decision
Monitoring without decisions produces a dashboard nobody reads. Reconciliation is the process that closes each difference.
-
Detect
Compare the live view of each location with the source of truth, on a schedule agreed per field — hours more often than categories.
-
Classify
Decide whether the difference is a Google update, a pending edit, a direct change or an error in the source.
-
Resolve
Accept a correct update into the source of truth, or restore the approved value on the profile — and fix the process that caused the difference.
-
Record
Log the difference, the decision, who made it and the live state afterwards.
- RuleCorrect the source when the world changed; correct the profile when the source is right.
Audit trail
Why the record matters
In regulated networks and in disputes, “the data was correct” is not enough. You need to show when it was correct and who changed it.
For regulated networks
A dated record of hours, closures and contact details shows what customers were told at any point — useful for complaints, compliance reviews and internal audits at banks and healthcare groups.
For shared teams
When several parties work on profiles, the record shows which change came from where — and ends discussions about who broke what.
For the next change
Patterns in the record — the same field drifting at the same locations — show where the process, not the profile, needs fixing.
Experience
Part of how we operate
Monitoring is part of every MapsExperts operating model, not a separate report.
Outdated data found and fixed
Profiles contained outdated information and inconsistent categories, and reviews revealed inaccurate weekend opening hours. MapsExperts corrected the foundations and fed recurring issues back to the client’s team; after customers’ concerns were resolved, the average Google rating rose by 0.4 stars.
HealthcareDifferences flagged, tasks tracked
The MapsExperts Platform flags differences between source data and profiles, failed validations and disconnected locations, and tracks the resulting tasks and alerts.
PlatformAccuracy across 600+ locations
In a retail network of more than 600 locations, MapsExperts operates the complete Google Business Profile program — including protecting data accuracy across the network.
Boundaries
What monitoring can and cannot do
Monitoring makes differences visible and decided. It does not control the platforms.
- Google decides what it displays. Rejecting a Google update restores your value, but if Google’s sources keep disagreeing, the same difference can come back — a signal to re-check the real-world facts.
- Not every difference is an error. Some Google updates are correct and should flow back into your source of truth.
- Fields, frequency and platforms are agreed per engagement; not every platform exposes changes in the same way.
Related
Connected parts of location operations
Differences found in monitoring often lead to a verification case or a change to the network.
Questions
Monitoring FAQ
Why did Google change our business hours?
Google may update profile information when its sources — such as user reports or licensed data — indicate that the current information is wrong or outdated. Sometimes those sources are right, for example after a change that never reached your own system; sometimes they are not. Either way, the change should be reviewed, not discovered by a customer.
Should we reject every Google update?
No. Reject updates that contradict verified facts; accept those that reflect a real change your source missed — and update the source, so the difference does not return.
How often should location data be checked?
It depends on the field and the network. Hours and status change most often and matter most to customers; names and categories change rarely but matter for compliance and visibility. Frequencies are agreed per field.
Does monitoring cover Apple Maps, Bing and TomTom?
Google Business Profile comes first, because Google exposes its own updates directly. Apple Maps, Bing and TomTom are included where they are in scope; how each one is checked depends on the access and data that platform provides.
Is this the same as Location Intelligence?
No. Monitoring keeps the facts about each location correct. Location Intelligence analyses visibility, competitors, customer feedback and AI discovery. They use different signals and answer different questions.
Know the live state
Find out what your profiles show today.
Send us a sample of locations or the full list. We will compare what Google shows with your data and show you where — and why — the two differ.