How to use the Organization Schema Generator

The organization schema generator turns a short form into Organization JSON-LD. It runs entirely in your browser, so the details you enter stay on your device.

  1. Enter your organization name exactly as you want it to appear everywhere, for example “Example Co”. If your registered name is different, add it as the legal name.
  2. Enter your website’s home page URL, including https and the preferred hostname, such as https://www.example.com/. Use the same version of the URL that you redirect to.
  3. Add a logo URL. Use a stable, publicly reachable image address (PNG, JPG, SVG or WebP) that shows your logo clearly on a white background. Square or near-square images work best.
  4. Add a short description of what the organization does, in one or two plain sentences.
  5. Paste your social and profile URLs, one per line: LinkedIn, X, YouTube, GitHub, Crunchbase, Wikipedia, Wikidata or any other page that is clearly about your organization.
  6. Optionally add contact details: a public email address, a phone number, a contact type such as customer support or sales, and a postal address if you want one shown.
  7. Review the JSON-LD in the output panel, copy it, and paste it inside a <script type="application/ld+json"> tag on your home page. Run it through a validator before you publish.

Tip: Only include details that are already public and that you want public. Leave a field empty rather than inventing a value. Missing properties are fine. Wrong ones are not.

What Organization schema is

Organization schema is structured data that describes a company, nonprofit, school, club or any other group using the Organization type from schema.org. It states, in machine-readable form, the basic facts about you: what you are called, where your website lives, what your logo looks like, which official profiles belong to you and how people can reach you.

Without it, a search engine or AI assistant has to work these facts out by reading your pages and cross-referencing other sources. That works most of the time for large, famous brands. For smaller companies, new brands and names that are shared with other things, it is much less reliable. A company named “Atlas” or “Mercury” competes for identity with every other thing that carries that name.

Organization markup gives you a way to say, in your own words and on your own domain: this is the entity, this is its canonical site, and these profiles belong to it.

The core properties

The most useful properties are short and familiar.

  • name: the name people know you by.
  • legalName: the registered company name, if different.
  • url: the canonical home page.
  • logo: a URL to your logo image, or an ImageObject.
  • description: a one-or-two-sentence statement of what you do.
  • sameAs: a list of URLs of your official profiles elsewhere on the web.
  • contactPoint: one or more ContactPoint entries with a contact type, email or phone, and optionally languages and areas served.
  • address: a PostalAddress, if you want a public address associated with the organization.
  • foundingDate: the year or full date the organization was founded.
  • @id: a stable identifier for the entity, such as your home page URL plus a fragment, which lets other markup refer to it.

Organization and its subtypes

Schema.org has many more specific types that inherit from Organization, including Corporation, NGO, EducationalOrganization, OnlineStore and LocalBusiness with its own subtypes such as Restaurant or Dentist. If a more precise type genuinely fits, use it, because it carries the same properties plus more specific ones. If you are unsure, plain Organization is always valid.

Businesses with a physical location that serve customers locally should look at LocalBusiness markup, which adds opening hours and a geographic location. The generator on this page focuses on the general case: a company or brand with a web presence.

When a person asks an AI assistant “who is Example Co?” or “is Example Co a good option for X?”, the assistant has to resolve a name to an entity before it can say anything useful. Organization schema is one of the clearest tools you have to help with that step.

It helps with entity disambiguation

Search and answer engines build their understanding of the web around entities: distinct things with names, attributes and relationships. Your markup contributes a statement from the source itself: the legal name, the official site and the official profiles. When those match what the engine sees on third-party sites, confidence goes up. When your name collides with another entity, a consistent set of identifiers helps it tell the two apart.

It connects your site to your profiles

The sameAs property links your website to your profiles on other platforms. This is how a machine can conclude that the LinkedIn page, the GitHub organization and the website all describe one organization. If one of them is a Wikipedia article or a Wikidata item, the link ties you to a widely used knowledge base that many systems consult.

It supports logo and brand display in Google

Google documents Organization structured data as a way to help it understand your organization’s administrative details and to disambiguate it from other organizations. It also uses the logo property to choose a logo to show in search results, such as in knowledge panels, when it decides to show one. Google does not promise any specific display.

