How to Add Schema for a Local Business Site
Add LocalBusiness schema first, or the most specific subtype that matches the business. Put the JSON-LD on a page with business information and validate it against visible copy. The goal is cleaner entity data for search, not a guaranteed result.
| Term |
Meaning |
Why it matters |
LocalBusiness |
A schema type for a specific physical business or branch |
It is the first markup most local businesses should evaluate |
Organization |
The broader company or brand entity |
It helps when the page needs to describe the company behind the location |
Service |
The service the business offers |
It fits pages that explain a service, not just the business entity |
JSON-LD |
Google's recommended structured-data format |
It is the easiest format to place and validate |
Visibility Score |
Maps Agent's 0-100 benchmark for local visibility |
It helps measure whether clearer entity signals align with stronger local presence |
What schema should a local business add first?
Start with LocalBusiness JSON-LD, or the most specific subtype that matches the business, because it gives search engines a clean local entity to read. Add only the markup that matches the page's real business facts, then validate it before you expect any search feature to use it.
Google Search Central says local business structured data can appear on any page, but it is most useful on pages that already contain business information such as the homepage, a location page, or a service page. That is different from a Google Business Profile, which lives on Google and manages profile-side business data rather than website markup.
Should you use LocalBusiness or Organization?
Use LocalBusiness when the page represents a real local branch or service location. Use Organization when you need to describe the broader company, then pair it with the more specific local subtype only when that better matches the page and the visible content.
Think about the page's job. A single-location dentist usually needs Dentist, which is a subtype of LocalBusiness, on the main site or location page. A multi-location HVAC brand may also need Organization at the brand level, but each location page should still describe the local entity rather than repeat one generic company block everywhere.
Where should you put the JSON-LD?
Place the JSON-LD on a page that already contains business facts, such as the homepage, a location page, or a service page with clear contact and coverage details. Keep the markup in one clean block and avoid copying the same entity markup onto multiple pages with the same purpose.
Google recommends JSON-LD for structured data, and the page still needs visible content that supports the markup. Your address, service area, opening details, and service description should already be readable on the page. If the page cannot stand on its own, the markup will not rescue it. The same discipline supports stronger Google Maps optimization.
Which schema types belong on a local service page?
A local service page usually needs LocalBusiness or a specific subtype first, then Service if the page explains the service itself. Add BreadcrumbList only when the site structure benefits from it, and keep FAQPage visible only when the page truly includes a useful FAQ section.
For a plumber's water-heater repair page, LocalBusiness can define the business entity while Service clarifies the actual offering. Use breadcrumbs when they reflect navigation. Use FAQ markup only when the questions are visible and worth reading. Schema should describe the page's role, not decorate it.
Does schema help AI search?
Schema can help AI systems understand the entity and the page structure, but it does not replace visible text, accurate business facts, or profile consistency. It improves clarity for retrieval, not your odds of skipping the ranking and quality systems that still decide whether the page deserves attention.
Google says AI features still depend on the same fundamentals that support Search overall. Ahrefs (2025) found AI Overviews on 57.9% of question queries but only 7.9% of local searches. BrightLocal (2026) found 45% of consumers already use AI tools for local recommendations, and 97% still check reviews before trusting the answer. Maps Agent covers the system in its AEO playbook. Schema helps machines interpret the page. It does not replace proof.
How do you test and validate it?
Test the markup in Rich Results Test or Schema Markup Validator, then compare it against the rendered page and source. If the entity type, address, service details, or coverage claims do not match the visible content, fix the page before you ship the markup.
The sequence is simple: add the markup, test the markup, compare it with the visible page, and confirm the chosen type still fits the intent. Then check supporting trust signals such as local citations, because mismatched business details weaken the same entity clarity you are trying to create. After launch, track whether the page supports a stronger Visibility Score over time.
FAQ
These questions mirror the exact follow-ups owners ask after the first implementation pass. Keep each answer short, visible, and factual so the section helps snippets, voice answers, and AI retrieval without turning into a second article.
What schema should a local business add first?
Start with LocalBusiness, or the most specific subtype that matches the business. That gives search engines a clear entity to interpret before you layer on extra markup. Add more types only when the page actually needs them and the visible content supports each field you mark up.
Should I use LocalBusiness or Organization?
Use LocalBusiness for a real location, branch, or service-area business page. Use Organization for the broader company entity when the page is about the brand itself. Many local businesses need both across the site, but not every page should carry both blocks at the same level.
Where should JSON-LD go on the page?
Put JSON-LD on a page with real business information, usually the homepage, a location page, or a service page with clear business details. Keep it in one clean block. The markup can live in the source, but the facts still need to be visible in the page content.
Does schema help AI search?
Yes, but mostly by improving entity clarity and page structure. It gives search and AI systems cleaner data to interpret. It does not guarantee a citation, a rich result, or an AI Overview mention. Those outcomes still depend on page quality, trust, and consistency across the business presence.
How do I test and validate local business schema?
Run the page through Rich Results Test or Schema Markup Validator, then compare the output with the visible page. Confirm that the entity type, business details, and service claims match the copy exactly. If the markup says more than the page proves, revise the page first.
Clean schema helps a local business page say exactly what it is, where it operates, and what it offers. If you want to measure whether those signals line up with stronger local visibility, Get Your Visibility Score -- Free.