Local Business Schema Generator

Most schema generators hand a shop the same flat opening-hours string a 1990s directory would have used, and then a restaurant that shuts between lunch and dinner has nowhere to put the gap. The Local Business Schema Generator writes openingHoursSpecification instead, which is an array of objects rather than a line of text, so a split shift and a half-day Friday are both expressible.

Fill in the name, address and week; the JSON-LD block updates as you type and is ready to paste into the page head. Two things it does that are easy to get wrong by hand: consecutive days sharing identical hours are merged into a single entry with a dayOfWeek array rather than emitted seven times, and round-the-clock trading is written as 00:00 to 23:59, because schema.org has no always-open flag and 24:00 is not a time it accepts.

Closed days produce nothing at all, which surprises people. There is no closed object in the vocabulary; a day with no specification is a day you are shut. The tool lists those days under the output so the absence reads as deliberate rather than as something that went missing.

Walkthrough: A Bakery With One Closed Day

Press Load Sample and the form fills with Thornbury Lane Bakehouse, a London bakery trading 07:00 to 15:00 on weekdays, 08:00 to 13:00 on Saturday, and closed on Sunday. Seven days of input come out as two openingHoursSpecification entries: one carrying a five-item dayOfWeek array for Monday through Friday, one for Saturday on its own. Sunday appears nowhere in the JSON-LD, and is instead named in the line beneath it. Cycle the sample again and you reach a restaurant whose Tuesday-to-Saturday runs 11:30–14:30 and 17:00–22:00, which comes out as three entries rather than two, because the Sunday lunch service has no dinner sitting to pair with.

How It Calculates the Day Groupings

• Each day is reduced to a signature: the list of its open ranges, or the word closed. Days are then walked Monday first, and any run of neighbours sharing a signature becomes one group.
• Grouping is deliberately restricted to consecutive days. Monday and Thursday sharing hours while Tuesday differs stay separate entries, because a dayOfWeek array that skips days is legal but reads as an error to anyone auditing the markup later.
• A group holding one day emits dayOfWeek as a plain string; a group holding several emits an array. Both forms are valid, and using the string for a single day keeps the block readable.
• A day carrying two ranges produces two entries for that same group, one per shift. This is the case a flat hours string cannot represent at all, and the + split shift control beside each day is how you add the second one.
• The @type selector offers 25 schema.org subtypes, from Bakery to AccountingService. Picking the narrowest one that fits is worth doing: Dentist tells Google more than LocalBusiness, and both inherit the same address and hours properties.

Tricky Inputs: Split Shifts, Midnight and Two-Letter Countries

• Type UK into the country field and it is refused: “‘UK’ is not an ISO 3166-1 alpha-2 country code. Google expects the two-letter form, so the United Kingdom is GB and not UK.” The field is checked against all 249 assigned codes.
• A closing time that is not after its opening time is an error rather than a silent export, and the message says what to do about it. A bar trading until 02:00 is two days in schema.org terms, not one day ending before it started.
• Times are 24-hour HH:MM only. There is no place for 5:00 PM in this vocabulary, and a value that shape is rejected rather than guessed at.
• Name, street and city are hard requirements; telephone and price range raise warnings instead, since the markup is still valid without them but the rich result usually shows both.
• Mark every day closed and the property is dropped from the output entirely rather than written as an empty array, with a warning explaining why the block got shorter.