Local Business Schema Generator

Build business markup locally; actual local-search visibility depends on the published page and broader business/site signals.

Business name

Schema subtype

Street address

City

Region

Postal code

Country

Telephone

Website URL

Image URL

ReadyOutput is generated locally in your browser.

Structured data is not a rich-result guaranteeUse markup only for content that is visible and true on the page. Google eligibility also depends on feature-specific rules, content policies, crawlability, and validation after deployment.

LocalBusiness publication preflight

The primary JSON-LD generator remains first. This optional workspace reuses WTASchema100.localBusiness() for the core entity, then adds publication fields that commonly matter in real location handoff: geo, hours, price range, sameAs profiles, and area served.

Price rangeLatitudeLongitudeArea served

Opening hours — one row as day codes | opens | closessameAs profile URLs — one per line

Publication JSON-LDPreflight evidence

Valid Schema.org does not guarantee a search feature; validate the published page separately against current search-engine requirements.

Search-engine boundaries

Local markup checks cannot know what a crawler fetched, rendered, indexed or selected as canonical. Search engines may rewrite title links/snippets, choose different canonicals, ignore invalid or ineligible structured data, and apply live HTTP/robots conditions that are not present in pasted text. Treat these tools as pre-publish QA, then verify live behavior with the relevant search-engine tools.

Publication preflight, not an SEO score

Generated or pasted SEO data is checked for concrete structural conflicts, malformed values and handoff risks. The tool does not predict rankings, indexing certainty or rich-result eligibility.

Practical guide and verification

Use the tool first, then apply these checks to verify the inputs, interpret the result, and hand it off without displacing the primary workflow.

Match markup to facts visible on the page

Structured data should describe the business information a visitor can actually verify. Keep name, address, phone, URL, hours, service area, and price information aligned with the visible page instead of adding attractive values only to the JSON-LD. Markup is a machine-readable representation, not a place to invent missing business facts.

Use the most specific defensible business type

A subtype such as Restaurant or ProfessionalService can be useful when it genuinely describes the entity, but a narrower type is not automatically better. Choose a Schema.org type that matches the business and keep a general LocalBusiness fallback in mind when a specialized vocabulary does not fit cleanly.

Represent hours and location data carefully

Opening hours, coordinates, and service areas are easy to copy incorrectly across branches. Verify that hours belong to this location, coordinates point to the actual site, and closed days or split shifts are represented intentionally. A technically valid JSON object can still communicate the wrong branch information.

Validate syntax separately from search eligibility

After generating JSON-LD, parse it and inspect the page where it will be published. Search engines can change supported rich-result features and policies, and valid Schema.org does not guarantee a special search display. Use current official validation tools and documentation as a separate publication check.