TL;DR: No, you don’t need to. Google allows LocalBusiness schema on any page, but repeating it everywhere is unlikely to give Google anything new, and Google doesn’t present it as a way to rank higher. Describe each real business location once, on the page about that location: usually your homepage or contact page, or a dedicated page for each branch. Everywhere else, use markup that describes that page’s own content, and let it point back to the business rather than repeating it.
LocalBusiness schema is structured data (code in your page that search engines read but visitors don’t see) describing a physical business: its name, address, phone number, opening hours and so on. Because it describes the whole business, it’s tempting to add it to every page. For most sites, that creates more maintenance and more room for mistakes without giving anything back.
If you’re new to schema in general, our guide to what schema is in SEO covers the basics first.
Can You Put LocalBusiness Schema on Every Page?
You can. Google’s local business structured data guidance says you can add it to any page on your site, though it may make more sense to put it on a page that contains information about your business. So a sitewide block isn’t against Google’s guidelines, provided the details in it are accurate and match what’s on your site.
For most sites, copying the same business details across blog posts, privacy policies and careers pages is unnecessary. Repeated blocks also give you more places to update when your phone number or opening hours change.
For most businesses, we recommend treating it the way Google treats organisation details: Google’s organization structured data guidance recommends putting them on your homepage or a single page about the organisation, and says you don’t need them on every page. LocalBusiness is a more specific kind of organisation, so the same logic fits.
There’s one version of “sitewide” that’s fine. Some SEO plugins define the business once and then have each page’s own markup refer back to it, for example naming the business as the publisher of a blog post. That’s different from pasting a separate LocalBusiness block onto every page, and if your plugin does this, you don’t need to undo it.
What LocalBusiness Schema Does, and What It Doesn’t
Google uses structured data to understand what a page is about, and it can make a page eligible for richer search results. For a local business, Google says the markup lets you tell it about things like opening hours and different departments, and that people searching for a business may see a knowledge panel with its details.
There’s no sign it’s a ranking lever. Google presents structured data as a way to understand pages and qualify for rich results, not as a ranking boost, and even correct markup doesn’t guarantee a rich result will appear. We cover this in more depth in Is Structured Data a Google Ranking Factor?
If what you’re really after is visibility in Google Maps and the local pack, that’s mainly your Google Business Profile’s job. Google’s own guidance on local ranking is built around your Business Profile: how well it matches the search, how far the business is from the searcher, and how well known the business is. Adding LocalBusiness markup to more pages of your website doesn’t change any of those. Our local SEO guide covers how Google ranks local businesses in more depth.
Businesses will often end up with LocalBusiness schema on every page of the site, assuming that it will help their local rankings if it’s there. In reality, this schema isn’t a ranking factor, and map rankings will normally come from the Google Business Profile, so it doesn’t have much impact. You can also give the LocalBusiness schema an ID within the JSON, which will allow you to refer to it in other schema if needed, rather than repeating it across every page.
Jamie Stowe, Senior SEO Account Manager
Where LocalBusiness Schema Should Go
The rule of thumb is one LocalBusiness entity for each real business location, placed on the page that describes that location.
If you have one location, your homepage is usually the natural home for it, since it tends to carry your name, address, phone number and what you do. Your contact page is the other obvious candidate. You don’t need a full copy on both: pick one as the main definition and have the other refer to it.
If you have several locations, Google recommends defining each location as its own LocalBusiness. In practice that means a dedicated page for each branch, with that branch’s own address, phone number, opening hours and page URL in its markup. You can link each branch to the wider brand using the schema.org property parentOrganization. Older guides often suggest branchOf instead, but schema.org has replaced it with parentOrganization.
Whichever applies, a few things hold for every LocalBusiness entity:
- Use the most specific type that fits. Google recommends the most specific LocalBusiness subtype available: a dental practice would use Dentist, a restaurant Restaurant, and so on. The full list is on schema.org’s LocalBusiness page.
- Include the business name and address. Google requires both for the markup to be eligible for its local business features, and recommends extras such as telephone, opening hours and URL.
- Give each entity a stable ID. A common approach is to give the business a fixed identifier, known as an @id, such as your homepage URL followed by #localbusiness. Other markup on the site can then refer to that ID instead of repeating the business details.
Here’s how that plays out across a typical site:
| Page | Its own LocalBusiness block? | What to do instead |
|---|---|---|
| Homepage (one location) | Usually yes | Define the business here, with the most specific subtype and a stable @id |
| Contact page | Optional | Either hold the main definition or refer to the one on your homepage, not both |
| Branch or location page | Yes, one per real location | That branch’s own details, linked to the wider brand with parentOrganization |
| Area page where you have no branch | No | Describe the service you offer in that area |
| Service, product and blog pages | No | Use markup for the page’s own content, naming the business as provider or publisher if needed |
| Policies, terms, careers | No | Nothing extra needed |
For the practical side of adding markup, including building it into location page templates, see our guide on how to add schema to your website.
Common LocalBusiness Schema Mistakes
- Several different versions of the same business. One possible cause is a theme and an SEO plugin both outputting LocalBusiness markup, or a block pasted into the site footer years ago that nobody remembers. You end up with the same business described two or three ways, sometimes with different names, phone numbers or IDs.
- Turning area pages into fake branches. A Sheffield plumber with pages for Rotherham, Barnsley and Chesterfield doesn’t have three extra businesses. Schema.org defines LocalBusiness as a particular physical business or branch, so marking each area page up as its own location describes branches that don’t exist. A quick test: if there’s no address someone could visit and no phone line for that location, it isn’t a branch.
- Markup that doesn’t match the page. Google’s structured data guidelines say markup must be a true representation of the page and shouldn’t describe content visitors can’t see. An address, phone number or set of opening hours that only exists in the code is a problem, and so is one that’s out of date.
- Adding review stars to your own business. Google’s review snippet guidelines say that if a business controls the reviews about itself, whether in its own markup or through an embedded third-party review widget, its pages using LocalBusiness or Organization markup aren’t eligible for review stars. Adding a star rating to a sitewide LocalBusiness block won’t earn you stars in search results.
We wouldn’t expect any of these to hurt your normal rankings on their own. Where Google does take manual action over structured data, the page loses eligibility for rich results rather than rankings. They do make your business details harder to trust and harder to keep accurate.
When working with local businesses, we often find that LocalBusiness schema is either incorrect or missing entirely. One client I worked with had an incorrect location listed in their schema for the website, which was inserted to the website using RankMath plugin. To resolve this, we simply had to update the business location in the plugin to the right address, which updated the LocalBusiness schema.
Andy Blanchard, SEO Account Manager
Top Tip: Before you add anything, run three pages through the Schema Markup Validator: your homepage, a blog post and a service page. Count how many LocalBusiness entities each one shows, and compare the name, phone number and @id between them. If you see two on one page, or different details on different pages, you’ve got duplicate markup, and the fix is at the source, usually by switching off one of the theme or plugin settings producing it, not by editing pages one at a time. Use the validator for this check rather than the Rich Results Test: the validator reads general schema.org markup, while the Rich Results Test is built around Google’s own search features. Our guide to testing structured data covers both.
LocalBusiness Schema FAQs
What if my business doesn’t have a public address?
Google requires an address for LocalBusiness markup to be eligible for its local business features, and its guidelines say markup shouldn’t describe things visitors can’t see on the page. So if you work from home or visit customers and don’t show an address on your site, we’d recommend describing the business with Organization markup on your homepage instead, and letting your area pages describe your services.
Do I need Organization schema as well as LocalBusiness?
Usually not for a local business. Google’s organisation guidance recommends that a local business, such as a restaurant or shop, uses the most specific LocalBusiness subtype for its details. A group with several branches can describe the brand as an Organization and each branch as a LocalBusiness, linked with parentOrganization.
How Wildcat Handles This
When we look at a local business’s website, we start with the technical SEO audit at the start of a campaign, which sets the priorities for the first few months. We can also check whether duplicated or conflicting LocalBusiness markup is an issue on your site.
We add structured data for local businesses as part of our technical SEO work, and we treat it as one piece of local SEO alongside your Google Business Profile, location pages and local citations in the directories that list you. From you, we’d need the real details for each location you trade from, plus access to your website or whoever manages it, so the markup matches what customers see. The aim is markup that describes each location once, accurately, with details that line up with your Business Profile and listings rather than contradicting them.
If you’re not sure what your site’s markup says about your business, or you’re planning location pages and want them set up properly, take a look at our local SEO services or book a free consultation with the team.
Lucy Young
SEO Senior Account Executive
