LocalBusiness schema: a template for clearer AI answers

The template

Replace every value, choose the most specific type for your business (for example Dentist, Plumber or HVACBusiness instead of LocalBusiness), and place it in your homepage’s HTML.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "name": "Your Business Name",
  "url": "https://yourdomain.com",
  "telephone": "+1-905-555-0142",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "Oshawa",
    "addressRegion": "ON",
    "postalCode": "L1H 0A0",
    "addressCountry": "CA"
  },
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
    "opens": "08:00",
    "closes": "17:00"
  }],
  "areaServed": ["Oshawa", "Whitby", "Courtice"],
  "sameAs": ["https://www.facebook.com/yourbusiness"]
}
</script>

Which schema type should I use?

Schema.org has specific subtypes of LocalBusiness. Use the most specific one that is true; if none fits, use LocalBusiness itself.

Rules that matter more than the markup

• The schema must match what is visible on the page and on your Google Business Profile — same name, address and phone.
• Use one canonical phone number; avoid tracking numbers in schema.
• Only describe facts that are true today; update hours when they change.
• Validate with Google’s Rich Results Test or the Schema Markup Validator after publishing.

What schema can and cannot do

Google documents LocalBusiness markup as a way to describe business details; it does not promise a ranking or appearance. There is no public evidence that other assistants reward it directly. Its value is accuracy: when a machine reads your page, it gets your facts unambiguously, which supports the consistency AI assistants rely on.

Frequently asked questions