Development Tips

Schema.org JSON-LD for Local Business Sites: A Practical 2026 Guide

By Ken Key Aug 15, 2026 6 min read Updated Oct 16, 2026

Schema.org JSON-LD for Local Business Sites: A Practical 2026 Guide
The short answer

Use LocalBusiness JSON-LD, or a specific subtype like Plumber or Dentist, with your real name, address, phone, hours, and geo coordinates. Keep every field matching what's visible on the page. Skip fake reviews and services you don't offer. Accurate markup helps Google and AI tools understand your entity.

Part of the complete SEO guide.

On this page

Most local business sites either have no structured data at all or have a pile of it that Google ignores. The difference usually comes down to a handful of details: using the right type, keeping the data in sync with what’s actually on the page, and not marking up things that don’t exist. Here’s how I approach JSON-LD on local sites in 2026, with code you can copy.

What JSON-LD Actually Does (and Doesn’t)

Structured data is a machine-readable description of your page. It doesn’t boost rankings by itself. What it does is help search engines understand your entity: who you are, what you do, where you are, what you sell, and how you relate to other things on the web. That understanding feeds rich results, Knowledge Panels, and increasingly, AI-generated answers that pull from your site.

If your markup contradicts your visible content, you lose. If it’s accurate and specific, you give search engines a reason to trust the page. That’s the whole game.

Start With LocalBusiness, Not Just Organization

The single most common mistake I see on service-area sites is using Organization when LocalBusiness is the right type. Organization is fine for a company with no physical location. If you have an address customers visit or a defined service area, use LocalBusiness or a more specific subtype.

Google and schema.org recognize a long list of subtypes: Plumber, Electrician, Dentist, LegalService, HomeAndConstructionBusiness, ProfessionalService, and so on. Pick the most specific one that’s honest. A generic LocalBusiness works, but a specific subtype tells the search engine more.

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "Plumber",
 "@id": "https://example.com/#business",
 "name": "Example Plumbing",
 "url": "https://example.com/",
 "telephone": "+1-516-555-0100",
 "image": "https://example.com/images/storefront.jpg",
 "priceRange": "$$",
 "address": {
 "@type": "PostalAddress",
 "streetAddress": "123 Main St",
 "addressLocality": "Hicksville",
 "addressRegion": "NY",
 "postalCode": "11801",
 "addressCountry": "US"
 },
 "geo": {
 "@type": "GeoCoordinates",
 "latitude": 40.7684,
 "longitude": -73.5251
 },
 "areaServed": [
 { "@type": "City", "name": "Hicksville" },
 { "@type": "City", "name": "Levittown" },
 { "@type": "City", "name": "Bethpage" }
 ],
 "openingHoursSpecification": [
 {
 "@type": "OpeningHoursSpecification",
 "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
 "opens": "08:00",
 "closes": "17:00"
 }
 ],
 "sameAs": [
 "https://www.facebook.com/exampleplumbing",
 "https://www.google.com/maps/place/..."
 ]
}
</script>

A few notes on that block. The @id gives the business a stable identifier so other markup on the site can reference it instead of repeating everything. areaServed is where a lot of Nassau and Suffolk businesses go wrong: they list forty towns they don’t actually serve. List the ones you’d drive to. sameAs should point to profiles that are genuinely yours, not directories you scraped.

Use @id to Connect Your Pages

Once you have a business entity with an @id, you don’t need to redefine it everywhere. Reference it. This keeps your markup lean and consistent, and it’s how you build a coherent graph instead of a bunch of disconnected blocks.

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "Service",
 "name": "Emergency Drain Cleaning",
 "provider": { "@id": "https://example.com/#business" },
 "areaServed": { "@type": "City", "name": "Hicksville" },
 "url": "https://example.com/services/drain-cleaning"
}
</script>

That provider reference resolves to the business block on your homepage. Search engines handle this fine, and it saves you from updating the same phone number in six places.

