Website Schema Generator.
Twelve schema.org types, a live JSON-LD preview that updates as you type, required-field validation, and a one-click merge so a page ships one @graph instead of five script tags. Everything runs in your browser — nothing you type is sent anywhere.
The generator
"Add to @graph" banks the current block and clears the form so you can build the next one. One page, one script tag.
Fill in the fields on the left — your JSON-LD appears here as you type.
Leave this on if you are pasting into HTML. Turn it off if your CMS or framework expects the raw JSON object — WordPress SEO plugins and most headless setups do.
Markup that earns its place.
Valid JSON-LD is the easy part. These are the four things that separate markup that does something from markup that just sits there.
Each page's markup should describe that page. Pasting your Organization block onto all 200 URLs does nothing except tell Google the same fact 200 times. Organization and WebSite belong on the homepage; Article belongs on the article.
Structured data has to match what a visitor actually sees. FAQ markup for questions that are not on the page, or a rating nobody left, is a spam violation — and it is the fastest way to lose rich result eligibility across a whole domain.
sameAs is where you tell Google which other profiles are the same entity as you. LinkedIn, X, Crunchbase, Wikidata, industry directories. It is the one property in an Organization or Person block that does real entity work, and most sites leave it empty.
Multiple script tags are legal but messy, and they make it harder for the entities to reference one another. Build each block here, add it to the graph, and paste a single script tag. That is what the "Add to @graph" button is for.
Common questions.
Where does the JSON-LD go?
Inside a <script type="application/ld+json"> tag. The <head> is conventional, but anywhere in the document works so long as it is in the server-rendered HTML. If it only appears after JavaScript runs, treat it as unreliable.
Does schema markup improve rankings?
Not on its own — Google has been consistent that structured data is not a ranking factor. What it does is make rich results possible and remove ambiguity about what a page is about. That second part matters more every year, as answers get assembled by models instead of read off a list of blue links.
Can one page carry several types?
Yes, and it is usually correct. A service page might legitimately carry Organization, Service, BreadcrumbList and FAQPage. Build each one here, add it to the graph, and copy the single combined block.
How do I check it works?
Use the "Test in Google" button — it copies your JSON-LD and opens Google's Rich Results Test, where you can paste it into the code tab. Once the page is live, the URL tab of the same tool and the Enhancements reports in Search Console are the sources of truth.
Is anything I type sent to your server?
No. This tool is plain JavaScript in your browser. There is no network request at any point, which also means it keeps working with the tab offline.
Which LocalBusiness type should I choose?
The most specific one that genuinely fits. Plumber beats HomeAndConstructionBusiness, which beats LocalBusiness. If nothing fits closely, use the generic LocalBusiness rather than forcing a type that is nearly right.
Markup declares it. Sources corroborate it.
Structured data tells Google what you claim to be. Whether that claim sticks depends on what independent sources say about you — citations, mentions and profiles that agree. That is the part we build.