US and International: +1-855-955-6650
Scroll for more

Adding JSON-LD Markup for Local Businesses: A Complete Guide with Examples

by | Nov 5, 2026 | Local Business Insights, Marketing

Local business schema is JavaScript Object Notation for Linked Data (JSON-LD) structured data that tells search engines your business name, address, phone number, hours, coordinates, and service area in a format machines read without guessing. Structured data won’t make your site rank better on its own. It makes your pages eligible for richer results, such as a knowledge panel with your business details, and it gives search engines one consistent copy of your facts.

For a plumber, law firm, or dental office, those details often decide whether a searcher calls you or the next listing. Wrong hours or an outdated phone number cost real jobs, and markup is one more place where those facts have to be right. This guide covers which properties matter, how to pick a subtype, copy-ready code for storefronts and service-area businesses, WordPress setup, validation, and keeping everything aligned with your Google Business Profile.

Schema is a technical task, but the goal behind it is practical. It belongs to the same effort as accurate listings, steady reviews, and fast replies to every inquiry, all of which help you win more local customers from search. Getting the markup right takes an afternoon. Keeping it right as your details change is the part most businesses skip.

Attract, convert, and retain more customers with less manual work

TL;DR

  • Schema clarifies your facts but won’t lift rankings: Google’s John Mueller has said structured data won’t make a site rank better, and Google bases local results mainly on relevance, distance, and popularity. The payoff is rich result eligibility and fewer chances for search engines to misread your hours or address.
  • Google requires only name and address: Telephone, geo, url, openingHoursSpecification, and priceRange are recommended. Service-area businesses that hide their address face a documented gap, and the areaServed template below shows how to handle it.
  • Your profile and markup must match: Different spellings, phone numbers, or hours across your schema, website, and Google Business Profile undercut the markup. Vendasta’s Listing Sync Pro keeps listing data synchronized across 50+ listing sites so your profile and directories agree.

What Local Business Schema Is

LocalBusiness is a schema.org type for “a particular physical business or branch of an organization.” When you add it to your site as JSON-LD, you hand search engines a labeled record of facts that would otherwise have to be parsed from page text.

The terms around it get mixed up often, and each one means something different:

  • Schema.org: The shared vocabulary of types and properties, such as LocalBusiness, Plumber, and openingHoursSpecification, that search engines read.
  • Structured data: Google’s term for a standardized format that provides information about a page and classifies its content.
  • JSON-LD: The structured data format Google recommends. It is a script block in your page code and does not change what visitors see.
  • Rich results: Enhanced search listings built from structured data. For local businesses, Google says markup can help it display a prominent knowledge panel with details about the business.
  • Search engine results page (SERP) features: The wider set of elements on a results page, including the Local Pack and AI Overviews. Many of them draw on sources other than your markup, especially your Google Business Profile.

The markup describes facts that already appear on the page. Google’s general guidelines say not to mark up content that visitors can’t see, even when it is accurate.

Does Local Schema Help Rankings

Not directly. In April 2025, Google’s John Mueller answered a question on Bluesky by stating that “structured data won’t make your site rank better,” as Search Engine Journal reported. Google’s Business Profile Help says local results are mainly based on relevance, distance, and popularity, and structured data isn’t on that list.

Markup changes how your listing can appear and how reliably Google reads your details. Google’s introduction to structured data cites Nestlé, which measured an 82% higher click-through rate on pages that showed as rich results compared with pages that didn’t. That figure is general rather than local.

Correct markup also doesn’t guarantee a rich result. Google’s general structured data guidelines state that it does not guarantee your structured data will show up in search results, even if the page is marked up correctly.

Rich result types also change over time. Google’s Search documentation updates log shows the FAQ rich result stopped appearing in Google Search starting May 7, 2026. That deprecation covered the FAQ feature, and Google’s LocalBusiness documentation remains in place.

Artificial intelligence (AI) search follows the same logic. Google’s guide to optimizing for generative AI features says structured data isn’t required for generative AI search and that there’s no special schema.org markup you need to add. The same guide notes that a Google Business Profile can help your products and services show up in AI responses.