It supports consistent descriptions

When the same name, description and facts appear in your markup, on your About page and in your profiles, an engine that summarizes your company is more likely to produce a consistent description. When your own pages disagree with each other, summaries drift and can mix details from different sources.

What it cannot do

Organization schema does not make a model say good things about you, and it will not override what independent sources say. It does not guarantee a knowledge panel, and it does not rank you. It states the facts you control. The other half of the work, third-party coverage, reviews and mentions that confirm those facts, happens outside your own site.

Where to place Organization markup

Put Organization markup on your home page. Google’s guidance is that it can go on one page, and the home page or an About page is the usual choice. You do not need to repeat the full block on every page of the site. Repeating it everywhere adds weight to every page without adding any new information.

If other pages need to refer to your organization, for example an Article that names you as publisher, give the Organization an @id and refer to it by that identifier. The Article example in the Article Schema Generator guide shows the pattern.

Home page, About page or both

Home page is the default. Some sites put the full markup on the About page because it already contains the facts. Pick one page, make it the place where the details are most visible, and keep the markup consistent with what the page says.

Fields in depth

Use the name your customers use for name. Use legalName only if the registered name differs, for example “Example Co” and “Example Company Limited”. If you use more than one common name, alternateName can hold the other forms. Keep these consistent with your site title, your logo text and your social profile names.

URL and @id

The url should be the canonical home page, the one you want people and machines to treat as the primary address. Pick one hostname, with or without www, and one protocol, and stick with it. For the @id, a common pattern is the home page URL followed by a fragment such as #organization. It is an identifier, not necessarily a page you can open.

Google’s logo guidelines ask for an image that is at least 112 by 112 pixels, crawlable and indexable, in a format that Google Images supports, and that looks good on a white background. A square or near-square logo avoids awkward cropping. Use a stable URL that does not change when you redeploy. Do not point to a logo hosted behind a login, behind hotlink protection, or in a robots-blocked folder.

Description

Write one or two factual sentences. Say what you do, for whom, and where. Avoid slogans and superlatives. “Example Co makes project planning software for small construction firms” is more useful than “The world’s most innovative platform.”

sameAs

List only profiles that you control or that are clearly about you. Good candidates are your LinkedIn company page, YouTube channel, X or Bluesky profile, GitHub organization, Crunchbase entry, Wikipedia article and Wikidata item. Use the full canonical URL of each profile. Do not list personal profiles of staff members here, and do not list pages that merely mention you. If you do not have a profile on a platform, leave it out. A short, accurate list beats a long, padded one.

Contact points

A ContactPoint describes a way to reach part of the organization. Give each a contactType such as “customer support”, “sales” or “technical support”, and an email or telephone. Add areaServed and availableLanguage if they apply. Only publish contact details that you are happy to have indexed. Role addresses such as support@ and sales@ are better than personal inboxes, because personal addresses attract spam and change when people leave.

Address

A PostalAddress includes a street address, locality, region, postal code and country. Include it if you have a public business address and want to associate it with the organization. If you work remotely, run from a home office or prefer not to publish an address, omit it. Do not use a placeholder or an address that is not yours.

Founding date, size and more

foundingDate accepts a year or a full date. Additional optional properties include numberOfEmployees, slogan, knowsAbout, parentOrganization and identifiers such as vatID and taxID. Add what is true and public. Skip anything you would need to guess.

Best practices

Make the markup match the page

Structured data should reflect what visitors can see. If the markup names an organization, a logo and a set of profiles, those should be visible somewhere on the site, in the header, footer, About page or contact page. If the markup says one thing and the page another, trust suffers.

Keep identity consistent across the web

Use the same name, the same description in spirit, and the same logo across your site, your social profiles and any directory listings. Inconsistent naming, such as “Example Co”, “ExampleCo” and “Example Company Inc.” on different platforms, makes it harder for a machine to treat them as one entity. The markup helps, but the underlying consistency is the bigger factor.

Fill in the profiles that matter

