LocalBusiness Schema: Complete Implementation Guide

What Is LocalBusiness Schema?

LocalBusiness schema is a schema.org type that describes a physical business with a customer-facing location. It provides structured data about your address, opening hours, phone number, geographic coordinates, price range, accepted payment methods, and the specific type of business you operate.

When you add LocalBusiness schema to your website, you create a machine-readable profile of your physical presence. Search engines use this data for local search results and map listings. AI models use it to make local recommendations — when someone asks ChatGPT "Where can I find a good dentist in Austin?", the AI needs structured location data to formulate its answer.

LocalBusiness is a subtype of Organization in the schema.org hierarchy, which means it inherits all Organization properties (name, url, logo, sameAs) while adding location-specific fields. It also has dozens of more specific subtypes — Restaurant, DentalClinic, AutoRepair, LegalService, and many more — that you can use for greater precision.

Why LocalBusiness Schema Matters for AI

Local search is one of the most common use cases for AI assistants. Consider these scenarios that happen millions of times daily:

• "Hey ChatGPT, recommend a plumber near me"
• "Gemini, what Italian restaurants are open late in downtown Chicago?"
• "Perplexity, find a family dentist in Portland that accepts Delta Dental"

For AI to answer these queries accurately, it needs structured, machine-readable data about local businesses. Without LocalBusiness schema, AI models must extract location data from unstructured text — a process that is error-prone and often incomplete.

The local AI opportunity

70% of queries to AI models in many markets have a local or industry component. This represents a massive opportunity for local businesses that implement proper schema markup. AI models cross-reference multiple data sources — your website schema, Google Business Profile, Yelp, industry directories — to validate business information. The more consistent and complete your structured data, the more confident AI becomes in recommending you.

Businesses with comprehensive LocalBusiness schema that matches their Google Business Profile and directory listings create what we call entity validation — AI can confirm your business details from multiple sources, increasing the likelihood of citation. For broader context on local AI optimization, see our local SEO for AI guide.

LocalBusiness vs Organization Schema

Choosing between LocalBusiness and Organization schema depends on your business model:

| Use LocalBusiness if... | Use Organization if... | |---|---| | Customers visit your physical location | You serve customers primarily online | | You have defined opening hours | You operate 24/7 digitally | | Walk-in traffic matters to you | Your address is just a headquarters | | You serve a specific geographic area | You serve customers globally | | You are a restaurant, clinic, store, repair shop | You are a SaaS company, agency, publisher |

Important: LocalBusiness inherits all Organization properties. If you choose LocalBusiness, you still get name, url, logo, sameAs, contactPoint, and every other Organization field — plus location-specific additions.

For businesses that are primarily digital but have a physical office, use Organization schema with an address property rather than LocalBusiness.

Complete LocalBusiness Schema Template

Here is a comprehensive LocalBusiness schema template with all recommended properties for AI visibility:

{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "name": "Bright Smile Dental Clinic",
  "alternateName": "Bright Smile Dentistry",
  "url": "https://www.brightsmile-dental.com",
  "logo": "https://www.brightsmile-dental.com/logo.png",
  "image": "https://www.brightsmile-dental.com/images/clinic-exterior.jpg",
  "description": "Family dental clinic in Austin, TX offering preventive, cosmetic, and emergency dental care since 2015.",
  "telephone": "+1-512-555-0123",
  "email": "info@brightsmile-dental.com",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "456 Oak Avenue, Suite 200",
    "addressLocality": "Austin",
    "addressRegion": "TX",
    "postalCode": "78701",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 30.2672,
    "longitude": -97.7431
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday"],
      "opens": "08:00",
      "closes": "18:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "Friday",
      "opens": "08:00",
      "closes": "15:00"
    }
  ],
  "priceRange": "$$",
  "paymentAccepted": "Cash, Credit Card, Insurance",
  "currenciesAccepted": "USD",
  "areaServed": {
    "@type": "City",
    "name": "Austin",
    "sameAs": "https://en.wikipedia.org/wiki/Austin,_Texas"
  },
  "sameAs": [
    "https://www.facebook.com/brightsmiledental",
    "https://www.yelp.com/biz/bright-smile-dental-austin",
    "https://www.google.com/maps/place/Bright+Smile+Dental"
  ],
  "foundingDate": "2015-03-01",
  "founder": {
    "@type": "Person",
    "name": "Dr. Sarah Johnson",
    "jobTitle": "Lead Dentist"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "247"
  }
}