Search Engine Journal’s May 2026 report describes an Ahrefs test that tracked 1,885 pages after they added JSON-LD, each matched against control pages. No platform showed a meaningful citation increase in AI Overviews, AI Mode, or ChatGPT.

We found no published study measuring whether schema changes what voice assistants say about a business. Keeping the markup matched to your page and your profile is the part you control. If AI answers are your main concern, measure them directly: Vendasta’s AI Search Specialist runs brand visibility reports covering ChatGPT, Gemini, and Perplexity, so you can see whether those tools describe your business correctly.

Schema vs Your Google Business Profile

Your Google Business Profile drives Google Maps and Local Pack listings. LocalBusiness markup describes the business on the website you own, so schema supplements the profile and does not replace it.

The markup still has a job. It lives on your pages, gets crawled with them, and can describe things a single profile can’t, such as departments with their own hours or one block per location page.

Consistency between the two matters most, and it starts with your name, address, and phone number. Google’s Business Profile guidelines ask that your name reflect your real-world business name, as used consistently on your storefront, website, and stationery.

Map each profile field to its schema property and keep the values identical:

Google Business Profile field Schema property What to match
Business name name Exact spelling, no added keywords
Business location address (PostalAddress) Same suite format and postal code
Primary phone telephone Same number, with country and area code
Hours openingHoursSpecification Same hours, including seasonal changes
Website url The page for that location
Service area areaServed Same cities or regions
Primary category @type subtype Closest matching schema.org type

Small differences cause conflicts. “Suite 42” on the site and “Ste 42” in the markup is the kind of mismatch to catch, and so are holiday hours updated in the profile but left unchanged in the code. Listing Sync Pro keeps your directory listings synchronized with your profile details, which covers the directory side of that alignment.

Required and Recommended LocalBusiness Properties

Google’s LocalBusiness documentation lists two required properties, name and address. Everything else is recommended.

Google’s introduction to structured data adds that it is more important to supply fewer but complete and accurate recommended properties than a long list of badly formed ones. The table and hours patterns below cover the core fields, followed by guidance on entity identifiers and review restrictions.

Here is what each property holds and the format rule that applies to it:

Property Status in Google’s docs What it holds Format rule
name Required Business name as customers know it Match signage and your profile
address Required PostalAddress: streetAddress, addressLocality, addressRegion, postalCode, addressCountry Include as many sub-properties as possible
telephone Recommended Primary customer phone number Include country code and area code
url Recommended Page for this specific location Fully qualified, working link
geo Recommended GeoCoordinates latitude and longitude At least 5 decimal places
openingHoursSpecification Recommended Days plus opens and closes times hh:mm:ss in Google’s property table (its examples use hh:mm); English schema.org day values
priceRange Recommended General price level “$$$” or “$10-15”; shorter than 100 characters
department Recommended Units with their own hours or phone Name as {store name} {department name}
areaServed Not in Google’s tables Cities, regions, or a radius you serve schema.org accepts AdministrativeArea, GeoShape, Place, or Text
sameAs Organization property Your profiles on other sites Full URLs; multiple allowed
review, aggregateRating Recommended only for sites reviewing other businesses Ratings data Leave out for your own business

Google documents these hours patterns:

  • Overnight hours: Use a single specification. Saturday with opens “18:00” and closes “03:00” means 6 p.m. Saturday to 3 a.m. Sunday.
  • Open 24 hours: Set opens to “00:00” and closes to “23:59”.
  • Closed all day: Set both opens and closes to “00:00”.
  • Seasonal hours or closures: Add validFrom and validThrough in YYYY-MM-DD format. Leaving them out means the hours apply year-round.

Because LocalBusiness is a subtype of Organization, the Organization fields apply too. Google’s Organization documentation asks local businesses to give a primary phone number and email at the LocalBusiness level before adding contactPoint entries.

sameAs and @id for Entity Consistency

