Local Business Schema Generator

Create LocalBusiness JSON-LD from your business name, website and postal address, then add confirmed contact details and opening hours if you have them. Generate code for one location, copy the script or download the JSON, and install the reviewed markup on your website. Generating code does not verify your business or establish eligibility for enhanced search results.

Choose a LocalBusiness schema type for one location

Schema.org defines LocalBusiness as a particular physical business or branch. Start with the location the page describes, rather than combining several branches under one address. For example, a dental practice should use Dentist when that accurately describes the business.

The form offers eight types: LocalBusiness, Restaurant, Dentist, Store, ProfessionalService, Hotel, AutoRepair and BeautySalon. Select the most specific truthful choice available. These are the generator's supported options, not the complete Schema.org vocabulary. There is no custom type field, multiple-type selection or department editor.

If your intended markup needs a more specific type absent from the list, the form cannot generate that exact type. Review the appropriate vocabulary and search requirements before adapting the output yourself. Changing a type should describe the business more accurately, not make an unrelated business appear eligible for a search feature. For several locations, prepare separate details and generate each location individually.

Fill in required and optional business details

This local business schema generator requires a name, website URL, street address, city or locality, postal code and country code. Those are requirements of this form; they are not a claim that every listed property is mandatory in every structured-data specification. Use actual public details for the location. If you cannot provide a required address or postal code accurately, do not invent one to submit the form.

Use country codes such as US, TR or GB, without extra spaces. Telephone input accepts digits and usual spacing or punctuation, with an optional leading +; do not include extension labels or other words.

Latitude must fall between −90 and 90, and longitude between −180 and 180. These bounds do not confirm the location. Google's LocalBusiness property guidance also specifies at least five decimal places of precision for coordinates; the generator does not check that precision or locate your business for you.

The sameAs property identifies the same entity. Add official profiles, not competitors or unrelated directory category pages. Blank optional fields are omitted; supplied URLs and contact details are not independently checked for availability or ownership.

Set weekly opening hours accurately

Add a schedule only when you know the location's opening hours. Each row needs at least one selected day and opening and closing times in 24-hour HH:mm format. Times describe the business's local hours. You can add up to fourteen rows; days with identical hours can share a row.

For a workshop open Monday to Friday from 09:00 to 17:00, select those five days together. Give Saturday its own row if it opens 10:00 to 14:00. If weekdays include a lunch closure, use two rows for the same days, such as 09:00–12:00 and 13:00–17:00, rather than implying continuous service.

An earlier closing time can be intentional. In OpeningHoursSpecification, closing before opening spans into the next day. A Saturday row from 18:00 to 03:00 describes Saturday evening through Sunday morning, not a Sunday evening session.

Google's business-hours examples represent a full day open with 00:00–23:59, and a full day closed with 00:00–00:00. Select the days that genuinely follow that recurring schedule. Do not use identical midnight values to mean 24-hour opening.

Review rows for overlapping or contradictory times yourself. The generator checks time format, not whether schedules match reality. It has no date fields for holiday or seasonal exceptions. A one-off holiday closure cannot be represented accurately by making that weekday closed every week; it needs appropriate dated markup outside this form.

Review the generated JSON-LD

After submitting the form, read the script as a description of your business. Check the selected @type, name, website and every address part before copying it. Optional properties appear only when you supplied them. The generator does not add reviews, ratings, prices, menus or other facts that you did not enter.

This fictional example shows the basic output for an imaginary workshop with no optional entries. Replace every business detail with your own; it is not evidence of a real location or verified search eligibility.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Example Workshop",
  "url": "https://example.com/workshop/",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "10 Example Road",
    "addressLocality": "London",
    "postalCode": "SW1A 1AA",
    "addressCountry": "GB"
  }
}
</script>

A green successful-generation result means code was produced from accepted entries. It does not mean the address, profiles or opening hours were independently verified.

Copy gives you the complete <script> block. The schema download saves local-business.json containing the JSON without that wrapper. Neither action installs anything on your website. Use the script for an HTML placement, or the inner JSON when your existing schema editor specifically asks for JSON-LD data.

Add the script to the matching business page

Place the reviewed markup on the page that describes that location. For a single-location business, that may be the homepage or contact page. A business with several branches can use the corresponding location page for each branch, with that branch's address, phone and hours. Do not reuse one branch's details as though they describe every location.

Google's JSON-LD format guidance allows the script in the HTML <head> or <body>. In a content management system, use a field or integration that actually preserves a JSON-LD script. Pasting it into an ordinary paragraph or a code-display block may only show text to visitors, rather than add structured data.

Check whether a theme or existing schema plugin already publishes business markup. Update the relevant information instead of adding another contradictory address or schedule. Multiple structured-data items can coexist, but their business facts should agree with the visible page. Saving the downloaded JSON file on your computer does not publish it; inspect the page after the actual installation.

Check the published markup and keep it current

Inspect the installed page, not only the saved example. Confirm that the JSON-LD is present and that its address, contact details and hours still match the location information a visitor can read. An editor or plugin can change what reaches the final page, even when the original generated code was correct.

Use Structured Data Checker to inspect JSON-LD syntax and its selected supported types. Its exact-type checks include LocalBusiness, but do not cover every subtype. A Restaurant or Dentist marked unsupported by that checker is not thereby invalid. Read its coverage before treating a result as a complete assessment.

Then use Google's Rich Results Test for applicable Google search features and review any reported errors or missing properties against the relevant official guide. A successful generation or a test pass does not establish factual accuracy. Google's structured-data policies also require relevant, current information and do not guarantee an enhanced search result.

Repeat the review after a move, changed telephone number, new profile URL or revised opening hours. Update the visible location page and its markup together. Keep the page accessible to search crawlers if you intend it to be eligible for search features; markup behind a login or on a blocked page is not made usable by generating it again.