Replace the example values with your actual business data. Use a specific subtype (Dentist, Restaurant, AutoRepair) instead of generic LocalBusiness whenever possible — specificity helps AI categorize your business correctly.

Key Properties Explained

Address (PostalAddress)

The address property must use a PostalAddress object with separate fields for street, city, state, postal code, and country. Never combine everything into a single string. Separate fields allow AI models to parse and validate each component independently.

Critical rule: The address in your schema must be character-for-character identical to your Google Business Profile. "123 Main St" and "123 Main Street" are different strings to a machine. Pick one format and use it everywhere.

Geo coordinates (GeoCoordinates)

Latitude and longitude pinpoint your exact location. While address data can be ambiguous (multiple businesses at the same address, addresses that match in different cities), geo coordinates are unique. Get your coordinates from Google Maps: right-click your location and copy the latitude/longitude values.

Opening hours (OpeningHoursSpecification)

Use openingHoursSpecification (not the simpler openingHours property) for maximum clarity. Each specification includes the day(s) of the week, opening time, and closing time. Group days with identical hours into a single specification. For holidays and special hours, use specialOpeningHoursSpecification with validFrom and validThrough dates.

Area served (areaServed)

This property tells AI which geographic area your business serves. Use City, State, or AdministrativeArea types. This is especially important for service-area businesses (plumbers, landscapers, delivery services) that serve customers beyond their physical location.

sameAs

The sameAs property links your business entity to external profiles — Google Business Profile, Yelp, Facebook, LinkedIn, industry directories. These connections strengthen entity recognition across AI models. For a deep dive, see our sameAs property guide.

Matching Schema to Google Business Profile

Entity consistency is the foundation of local AI visibility. AI models validate business information by cross-referencing multiple sources. When your data is consistent, AI confidence increases. When it is inconsistent, AI may avoid citing your business entirely.

NAP consistency checklist

Ensure these elements are identical across your LocalBusiness schema, Google Business Profile, Yelp, Facebook, and every other platform:

• Name — Exact same business name (including "Inc.", "LLC", etc.)
• Address — Same abbreviations, same suite/unit format, same punctuation
• Phone — Same primary phone number in the same format
• Hours — Same opening and closing times
• URL — Same website URL (with or without www — pick one)
• Categories — Consistent business categorization

Even small inconsistencies matter. If your schema says "Suite 200" but your Google Business Profile says "Ste 200," that is a discrepancy that can weaken entity validation. Audit all your listings quarterly and fix discrepancies immediately.

Multi-Location Businesses

If your business has multiple locations, each location needs its own LocalBusiness schema on its dedicated page. Do not combine all locations into a single schema block.

Best practices for multi-location schema

1. Create individual location pages — Each location should have its own URL (e.g., /locations/austin, /locations/dallas)
2. Unique schema per page — Each location page gets its own LocalBusiness schema with that location's specific data
3. Parent Organization — Use the parentOrganization property to link each location to your main Organization entity
4. Location-specific sameAs — Each location should have its own Google Business Profile and directory listings

{
  "@type": "Restaurant",
  "name": "Tony's Pizza - Downtown Austin",
  "parentOrganization": {
    "@type": "Organization",
    "name": "Tony's Pizza",
    "url": "https://www.tonyspizza.com"
  }
}

This structure helps AI models understand that "Tony's Pizza - Downtown Austin" and "Tony's Pizza - North Austin" are related but distinct entities with different addresses, hours, and contact details.

Common Implementation Mistakes

1. Using generic LocalBusiness instead of specific subtypes — If you run a restaurant, use Restaurant, not LocalBusiness. Schema.org has subtypes for nearly every business category. Specificity helps AI categorize you correctly.

2. Missing geo coordinates — Address alone can be ambiguous. Always include latitude and longitude for unambiguous location identification.

3. Inconsistent NAP data — The #1 local schema mistake. Your schema, Google Business Profile, Yelp, and all directories must match exactly. Even minor differences ("Avenue" vs "Ave.") create entity confusion.

4. Outdated opening hours — If your schema says you close at 6 PM but you changed to 8 PM last month, AI will give incorrect information about your business. Update schema whenever hours change.

5. No sameAs links — Without sameAs, AI models cannot connect your website entity to your Google Business Profile, Yelp page, and other authoritative listings. Include all relevant platform URLs.

6. Single schema for multiple locations — Each physical location requires its own LocalBusiness schema on its own page. Combining locations confuses AI about which data applies where.