sameAs tells search engines which outside pages describe the same business. Google’s Organization documentation defines it as the URL of a page on another website with additional information about your organization, and its example lists several URLs.

Google’s documentation doesn’t address putting a Google Business Profile or Maps URL in sameAs. Stick to profiles you control, such as Facebook, LinkedIn, and Yelp. A Wikidata entry belongs in the list only if one about your business already exists.

Keep a Permanent Entity Identifier

@id gives the business one permanent identifier, usually your URL plus a fragment, such as https://example.com/#localbusiness. Reuse the identical @id on every page that describes the business so location pages and your Organization block reference one entity.

Follow Google’s Review Restrictions

Leave review and aggregateRating out of your own block. Google’s review snippet documentation makes pages using LocalBusiness or Organization markup ineligible for star review snippets when the business controls the reviews about itself. That rule covers reviews added directly in structured data and those shown through an embedded third-party widget, such as Google Business or Facebook reviews.

You can still show customer reviews on your site so visitors see them. Just keep them out of the markup.

Choosing the Right LocalBusiness Subtype

Use the most specific subtype that describes the business. Google’s documentation says this directly, and schema.org nests trades under parent types: Plumber sits under HomeAndConstructionBusiness, which sits under LocalBusiness.

These are the closest types for common local service businesses:

Business Schema type Parent or note
Plumbing Plumber HomeAndConstructionBusiness
Heating and cooling HVACBusiness HomeAndConstructionBusiness
Roofing RoofingContractor HomeAndConstructionBusiness
Electrical Electrician HomeAndConstructionBusiness
Remodeling, general contracting GeneralContractor HomeAndConstructionBusiness
Locksmith Locksmith HomeAndConstructionBusiness
Law firm LegalService Replaces the deprecated Attorney type
Dental practice Dentist MedicalBusiness
Medical clinic MedicalClinic MedicalBusiness
Restaurant Restaurant FoodEstablishment

Two outdated types still show up in older tutorials. schema.org deprecated the general ProfessionalService type for local businesses because it was confused with Service, and it deprecated Attorney because LegalService is more inclusive and less ambiguous.

If the business fits more than one type, list them as an array, such as "@type": ["Plumber", "HVACBusiness"]. Google does not support additionalType, and plain LocalBusiness is valid when nothing more specific fits. Pick the type closest to your Google Business Profile primary category so both describe the same trade.

Organization describes the company as a whole. Google lists no required properties for it and recommends placing it on the homepage or a single page that describes the organization, such as an about page. LocalBusiness describes a physical business or branch, so a single-location shop uses LocalBusiness alone, while a multi-location company pairs one Organization block with a LocalBusiness block per location.

Copy-Ready JSON-LD Examples

The two templates below cover the most common setups for local service businesses: a storefront that customers visit, and a service-area business that travels to customers and keeps its address private. Pick the one that matches how your Google Business Profile is set up, since the markup should describe the business the same way the profile does.

Both templates use placeholder details. Replace every value with your own, keep each one identical to your Google Business Profile, and paste the full script block into the page it describes. Type the code in a plain text or code editor rather than a word processor, because curly quotes break JSON.

Storefront Business

This template fits a law firm with an office that clients visit. Swap the type for any storefront trade from the subtype table.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LegalService",
  "@id": "https://www.examplelawgroup.com/#localbusiness",
  "name": "Example Law Group",
  "url": "https://www.examplelawgroup.com/",
  "telephone": "+1-212-555-0142",
  "image": "https://www.examplelawgroup.com/images/office-front.jpg",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "148 W 51st St, Suite 42",
    "addressLocality": "New York",
    "addressRegion": "NY",
    "postalCode": "10019",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 40.76143,
    "longitude": -73.98278
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:30",
      "closes": "17:30"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "Saturday",
      "opens": "10:00",
      "closes": "14:00"
    }
  ],
  "areaServed": [
    { "@type": "City", "name": "New York" },
    { "@type": "City", "name": "Jersey City" }
  ],
  "sameAs": [
    "https://www.facebook.com/examplelawgroup",
    "https://www.linkedin.com/company/examplelawgroup",
    "https://www.yelp.com/biz/example-law-group-new-york"
  ]
}
</script>

