Organization
Person (optional)
Runs in your browser. Nothing you type is sent or stored. Test the result in Google's Rich Results Test or the Schema Markup Validator.
What the generator writes, and why
| Output | Value | Rule it follows |
|---|---|---|
Organization @id |
your home page + #organization |
JSON-LD 1.1: a node is identified with @id, and the identifier should lead to a representation of the node. One identifier per entity, used everywhere. |
Person @id |
the person's profile page + #person |
Same rule. The profile page is also the Person's url. |
WebSite @id |
your home page + #website |
Same rule; publisher points to the Organization. |
founder, worksFor, publisher |
{"@id": ...} references |
Nodes refer to each other by @id instead of repeating their details. |
url |
your home page, on https | Google: the URL of the organization's website "helps Google uniquely identify your organization". |
sameAs |
full URLs on other websites | schema.org: a reference page that unambiguously indicates the item's identity. Google: a page on another website, such as a profile. |
legalName, alternateName |
only when different from name | Google: legalName if different from name; alternateName for another common name. |
telephone, foundingDate, address.addressCountry |
checked formats | Google: country and area code; ISO 8601 date; two-letter ISO 3166-1 country code. |
| LocalBusiness | flagged if there is no address | Google requires name and address for LocalBusiness. |
How the sameAs check works
Each URL you list is recognized by its address pattern, taken from the formatter URLs of the matching Wikidata identifier properties: LinkedIn company (P4264) and person (P6634) pages, Crunchbase organizations (P2088) and people (P2087), Google Knowledge Graph links (P2671), Facebook (P2013), X (P2002), Instagram (P2003), YouTube (P2397) and GitHub (P2037), plus Wikidata items, Wikipedia articles and Google Maps links. The generator leaves a URL out when:
- it isn't a full URL starting with https://;
- it repeats a URL already listed;
- it is on your own website (Google describes sameAs as a page on another website);
- it is a person's profile in the Organization list, or an organization's page in the Person list.
It doesn't open the URLs, so it can't tell whether a profile exists or belongs to you. That check, along with name, address and phone consistency across profiles, is part of an entity audit. The rules behind each profile type are in the entity signals reference.
Where to put it
Google recommends placing Organization markup on your home page or a single page that describes the organization, such as the about page, and says it doesn't need to be on every page (Organization structured data, last updated 8 September 2026). Use the same @id values whenever other pages refer to the organization or the person, for example as an article's author or publisher.
Sources
All checked 13 November 2026: Google's Organization structured data guide and Local business guide (both last updated 8 September 2026); schema.org/sameAs (version 30.1); W3C JSON-LD 1.1, section 3.3; the Wikidata properties linked above.
Frequently asked questions
- Where do I put the generated code?
- In the HTML of your home page or about page, inside a script element with type application/ld+json. Google recommends placing Organization markup on the home page or a single page that describes the organization; it doesn't need to be on every page.
- Why does the Organization @id end in
- The fragment gives the organization its own identifier on your home page URL, separate from the page itself. Any identifier works if you use the same one everywhere; this is a common convention, not a Google requirement.
- Does the generator store what I type?
- No. It runs entirely in your browser and sends nothing anywhere.