The Types That Matter for Most Local Sites

  • LocalBusiness (or a subtype) on the homepage or contact page.
  • Service for individual service pages, each pointing back to the business via provider.
  • BreadcrumbList on interior pages so search results show a path instead of a raw URL.
  • FAQPage only when the questions and answers are actually visible on the page. Google has gotten stricter about this.
  • Article or BlogPosting for posts, with a real author and datePublished.
  • Product or Offer if you sell anything online, with real price and availability.

Breadcrumb markup is boring and it works. It replaces the ugly URL in the search result with a readable path, which helps click-through on category and service pages.

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "BreadcrumbList",
 "itemListElement": [
 {
 "@type": "ListItem",
 "position": 1,
 "name": "Home",
 "item": "https://example.com/"
 },
 {
 "@type": "ListItem",
 "position": 2,
 "name": "Services",
 "item": "https://example.com/services/"
 },
 {
 "@type": "ListItem",
 "position": 3,
 "name": "Drain Cleaning",
 "item": "https://example.com/services/drain-cleaning"
 }
 ]
}
</script>

FAQ Markup in 2026: Read the Room

Google cut back how often FAQ rich results appear in search, but the markup still helps machines parse your content, especially for AI answers. The rule hasn’t changed: only mark up questions that a real visitor can see on the page. Don’t hide a wall of keyword-stuffed Q&A in the source and expect a reward.

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "FAQPage",
 "mainEntity": [
 {
 "@type": "Question",
 "name": "Do you offer same-day drain cleaning?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Yes. We keep same-day slots open Monday through Friday for emergency calls in our service area."
 }
 }
 ]
}
</script>

Where People Break It

  • Wrong type. Using Organization for a business with a storefront, or LocalBusiness when Dentist fits.
  • Stale data. Hours changed two years ago, markup still says the old schedule. This is a real trust problem, not just a cosmetic one.
  • Conflicting NAP. The name, address, and phone in your markup don’t match your Google Business Profile. Search engines notice.
  • Marking up invisible content. FAQ or review markup for content that isn’t on the page.
  • Fake reviews. Review snippets in structured data you didn’t earn. This can get you a manual action.
  • Duplicate blocks. The same business defined three different ways across the site with slightly different details.

How to Validate Without Guessing

Two tools do most of the work. The Schema Markup Validator checks that your JSON is syntactically valid and parses as the types you intended. Google’s Rich Results Test tells you which rich result types Google can actually extract from the page. Run both after every change. A missing comma will silently kill the entire block.

Then check Search Console under the “Enhancements” section. It reports errors and valid items per type, and it’s the only place that tells you what Google is actually seeing on your live pages.

Keep It Maintained

Structured data isn’t a one-time install. If your hours change, your markup changes. If you add a service page, it gets a Service block. If you rename the business, everything referencing the @id needs to agree. On a small site this is a fifteen-minute job. On a site with hundreds of pages, it’s worth wiring into your templates so it can’t drift. That’s usually where custom web development pays for itself: structured data generated from your actual content, not hand-typed into a plugin field that nobody updates.

If you’d rather not manage the markup yourself, the same principles apply to Long Island SEO work more broadly. Accurate data in, better results out. There’s no shortcut around that.

FAQ

Do I need JSON-LD if I already have a Google Business Profile?

Yes. Your profile covers Google’s own surfaces. JSON-LD covers your website, which is what search engines and AI systems read when they’re evaluating your pages directly. They should agree with each other.

Will structured data improve my rankings?

Not directly. It improves how search engines understand and display your pages, which can improve click-through and eligibility for rich results. Rankings still come from content, links, and technical health.

Can I put all my structured data in one block?

You can, using an @graph array, and it’s a clean approach for a single page with multiple entities. Just make sure each entity has a distinct @id and that cross-references resolve correctly.

Have a project like this?

I do custom web development for Long Island businesses. If you need this done right, let’s talk.