Claim the major profiles for your brand and make them complete. A LinkedIn page with a description and a link back to your site, a YouTube channel with the same logo, a Crunchbase or similar business directory entry: these are the kind of sources that confirm what your markup says. A Wikidata item is helpful if you meet its notability requirements. Do not create promotional or fake entries to pad your sameAs list.

Use one block, not many

Keep one Organization entity per site. If several plugins, your theme and your SEO tool each output their own Organization block, you may end up with duplicates that conflict. Choose one source for the markup and disable the others.

Validate and monitor

Test the page with the Schema Markup Validator at validator.schema.org and with Google’s Rich Results Test. Check Search Console’s enhancements and any structured-data reports for warnings. Re-test after redesigns, domain moves and theme changes, because those commonly break or duplicate markup.

Update it when the facts change

If you rebrand, move, change your support address or close a social account, update the markup the same day. Stale facts in structured data are a source of wrong answers about you.

Use @id to build a connected graph

Give your Organization a stable @id and reference it from other markup, for example as the publisher of an Article or the isPartOf parent of a WebSite. A connected graph tells machines that every piece of markup on your site points to the same entity, instead of leaving them to match names.

Examples

A basic Organization

This is a solid starting point for most companies. Replace the sample values with your own.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com/#organization",
  "name": "Example Co",
  "legalName": "Example Company Limited",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/images/logo-512.png",
  "description": "Example Co makes project planning software for small construction firms.",
  "foundingDate": "2018",
  "sameAs": [
    "https://www.linkedin.com/company/example-co",
    "https://github.com/example-co",
    "https://www.youtube.com/@exampleco"
  ]
}
</script>

Organization with contact points and address

This version adds role-based contact points and a postal address.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com/#organization",
  "name": "Example Co",
  "url": "https://www.example.com/",
  "logo": {
    "@type": "ImageObject",
    "url": "https://www.example.com/images/logo-512.png",
    "width": 512,
    "height": 512
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Example Street",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62701",
    "addressCountry": "US"
  },
  "contactPoint": [
    {
      "@type": "ContactPoint",
      "contactType": "customer support",
      "email": "support@example.com",
      "availableLanguage": ["English", "Spanish"]
    },
    {
      "@type": "ContactPoint",
      "contactType": "sales",
      "email": "sales@example.com",
      "areaServed": "US"
    }
  ],
  "sameAs": [
    "https://www.linkedin.com/company/example-co"
  ]
}
</script>

Organization connected to a WebSite and an Article

Using @graph, you can define the Organization once and reference it from other entities by @id.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.example.com/#organization",
      "name": "Example Co",
      "url": "https://www.example.com/",
      "logo": "https://www.example.com/images/logo-512.png"
    },
    {
      "@type": "WebSite",
      "@id": "https://www.example.com/#website",
      "url": "https://www.example.com/",
      "name": "Example Co",
      "publisher": { "@id": "https://www.example.com/#organization" }
    },
    {
      "@type": "Article",
      "headline": "How to plan a small build",
      "author": { "@type": "Person", "name": "Jane Doe" },
      "publisher": { "@id": "https://www.example.com/#organization" },
      "datePublished": "2026-03-04"
    }
  ]
}
</script>

A more specific subtype

If you are an online store, you can use OnlineStore in place of Organization. Everything else stays the same.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "OnlineStore",
  "name": "Example Goods",
  "url": "https://shop.example.com/",
  "logo": "https://shop.example.com/images/logo.png",
  "sameAs": ["https://www.instagram.com/examplegoods"]
}
</script>

Adding the markup to your site

WordPress

Many SEO plugins already output Organization data based on your site name and logo settings. Check what your site produces before you add anything: view the page source and search for "@type":"Organization". If a plugin already does it, fill in that plugin’s organization settings instead of pasting another block. The free aeoora WordPress plugin generates schema without creating duplicates and works alongside Yoast, Rank Math, AIOSEO and SEOPress. See the WordPress integration page.

Other platforms

Add the script to the template of the page you chose, ideally in the head. Most site builders have a custom-code field for a single page. Avoid pasting the same Organization block into a global footer if your SEO plugin also outputs it.