Each block in the template does a specific job:

  • @type: LegalService is the current type for law firms. Replace it with Plumber, Dentist, or another subtype as needed.
  • @id: This is the permanent identifier for the location. Keep it unchanged on every page that references the business.
  • telephone: The number carries the country code and area code and matches the profile’s primary phone.
  • geo: Both coordinates use five decimal places, the minimum precision Google sets.
  • openingHoursSpecification: Weekdays with the same hours share one object, and Saturday gets its own.
  • areaServed: This is optional for a storefront. List the cities your clients come from.
  • sameAs: These are profiles you control on other sites.

Service Area Business Without a Public Address

Google’s Business Profile guidelines say service-area businesses should hide their business address from customers. A plumber who runs the business from home should keep that address off the profile. This template omits the street address and uses areaServed to describe where the business works.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "@id": "https://www.exampleplumbing.com/#localbusiness",
  "name": "Example Plumbing Co.",
  "url": "https://www.exampleplumbing.com/",
  "telephone": "+1-614-555-0187",
  "image": "https://www.exampleplumbing.com/images/service-van.jpg",
  "priceRange": "$$",
  "areaServed": [
    { "@type": "City", "name": "Columbus" },
    { "@type": "City", "name": "Dublin" },
    { "@type": "City", "name": "Westerville" }
  ],
  "openingHoursSpecification": {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"],
    "opens": "00:00",
    "closes": "23:59"
  },
  "sameAs": [
    "https://www.facebook.com/exampleplumbing",
    "https://www.yelp.com/biz/example-plumbing-columbus"
  ]
}
</script>

Understand Rich Result Eligibility

Google’s LocalBusiness documentation lists address as required and does not mention service-area businesses. Under Google’s own rules, this block is not eligible for Local Business rich results.

The template still matches your profile and describes the business accurately. Don’t add your home address to the markup to clear the warning. Google’s guidelines say not to mark up content that visitors can’t see, so the address belongs in the markup only if it also appears on the page.

Describe a Service Radius

If you serve a radius instead of named cities, schema.org’s GeoCircle, a type of GeoShape, works inside areaServed. The geoRadius value is in meters:

"areaServed": {
  "@type": "GeoCircle",
  "geoMidpoint": {
    "@type": "GeoCoordinates",
    "latitude": 39.96118,
    "longitude": -82.99879
  },
  "geoRadius": 40000
}

Keep the areas aligned with your profile’s service area. Google’s guidelines say that area shouldn’t extend farther than about two hours of driving time from where the business is based, though larger service areas may be appropriate for some businesses.

Where to Place Your Schema and How to Add It

Put the LocalBusiness block on the page that shows those business details to visitors, whether that’s your homepage, contact page, or a location page. The markup should describe what a visitor can read on that page, so the right home for it depends on where your name, address, phone, and hours actually appear.

How you add it depends on your site. Most WordPress sites can use an SEO plugin’s local business settings or paste the code by hand, while other sites take the same script block in their page templates. Google Tag Manager can inject it too, with some tradeoffs covered below. Whichever route you pick, use only one, so the page never outputs two competing LocalBusiness blocks.

Homepage vs Location Pages

A single-location business can put one block on the homepage or the contact page, whichever displays the name, address, phone, and hours in visible text. Don’t repeat the block across every page of the site.

A multi-location business should give each location page its own LocalBusiness block, each with its own @id, address, phone, and hours. The parent company gets one Organization block on the homepage or about page, and each location points back to it:

"parentOrganization": { "@id": "https://www.exampleplumbing.com/#organization" }

parentOrganization supersedes the older branchOf property in schema.org. Google’s documentation doesn’t confirm whether it reads parentOrganization on a LocalBusiness, but the property is valid schema.org and costs nothing to include.

