How to use it
- 1
Choose the most accurate supported @type and enter the factual name.
- 2
Add only published URL, logo, address, sameAs, and contact data.
- 3
Copy the JSON-LD, validate it, and compare it with visible page content.
What the tool can do
- Builds a stable @id from the URL or accepts an explicit HTTP(S) or fragment identifier.
- Supports legalName, description, email, telephone, logo, and up to 20 sameAs URLs.
- Creates PostalAddress and ContactPoint structures with explicit areaServed and availableLanguage input.
Common use cases
- Prepare the primary Organization entity for a corporate home page.
- Describe a LocalBusiness with a published address and contact point.
- Standardize @id, logo, and sameAs before linking other schema entities.
How it works inside
Values are serialized locally; the less-than character is escaped so user input cannot close the script element.
Empty optional properties are omitted and placeholder data is never generated.
Questions and answers
Should I use Organization or LocalBusiness?
Choose the most accurate type matching the real entity and published content. The generator does not infer the type automatically.
Can I add multiple contact points?
The current bounded form creates one contact point. For a complex model, edit the JSON-LD manually and validate it again.