Rich result: supported

LocalBusiness schema markup

Describes a business with a physical location or service area — address, hours, contact details.

Does Google still show a rich result for this?

Supported. Business details can appear in the Google knowledge panel, including opening hours and directions. Google does not guarantee that any structured data feature appears.

When to use it

On the home page or contact page of any business customers can visit or call. One of the highest-value types still available to a small business.

Required properties

  • address
  • name

Recommended properties

  • aggregateRating
  • department
  • geo
  • menu
  • openingHoursSpecification
  • priceRange
  • review
  • servesCuisine
  • telephone
  • url

Example

{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "Example Plumbing Ltd",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 High Street",
    "addressLocality": "Leeds",
    "postalCode": "LS1 4AB",
    "addressCountry": "GB"
  },
  "telephone": "+44 113 496 0000",
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "08:00:00",
    "closes": "17:30:00"
  }]
}

Common mistakes

  • Adding aggregateRating or review for your own business. Google states that a business controlling its own reviews is ineligible for the star feature — those properties are for sites reviewing other businesses.
  • Using LocalBusiness when a more specific subtype exists, such as Plumber, Restaurant or DaySpa.
  • Giving latitude and longitude to too few decimal places. Google asks for at least five.
  • Writing opening hours as "9-5". The format is hh:mm:ss.

Check what your own pages are missing

Our free checker reads the markup already on a page and names the types it is missing for its page type. No account needed.

Run the schema checker →

Verified against Google’s structured data documentation and its changelog on 28/07/2026. Google changes what it supports without much notice — if you are reading this long afterwards, check the current documentation before acting on it. Background on why this markup matters beyond rich results is in the answer engine optimisation guide.