Use department for units inside one location that keep their own hours or phone number, such as a parts counter within an HVAC showroom. Google’s naming pattern is {store name} {department name}. Match your page structure to your profiles: Google’s Business Profile guidelines don’t allow more than one profile for each location.

Adding It in WordPress

Pick one method and stick with it. Two sources that both output LocalBusiness on the same page create duplicate markup.

Vendor documentation for two of the main SEO plugins describes their local features this way:

Plugin LocalBusiness features Plan notes
Yoast SEO Local SEO features for business details and locations Included in Yoast SEO Premium, Yoast WooCommerce SEO, and Yoast SEO AI+
Rank Math Local SEO module with LocalBusiness schema settings The module is in the free plugin; multiple locations is a PRO feature

All in One SEO (AIOSEO) and SEOPress also offer local business schema features. Check each plugin’s current plan details before you buy, especially if you need multiple locations or a service-area setup.

To add the code by hand instead, follow these steps:

  1. Copy the matching template above and replace every placeholder.
  2. Paste the code into the Rich Results Test before publishing.
  3. Add the script block to the page through your theme’s header settings, a child theme, or a code snippets plugin, limited to the page it describes.
  4. Turn off LocalBusiness output in any SEO plugin you also run.
  5. Test the live URL after publishing.

Placement and JavaScript Rendering

Google processes JSON-LD it finds in the rendered page. Google’s guide to generating structured data with JavaScript says Google Search can process structured data available in the page when it renders it, so Google Tag Manager works. The same guide recommends using variables that pull values from the page instead of duplicating them in Google Tag Manager, because duplicates raise the risk of a mismatch between page content and markup.

Other crawlers are less forgiving. A December 2024 Vercel study of AI crawler traffic found that none of the major AI crawlers, including GPTBot, ClaudeBot, and PerplexityBot, render JavaScript. Markup that only exists after a script runs is invisible to them, so code placed directly in the page is the safer choice.

Test Hosting Changes Before Publishing

If your site runs on Vendasta’s WordPress Hosting, use the staging environment to test plugin or header changes before they go live.

Sites built outside WordPress take the same script block in the page code. Vendasta Vibe builds production-ready websites from plain-language instructions and starts with your business details from your business profile, which helps keep the page text and the markup in agreement.

Vendasta Vibe chat prompt asking for a pipeline distribution dashboard, next to the generated dashboard with a sales funnel bar chart and pipeline health indicators

Testing and Validating Your Markup

Test twice: once on the code before it goes live, and again on the live URL afterward. Google’s guidelines say to check structured data with the Rich Results Test during development, and its Rich Results Test help page lists Local business among the supported result types.

Run this sequence for every new or edited block:

  1. Paste the code into the Rich Results Test, choose Code instead of URL, and fix every error.
  2. Run the same code through the Schema Markup Validator to check schema.org structure, including properties beyond Google’s rich result requirements, such as areaServed.
  3. After publishing, test the live URL in the Rich Results Test so markup injected by plugins or JavaScript is rendered and checked.
  4. In Search Console, run a URL Inspection live test and view the tested page’s rendered HTML to confirm the block is present.
  5. Check the Manual Actions report in Search Console for structured data issues.

Each tool answers a different question:

Tool What it checks What it misses
Rich Results Test Google rich result eligibility for a URL or a code snippet; errors disqualify, warnings may limit appearance Guideline problems such as self-serving reviews
Schema Markup Validator schema.org syntax and structure, without Google-specific checks Whether Google will show a rich result
Search Console Indexed pages, rendered HTML, manual actions Pre-publish code, since it reports on pages Google has crawled

Common Errors and Fixes

Most failures trace back to a short list of causes:

