Free tools / organization-schema-generator
Organization Schema Generator
free · runs in your browserValid Organization JSON-LD in seconds — including the sameAs array that tells an engine which entity you actually are, which is the field almost everyone leaves empty.
Your organization
0 fields filled
organization-schema.json
valid ✓Local validation
Runs entirely in your browser. Nothing you type leaves this page. (checkable — open your network tab)
Why this tool exists
Organization schema describes the entity, not the page
Every other tag on your site describes a page. Organization schema describes you — the company behind all of them. That is a different job, and it is the one answer engines care about first, because their opening problem with your brand is not ranking it. It is telling it apart from the other companies with a similar name, a similar product and a similar description.
Which is why the field that matters most is the one most generators treat as an afterthought: sameAs. It is an array of URLs pointing at profiles that already describe you — LinkedIn, Wikidata, Crunchbase, GitHub, a YouTube channel, a review-site listing. Each one is a corroborating record on a domain the engine already has an opinion about. Filling it turns “a site claiming to be Acme” into “the Acme with this LinkedIn page and this Wikidata item.” That is entity disambiguation, and it is the strongest thing this file does.
Be exact about what that buys. Schema does not make an engine mention you — nothing in a file on your own server does. It makes you unambiguous, which is a smaller and different claim. What it changes is the failure where an engine is already talking about your category, means you, and attaches another company’s founding date, another company’s logo and another company’s reputation.
Field by field — what to fill, and what is cargo cult
Nine properties are on the form. They are not equally worth your time, and two of them are where the mistakes live.
01
name
What people actually call you — the trading name on your homepage, not the entity on the incorporation certificate unless they are the same string.
02
legalName · alternateName
legalName earns its place only when it differs from name. alternateName is for acronyms and the name you rebranded away from — that is how you carry a rename, not by deleting the old one.
03
url
One canonical homepage: the exact protocol and host you serve. A url that redirects makes the entity’s own anchor ambiguous.
04
logo
An absolute URL to a real image file that is crawlable and indexable. Google’s documented floor is 112×112px; square-ish on a plain background is what survives being shrunk to a chip. A logo behind a login or a hotlink guard is not a logo.
05
sameAs
Profiles on domains you do not control, one URL each. Two verified ones beat ten stale ones, and a Wikidata item is worth more than any social account. This is the field the whole page is about.
06
contactPoint
Worth it when the contact is real and routed — a support line someone answers. An unmonitored info@ added to satisfy a checklist is the cargo cult version.
07
address
Fill it if you have a location a customer could visit or post to. All parts or none: a PostalAddress with a city and no country is worse than no address at all.
08
foundingDate
A single ISO date. Cheap, factual, and one of the few numbers an engine can attribute to you with confidence — so do not approximate it.
How to use the output
- Paste the generated
<script type="application/ld+json">block into one page — your homepage or your about page, not both. - Reference it instead of repeating it. The block carries an
@idending#organization; pointpublisherandauthoron your other pages at that@id. - Regenerate when something changes — a new profile, a rebrand, a moved logo. A
sameAsURL that 404s is worse than an empty array.
The sameAs rule most Organization markup gets wrong
sameAs is not a link dump, and it is not a place for your own pages. Every URL should be a profile describing the same entity on a domain you do not control — and every one should resolve, be public, and actually be yours.
Three checks before you add a URL: does it load signed out, does it name the same company, and is it current? A dead Crunchbase page and an X account you abandoned are two claims an engine can go and check, and find wanting.
Limitations, stated plainly
This tool validates structure, not truth. It can see that a sameAs URL is well-formed; it cannot open it, confirm it is yours, or confirm the profile is still live — nothing on this page fetches anything. It generates Organization JSON-LD only (FAQ, Product and Article have their own generators, linked below). And no schema markup, from any tool, makes an engine mention you. It makes you unambiguous when one does.
Fair questions.
The same five answers feed this page’s own FAQPage markup — one array, one source.
What is Organization schema actually for?
It tells any parser which entity a website belongs to, in machine-readable form: the name, the canonical URL, the logo, and the outside profiles that corroborate all three. Search engines use it for knowledge-panel style facts; answer engines use it to tell you apart from similarly named companies before they describe you. It describes the company, not the page it sits on.
What should go in the sameAs array?
URLs of profiles describing the same entity on domains you do not control — LinkedIn, Wikidata, Crunchbase, GitHub, YouTube, a review-site listing, an industry directory. Not your own pages, not affiliate links, not a profile you abandoned three years ago. Every entry is a claim an engine can go and check, so quality beats quantity.
Does Organization schema get my brand mentioned in AI answers?
No — and be suspicious of any tool that says it does. Markup makes your identity unambiguous and machine-readable; it does not decide what a model says. What it fixes is the case where an engine is already describing your category, means you, and attaches the wrong company’s details.
Where do I put the JSON-LD, and on how many pages?
One canonical block on one page — homepage or about page. Give it an @id and reference that @id from other markup rather than repeating the whole Organization block on every URL. Duplicated copies drift apart, and the drift is what causes the mismatch.
Where does my data go when I use this generator?
Nowhere. This tool runs entirely in your browser — what you type is never sent to a server, and nothing is stored. (That’s checkable: open your browser’s network tab while you use it.)
Schema is the easy part.
See whether AI actually mentions your brand.