Pillar · Presence and discovery
If the listing is wrong, the Location does not exist.
Mapboard keeps one version of every Location, publishes it to Google and Meta, checks that it actually went live, and watches every day that it stays right.
Downtown Brooklyn
- Address
- 240 Livingston St, Brooklyn, NY
- Hours
- Open 24 hours
- Services
- Clinic · Vaccinations · Delivery
- Category
- Pharmacy
Publishing status
- GooglePublished 2 h ago
- MetaPublished 2 h ago
- WazeIn the network export
Verified by reading the platform back after publishing, not assumed.
01 · The problem
The listing decays even if nobody touches it
The customer decides on the map, before walking in. And as the network grows, the information for each Location fragments: an agency edits one thing, the local team another, and corporate holds a spreadsheet that no longer matches either.
What almost nobody accounts for is that the listing changes on its own. Google accepts suggestions from users, franchisees and in-store services create pins of their own, and a listing gets suspended without warning. Your team did not cause that decay, so your team does not catch it either.
02 · How it works
From your record to the map, and back
Five steps. The last two are the ones almost nobody does, and they are the ones holding up the other three.
- 01
It gets declared
One version of every Location: address, hours, services, attributes and photos. More than 300 fields that stop living in a spreadsheet last edited eight months ago.
With custom fields for your operation, Location templates so an opening is born complete, and bulk upload by spreadsheet with a preview of the changes before they apply.
- 02
It gets published
The change goes out to Google and Meta from one place, with publishing status per Location and per platform. The full network exports for Waze.
An hours change can go out to the whole network, to one area or to a group. We never say it appears instantly: each platform defines that timing, and what Mapboard shows you is what was sent and what was confirmed.
- 03
It gets verified
After publishing, Mapboard reads the platform back and compares. A change is not done until it is verified.
You are left with a Location-by-platform matrix showing the state of every field, and the history of what was published and when. That turns differences into work, instead of into a suspicion.
- 04
It gets watched
A daily health check on every listing, every day: duplicated, unverified, suspended, closed or gone.
When someone outside edits your listing, Mapboard compares field by field against what you declared and tells you exactly what changed. And it compares the full inventory of your Google account against your network to flag Locations that appeared or disappeared without anyone registering them.
- 05
It gets found
Your public store directory, on your own domain, with one indexable page per Location.
With search, directions, sorting by distance, structured data and its own sitemap. It is fed by the same source you publish to Google, so there is no second truth to maintain.
Your listing changes even when you do not touch it.
Google accepts suggestions from anyone, duplicates appear on their own, and a suspension gives no warning. That is why the check is daily and automatic, and each finding closes only when the platform confirms it was corrected.
- 3DuplicatedSame address, two pins
- 11UnverifiedCannot receive changes
- 1SuspendedGoogle blocked it
- 4Edited by a third partyPhone and hours
Each finding closes only when the platform confirms the correction.
03 · The difference
What a listings manager does not tell you.
Publishing is not the same as having published
Most tools tell you they sent the change. Mapboard reads the platform back and confirms it landed. And when a platform is slow, it says so instead of promising real time, because a promise of instant updates that does not hold is the fastest way to lose the trust of the team using it.
Clean identity is the prerequisite for everything else
To say anything about Location 47, you first have to know which listing is Location 47. Duplicates and spelling variants of the name are what break that identity, which is why they are the first thing to resolve. Without it, reputation and cases hang off the wrong pin.
The same source feeds the map and your site
Your public store directory is served from the same data that was published to Google, not from a separate database somebody has to keep updated. You fix it once and it is fixed on both sides, with the record of what was published and when.
Downtown Brooklyn
240 Livingston St, Brooklyn, NY
Open 24 hours · Walk-in clinic
Your domain · one page per Location
With structured data and its own sitemap, fed by the same source you publish to Google.
04 · Made to fit
It adapts to how your network is organized
A chain with different formats and franchisees is not governed with a flat list of stores.
Nested groups
Region, area and format as a real tree, so you operate on the group and not on the list.
Custom fields
The attributes your industry needs and Google does not cover, included in the spreadsheet upload.
Location templates
Save a model listing and apply it to openings so they are born complete.
Permissions by level
Which fields corporate touches, which the area touches and which the franchisee touches, with no silent overwrites.
Directory scope
Which Locations show on your public site, by group or by saved filter.
Directory branding
Logo, color and link back to your site, and for multi-brand networks, a section per brand.
Google Business Profile and Meta receive changes directly from Mapboard. For Waze it generates the full-network export in the format their panel expects. Apple Maps and Bing do not receive publishing today, and we would rather say so than leave it to the interpretation of a logo on a page.
Mapboard finds out and compares field by field against the version you declared: name, phone, website, address and description. It shows you exactly what changed, so you decide whether to accept the platform's data or publish yours again.
The daily listing health check flags them along with suspended ones, unverified ones and ones showing as closed. Your team runs the consolidation, reviewing each merge before applying it, because a wrong merge takes reviews and photos with it and those do not come back.
It is sent the moment you approve it. How long each platform takes to reflect it is defined by the platform, not by us, which is why we do not promise it as instant. What we do is read back and confirm once it has landed, with the date it was published.
Yes. It is served under your own subdomain, with an indexable page per Location and its own canonical and sitemap, so search authority accrues to your domain and not to ours. We set the domain up with you; it is not self-service.
Yes, by spreadsheet, in both directions. You export the network, edit, and when you upload it back Mapboard shows you the detail of what is going to change before anything is applied. Hours and custom fields travel in the same file.
Let's look at how you govern a real network.
You tell us how yours is organized today and we show you, on a demonstration network, what the actual work looks like: what gets published, what gets verified after publishing, and what the daily check turns up.
