Local Business Schema Generator for JSON-LD Structured Data

How to use the local business schema generator

1. Select the business type from the dropdown (e.g. Restaurant, Store, Dentist).
2. Enter the required details: business name, street address, city, region, postal code, country and phone number.
3. Optionally add latitude and longitude, price range, opening hours for each day and social profile URLs.
4. Copy the generated <script> block and paste it into the <head> of your web page.

How the LocalBusiness JSON-LD is built

The output follows the schema.org LocalBusiness specification. Every script starts with the @context set to https://schema.org and the @type matching the business category you select. Google requires name and address (as a PostalAddress object) and recommends telephone, so the phone number is optional here but a note appears if you leave it out.

When you provide latitude and longitude, the generator nests them inside a GeoCoordinates object under the geo property. Opening hours use the schema.org openingHoursSpecification array, where each entry contains a dayOfWeek, opens and closes value formatted as HH:MM. For example, Monday 09:00 to 17:00 becomes:

{ "@type": "OpeningHoursSpecification", "dayOfWeek": "Monday", "opens": "09:00", "closes": "17:00" }

Social profile URLs are collected into a sameAs array. Search engines use this to associate your website with your verified social accounts.

Common schema.org business types

Choosing the most specific @type helps search engines understand your business. Here are frequently used subtypes of LocalBusiness:

If none of the specific types fit, use the generic LocalBusiness type. You can always refine it later without breaking existing markup.

Where to place the JSON-LD script

Paste the generated <script type="application/ld+json"> block inside the <head> element of the relevant page. For a single-location business, the home page is the standard placement. If you operate multiple locations, create a separate page for each branch and embed the corresponding schema on that page.

Search engines read JSON-LD regardless of its position in the document, but placing it in the head keeps your HTML body clean. Avoid duplicating the same markup across every page unless all pages represent the exact same entity.

After publishing, verify the markup using Google's Rich Results Test or the Schema Markup Validator. These tools confirm that the syntax is correct and that all required properties are present.

Opening hours format explained

Schema.org supports two ways to express hours. This local business schema generator uses openingHoursSpecification because it is the structure Google documents and it can carry seasonal dates (validFrom and validThrough) that the older comma-separated string format cannot.

Each day requires an open time and a close time in 24-hour HH:MM format. If a business is closed on a given day, simply leave both fields empty for that day and the generator will omit it from the output. For a business open 24 hours, Google documents opens 00:00 with closes 23:59. A closing time after midnight, such as 03:00, is valid in the same entry as the opening time.

If you need to calculate total weekly operating hours for staffing purposes, an hours calculator can help sum the durations once you have the open and close times.

Avoiding common structured data mistakes

Several errors routinely cause search engines to ignore LocalBusiness markup. First, avoid a P.O. Box as the street address, because local business markup describes a place customers can visit. Second, ensure the phone number includes the international dialing prefix (for example, +1 for North America).

Third, do not stuff keywords into the name field. Use the name your customers see on your storefront. Fourth, if you provide geo coordinates, they must actually point to your address. Google recommends at least five decimal places so the pin lands on the right building.

Finally, keep the sameAs URLs limited to profiles you control. Do not list profiles that belong to other businesses. If you also need FAQ markup for your site, consider pairing this with a dedicated FAQ schema generator for question-and-answer content.

Worked examples