LocalBusiness Schema Markup Best Practices 2026 (with Code Examples)

LocalBusiness schema is the structured-data type you add to a local business website to tell search engines (and AI search engines) the verified details of the business: name, address, phone, hours, services, geo-coordinates, and reviews. In 2026, it's the single highest-leverage technical SEO win for any local business, required for local pack visibility, increasingly required for AI search citations in local queries, and one of the only places where the more specific schema sub-type you choose materially affects outcomes. This guide covers the 2026 best-practice configuration, the specialised LocalBusiness sub-types most teams miss, common mistakes from auditing client sites at StudioHawk, and validation tools.

What Is LocalBusiness Schema and Why It Matters in 2026

LocalBusiness is a Schema.org type that lets you mark up a business's identity in machine-readable JSON-LD. When implemented correctly, it feeds:

• Google's Knowledge Graph and the local pack (Maps + 3-pack)
• Bing's local results
• Apple Maps and Yelp via syndication partners
• AI search engines that increasingly use schema as the structural signal for "is this a real local business?"

The 2026 shift: AI search engines (ChatGPT, Perplexity, Google AI Overviews) cite local businesses far more often when the page has well-formed LocalBusiness schema. Without it, the AI engine has to infer business details from on-page text, much higher error rate, much lower citation likelihood.

The Required and Recommended Properties for 2026

Google's official LocalBusiness documentation lists what's required vs. recommended. The 2026 best-practice config:

Required (Google won't accept the schema without these)

• @type, use the most specific sub-type (more on this below)
• name, the business name as it appears on signage and in legal documents
• address, full PostalAddress object

Strongly Recommended (Google uses these for richer features)

• @id, a unique permanent identifier URL for the business entity (e.g. https://yoursite.com/#localbusiness)
• url, your website URL
• telephone, formatted with country code: +61 3 9000 0000
• image, high-quality storefront or logo image (multiple aspect ratios ideal)
• priceRange, $, $$, $$$, or $$$$
• openingHoursSpecification, structured hours (more reliable than openingHours shorthand)
• geo, GeoCoordinates with latitude and longitude
• sameAs, array of URLs to verified social/business profiles (Facebook, Instagram, LinkedIn, Yelp)

Recommended for Service Businesses

• areaServed, geographic regions you service
• hasOfferCatalog, structured services list
• aggregateRating, only if displayed visibly on the page
• review, array of structured Review objects

The Specialised LocalBusiness Sub-Types You Should Be Using

This is where most implementations leave value on the table. Schema.org defines dozens of LocalBusiness sub-types, using the most specific one is a stronger entity signal than generic LocalBusiness.

The sub-types Google and Bing recognise (selected list):

The rule: if there's a more specific type that fits, use it. HealthAndBeautyBusiness beats LocalBusiness for a salon. MedicalBusiness beats HealthAndBeautyBusiness for a dental clinic. The more specific the type, the cleaner the entity signal.

2026 Best-Practice LocalBusiness Schema (Full Example)

Paste-ready example for a hypothetical Melbourne hair salon. Adapt for your business:

{
  "@context": "https://schema.org",
  "@type": "HealthAndBeautyBusiness",
  "@id": "https://example.com/#localbusiness",
  "name": "Example Hair Salon",
  "url": "https://example.com",
  "telephone": "+61 3 9000 0000",
  "image": [
    "https://example.com/storefront-1x1.jpg",
    "https://example.com/storefront-4x3.jpg",
    "https://example.com/storefront-16x9.jpg"
  ],
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Collins Street",
    "addressLocality": "Melbourne",
    "addressRegion": "VIC",
    "postalCode": "3000",
    "addressCountry": "AU"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": -37.8136,
    "longitude": 144.9631
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "09:00",
      "closes": "18:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "Saturday",
      "opens": "09:00",
      "closes": "16:00"
    }
  ],
  "sameAs": [
    "https://www.facebook.com/examplehairsalon",
    "https://www.instagram.com/examplehairsalon",
    "https://www.google.com/maps/place/?q=place_id:CHIJ..."
  ],
  "areaServed": {
    "@type": "City",
    "name": "Melbourne"
  },
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Services",
    "itemListElement": [
      {
        "@type": "Offer",
        "itemOffered": {"@type": "Service", "name": "Women's Haircut"},
        "price": "85.00",
        "priceCurrency": "AUD"
      }
    ]
  }
}

Drop this into a <script type="application/ld+json"> block on the homepage and (optionally) the contact page.