Error or symptom Likely cause Fix
Missing field “address” Address omitted, often on a service-area business Add a full PostalAddress, or accept non-eligibility for a hidden-address business and keep areaServed
Invalid JSON document or parsing error Missing comma, bracket, or colon Fix the syntax and re-run the code test
Incorrect value type Curly quotes pasted from a word processor, or text where a number belongs Retype with straight quotes; enter geo values as numbers
Duplicate LocalBusiness items Plugin output plus manual code Disable one source
Price range not displayed priceRange of 100 characters or more Use “$$” or a short numeric range
Hours ignored Non-English day names or nonstandard values Use English schema.org day values and hh:mm times
Imprecise location Fewer than five decimal places in geo Add precision to both coordinates
URL problems Relative or broken link Use the fully qualified, working URL of the location page
Structured data issue in Manual Actions Markup that is invisible or misleading, or self-serving review markup Correct the markup, then select Request Review

Local Business Schema Works When It Matches Your Profile

Local business schema won’t move you up the Local Pack. It does give Google and other crawlers one clean, machine-readable copy of your name, address, phone, hours, and service area. That copy helps only when it agrees with your Google Business Profile, your directory listings, and the text on the page.

The failure to watch for is drift, such as new hours in the profile and old hours in the code. Vendasta’s Listing Sync Pro handles directory synchronization, so the remaining manual task is updating the schema block whenever your details change. Rerun the Rich Results Test after every edit.

To see how Vendasta keeps your listings, reviews, and search visibility working together, book a Vendasta demo.

Local Business Schema FAQs

1. Does local business schema improve my Google rankings?

Not directly. Google’s John Mueller has said structured data won’t make a site rank better, and Google says local results are mainly based on relevance, distance, and popularity. Schema makes your pages eligible for richer results, such as a knowledge panel with your business details, and gives Google a consistent, machine-readable record of your business.

2. Which LocalBusiness subtype should a plumber or law firm use?

Use the most specific type available. A plumber uses Plumber, which sits under HomeAndConstructionBusiness, and other trades have their own types, such as HVACBusiness and RoofingContractor. Law firms use LegalService, because schema.org deprecated Attorney. Avoid ProfessionalService, which is also deprecated, and match the type to your profile’s primary category.

3. Do I still need schema if my Google Business Profile is complete?

Yes, if you want your website to describe the business in a form search engines read directly. Your profile powers Maps and the Local Pack, while schema sits on pages you control and can describe location pages and departments. Keep the name, address, phone, and hours identical in both places.

4. Does local business schema help with AI Overviews and voice search?

Google’s generative AI guide says structured data isn’t required and no special markup exists for AI features, and an Ahrefs test found adding schema produced no meaningful AI citation lift. We found no published study measuring its effect on voice assistants. Accurate markup still keeps your facts consistent with your page and your profile.

5. Can a service-area business use LocalBusiness schema without an address?

It can, with a tradeoff. Google lists address as required and doesn’t mention service-area businesses, so a block without one isn’t eligible for Local Business rich results. Use your subtype with areaServed listing your cities or a GeoCircle radius, and don’t publish a home address your profile hides.

6. How do I set up schema for multiple locations?

Give each location page its own LocalBusiness block with a unique @id, address, phone, and hours. Put one Organization block on the homepage or about page, and link each location to it with parentOrganization. Use the department property only for units inside a single location that keep separate hours or phone numbers.

7. Should I use LocalBusiness or Organization markup?

Use LocalBusiness for any physical location customers visit or that serves a defined local area. Organization describes the company as a whole, has no required properties in Google’s documentation, and belongs on the homepage or about page. Multi-location companies use both.

8. Can I mark up my Google reviews to get star ratings?

No. Google makes pages using LocalBusiness or Organization markup ineligible for star review snippets when the business controls the reviews about itself, and that includes embedded Google Business or Facebook review widgets. You can still display those reviews on your site. Leave review and aggregateRating out of your markup.

9. How do I check that my local business schema works?

Paste the code into Google’s Rich Results Test before publishing, then run the Schema Markup Validator for schema.org structure. After the page goes live, test the live URL and use Search Console’s URL Inspection to view the rendered HTML. Check the Manual Actions report occasionally for structured data issues.

Attract, engage, and retain more
customers with AI software

Share