Implementing schema markup, a form of structured data, can help search engines understand the content and entities on your website. It can also make eligible pages available for certain rich-result features.
If you own a local business and have researched how to improve your local search visibility, you have probably come across LocalBusiness schema. However, adding schema to a website is not simply a case of placing the same code on every page.
So, should you add LocalBusiness schema on every page?
No. You do not normally need to add LocalBusiness schema to every page of your website. It’s generally most relevant on your homepage, contact page, and dedicated location pages. Other pages should use schema that reflects their main content, such as Article, Service, Product, or FAQPage schema.
Adding the same LocalBusiness markup to every page is unlikely to provide an extra SEO benefit. It can also make your structured data harder to manage and create confusion if different pages contain conflicting business information. A separate LocalBusiness block on every page is unnecessary, but some plugins create a connected sitewide schema graph in which other page types reference the same LocalBusiness entity using a consistent @id.
In this guide, we explain when LocalBusiness schema is appropriate, where it should be placed, and how to use it without confusing search engines or website users.
What is LocalBusiness Schema?
LocalBusiness schema is a type of structured data that helps search engines understand information about a physical business or a particular branch of an organisation.
This information may include:
- The business name
- The type of business
- The address
- The telephone number
- Opening hours
- Geographic coordinates
- The website URL
- Images
- Departments
- Accepted payment methods
LocalBusiness is a subtype of both Organisation and Place schema. There are also more specific LocalBusiness subtypes, including FoodEstablishment, ProfessionalService, and RealEstateAgent.
Where possible, you should choose the most specific, accurate subtype for the business. For example, a restaurant should normally use FoodEstablishment schema rather than the more general LocalBusiness type. Google also recommends defining each individual business location as a LocalBusiness and using the most specific available subtype.
For a broader introduction, read our guide explaining what schema is in SEO.
When Should I Use LocalBusiness Schema?
LocalBusiness schema is most appropriate when a page describes a genuine physical business, office, shop, clinic, restaurant, or individual branch.
It may be suitable for:
- A single-location business homepage
- A contact page containing the business address and contact details
- A dedicated location page
- A branch page for a multi-location organisation
- An About page that provides clear information about the business and its location
Schema.org describes LocalBusiness as a particular physical business or a branch of an organisation. This means it should represent a real business location rather than being added simply because a page targets a particular town or city.
For example, a Sheffield dental practice with one clinic could use Dentist schema on its homepage and contact page. A dental group with clinics in Sheffield, Leeds, and Manchester should ideally have a separate location page and LocalBusiness entity for each clinic.
LocalBusiness schema may be less appropriate for a business with no clear physical location or for a national company where the page does not describe a specific branch. In these cases, Organisation or another more suitable subtype may provide a clearer description.
Never create false locations or mark a service-area landing page as a physical branch when the business does not actually operate from that address.s.
Should You Add LocalBusiness Schema on Every Page?
You do not need to add LocalBusiness schema to every page of your website.
Google recommends placing organisation information on the homepage or another page that describes the organisation, such as an About page. Its guidance specifically states that you do not need to include organisation markup on every page. This same page-level principle should be applied to LocalBusiness schema. Your structured data should reflect what the page is mainly about.
For example:
| Page type | Most relevant schema |
| Homepage for a local business | LocalBusiness or a specific subtype |
| Contact page | ContactPage and LocalBusiness |
| Individual branch page | LocalBusiness or a specific subtype |
| Service page | Service |
| Product page | Product |
| Blog post | Article or BlogPosting |
| FAQ page | FAQPage, where appropriate |
| Event page | Event |
| About page | AboutPage and Organisation or LocalBusiness |
| General content page | WebPage |
A page can contain more than one schema type where each one accurately describes visible content. For example, a contact page could include ContactPage schema alongside a linked LocalBusiness entity.
The important point is that the primary schema should describe the main purpose of the page.
Google’s guidelines say that structured data should be a true representation of page content and should be placed on the page it describes. Structured data that is irrelevant, misleading, or unrelated to the main content may not be eligible for rich results.
Required Properties
Google requires the following properties. If these properties are missing, your schema will return an error when validating and your page won’t be eligible for related rich results.
Where Should You Put LocalBusiness Schema?
For most local businesses, LocalBusiness schema should be considered for the following pages.
Homepage
The homepage is usually the main place to define the business entity, as it often contains the business name, services, location, contact details, and links to important pages. This makes it a logical location for LocalBusiness schema.
Your homepage schema should include accurate information and use a consistent @id, such as:
https://www.example.co.uk/#localbusiness
This identifier can then be referenced from other schema across the website.
Contact Page
The contact page is another suitable place for LocalBusiness schema because it usually contains:
- The business address
- Telephone numbers
- Email addresses
- Opening hours
- Maps
- Directions
- Contact forms
You can use ContactPage schema to describe the page itself and connect it to the LocalBusiness entity.
The information in the schema should match the information users can see on the page. Do not hide a different address, telephone number, or set of opening hours in the structured data.
Location Pages
Each genuine business location should ideally have its own dedicated page and its own LocalBusiness entity.
For example:
- /locations/sheffield/
- /locations/leeds/
- /locations/manchester/
Each location page should contain information specific to that branch, including its address, telephone number, opening hours, services, and directions.
Google recommends defining each business location as a LocalBusiness type.
You can connect each location to the wider organisation using properties such as:
Each location should also have its own stable @id. This helps search engines understand that the pages describe different branches of the same wider organisation.
About Page
LocalBusiness or Organisation schema may also be relevant on an About page when the page provides clear information about the business. However, you do not need to copy a large standalone block of LocalBusiness markup onto the page if the business has already been clearly defined elsewhere.
You could instead use AboutPage schema and connect the page to the existing business entity using the same @id.
Examples of LocalBusiness Schema Misuse
Incorrect schema doesn’t always cause an immediate penalty, but it can reduce clarity and make structured data harder to trust, test, and maintain. Below are some of the most common LocalBusiness schema misuses we come across when auditing websites.
Copying the Same Schema Across Every Page
A common mistake is adding a separate LocalBusiness entity to every page, particularly when the markup uses inconsistent information or different @id values. This is unnecessary and can make the structured data harder to manage and interpret.
A consistent LocalBusiness entity may still appear within a connected sitewide schema graph, where relevant page types reference the business as their publisher or provider. The important point is to define the business clearly and ensure the main schema on each page reflects its content.
Adding a LocalBusiness entity to every page may result in the markup appearing on:
- Every blog post
- Every product page
- Every service page
- Privacy policies
- Terms and conditions
- Recruitment pages
The business may be connected to these pages, but it is not necessarily the main subject of each one. For example, a blog should normally use Article or BlogPosting schema, a product page should use Product schema, and a service page should use Service schema.
These page entities can still reference the business as the publisher, provider, or organisation behind the content, but using the same LocalBusiness schema across every page when it is not needed or relevant reduces clarity and makes it harder to maintain a consistent representation of the business.
Creating Fake Locations
Another misuse is adding LocalBusiness schema to every service-area page, even when the business does not have a genuine branch in those areas.
For example, a plumber based in Sheffield may have pages targeting Rotherham, Barnsley, and Chesterfield. But those pages don’t automatically represent three additional LocalBusiness entities. Marking each page as a separate physical location could suggest that the company has branches that do not exist.
Service-area pages should focus on the service being offered in that area.
Using Conflicting Business Information
Confusion can also be caused by inconsistent information across the website.
Examples include:
- Different telephone numbers in the schema and page content
- Old opening hours remaining in the markup
- An incorrect postcode
- Different versions of the business name
- Multiple LocalBusiness items with different @id values for the same location
- Location pages referencing the wrong branch
Structured data should be reviewed whenever the business changes its address, telephone number, opening hours, or branding to ensure this information remains correct.
Marking Up Information That Users Cannot See
You should not add business details, reviews, services, or claims to your schema if users cannot find that information on the page.
Google states that structured data should represent visible page content and should not contain irrelevant or misleading information. Adding information that isn’t represented on the page may breach Google’s structured data guidelines and affect eligibility for rich results, as the machine data and human data will not match up.
LocalBusiness Schema and Entity Clarity
An entity is a recognisable person, place, organisation, service, product, or topic.
For a local business, the main business entity may be connected to:
- Its physical location
- Its services
- Its team members
- Its website
- Its Google Business Profile
- Its social media accounts
- Its parent organisation
- Its individual branches
Structured data helps search engines understand these relationships. For example, Service schema can identify the LocalBusiness as the provider, while article schema can identify the business as the publisher, and location pages can identify the main organisation as their parent organisation.
Using the same stable @id whenever you refer to the business can help prevent search engines from interpreting each mention as a different company.
This does not guarantee improved rankings or inclusion in AI-generated answers. However, it gives search engines and other systems clearer, more consistent information about the business and its relationships.
Why Entity SEO Helps Users and Businesses
Maintaining consistent business information across visible content, listings, and structured data can also create a better experience for potential customers.
Clear and consistent business information can help users quickly find:
- The correct branch
- Accurate opening hours
- The right telephone number
- Directions to the location
- Relevant services
- Booking or enquiry options
For the business, clearer entity information can reduce the risk of customers calling the wrong branch, visiting at the wrong time, or seeing outdated information.
Schema itself is not a direct ranking factor. However, it can support search engines in understanding your content and may improve how pages are presented in search results.
Read more in our guide: Is Structured Data a Google Ranking Factor?
Get Expert Support With LocalBusiness Schema
LocalBusiness schema can help search engines understand your business, locations, and services, but only when it has been implemented clearly and accurately.
Adding it to every page is not necessary. A better approach is to define the business on the most relevant pages, use page-specific structured data elsewhere and connect the entities consistently across the website.
At Wildcat Digital, our technical SEO team can review your existing structured data, resolve conflicting markup, and implement schema that reflects the purpose of each page.
Get in touch to arrange a free consultation and learn how we can support your local SEO and wider organic search strategy.