Common mistakes

  • Using a logo URL that is blocked or changes. If crawlers cannot fetch the image, the logo does nothing. Host it on a stable, public URL.
  • Inconsistent names. Different spellings across your markup, site and profiles weaken the connection between them.
  • Padding sameAs with weak links. Directory spam pages, stale accounts and unrelated pages dilute the signal. Link only to profiles that are clearly yours.
  • Listing personal profiles. Staff social accounts belong in Person markup, not in the organization’s sameAs.
  • Duplicate Organization blocks. A theme, an SEO plugin and a hand-pasted block can all output one. Keep exactly one source.
  • Publishing placeholder or fake details. A made-up address, phone number or founding date is misleading. Omit what you do not have.
  • Using personal email addresses. They get harvested and go stale. Use role addresses.
  • Marking up details that are not visible anywhere on your site. Facts in the markup should be supported by the visible site.
  • Wrong type for the business. Calling a local shop a plain Organization is valid, but you lose the chance to use LocalBusiness properties. Calling a software company a LocalBusiness is misleading.
  • Forgetting to update after a rebrand. Old names and logos in markup can persist in knowledge systems for a long time.

Frequently asked questions

Do I need Organization schema?

It is not required, and your pages will be indexed without it. It is a low-effort way to state your basic facts clearly, and it is most useful for smaller or newer brands and for names that are easy to confuse with other things. It takes a few minutes to add and costs nothing to maintain once it is correct.

Will Organization schema get me a Google knowledge panel?

It can contribute, but it does not guarantee one. Knowledge panels depend on whether Google has enough reliable information about the entity from many sources. Your markup supplies your side of the story. Independent coverage, consistent profiles and a recognizable brand supply the rest.

Does Organization schema help with ChatGPT, Gemini or Perplexity?

It can help these systems resolve who you are when they read your page, but no provider has published exactly how markup is used in answer generation, so there is no guarantee. The more dependable benefit is the discipline: clear identity, consistent facts and verified profiles across the web, which every engine draws on.

What should I put in sameAs?

Your official profiles on other platforms: LinkedIn company page, YouTube, X, GitHub, Crunchbase, Wikipedia and Wikidata if they exist. Use full canonical URLs. Leave out anything you do not control, anything outdated and anything that is not specifically about your organization.

Should the logo be a PNG, SVG or JPG?

Use a format that crawlers and Google Images support. PNG, JPG and WebP are safe, and a square or near-square image of at least 112 by 112 pixels is the minimum guidance from Google. A larger version such as 512 by 512 pixels is a sensible choice. Check that it looks right on a white background.

Can I use the same markup on every page?

You can, but there is little reason to. The Organization entity needs to be defined once, on your home page or About page. Other pages can reference it by @id from their own markup, such as an Article’s publisher. Repeating the full block everywhere just adds duplication and can cause conflicts.

Should I include a phone number?

Only if you want it public and answered. A phone number in markup can be quoted by search and assistant products. Give it with the country code, and attach it to a ContactPoint with a clear contact type. If you do not take calls, leave it out and use an email contact point instead.

How do I test my Organization markup?

Use the Schema Markup Validator at validator.schema.org to confirm syntax and types, and the Rich Results Test to see how Google reads the page. In Search Console, check the enhancement and structured-data reports for errors after Google has crawled the page. Then compare your markup against your site and profiles for consistency.

Go further with aeoora

An Organization block is the foundation of your brand’s identity online, but it is only one part of how AI engines see you. aeoora Cloud shows you how ChatGPT, Gemini, Perplexity, Claude and Google’s AI features actually describe your brand, which sources they cite, and where they get facts about you wrong, so you can fix the pages and profiles behind the answers. On Signal and above, the schema generator in the GEO tools can produce JSON-LD for your pages, and the Site Audit checks structured data across your whole site. Compare plans or start a 2-day free trial.

Using WordPress? The free aeoora plugin handles schema without duplicates, along with llms.txt, Markdown pages and AI crawler rules. Read about the WordPress integration. You can also try the other free tools, including the FAQ and Article schema generators.