Which schema type should you put on your website?
Use LocalBusiness schema when the page represents a real local office, shop, clinic or branch, and use Organization schema when the page represents the wider company or brand. Some sites need both, but the right choice starts with the real business details shown on the page.
That matters because schema is a label for search systems. If the label does not match the page, the code creates confusion instead of clarity.
You do not need to write the code yourself. Your job is to know which facts are true: the business name, address where relevant, phone number, opening hours, service model and page purpose. We can then make the technical choice fit those facts.
A good decision starts with the page in front of you. A homepage for a single site business, an About page for a wider brand and a branch page for one location do different jobs, so their schema should reflect that.
Technical SEO consultants investigating website issues and search performance
What Is In This Article
- Which schema type should you put on your website?
- Schema should match the visible business
- LocalBusiness and Organization do different jobs
- Your business setup decides the right type
- Page choice controls where schema belongs
- The details must match before markup goes live
- Search and AI answers need clear entities
- Questions we get asked about business schema
Schema should match the visible business
A common mistake is adding Organization schema across a whole site because it sounds broad and safe. The homepage might clearly show a real local business with an address, phone number and opening hours, yet the schema labels it only as a general company.
Use schema to describe the real business shown on the page, not the version you wish Google would infer. Structured data is there to give search engines clear clues about the meaning of page content. It works best when those clues match what a person can already read on the page.
At First Place SEO, we start with the page and the business facts before choosing the business schema type. For a normal business owner, the useful check is simple: can you point to the same details on the page that the schema is going to describe?
Hidden details are a warning sign. If the page does not show a service model, address, phone number or opening time, the schema should not quietly add that detail behind the scenes. Strong schema markup for Google follows the page, then gives search systems a cleaner way to read it.
LocalBusiness and Organization do different jobs
LocalBusiness and Organization answer different questions about your business. One describes a real local place or branch, and the other describes the wider company or brand identity.
The table below compares LocalBusiness schema with Organization schema.
| Schema type | What it describes | Typical page |
|---|---|---|
| LocalBusiness | A real local business location or branch shown on the page | Homepage for a single location, or a specific location page |
| Organization | The overall company, brand or organisation | Homepage or About page |
LocalBusiness identifies a real business location, not the whole company in every context. Google’s guidance also treats LocalBusiness as a subtype of Organization, which means the choice is not a crude split between two unrelated labels.
In practice, the best schema type for a business is the most specific accurate type that fits the page. A real branch page should use the most specific LocalBusiness subtype that matches the business. A page about the company as a whole may suit Organization, especially where it carries broader details such as logo, brand name and company identity.
Avoid duplicate blocks that say different things about the same entity. Search systems handle clean structure better than a page full of overlapping labels.
Your business setup decides the right type
The right schema follows how your business actually works. Before we choose which schema type to use, we separate three things: the company entity, any physical location, and the page being marked up.
One physical location
A business with one real customer-facing location will normally have a page where LocalBusiness is the clearer fit. That could be the homepage if the whole site represents that one place.
The page should show the local details the schema uses. Name and address matter for LocalBusiness, and the visible content should support the same business details in schema.
Service area business
A service area business still needs schema that reflects the real operating model shown on the page. If customers do not visit you, the page should make the service model clear in plain text.
Local visibility also depends on relevance, distance and prominence. Complete and accurate Google Business Profile details, including the full address where customers can visit, business hours and category, still matter alongside local business structured data.
This is where our Local SEO Services work often starts: the website, schema and Google Business Profile have to say the same thing in the same basic way.
Online only business
An online only business with no customer-facing local location may be better described through Organization schema on the page that represents the company entity.
That keeps schema for a company website clean. The page can still explain who you are, what you sell and how the brand is known, without forcing a local business label onto a model that does not fit.
Multiple locations
A business with several real locations normally needs a clear page for each branch. Each location page can then carry location page schema that matches the branch shown there.
The useful rule is page first, location second. If the page is about one branch, the schema can be specific to that branch. If the page is about the whole company, broader Organization details fit better.
Pro Tip: Save a screenshot of each page before markup goes live. It gives you a simple record of the visible details if the page changes later.
Page choice controls where schema belongs
When a site has both a homepage and separate location pages, the schema has to follow the page purpose. Copying the same block everywhere is where business details start to blur.
A single location business may use the homepage as the main local business page. A larger site might use the homepage for the brand entity and branch pages for each location. An About page can also carry Organization details where it clearly describes the organisation.
JSON-LD is a format for adding structured data to a page, and Google recommends it in most cases. Microdata and RDFa are also supported, but JSON-LD is usually the easier one to ask your developer or SEO team to manage.
Correct implementation still needs checking. The Google Rich Results Test can check the structured data before publishing, and the Google Search Console URL Inspection tool can help review how Google sees the page after publishing. A clean test still does not promise that a rich result appears in search.
At First Place SEO, we treat this as part of Technical SEO because the code choice depends on the page’s job. The schema type, the visible copy and the testing all need to point at the same entity.
technical seo consultant checking website on mobile device
The details must match before markup goes live
Most schema mistakes come from mismatched business details. Before any LocalBusiness or Organization markup is added, gather the facts a person can verify on the site and, where relevant, in Google Business Profile.
- Business name: Use the name shown on the page and in your main business listings.
- Address: Include it for LocalBusiness where the page represents a real location. Google lists name and address as required for Local Business rich result eligibility.
- Phone number: Match the visible contact number on the page.
- Website URL: Use the correct page address for the entity being marked up.
- Opening hours: Check the visible hours before adding openingHoursSpecification.
- Service area: Make sure the page text supports the areas the business says it serves.
- Logo: Use the same brand asset that represents the company clearly.
- Extra local fields: Google also lists recommended LocalBusiness properties such as geo, telephone, url, priceRange, review and department, depending on the business and page.
Testing should come after the facts are clean. Use the Google Rich Results Test before publishing, then use URL Inspection after publishing so the page and the structured data can be checked in place.
Once the business details agree, the technical setup becomes a much smaller job.
Pro Tip: Check the page source for any existing schema blocks before adding new ones. Duplicate markup often comes from old plugins or templates that were never removed.
Search and AI answers need clear entities
Search results now pull meaning from several places at once: your website, your structured data, your Google Business Profile and other business signals. AI answers also need clean entity data, because they work better when the business, location and page purpose are easy to tell apart.
The schema decision should feel simple by this point. Match the type to the real entity on the page, keep the details consistent, and use JSON-LD to make the information easier for search systems to read.
Clear schema helps search systems connect your business details, not guess at them from scattered signals.
seo consultant discussing technical website audit with colleagueseo consultant discussing technical website audit with colleague
Questions we get asked about business schema
Do I need to know JSON-LD before asking someone to add schema?
No. You only need to know that JSON-LD is the format to ask for in most cases, and that the details inside it must match the page. Your developer or SEO specialist can handle the code.
Can schema fix wrong details in my Google Business Profile?
Schema will not fix a wrong Google Business Profile. The profile and the website need to be corrected so the same basic details appear in both places.
Should every service page have business schema?
Every service page does not need a repeated block of broad business schema. The schema should fit the job of the page, so a service page may need different structured data from the homepage or a location page.
Can I add reviews into LocalBusiness schema if they are not on the page?
Review details should match visible page content and the rules for the type of review being marked up. If the review information is hidden from users, it should not be added quietly in schema.
Who should decide the schema type, the developer or the SEO specialist?
The schema type should be chosen from the SEO purpose of the page, then implemented cleanly by someone who can handle the code. A developer can add the markup, but the business and page logic should come first.