What the markup does and does not do
Google's LocalBusiness documentation describes the markup (Schema MarkupStructured data vocabulary.) as a way to tell Google about a business's hours, departments, reviews and other details, which can be shown in features such as a business's knowledge panel. Its introduction to structured data explains that markup helps Google understand a page and can make it eligible for search features, and its general guidelines state that correct markup does not guarantee any feature will appear. The structured data guide covers JSON-LD, validation and monitoring in general; this tutorial applies them to one location page.
| The markup does | The markup does not |
|---|---|
| State the location's name, address, phone, hours and coordinates unambiguously | Replace the Business Profile, which is managed separately and drives the map pack |
| Help Google match the page to the business and its details | Guarantee a knowledge panel or any other feature |
| Express departments with their own hours and phone numbers | Make up for details missing from the visible page |
| Give each branch page its own description | Act as a general ranking boost |
The location pages guide and the citations and NAP guide both say that location pages should carry this markup, generated from the master record. This is the how. The local hub explains where the markup sits among the profile, the website, citations and reviews.
Before you start
- The JSON-LD basics. The prerequisite is the structured data guide: script blocks, types, properties, nesting and testing.
- The master record. One table that holds each location's canonical name, address, phone (NAPA business's name, address and phone number as they appear across the web.), website URL, hours and exceptions, coordinates and departments. The citations guide describes it; if it does not exist yet, build it first, because every step below reads from it.
- The Business Profile (GBPLocal listing on Google Search and Maps.) for each location, set up as the Business Profile tutorial describes, so its details can be checked against the record.
- The location page template and access to change it, or a developer who can.
- A testing route: Google's Rich Results Test, a schema validator and access to Search Console for the site.
The steps
Pick the most specific business type
Google's documentation asks for the most specific LocalBusiness subtype that fits, so a dental practice uses the dentist type rather than the generic LocalBusiness, and a restaurant uses the restaurant type. Browse the schema.org list of LocalBusiness subtypes for the closest match to what the business is, not to the services it would like to rank for. Record the chosen type in the master record so every page of that kind uses it.
Take the facts from the master record
List the fields the markup will use and map each to a column in the master record: name, street address, locality, region, postal code, country, phone, page URL, latitude, longitude, opening hours, special hours and departments. The same record already feeds the visible Location PageA web page dedicated to one physical location or service area, with its address, hours, services and local detail. and the profile. Google's general guidelines require markup to represent content visible on the page, so any field the page does not show should be added to the page or left out of the markup.
Write the core properties
The documentation lists the name and the address as required, with the address as a nested postal address broken into its parts. Add the telephone, the page's own URL and, where they apply, the price range and, for restaurants, the menu and the cuisine. Use the name exactly as the business trades, matching the profile, which Google's representation guidelines require to be the real-world name without added keywords. Give the node a stable identifier based on the page URL so other markup can refer to it.
Add opening hours and exceptions
Express regular hours as opening hours specifications, one per set of days with the same times. The documentation shows patterns for a day open around the clock, a day closed all day and hours that run past midnight; copy those patterns rather than inventing your own. For seasonal hours and holiday closures, add specifications with start and end dates of validity. Hours must match the profile and the page on every day, including the exceptions, because a page that says open while the profile says closed is the drift this markup exists to prevent.
Add coordinates and the page URL
Add a geo node with latitude and longitude taken from the map pin in the master record, at the precision the documentation asks for. Set the URL to the location page itself, not the homepage, so the markup, the page and the profile's website link all point to the same address. Where the business uses tracking parameters on the profile link, keep them out of the markup's URL.
Handle departments and branches
A department is a part of one location with its own hours or phone, such as a pharmacy in a store or a hygiene clinic in a dental practice. The documentation nests each department inside the main business, with its own type, name, phone and hours, and asks that the department name include the main business name unless the department is separately branded. Branches are different: each branch is its own location with its own page, and each page carries the markup for that branch only. Never list every branch on every page or copy one branch's markup to another; the location pages guide explains why a hundred pages ended up claiming the same phone number.
Generate the markup from data
Write the template once and fill it from the master record when the page is built, so that changing the record changes the page and the markup together. Prefer rendering the script in the HTML the server sends; markup injected later depends on the page's scripts running as expected, which is one more thing to test. Handle missing values by omitting the property, never by printing an empty string or a placeholder. Service-area businessesA business that serves customers at the customer's location, such as a plumber or cleaner, listing the areas it serves rather than a shopfront. that hide their address on the profile, as Google's representation guidelines require when customers are not served there, should not publish that address in markup; describe the areas served in the page text instead.
Test it and inspect what Google read
Run a sample of location pages through the Rich Results Test and a schema validator: one ordinary location, one with departments, one with special hours and any with unusual data. Fix errors, then decide on warnings: a missing recommended property is worth adding if the record holds it. After deployment, inspect a live URL in Search Console to see the page as Google fetched it, including the structured data detected. The SEO page checker is a quick first check that a live page carries structured data at all.
Re-check after any change to the record
Moves, new phone numbers, changed hours, new departments and closures all start in the master record. After each change, test the affected page again and compare the markup with the profile and the visible page. Add the markup to the template's tests so that a release that breaks it fails before it ships, and repeat the sample test after every template change.
A location page's markup (illustrative)
A two-site dental practice maps its master record to markup
Brambleknot Dental Practice, an invented practice, has two sites in the invented town of Exampleton. The Riverside site opens late on Thursdays and has a hygiene clinic with its own phone line and hours; the Station Road site closes at lunchtime on Saturdays. The master record holds one row per site and one per department. The markup below is generated for the Riverside page only; the Station Road page gets its own block from its own row, with its own identifier, phone and hours. The holiday closure comes from the record's exceptions table and drops out of the markup automatically once the end date passes. The phone numbers use a range reserved for fiction.
{
"@context": "https://schema.org",
"@type": "Dentist",
"@id": "https://brambleknot.example/locations/riverside#practice",
"name": "Brambleknot Dental Practice",
"url": "https://brambleknot.example/locations/riverside",
"telephone": "+44 20 7946 0123",
"address": {
"@type": "PostalAddress",
"streetAddress": "4 Riverside Walk",
"addressLocality": "Exampleton",
"postalCode": "ZZ1 1ZZ",
"addressCountry": "GB"
},
"geo": { "@type": "GeoCoordinates", "latitude": 49.51234, "longitude": -4.51234 },
"openingHoursSpecification": [
{ "@type": "OpeningHoursSpecification", "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Friday"], "opens": "08:30", "closes": "17:30" },
{ "@type": "OpeningHoursSpecification", "dayOfWeek": "Thursday", "opens": "08:30", "closes": "20:00" },
{ "@type": "OpeningHoursSpecification", "opens": "00:00", "closes": "00:00", "validFrom": "2026-12-25", "validThrough": "2026-12-26" }
],
"department": {
"@type": "Dentist",
"name": "Brambleknot Dental Practice Hygiene Clinic",
"telephone": "+44 20 7946 0124",
"openingHoursSpecification": [
{ "@type": "OpeningHoursSpecification", "dayOfWeek": ["Tuesday", "Thursday"], "opens": "09:00", "closes": "19:00" }
]
}
}
Each value traces to a column: the type to the practice's category, the name to the trading name on the signage and the profile, the coordinates to the map pin, and the hours to the same rows that print the opening times on the page.
Common mistakes
- The generic type when a specific one exists. The documentation asks for the most specific subtype.
- Hand-written markup copied between branches. Wrong phone numbers and hours on every page but the first.
- Values the page does not show. Hours or phone numbers in the markup but not in the visible text.
- Keywords in the name. The markup name should match the real-world name the profile uses.
- Every branch on every page. Each location page describes its own location.
- Forgetting the exceptions. Regular hours in the markup while the page announces a holiday closure.
- Publishing a hidden address. A service-area business's private address in markup on a public page.
- Testing once. Template changes break markup quietly; test a sample after every release and every change to the record.
