Tool
What the Local Business Schema Generator does
Local Business Schema Generator: generates JSON-LD only from Business name, Street address and City. Example: business name Example Coffee, street address 12 High Street and city Manchester gives JSON-LD only { "@context": "https://schema.org", "@type": "LocalBusiness", "name": "Example Coffee", "telephone": "+44….
From Business name, Street address, City and Region / state, this tool derives JSON-LD only. The result recalculates on every keystroke without a button press or a page reload.
It is mostly used by site owners checking their markup. Structured data is easy to get subtly wrong and hard to notice when you do.
There is no account, no upload and no server round trip, because the page does the work itself.
The method, a field-by-field reference and a worked example built from the defaults are all on this page.
What do the Local Business Schema Generator fields mean?
The Local Business Schema Generator uses 9 inputs. The form opens pre-filled, so the fastest way in is usually to overwrite the one field you actually care about.
| Field | What to enter | Default |
|---|---|---|
| Business name | required | Example Coffee |
| Street address | required | 12 High Street |
| City | required | Manchester |
| Region / state | required | Greater Manchester |
| Postal code | required | M1 1AA |
| Country code | required | GB |
| Telephone | required | +44 161 000 0000 |
| Opening hours | required | Mo-Fr 08:00-18:00 |
| Website | optional | https://example.com |
How does the Local Business Schema Generator work?
Each output is derived from the inputs above in a single pass; there is no hidden state carried between runs, so the same inputs always give the same generated output.
Nothing is computed until the inputs pass their checks, so you will not get a confident answer built on a typo.
Worked example
These are the values the Local Business Schema Generator loads by default, and the result it produces from them. These are the tool’s own default values and the result they produce, not an invented illustration.
| Business name | Example Coffee |
|---|---|
| Street address | 12 High Street |
| City | Manchester |
| Region / state | Greater Manchester |
| Postal code | M1 1AA |
| Country code | GB |
| Telephone | +44 161 000 0000 |
| Opening hours | Mo-Fr 08:00-18:00 |
| Website | https://example.com |
| JSON-LD only | { "@context": "https://schema.org", "@type": "LocalBusiness", "name": "Example Coffee", "telephone": "+44… |
|---|
This is not a substitute for a Google Business Profile
LocalBusiness structured data does not, on its own, produce local pack rankings or map results: those come from a verified Google Business Profile. This schema instead reinforces the same details (name, address, phone, hours) in machine-readable form on the website itself.
Worth knowing
- name, a complete address, and telephone are the fields Google’s documentation treats as the meaningful minimum. An incomplete address (missing postal code or region) weakens the entity match even where the schema still technically validates.
- openingHours should follow the schema.org day-range/time format precisely (Mo-Fr 09:00-17:00). Inconsistent or ambiguous formatting is a common validation failure that a human reading the same string would parse correctly but a strict validator will not.
- NAP consistency (the exact same Name, Address and Phone number represented identically across the website, the Google Business Profile, and any directory listings) matters more for local search than the structured data format itself. The schema documents whatever is inconsistent just as faithfully as whatever is correct.
How to use it
- Fill in Business name.
- Type Street address.
- Enter City.
- Set Region / state.
- Put Postal code.
- Key in Country code.
- Fill in Telephone.
- Type Opening hours.
- Enter Website.
- Type a value and the answer is already there by the time you stop.
- The panel reports JSON-LD only.
- Both Copy Link and Print capture the current state, so pick whichever suits how you file things.
What this tool does not do
- Search engines weigh hundreds of signals. No single on-page check predicts position.
- This checks what is visible in the page you provide; it cannot see server headers or your live rankings.
- There is no audit trail: if you need one, record the inputs alongside the output.
Frequently asked questions
Just Business name, Street address, City, Region / state, Postal code, Country code, Telephone, Opening hours and Website. A starting value is in place for each, which means a single edit is enough to get a meaningful answer.
With the values loaded when the page opens, JSON-LD only comes out as { "@context": "https://schema.org", "@type": "LocalBusiness", "name": "Example Coffee", "telephone": "+44…. It recalculates the moment an input changes, which makes comparing scenarios quick.
It never leaves the tab. The page does the work itself rather than asking a server to.
It costs nothing, and there is no limit on repeat use.
The output is deterministic. The same inputs always give the same answer, and the method is documented above so you can check it.