How LocalBusiness schema works
LocalBusiness is a type in the shared schema.org vocabulary, the agreed set of names search engines use for things like a business, an event or a recipe. Marking a page up with it means adding a block of machine-readable data that states, in a fixed format, what the business is called, where it is, how to reach it and when it is open.
The usual way to add that block is JSON-LD, a small script in the page’s code that describes the business without changing anything a visitor sees. A typical block declares:
- The business name, website address and a photograph or logo
- A postal address broken into street, city, region, postcode and country
- A telephone number, plus map coordinates where the exact location matters
- Opening hours, stated day by day rather than as a sentence
- Links to the business’s own profiles elsewhere, which corroborate the rest
The vocabulary also holds narrower types beneath LocalBusiness, for restaurants, dental practices, legal practices and many other trades. Using the most specific type that genuinely fits says more than the general one does.
Why LocalBusiness schema matters
It removes guesswork. Without it, a search engine has to infer your address from text in a footer and your opening hours from a table it must interpret. With it, the same facts arrive already labelled, which makes them easier to trust and much harder to misread.
It also corroborates. Google compares what your website states against your Google Business Profile and your listings elsewhere, and markup that agrees with them strengthens the whole local picture. What it does not do is control the map listing or promise a rich result. Structured data describes; it does not instruct.
Common mistakes with LocalBusiness schema
Marking up something the page does not show is the most serious. Structured data is meant to describe visible content, so declaring opening hours or an address that appear nowhere on the page is a guidelines breach, and it can cost the site its rich results altogether.
Adding a rating is the trap most sites fall into. Ratings you collect and display on your own site, about your own business, are not eligible for a rich result, and inventing one is far worse than leaving it out. Leave aggregate ratings to the platforms that actually host the reviews.
The quieter faults are drift and duplication: markup left behind after a move or a change of number, one address block repeated on every page of a multi-location site, a plugin and the theme both writing a business block so the page carries two conflicting descriptions, and a type chosen because it sounded impressive rather than because it fits.
How to get it right
Write the business details once, put them in visible text on a contact or location page, then mirror exactly those details in the markup. Where the two disagree, the visible page is the one to correct first. Use the same name, address and phone number that appear on your listings, because matching details across the web is the whole point of the exercise.
Put one business block where it belongs — the homepage and the contact or location page — rather than on every page of the site, and give a multi-location business one block per location page. Validate with Google’s Rich Results Test and the schema.org validator, then check again after any theme or plugin update, because markup is broken by accident far more often than it is changed on purpose. Where the site also needs markup for services, articles or products, plan the whole set together as schema markup rather than bolting on one type at a time.