Common LocalBusiness Schema Mistakes

From auditing 100+ local business client sites at StudioHawk, the mistakes we see most:

1. Using generic LocalBusiness when a sub-type fits. Salons should be HealthAndBeautyBusiness, not LocalBusiness. Lawyers should be LegalService. The specific type is a stronger entity signal.
2. NAP mismatch. The Name/Address/Phone in your schema doesn't match Google Business Profile, Yelp, or your website footer. Even small inconsistencies (Suite 1 vs Ste 1, +61 3 vs (03)) hurt local trust signals.
3. Missing @id. Without a permanent @id URL, Google can't reliably link your LocalBusiness entity across multiple pages and structured data blocks. Use something like https://yoursite.com/#localbusiness on every page.
4. Fake or placeholder geo-coordinates. Schema generators sometimes auto-fill with city-centre coordinates. Use the actual lat/long of your business location, Google cross-references this with Maps data.
5. Marking up an aggregateRating that doesn't appear visibly on the page. Google's review snippet guidelines require visible reviews. Schema-only ratings are a violation and can trigger manual actions.
6. Putting LocalBusiness schema on every page of the site. Once on the homepage is enough. Repeating the same business entity on 200 pages doesn't help and can cause duplicate-entity confusion.
7. Including hours that don't match Google Business Profile. Schema hours and GBP hours should match exactly. Mismatch is treated as low-quality data signal.
8. Skipping sameAs. The sameAs array is one of the strongest entity-disambiguation signals. Always link to your verified Google Maps place URL, Facebook, Instagram, LinkedIn, and Yelp profiles.

Validation Tools (2026)

• Google Rich Results Test, checks if your LocalBusiness schema qualifies for SERP enhancements
• Schema.org Validator, generic syntax + spec validation
• Google Search Console, under "Enhancements," shows aggregated structured data errors at scale
• Bing Webmaster Tools, has a similar structured data check under SEO Reports

FAQ: LocalBusiness Schema Best Practices in 2026

What is LocalBusiness schema markup?

LocalBusiness schema is structured data (typically JSON-LD) that you add to a local business website to tell search engines and AI engines the verified details of the business, name, address, phone, hours, services, geo-coordinates. It's the foundation for local pack visibility on Google, Bing's local results, and increasingly for AI search citations on local queries.

Should I use LocalBusiness or a more specific sub-type?

Always use the most specific sub-type that fits. HealthAndBeautyBusiness for salons. MedicalBusiness for clinics. LegalService for law firms. The specific type is a stronger entity signal than generic LocalBusiness and Google supports them all.

Does LocalBusiness schema affect Google rankings directly?

Not as a direct ranking factor, but as a strong relevance and trust signal. Sites with well-formed LocalBusiness schema rank consistently better in local pack results and get cited more often by AI search engines. The mechanism is entity disambiguation, not raw keyword matching.

Where should I put LocalBusiness schema on my site?

Once on the homepage is enough for most businesses. Multi-location businesses should also include location-specific LocalBusiness schema on each location page. Don't repeat the same entity schema on every page, it doesn't add value and can confuse entity linking.

Can I include reviews and ratings in LocalBusiness schema?

Yes, but only if the reviews are visibly displayed on the page. Google's review snippet guidelines explicitly prohibit "schema-only" reviews, the structured data must reflect content actually visible to users. Schema-only ratings can trigger manual actions.

What's the difference between LocalBusiness schema and Google Business Profile?

LocalBusiness schema is structured data on your website. Google Business Profile is a Google-hosted listing that powers the local pack and Maps. Both should exist for local businesses, and the data in both should match exactly (same name, address, phone, hours). Mismatch hurts local trust signals.

Does LocalBusiness schema help with AI search citations?

Yes, significantly in 2026. AI search engines (ChatGPT, Perplexity, Claude, Google AI Overviews) increasingly use structured data as the primary signal for verifying that a local business is real. Pages with well-formed LocalBusiness schema get cited far more often in local-intent AI queries than pages relying on inferred on-page text.

Sources & Further Reading

• Google: LocalBusiness structured data documentation
• Schema.org: LocalBusiness type reference
• Schema.org: HealthAndBeautyBusiness sub-type
• Google Rich Results Test

Keep Reading

• Official SEO Guidelines Cheatsheet
• Local SEO: A Practitioner Guide
• Google Business Profile Optimisation
• Local Link Building Strategies