Organization schema: every property and what it actually does

Most schema types buy you something you can see. Organization is not one of them.

It is still one of the first blocks we add to a client site.

This page is the property table — what each field is for, which ones Google says it actually uses, and what you lose by leaving one out. If the format itself is new to you, read our wider guide to how schema markup works and where Google uses it first, then come back for the detail.

What Organization schema is

Organization schema is a block of code that states the administrative facts about a company and links them to the other places that represent the same company online.

Google's own documentation says the markup "helps Google understand an organisation's administrative details" and tell it apart from other organisations in search results.

It describes four kinds of fact:

• Identity — the name you trade under, your legal name, your website.
• Representation — your logo and the profiles that are also you.
• Contact — how a person reaches you, and from where.
• Provenance — founding date, headcount, registration and tax identifiers.

Organization is one of the 25 structured data types Google Search currently supports (search gallery, last updated 16 October 2026). FAQ and HowTo are no longer on that list. Organization is.

What it gets you — and what it does not

This is where most articles on the topic overpromise. Here is the honest version, with Google's wording.

Google also states plainly that it "does not guarantee that features that consume structured data will show up in search results". So treat anyone promising a panel with suspicion.

So the sentence to hold on to: still worth adding, but it will not draw a rich result.

The Organization property table

Google's documentation is unusually blunt here: "There are no required properties; instead, we recommend adding as many properties that are relevant to your organisation."

So the useful split is not required versus optional. It is priority — what to fill in first, and what each field buys you.

Worth adding when they apply: alternateName for the other name you are known by, description, email and telephone. Google also supports identifier fields — iso6523Code, naics, taxID, vatID, duns — and describes them as being "used behind the scenes to disambiguate your organisation". Nobody sees them. They still help.

One choice to get right first: use the most specific schema.org subtype that fits. Google recommends OnlineStore for ecommerce over the vaguer OnlineBusiness.

Logo is the one property with hard rules

Every other property is a free-text or date field. The logo has technical requirements, and they are the single most common reason a valid-looking block does nothing.

• At least 112 × 112 pixels. Google's wording: "The image must be 112x112px, at minimum."
• Crawlable and indexable. An image URL disallowed in robots.txt or behind a login cannot be used.
• A format Google Images supports. PNG, JPEG, WebP and SVG are all fine.
• Readable on white. Google notes light logos may not display well on white — a white wordmark on a transparent PNG disappears.

Use a stable, permanent URL. If your theme regenerates image paths on optimisation, the reference quietly breaks later.

sameAs is the entity-reconciliation signal

If you only fix one thing after reading this, fix sameAs.

Google describes it as "the URL of a page on another website with additional information about your organisation", and multiple values are allowed. In practice it bridges your site and every other profile describing the same company — which is why it matters far more than headcount or founding date.

This is the mechanism behind what we cover in entity-based SEO: search engines do not store "a website", they store a thing with attributes and links to corroborating sources. sameAs hands them the links.

What we see on Indian brands (first-hand)

This is our own observation across client accounts, not a Google-documented ranking — treat it as the order we work in, not a law.

The profiles we see reflected back most reliably for Indian brands are the complete, verified ones whose handle matches the brand name exactly. The order we add them in:

1. LinkedIn company page — the most consistently picked-up profile for B2B and services brands in our accounts, and usually the most complete one a company already has.
2. Wikidata or Wikipedia entry — only where one genuinely exists. Where it does, it is the strongest corroboration available. Do not create one for a brand that does not merit it.
3. YouTube channel — reliable when the channel is branded and active, less so for a dormant one.
4. Instagram and Facebook — these get picked up when the handle matches the brand name. Where the handle is an abbreviation or has a suffix, we see it ignored more often.
5. Crunchbase, industry bodies and verified directory listings — added last, and only where the listing is claimed and the details match the site.

Two rules we hold to. Only list profiles you control and keep current — a dead handle in sameAs is a contradiction, not a signal. And keep the name, address and phone number identical across all of them, which is the same discipline behind citation and NAP consistency.

Our guide to Google's Knowledge Graph covers where those facts land.

Organization or LocalBusiness?

Short version: Organization is the entity, LocalBusiness is a place you can visit.

LocalBusiness is a subtype of Organization built for physical, visitable locations — the properties it adds are about opening hours, a street you can turn up at, and a specific branch. If customers come to you, you want it, and Google asks you to use the most specific LocalBusiness subtype that fits.

Organization describes the company itself, whether or not anyone can walk in. A SaaS business with no footfall uses Organization and stops there. A clinic chain uses Organization for the brand and LocalBusiness on each branch page.

LocalBusiness properties and errors are a separate topic, and we will not half-cover them here.

Where to put it, and how to add it safely

Placement is simpler than people assume.

1. One page only. Google says to put it on your home page, or on a single page that describes the company such as an about page. You do not need it on every page.
2. Check what your plugin already emits. Most SEO plugins output an Organization block automatically. Two competing blocks with different values is worse than one imperfect block.
3. Add it where the theme outputs it, not in the post body. Many WordPress setups strip script tags from post and page content, so a block pasted into the editor silently vanishes. In All in One SEO it goes into Schema > Custom Schema; otherwise use your theme's header hook.
4. Validate, then leave it alone. Run it through a validator once, fix what it flags, and re-check only when the company's facts change.

A minimal block worth copying — the shape, not the values:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Textiles",
  "alternateName": "Example",
  "url": "https://example.in/",
  "logo": "https://example.in/img/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example-textiles/",
    "https://www.youtube.com/@exampletextiles",
    "https://www.instagram.com/exampletextiles/"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "Customer Service",
    "telephone": "+91-22-1234-5678",
    "email": "hello@example.in"
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 MG Road",
    "addressLocality": "Mumbai",
    "addressRegion": "MH",
    "postalCode": "400001",
    "addressCountry": "IN"
  },
  "legalName": "Example Textiles Private Limited",
  "foundingDate": "2016-04-01"
}

Wrap that object in a JSON-LD script tag wherever your setup emits schema. If you would rather not hand-write it, our schema markup generator builds the block and the wrapper for you.

Mistakes we fix most often

• Two Organization blocks disagreeing. A plugin emits one, a developer hard-coded another, and the names differ by a "Pvt Ltd".
• A logo URL that cannot be fetched. Blocked in robots.txt, or on a CDN path that has since changed.
• sameAs stuffed with everything. Abandoned profiles and listings someone else created dilute rather than confirm.
• name that does not match the site name. Pick one trading name and use it everywhere, with the variant in alternateName.
• Loose data types. "50+" in numberOfEmployees, "2016" in foundingDate. Use QuantitativeValue and ISO 8601.
• Marking up a company that is not you. Organization describes the site's owner, not a brand you resell.

Where entity data pays off next

Organization schema is a one-time job that stays done. It is the cheapest part of being identifiable.

The expensive part is the corroboration — being described consistently in places Google already trusts, which is what we cover in our guide to brand mentions and unlinked citations. Markup states who you are. Everything else is the evidence.