Skip to content

LocalBusiness schema: required properties, hours and locations

How to write LocalBusiness structured data Google accepts: required and recommended properties, the right subtype, opening hours, multiple locations and testing.

By Crawlito · 6 min read

In short

  • Google requires only name and address for LocalBusiness markup, and recommends properties such as telephone, url, geo, openingHoursSpecification and priceRange.
  • Use the most specific schema.org subtype, such as Dentist, Plumber or LegalService, and an array when a business fits more than one.
  • Google documents special patterns for opening hours: 00:00 to 23:59 for open all day, 00:00 to 00:00 for closed, and validFrom/validThrough for seasonal changes.
  • Each physical location needs its own LocalBusiness markup, ideally on that location's own page with its own URL.
  • Google's review guidance says aggregateRating and review on LocalBusiness are for sites that capture reviews about other businesses, not for a business marking up its own.
On this page

LocalBusiness structured data is JSON-LD that describes a physical business: its name, address, phone number, opening hours and location. Google requires only two properties, name and address, and recommends several more, including telephone, url, geo and openingHoursSpecification. Use the most specific subtype that fits, mark up each location separately, and make sure every value matches what the page shows.

This guide goes property by property through Google's LocalBusiness documentation, with examples for the cases people get wrong: hours that pass midnight, holidays, multiple types and multiple locations.

What LocalBusiness markup is used for

Google says LocalBusiness markup can help it show business details in a knowledge panel in Search and Maps, and in business carousels for relevant queries. The markup is a way to state your facts in a format machines read without guessing: which text is the address, which number is the phone, which hours apply on which day.

That matters beyond Google. Any system that reads your page, including AI assistants answering "is this place open on Sunday", has to extract the same facts. Clean markup that agrees with the visible page removes one source of ambiguity. It does not decide whether anything shows your business; it makes your own statement of the facts unambiguous. Our overview of structured data for AI search covers what is and is not known about how AI systems use it.

PropertyStatus in Google's docsNotes
nameRequiredThe business name as customers know it
address (PostalAddress)RequiredInclude as many sub-properties as possible: streetAddress, addressLocality, addressRegion, postalCode, addressCountry
telephoneRecommendedInclude country and area codes
urlRecommendedThe URL of this specific location, and it must work
geoRecommendedlatitude and longitude with at least 5 decimal places
openingHoursSpecificationRecommendedOne object or an array
priceRangeRecommendedUnder 100 characters, such as $$ or $10-15
menuRecommendedFull URL of the menu, for food businesses
servesCuisineRecommendedFor food businesses
departmentRecommendedNested LocalBusiness items for departments
aggregateRating, reviewRecommended, with conditionsOnly for sites that capture reviews about other local businesses

A complete example for a single location:

json
{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "name": "Harbour Dental Clinic",
  "image": "https://www.example.com/images/clinic-front.jpg",
  "url": "https://www.example.com/locations/harbour/",
  "telephone": "+44 20 7946 0123",
  "priceRange": "££",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 Quay Street",
    "addressLocality": "London",
    "postalCode": "E1 8AA",
    "addressCountry": "GB"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 51.50721,
    "longitude": -0.07134
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:30",
      "closes": "18:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "Saturday",
      "opens": "09:00",
      "closes": "13:00"
    }
  ]
}

Put it in a <script type="application/ld+json"> element in the server-rendered HTML, so crawlers that do not run JavaScript still receive it.

Choosing the right LocalBusiness subtype

Google asks you to use the most specific type available. schema.org has dozens of LocalBusiness subtypes, including Restaurant, Dentist, Plumber, AutoRepair, HealthClub, HairSalon and LegalService. Browse the full tree on schema.org/LocalBusiness and pick the deepest type that is true.

When a business fits several types, Google's example uses an array:

json
"@type": ["Electrician", "Plumber", "Locksmith"]

Google notes that additionalType is not supported for this purpose, so use the array form. If nothing specific fits, plain LocalBusiness is valid.

For a business that serves customers at their location and has no public storefront, be careful. LocalBusiness describes a place. If you do not want an address shown, the honest options are to mark up the organization with Organization schema instead, or to work out with your SEO lead which address you publicly list. Do not invent an address to satisfy the required property.

Opening hours: the patterns Google documents

openingHoursSpecification takes dayOfWeek, opens and closes, plus optional validFrom and validThrough. Times use 24-hour hh:mm format. Google's documentation covers these cases:

SituationHow to mark it up
Same hours on several daysOne object with an array of days
Hours past midnightOne object, for example Saturday opens 18:00, closes 03:00
Open 24 hoursopens 00:00, closes 23:59
Closed all dayopens 00:00, closes 00:00
Seasonal or holiday changeAdd validFrom and validThrough in YYYY-MM-DD format

Hours without validFrom and validThrough apply all year. A holiday closure on top of normal hours looks like this:

json
{
  "@type": "OpeningHoursSpecification",
  "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"],
  "opens": "00:00",
  "closes": "00:00",
  "validFrom": "2026-12-24",
  "validThrough": "2026-12-27"
}

Remove expired entries once the dates pass, and update the visible hours on the page at the same time. Hours in markup that contradict the hours in the page text, or in your Google Business Profile, are worse than no markup. Our article on holiday hours on location pages covers keeping all three in step.

Multiple locations and departments

Google's guidance for chains and multi-location businesses is to mark up each location as its own LocalBusiness. In practice that means:

  1. Give each location its own page with its own URL, such as /locations/harbour/.
  2. Put that location's LocalBusiness markup on that page, with url pointing to the page.
  3. Link every location page from a locations index page with plain HTML links, so crawlers can find them.
  4. Use the same brand name pattern across locations, with a location qualifier only where customers use one.

Avoid putting twenty LocalBusiness objects on the homepage. It is not invalid, but one page per location gives each set of hours, phone number and address its own context, which is also what a person searching for one branch wants.

For a location with distinct departments, such as a store with a pharmacy, Google's example uses department. Each department is a nested LocalBusiness subtype that defines only the properties that differ from the main store, like its own hours or phone. Google's naming advice is to use "{store name} {department name}" for unbranded departments and the department's own name when it is branded.

Reviews and ratings on LocalBusiness

Google lists aggregateRating and review as recommended, but only "for sites that capture reviews about other local businesses", and points to its review snippet guidelines. A business marking up reviews of itself on its own site is self-serving in Google's terms and does not qualify for review rich results. Our guide to review and aggregate rating schema covers the rules in detail. If you show testimonials, keep them as visible text and leave them out of the LocalBusiness markup.

Mistakes that make LocalBusiness markup unreliable

The common problems are not syntax errors. They are markup that is valid but wrong:

  • Copied markup. A template's LocalBusiness block reused on every location page, so all branches claim the head office phone number.
  • Stale hours. Holiday entries left in place for years, or summer hours that never got switched back.
  • Plugin plus theme. A theme and an SEO plugin each output a LocalBusiness block with slightly different names or addresses.
  • Wrong country format. addressCountry written as a full name in one place and a code in another. Use the two-letter ISO 3166-1 code, such as GB or US, consistently.
  • Rounded coordinates. Latitude and longitude with two or three decimals point to a neighbourhood, not a door. Google asks for at least five.

Each of these is easy to fix once spotted, and spotting them is mostly a matter of comparing the markup with the visible page.

How to validate and check your markup

  1. Rich Results Test. Paste the URL into Google's Rich Results Test to see whether the LocalBusiness item is detected and whether required properties are missing.
  2. Schema Markup Validator. validator.schema.org checks the markup against schema.org, including types Google does not use for rich results.
  3. Check the raw HTML. Confirm the JSON-LD is in the server response, not injected later:
bash
curl -s https://www.example.com/locations/harbour/ | grep -c 'application/ld+json'
  1. Compare with the visible page. Name, address, phone and hours in the markup should match the page text character for character where possible.
  2. Re-check after changes. Moving a location, changing a phone number or changing hours means updating the page, the markup and your Business Profile together.

Common errors are covered in our guide to JSON-LD errors.

Frequently asked questions

Which properties are required for LocalBusiness?

Google requires name and address. It recommends telephone, url, geo, openingHoursSpecification, priceRange and, for food businesses, menu and servesCuisine.

How do I mark up a business that is open 24 hours?

Use an openingHoursSpecification with opens set to 00:00 and closes set to 23:59 for the relevant days, as Google's documentation shows.

Should every location page have its own LocalBusiness markup?

Yes. Google recommends marking up each location as its own LocalBusiness, and a dedicated page per location keeps each set of details tied to the right URL.

Can I add my Google reviews to LocalBusiness markup?

Google's guidance limits review and rating markup on LocalBusiness to sites that collect reviews about other businesses. A business marking up its own reviews is not eligible for review rich results.

Check your location pages

LocalBusiness markup only helps when it is in the HTML crawlers receive and agrees with the page. Run the free check on a location page to see the markup and content a crawler gets.

Filed under Structure and schema. Topics: structured-data, json-ld, local-seo, google