Local Business schema generator (JSON-LD)
A shop, restaurant, practice, or office that customers visit or call.
Rich result available: Local business details. Schema.org type LocalBusiness.
LocalBusiness rich results in Google
Google can show hours, address, and ratings from this markup. Your Google Business Profile usually takes priority, so keep the two consistent.
When to use Local Business schema
Use on location pages for shops, clinics, restaurants, and service areas with a fixed address. Pick a specific subtype such as Restaurant or Dentist when it matches.
LocalBusiness properties Google requires and recommends
| Property | Status | In the form |
|---|---|---|
| businessType | Recommended | Type of business |
| name | Required | Business name |
| address | Required | Address |
| telephone | Recommended | Phone |
| url | Recommended | Website |
| image | Recommended | Photos |
| openingHours | Recommended | Opening hours |
| priceRange | Recommended | Price range |
| geo | Recommended | Coordinates |
Local Business JSON-LD example
This is what the builder produces from the example data. Paste it into the page's HTML, in the <head> or the body.
{
"@context": "https://schema.org",
"@type": "CafeOrCoffeeShop",
"name": "Café Kranzler",
"url": "https://example.com",
"telephone": "+49 30 8877200",
"image": [
"https://example.com/storefront.jpg"
],
"address": {
"@type": "PostalAddress",
"streetAddress": "Kurfürstendamm 18",
"addressLocality": "Berlin",
"postalCode": "10719",
"addressCountry": "DE"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 52.50366,
"longitude": 13.33166
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "08:00",
"closes": "19:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Saturday",
"Sunday"
],
"opens": "09:00",
"closes": "18:00"
}
],
"priceRange": "€€"
}Local Business schema FAQ
- Does markup replace a Google Business Profile?
- No. Structured data complements your profile. Keep NAP data consistent across both.
- Multiple locations?
- One LocalBusiness (or subtype) object per location page. Link branches with parentOrganization when useful.