Private JSON-LD builder

Local Business Schema Generator

Build a precise Schema.org LocalBusiness entity from facts visitors can verify on the page. Validate addresses, hours, coordinates, URLs, and type-specific details before copying the JSON-LD.

Markup describes content; it does not create or guarantee rankings, map placement, a knowledge panel, or a rich result. Publish only accurate facts that are visible or supported on the marked-up page.

Business identity

Choose the most specific accurate type. Name and physical address are required for Google’s LocalBusiness feature.

Physical address and map position

Describe one real branch or location. This tool does not create service-area-only Organization markup.

Images and official profiles

Opening periods

Add one period per day; repeat a day for split shifts. A closing time earlier than opening represents an overnight period. Maximum 21 periods.

What LocalBusiness markup communicates

A LocalBusiness entity describes one physical business or branch using machine-readable facts: its specific type, public name, structured postal address, contact details, canonical location page, opening periods, images, profiles, and optional map coordinates. The generated object uses https://schema.org as its context and a supported LocalBusiness subtype as its type.

Use one entity per real location. Keep the name, address, telephone, hours, and other facts consistent with what visitors can see on the page and with the business’s real-world information.

How to use the generated JSON-LD

  1. Choose the narrowest accurate subtype and enter facts for one physical location.
  2. Generate, resolve every blocking error, and review warnings rather than treating them as automatic SEO instructions.
  3. Copy the safe script element into the relevant location page, or give the JSON-LD object to the developer or CMS responsible for structured data.
  4. Validate the final published page with Schema.org’s validator and Google’s Rich Results Test, then monitor Search Console.
Do not publish invented fields. An omitted optional fact is better than an inaccurate coordinate, profile, image, price, or opening period.

Addresses, coordinates, and hours

Physical location

Google lists name and address as required LocalBusiness properties. This generator requires street, locality, postal code, and an officially assigned ISO 3166-1 alpha-2 country code, while preserving region when supplied. Entering lowercase is accepted and emitted uppercase. User-assigned and exceptionally reserved codes such as XK and EU are not accepted by this focused model.

Coordinates

Latitude and longitude must be supplied together. Latitude is limited to −90 through 90 and longitude to −180 through 180. Google recommends at least five decimal places for precise LocalBusiness coordinates; lower precision produces a warning, not fabricated digits.

Opening periods

Each row becomes an OpeningHoursSpecification. Repeat a day for split shifts. A close time earlier than the open time represents overnight hours, consistent with Google’s examples. Use 00:00 through 23:59 for all-day hours. Omit rows rather than guessing.

Type-specific fields and intentional exclusions

Food-establishment subtypes can include servesCuisine, menu, and acceptsReservations. Lodging subtypes can include checkinTime and checkoutTime. These controls are disabled and excluded when the chosen type does not support them.

This focused generator does not create reviews, aggregate ratings, departments, offers, booking actions, products, or service-area geometry. Review markup has additional eligibility rules, including Google’s restriction on self-serving LocalBusiness reviews, and should not be generated from unverified star counts.

Validation and limitations

  • Local validation checks required fields, supported types, HTTP(S) URLs, email shape, address completeness, country code, coordinate pairing/ranges/precision, bounded lists, opening-period pairs, type-specific properties, JSON serialization, parse-back, and output size.
  • It cannot fetch pages or confirm that a URL resolves, an image is crawlable, a profile is official, coordinates match an address, facts are visible, or the published page follows every current search policy.
  • Schema.org vocabulary validity and Google feature eligibility are different questions. A parseable Schema.org object may still be ineligible or unused by a search engine.
  • Google explicitly says structured data enables eligibility but does not guarantee display. Search appearance depends on content, policies, indexing, algorithms, location, device, and other factors.

Privacy

All form processing, validation, formatting, copying, and file creation happen in the current browser tab. No business data is sent to this site or a third party, and nothing is saved after reset or navigation. External validators are not contacted automatically.