Skip to content

Organization Schema Generator

Fill in a name, logo, URL and social profile links, and get a ready-to-paste Organization JSON-LD script tag — the schema Google actually reads to source a Knowledge Panel logo and to connect a site to its official social profiles via sameAs, one link per line, validated as it goes.

  • sameAs social profile links, one per line, validated as a list
  • Optional ContactPoint with phone and contact type
  • Warns on a missing logo, which Google reads for Knowledge Panels
  • Ready-to-paste <script> tag
  • Runs fully client-side

Generator

Built in your browser, never sent anywhere

    Fill in the required fields to generate Organization schema.

    How to generate Organization schema

    1. 01

      Fill in name, URL and logo

      The logo in particular is what Google looks for to source a Knowledge Panel image.

    2. 02

      List social profiles

      One URL per line — official X/Twitter, LinkedIn, GitHub, Wikipedia, wherever this organization is verifiably present.

    3. 03

      Add contact info, if relevant

      A phone number needs a contact type alongside it, like "customer service".

    4. 04

      Copy the script tag

      Paste it once, on the site's homepage — this schema describes the organization, not a single page's content.

    What sameAs is actually for#

    sameAs is how a site tells Google (and other consumers of structured data) which social profiles, Wikipedia entry, or other web presence genuinely belong to the same real-world organization this schema describes — it is a disambiguation signal, not a list of related links. Google's guidance is specific that these should be official, verifiably-owned profiles, not every mention of the organization that happens to exist online. Each line here is validated as its own absolute URL for exactly that reason: a broken or relative sameAs link fails silently, providing no disambiguation value at all.

    Why the logo matters more than it looks like it should#

    This schema, placed on the homepage, is one of the sources Google can use to source the small logo that sometimes appears next to a brand's name in search results and in a Knowledge Panel. A missing logo does not break anything else on the page, but it does mean this specific opportunity is left on the table — which is why this tool flags a missing logo as a warning rather than silently omitting it.

    Where this schema belongs, versus where it doesn't#

    Organization schema describes the entity behind a site as a whole — it belongs once, typically on the homepage, not repeated identically on every page. It is a different concern from Article or Product schema, which describe one specific piece of content; a page can reasonably carry both an Organization schema (identifying who published it) and an Article schema (describing the article itself) at the same time.

    Frequently asked questions

    What should go in sameAs?

    Official, verifiably-owned profiles for this same organization — its X/Twitter, LinkedIn, GitHub, Wikipedia entry, and similar — not every page that happens to mention it. It is a disambiguation signal, not a general link list.

    Does the logo actually matter for SEO?

    It's one of the sources Google can use to source the small brand logo shown next to a site's name in search results and Knowledge Panels. It won't break anything if missing, but it is an opportunity worth not skipping.

    Should Organization schema go on every page?

    No — it identifies the organization as a whole and typically belongs once, on the homepage. It is separate from page-specific schema like Article or Product, which a page can carry alongside it.

    Is my data sent anywhere?

    No. The JSON-LD is assembled entirely in your browser — nothing you enter is transmitted or stored.