Which business type should I pick?

Pick the most specific type that fits: Restaurant for food service, Store for retail, ProfessionalService for services like consulting or legal, MedicalBusiness for healthcare providers, and plain LocalBusiness as a safe fallback when none of the more specific types clearly apply. Schema.org has dozens of more specific subtypes beyond these five, but these cover the most common cases and all inherit the same core properties this generator fills in.

Why does dayOfWeek need a full URL instead of just the word 'Monday'?

That's the exact format schema.org's spec defines for dayOfWeek: a reference to a DayOfWeek enumeration member (https://schema.org/Monday, https://schema.org/Tuesday, and so on), not a bare string. This generator builds that full URI automatically from the day you select, so you never need to type or remember the format.

What if my business has different hours on different days?

That's exactly what the opening-hours list is for - add one row per distinct schedule. If Monday through Friday share the same hours, you'd add five separate rows (one per day) rather than trying to express a range in a single entry, since openingHoursSpecification is per-day, not per-range, in this generator.

Is a physical address required for LocalBusiness?

Yes, in practice - a LocalBusiness without an address isn't distinguishable from a general Organization, and Google's guidance expects a real, verifiable address for local business rich results. This generator requires at least a street address and city before it will generate output.

Local Business Schema Generator - LocalBusiness JSON-LD with Hours

Overview

Introduction

LocalBusiness schema tells search engines where a business is physically located and when it's open, the kind of information that shows up directly in local search results and map listings. It's more structurally involved than Organization schema: address is a nested PostalAddress object, and opening hours are a whole array of per-day specifications.

This generator handles both of those nested shapes from plain form fields, including a dynamic add/remove list for opening hours where each entry's day-of-week is automatically expanded to the full schema.org URI format the spec requires.

What Is Local Business Schema Generator?

A form-driven generator for LocalBusiness JSON-LD (or one of four common subtypes: Restaurant, Store, ProfessionalService, MedicalBusiness), covering name, address, contact details, price range, and a list of opening-hours entries.

The address is built as a nested PostalAddress object and opening hours as an array of OpeningHoursSpecification objects, matching the exact nested shape schema.org's spec defines rather than flattened top-level fields.

How Local Business Schema Generator Works

Street address, city, region, postal code, and country are combined into a nested address object (PostalAddress) with the correct property names (streetAddress, addressLocality, addressRegion, postalCode, addressCountry).

Each opening-hours row (a day toggle plus open/close times) becomes one entry in an openingHoursSpecification array, with dayOfWeek expanded from the selected day to its full https://schema.org/Monday-style URI automatically.

When To Use Local Business Schema Generator

Setting up structured data for a business with a physical location customers visit, like a restaurant, retail store, or clinic.

Adding machine-readable opening hours so search engines and map listings can show accurate hours without you maintaining them separately in a business-listing dashboard.

Often used alongside Structured Data Validator, Organization Schema Generator and Review Schema Generator.

Features

Advantages

Builds the nested PostalAddress and openingHoursSpecification structures automatically, both easy to get wrong writing JSON-LD by hand.
Expands day-of-week values to the full schema.org URI format automatically, rather than requiring you to remember or type it.
Supports switching between LocalBusiness and four common, more specific subtypes without re-entering any other field.

Limitations

Only supports one set of opening hours per business; multi-location businesses need one generated schema per location, run separately.
Doesn't verify the address is a real, deliverable location - that accuracy is a manual responsibility.
Covers the five most common business subtypes; schema.org defines dozens more specific ones (like Dentist or AutoRepair) not exposed as toggles here, though you can still describe those with the generic LocalBusiness type.

Examples

A restaurant with weekday hours

Input

Name: Corner Bistro
Type: Restaurant
Address: 45 Market St, Springfield, IL, 62701, US
Phone: +1-555-0142
URL: https://cornerbistro.example.com
Price range: $$
Hours: Monday-Friday 11:00-21:00

Output

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "Corner Bistro",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "45 Market St",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62701",
    "addressCountry": "US"
  },
  "telephone": "+1-555-0142",
  "url": "https://cornerbistro.example.com",
  "priceRange": "$$",
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "https://schema.org/Monday",
      "opens": "11:00",
      "closes": "21:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "https://schema.org/Tuesday",
      "opens": "11:00",
      "closes": "21:00"
    }
  ]
}
</script>

Each weekday with matching hours is added as its own OpeningHoursSpecification row (two shown here for brevity), with dayOfWeek expanded to the full schema.org URI automatically.

Best Practices & Notes

Best Practices

Keep hours in the schema in sync with any hours shown elsewhere (Google Business Profile, the page's own visible hours), since conflicting hours across sources confuses both search engines and customers.
Use a real, verifiable street address; a P.O. box or virtual address undermines LocalBusiness eligibility and can conflict with map-listing verification.
Pick the most specific business type available (Restaurant, Store, and so on) rather than defaulting to generic LocalBusiness, since more specific types can unlock more relevant rich-result features.
Update the schema whenever hours change seasonally (holiday hours, and so on) rather than leaving stale hours in place.

Developer Notes

openingHoursSpecification entries are only included when both opens and closes are filled in for a row, so an incomplete row being edited doesn't produce a broken specification entry in the meantime; dayOfWeek is always expanded to its full https://schema.org/<Day> URI form per the spec's documented format.

Local Business Schema Generator Use Cases

Adding structured data to a restaurant, retail store, or clinic's website homepage
Publishing machine-readable opening hours for a business with hours that differ by day
Marking up multiple business locations, one generated schema per location

Common Mistakes

Writing dayOfWeek as a bare string like "Monday" instead of the full https://schema.org/Monday URI the spec requires.
Letting the schema's opening hours drift out of sync with the business's actual current hours after a seasonal change.

Tips

If your business has identical hours every day, you'll still need one row per day in this generator, since openingHoursSpecification doesn't support a compact day-range shorthand.
Run the output through the Structured Data Validator tool afterward to confirm the required name and address fields are both present.

Local Business Schema Generator