The location data problem
Every location has a set of facts: its name, address, phone number, opening hours, holiday hours, services, accessibility details, parking, manager, photos and the URL of its page. Each fact is used in several places. The website's location pageA web page dedicated to one physical location or service area, with its address, hours, services and local detail. and store finder use it. The business profile (GBPLocal listing on Google Search and Maps.) uses it. Directories, maps, satnav providers, aggregators, delivery apps and booking platforms use it. Paid campaigns use it in location assets. Internal systems such as rotas and point-of-sale use parts of it.
In a small business, a change to the hours is made in a few places by one person. In a chain, the change is made by whoever notices, in whichever system they can reach, and the rest are left behind. Customers then find the old hours on one source and the new ones on another, turn up to a locked door, and leave a review. Search engines, which compare sources, see inconsistent information and have less reason to trust any of it. The citations and NAP consistency guide covers the audit for a single business; at scale, the same consistency has to be engineered rather than checked by hand.
The scale problem also shows up in events that single sites rarely face: openings, closures, relocations, rebrands, temporary closures for refurbishment, seasonal hours across hundreds of sites at once. Each is a data change that must reach every copy, and each goes wrong if nobody owns the route. For a store network these listings are often where a shopping trip is decided, which is why the retail industry marketing guide treats them as the core of store-led marketing.
A single source of truth
The answer is one master record of every location, kept outside the website and the platforms, with a named owner for each field and a known list of systems that read it. It can be a dedicated location data platform, a table in an existing operations system, or, for a smaller chain, a well-governed spreadsheet. What matters is that it is the only place where changes are made, and everything else is a copy.
| Field | Owner | Used by |
|---|---|---|
| Location name | Brand or central marketing, against a naming rule | Website, profiles, directories, ads, structured data |
| Address and map pin | Property or operations | Website, profiles, directories, maps, delivery and booking platforms |
| Main phone number | Operations, with tracking numbers managed by marketing | Website, profiles, directories, call assets |
| Regular opening hours | Operations or the site manager, approved centrally | Website, profiles, directories, structured data |
| Holiday and temporary hours | Site manager, with a central calendar for national holidays | Profiles, website, directories |
| Services and attributes | Central product or service team, with local additions approved | Profiles, location pages, structured data |
| Photos | Site manager supplies, central team approves | Profiles, location pages |
| Location page URL | Central web team | Profiles, directories, ads, internal links |
| Status: open, temporarily closed, closed, opening soon | Operations | Every system above |
Write the naming rule down. "Brand name, then location" or "Brand name only, with the area in the address" both work; mixing them across sites does not, and the help centre's guidelines on business names constrain what can go into the name field on a profile. Decide which phone number is canonical for each site and whether tracking numbersAttributing phone calls to the marketing source that produced them, usually by showing different tracking numbers per source or visitor. are used anywhere, since tracking numbers on profiles need the care the help centre describes.
Location page templates that stay useful
A location page has two jobs. For the person, it answers practical questions: where is it, when is it open, how do I get there, what can I do there, who will I see, can I book. For search engine optimisation (SEOImproving visibility in unpaid search results.), it gives a clear, crawlable page to associate with the profile and with local queries. Google's SEO Starter Guide asks for content that is helpful and distinct; a template that changes only the town name produces pages that are neither. For templated pages built from other datasets, such as roles, products or integrations, the programmatic SEO guide sets out the test each page must pass.
Build the template in two layers. The structured layer comes straight from the master record and is the same shape on every page: name, address, map, phone, hours, services, accessibility, parking, booking link. The local layer is written or curated for each site: an introduction to the location and the area it serves, the team, directions from local landmarks and transport, services or departments specific to that site, local events and community activity, reviews from that site's customers, and photos of the actual premises. The local layer is the expensive part, which is why it should be prioritised by site value and grown over time rather than skipped.
Link the pages properly. A location finder or index page should link to every location page with plain, crawlable links, not only through a search box. Regional pages can group locations where people search by region. Each location page should link to nearby locations and to the services it offers. Set a self-referencing canonical tag (Canonical TagTells search engines the preferred URL.) on each location page so that tracking parameters do not create duplicates, and never canonicalise location pages to one another: they are different pages about different places. For brands running sites across countries or languages, Google's guidance on managing multi-regional sites covers the URL structure and language annotations.
Bulk listing management and verification
Managing many profiles one by one does not survive contact with a large estate. The Google Business Profile help centre documents several tools for businesses with many locations. Profiles can be organised into groups with shared access, so that the central team owns every profile and local managers get limited rights to their own. Chains above the threshold the help centre sets can apply for bulk verification rather than verifying each site separately. Spreadsheet uploads allow many profiles to be created or edited in one pass, and an API allows a location database to update profiles directly.
Use those routes to enforce the master record. The central account should own every profile, with local staff added as managers rather than owners, so that a departing manager does not take a profile with them. Search for duplicate or rogue profiles created by staff, customers or former owners, and merge or remove them through the help centre's routes. Decide which fields local managers may change directly, such as replying to reviews and posting updates, and which must go through the master record, such as hours and addresses. The profile optimisation tutorial covers what a good individual profile contains; this section covers keeping hundreds of them that way. When a new branch opens, the Google Business Profile setup checklist is run once for that location, including the link to its own location page.
Beyond Google, listing management platforms push the master record to other directories, maps and apps, and report where copies differ. They are useful at scale, but they are a delivery mechanism, not a source of truth; keep the master record yours, so that switching platforms does not mean rebuilding the data.
Structured data for locations
Structured data (Schema MarkupStructured data vocabulary.) describes each location in a form search engines can read reliably. The usual approach is local business markup on each location page, generated from the master record, with the name, address, phone, geographic coordinates, opening hours, URL and, where relevant, a link to the parent organisation. The structured data guide covers markup types, syntax and testing in general; at scale, three rules matter most.
Generate, do not hand-write. Markup produced from the same record as the visible page cannot contradict it. Hand-written markup copied from one location to the next is how a hundred pages end up claiming the same phone number. Match the page: markup should describe what the page shows, and every value in it should be visible to a reader somewhere on the page. Test at the template level: validate a sample of pages after any template change, including sites with unusual data such as split hours, temporary closures or no phone number, because those are where generated markup breaks. The LocalBusiness structured data tutorial works through the type, properties, opening hours, departments and testing for a single location page.
Audits and change control
Data drifts even with a master record, because platforms accept edits from the public, aggregators overwrite each other, and staff make changes in the wrong place. A standing audit catches it. Compare each location's details across the master record, the website, the profile and the main directories on a schedule, flag differences, and route each one to the field's owner. The checker below shows the kind of comparison involved for a single location; at scale the same check runs from the master record across every site.
NAP consistency checker
Change controlThe routine a proposed change to a live system follows: written down first, reviewed, tested, signed off and recorded before it reaches customers or data. matters most for events. Write a short procedure for openings, closures, relocations, temporary closures and holiday hours, each with an owner, a list of systems to update in order, and a check some days later that every copy reflects the change; the opening hours change SOP writes that procedure out for holiday, special and changed hours. Link operations to marketing so that marketing hears about a closure before customers do. Keep a change log against the master record: who changed what and when. When a customer complains that the website said one thing and the shop another, the log shows where the process failed.
An optician chain cleans up after a rebrand
Clearview Opticians rebranded its 120 practices and changed every practice's phone number to a new central system in the same month. Six weeks later an audit found 47 profiles still showing the old brand name, 63 directory listings with old numbers, and 18 location pages whose markup carried the head office number. Calls routed to disconnected numbers were running at an estimated 400 a week. The central team built a master location table, pushed it to profiles by spreadsheet upload and to directories through a listing platform, regenerated markup from the table, and set a monthly audit. Within a month, mismatches fell to 9, all on minor directories.
Accurate per-location data also makes campaigns measurable, and the measurement plan for store visits shows how store identifiers and profile actions feed a footfall readout.
Common mistakes
- No master record. If hours are edited in the profile, the website and the booking system separately, they will disagree.
- Template pages with only the town changed. They help neither people nor search engines; add a local layer, starting with the most valuable sites.
- Local staff owning profiles. When they leave, access leaves with them; the central account should own every profile.
- Hand-written markup. Copied markup is the fastest route to a hundred pages with the wrong phone number.
- Canonicalising location pages to a single page. Each location is a different page; give each a self-referencing canonical.
- Store finders without crawlable links. A search box alone hides location pages from crawlers.
- Deleting profiles for closed sites. Mark them closed through the documented route and redirect or update the page.
- Treating a listing platform as the source of truth. Keep the master data yours; the platform is a pipe.
- No change procedure for closures and holiday hours. The busiest days are when wrong hours do the most damage.
The centralised versus local control comparison covers who decides what across the estate, and the multi-location hub covers reporting by location.
