Blog

Organization Schema: Template and Examples

Organization schema is a block of schema.org structured data, usually JSON-LD, that tells search engines who runs a website: the official name, logo, URL, contact details, social profiles and business identifiers. You add it once, on your home page or About page. It doesn’t need to go on every page. Google’s organization structured data documentation says it has no required properties. Google can use the markup to work out which logo to show in Search results and your knowledge panel, and to tell your organization apart from others with similar names.

This guide gives you four templates you can paste and edit: a basic company, an ecommerce store (OnlineStore), a local business, and an author (Person) block for the people who write your content. Each property used comes from the current schema.org and Google Search Central docs. You’ll also see how a few real sites structure their markup and what Google and Bing say about structured data in AI answers. Last updated: November 3, 2026.

What Is Organization Schema?

Organization is a schema.org type that schema.org defines as “an organization such as a school, NGO, corporation, club, etc.” Organization schema is that type written into your page code, so machines get a clean, labeled version of facts that are already visible to people.

Google splits the properties into two jobs. Some, like iso6523Code and naics, work behind the scenes to tell your organization apart from others. Others can change what people see, such as the logo shown in Search results and your knowledge panel. Merchants can also feed details like return policy, address and contact information into their merchant knowledge panel and brand profile (Google Search Central).

It’s one of the most common schema types on the web. Schema.org’s usage counter, based on monthly aggregations from Google’s web index, lists Organization on 10M+ domains as of August 2026 (schema.org).

Where Should Organization Schema Go?

Google gives three placement rules in its technical guidelines:

  1. Put it on one page. Use your home page or a single page that describes the organization, such as the About page. You don’t need it on every page.
  2. Use the most specific type. An ecommerce site should use OnlineStore rather than the broader OnlineBusiness. A restaurant or physical store should use the most specific subtype of LocalBusiness and follow Google’s local business fields too.
  3. Keep it consistent with your site name. Google asks you to use the same name and alternateName you use for your site name.

WordPress SEO plugins such as Yoast and Rank Math often output an Organization node on every page as part of a larger @graph. Google’s guidance says you don’t need it everywhere; it doesn’t say repeating it is a problem. What matters is that every copy says the same thing.

Which Organization subtype should you use?

Schema.org lists a long set of more specific types under Organization, including Corporation, EducationalOrganization, GovernmentOrganization, LocalBusiness, MedicalOrganization, NGO, NewsMediaOrganization and OnlineBusiness (schema.org). Pick the one that matches what you are:

If your site is…Use this @typeNotes
A company, agency, SaaS or publisherOrganization (or Corporation)The default. Most B2B sites stop here.
An online-only storeOnlineStoreSchema.org’s hierarchy is Organization > OnlineBusiness > OnlineStore. Google recommends it for ecommerce sites.
A shop, restaurant, clinic or office people visitA LocalBusiness subtype (for example Restaurant, Dentist)Google requires name and address for local business markup.
A news publisherNewsMediaOrganizationSchema.org has news-specific policy properties, such as actionableFeedbackPolicy.
A nonprofitNGOSame core properties as Organization.

Organization Schema Properties at a Glance

These are the properties Google documents for Organization. None are required, so add the ones that are true and visible for your business.

PropertyWhat it tells GoogleTip from Google’s docs
nameYour organization’s nameMatch the name you use for your site name
alternateNameAnother common name you go byUse for acronyms or short names
legalNameRegistered legal nameOnly if it differs from name
urlYour websiteHelps Google uniquely identify the organization
logoLogo for Search results and knowledge panelsAt least 112x112px, crawlable, and it should look right on a white background
sameAsProfiles on other sitesSocial or review profiles; you can list several
descriptionWhat the organization doesA plain description, not a slogan
addressPhysical or mailing addressYou can list several addresses
contactPointBest way for users to reach youInclude country and area code on phone numbers
telephone, emailPrimary contact methodsPhone should include country code
foundingDateWhen you were foundedISO 8601 format
numberOfEmployeesHeadcount or a rangeUse a QuantitativeValue
iso6523Code, vatID, taxID, naics, duns, leiCodeOfficial business identifiersGoogle prefers iso6523Code with a prefix (0060 DUNS, 0088 GLN, 0199 LEI) over duns and leiCode
hasMerchantReturnPolicy, hasShippingServiceStore-wide return and shipping policiesFor merchants; product-level markup can override them

Schema.org supports many more Organization properties, such as founder, knowsAbout, parentOrganization, subOrganization, brand, slogan and areaServed (schema.org). Google doesn’t list them in its organization docs, but they’re valid and can add context for other systems that read your markup.

Template 1: Basic Organization Schema (JSON-LD)

Use this for a company, agency, SaaS product or publisher. Paste it into a <script type="application/ld+json"> tag on your home page or About page, replace every value, and delete any line you can’t fill in truthfully.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com/#organization",
  "name": "Example Co",
  "alternateName": "ExCo",
  "legalName": "Example Company LLC",
  "url": "https://www.example.com/",
  "logo": {
    "@type": "ImageObject",
    "url": "https://www.example.com/images/logo-512.png",
    "width": 512,
    "height": 512
  },
  "description": "Example Co builds scheduling software for dental clinics.",
  "foundingDate": "2019-04-01",
  "founder": {
    "@type": "Person",
    "name": "Jane Doe"
  },
  "email": "hello@example.com",
  "telephone": "+1-555-010-0199",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Example Ave, Suite 200",
    "addressLocality": "Austin",
    "addressRegion": "TX",
    "postalCode": "78701",
    "addressCountry": "US"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@example.com",
    "telephone": "+1-555-010-0100"
  },
  "sameAs": [
    "https://www.linkedin.com/company/example-co",
    "https://x.com/exampleco",
    "https://www.youtube.com/@exampleco",
    "https://www.wikidata.org/wiki/Q00000000"
  ],
  "knowsAbout": ["Dental practice management", "Appointment scheduling"]
}

A few notes on the fields:

  • @id is a JSON-LD identifier, not a schema.org property. It gives the node a stable name so other blocks (your WebSite, articles and authors) can point to it instead of repeating it.
  • sameAs should point to pages that, in schema.org’s words, “unambiguously” indicate the entity’s identity, such as a Wikipedia page, Wikidata entry or official profile (schema.org). Only list profiles you control or that are clearly about you.
  • logo can be a plain URL or an ImageObject. If you use ImageObject, Google needs a valid url or contentUrl.

Template 2: Ecommerce Organization Schema (OnlineStore)

For an online store, swap the type to OnlineStore, which schema.org defines simply as “an eCommerce site.” Google’s own OnlineStore example adds a store-wide return policy and shipping service, which can feed your merchant knowledge panel. This template keeps the return policy and leaves shipping out for brevity. Google’s merchant return policy documentation covers the full set of return fields.

{
  "@context": "https://schema.org",
  "@type": "OnlineStore",
  "@id": "https://www.example-store.com/#organization",
  "name": "Example Store",
  "url": "https://www.example-store.com/",
  "logo": "https://www.example-store.com/assets/logo.png",
  "description": "Example Store sells refillable cleaning products online.",
  "sameAs": [
    "https://www.instagram.com/examplestore",
    "https://www.tiktok.com/@examplestore",
    "https://www.trustpilot.com/review/example-store.com"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "email": "support@example-store.com",
    "telephone": "+1-555-010-0150"
  },
  "hasMerchantReturnPolicy": {
    "@type": "MerchantReturnPolicy",
    "applicableCountry": ["US", "CA"],
    "returnPolicyCountry": "US",
    "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
    "merchantReturnDays": 30,
    "returnMethod": "https://schema.org/ReturnByMail",
    "returnFees": "https://schema.org/FreeReturn",
    "refundType": "https://schema.org/FullRefund"
  }
}

The return values here are placeholders. Copy your real policy, word for word in meaning, from your returns page. If some products have different rules, Google says you can override the store-wide policy in your product (merchant listing) markup.

Template 3: Local Business Variant

If customers visit you in person, use a LocalBusiness subtype instead of plain Organization. Schema.org describes LocalBusiness as “a particular physical business or branch of an organization,” such as a restaurant, a bank branch or a medical practice. Google’s local business documentation requires two properties, name and address, and recommends geo, openingHoursSpecification, telephone, url and priceRange, among others.

{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "@id": "https://www.example-dental.com/#organization",
  "name": "Example Dental Austin",
  "url": "https://www.example-dental.com/",
  "logo": "https://www.example-dental.com/images/logo.png",
  "image": "https://www.example-dental.com/images/clinic-front.jpg",
  "telephone": "+1-555-010-0177",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "200 Example St",
    "addressLocality": "Austin",
    "addressRegion": "TX",
    "postalCode": "78702",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 30.26715,
    "longitude": -97.74306
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:00:00",
      "closes": "17:00:00"
    }
  ],
  "sameAs": [
    "https://www.facebook.com/exampledental",
    "https://www.yelp.com/biz/example-dental-austin"
  ]
}

Local details that trip people up:

  • Coordinates need at least 5 decimal places for latitude and longitude, according to Google.
  • priceRange must be under 100 characters, or Google won’t show it.
  • Each location gets its own markup. The url should be the specific location’s page, and it must be a working link.
  • Keep it in sync with your Business Profile. Google’s AI features guidance tells site owners to keep Merchant Center and Business Profile information up to date.

Author Schema: Marking Up the People Behind Your Content

Author schema is Person markup attached to the author property of an article. Organization schema says who runs the site. Author schema says who wrote each page. Google’s Article structured data documentation lists author as a recommended property and publishes author markup best practices:

  • Include every author shown on the page in the markup.
  • Give each author their own entry. Don’t merge two names into one author field.
  • Add @type and url (or sameAs). Google “strongly” recommends them and says it can understand both url and sameAs when disambiguating authors.
  • Put only the name in author.name. No job title, no “posted by,” no honorifics and no publisher name. Use jobTitle, honorificPrefix and publisher for those.

Author schema template

This snippet goes on the article page. It references the Organization from Template 1 by @id, so you don’t have to repeat the company details.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Person",
      "@id": "https://www.example.com/#/schema/person/jane-doe",
      "name": "Jane Doe",
      "url": "https://www.example.com/authors/jane-doe/",
      "image": "https://www.example.com/images/jane-doe.jpg",
      "jobTitle": "Head of Content",
      "worksFor": { "@id": "https://www.example.com/#organization" },
      "knowsAbout": ["Technical SEO", "Structured data"],
      "sameAs": [
        "https://www.linkedin.com/in/janedoe-example",
        "https://x.com/janedoe_example"
      ]
    },
    {
      "@type": "BlogPosting",
      "@id": "https://www.example.com/organization-schema/#article",
      "headline": "Organization Schema: Template and Examples",
      "datePublished": "2026-11-03T08:00:00-06:00",
      "dateModified": "2026-11-03T08:00:00-06:00",
      "author": [{ "@id": "https://www.example.com/#/schema/person/jane-doe" }],
      "publisher": { "@id": "https://www.example.com/#organization" },
      "mainEntityOfPage": "https://www.example.com/organization-schema/"
    }
  ]
}

All the Person properties used here (jobTitle, worksFor, knowsAbout, sameAs) are standard on schema.org/Person. If the author has a profile page on your site, Google recommends marking that page up with ProfilePage structured data and the person as its mainEntity.

Real Organization Schema Examples

Templates are tidy. Live markup is messier. Here is what four sites output on their home pages or blog posts when we fetched them on November 3, 2026. The values are theirs; we only list which properties they use.

SitePage checked@type usedProperties on the organization node
YoastHome page and a blog postOrganization plus Brand, in an @graph with @idname, url, logo, image, sameAs, numberOfEmployees, founder, foundingDate, slogan, description, legalName, parentOrganization, memberOf
Rank MathHome page and blogOrganization in an @graph with @idname, url, sameAs, email, logo
Warby ParkerHome pageOrganizationname, url, logo, description, foundingDate, founders, sameAs, location, contactPoint, hasMerchantReturnPolicy
GymsharkHome pageOrganization next to a WebSite blockname, url, logo, sameAs

A few patterns stand out:

  • The plugin-style @graph is the norm on WordPress sites. Yoast’s blog post links its Article, WebPage, WebSite, Organization and Person nodes by @id. Its author node carries jobTitle, knowsAbout, sameAs and worksFor, which is close to the author template above.
  • Small markup is still valid. Gymshark’s four-property block covers name, site, logo and profiles. That’s the minimum that does the disambiguation job.
  • Ecommerce brands don’t always use OnlineStore. Both stores use plain Organization. Google recommends the more specific type, so if you’re building from scratch, start with OnlineStore.
  • Watch for superseded properties. Warby Parker uses founders. Schema.org now lists founder as superseding it, so use founder in new markup.

Organization Schema and AI Visibility

Answer engines have to decide which “Example Co” a question is about before they can describe it or cite it. Entity markup gives them a structured version of facts they’d otherwise piece together from text: your official name, your URL, your logo and the profiles that confirm you’re the same entity across sites.

What the platforms actually say is more cautious than most schema marketing:

  • Google says there are no special optimizations needed to appear in AI Overviews or AI Mode, and “no special schema.org structured data that you need to add.” Its SEO checklist for AI features does include “making sure your structured data matches the visible text on the page” (Google Search Central).
  • Bing says in its Webmaster Guidelines that structured data “may support clearer grounding but does not guarantee visibility or grounding traffic,” and that markup must reflect visible content. A separate guideline asks you to “define entities clearly and consistently” across people, organizations, products and locations, because “clear entity definition improves grounding visibility and citation accuracy.”
  • Microsoft Advertising’s guide to AI search answers describes schema as code that “helps search engines and AI systems understand your content” and includes “use schema” in its checklist.

So treat Organization and author schema as consistency work, not a ranking trick. The markup helps most when it agrees with everything else: the name on your About page, your LinkedIn company page, your Google Business Profile and the bylines on your posts. If those disagree, markup won’t settle it.

The schema only counts if crawlers can fetch the page that carries it. If you block AI crawlers in robots.txt, they never see your JSON-LD. Check your rules against the AI crawler list and these robots.txt examples.

How to Test Organization Schema

Google’s process for organization markup is: add the properties, validate with the Rich Results Test, deploy, then check a live URL with Search Console’s URL Inspection tool. The page has to be reachable by Google. It can’t be blocked by robots.txt, a noindex tag or a login.

Two free tools cover most checks:

If you use a JSON-LD generator or schema markup generator, run its output through both tools anyway. Generators often leave placeholder values or add properties you can’t support on the page.

Common Organization Schema Mistakes

  • Marking up facts that aren’t on the page. Google’s general structured data guidelines say not to mark up content that’s hidden from readers, and Bing says misleading markup “may be ignored.”
  • Different names in different places. “Example Co” in the markup, “Example Company, Inc.” in the footer and “ExampleCo” on LinkedIn makes the entity harder to resolve. Pick one name and put the variants in alternateName and legalName.
  • A logo that fails Google’s checks. It needs to be at least 112x112px, crawlable and indexable, in a format Google Images supports, and readable on a white background.
  • Padding sameAs. Directory listings you don’t control, or profiles for a different company with the same name, add confusion.
  • Two plugins outputting two Organization nodes with different values. Turn one off or align them.
  • Using Organization when a subtype fits. Stores and local businesses should use OnlineStore or a LocalBusiness subtype.
  • Stale details. Old phone numbers, moved addresses and retired social accounts linger in markup long after the footer is fixed.

Frequently Asked Questions

What is organization schema?

Organization schema is schema.org structured data that describes the company or group behind a website: its name, logo, URL, contact details, social profiles and identifiers. It’s usually added as JSON-LD on the home page or About page.

Where do I put organization schema?

Put it on your home page or on one page that describes your organization, such as the About page. Google says you don’t need it on every page. Google says JSON-LD can sit in a script tag in either the head or the body of the page.

Is organization schema required for SEO?

No. Google lists no required properties and says structured data doesn’t guarantee any feature. It can help Google choose your logo for Search results and knowledge panels and tell your organization apart from others with the same name.

What is the difference between organization schema and author schema?

Organization schema describes the business that runs the site. Author schema is Person markup in an article’s author property that describes who wrote that page. On a well-structured site, the author’s worksFor points to the Organization by @id.

Should an ecommerce site use Organization or OnlineStore?

Use OnlineStore. Google recommends the most specific schema.org subtype, and for ecommerce sites it names OnlineStore specifically. OnlineStore inherits every Organization property, and Google lets merchants add store-wide return and shipping policies to it.

Does organization schema help with ChatGPT and AI Overviews?

It can help with entity clarity, but no platform promises citations for it. Google says no special schema is needed for AI Overviews or AI Mode. Bing says structured data may support clearer grounding but doesn’t guarantee visibility. Accurate, consistent markup is the part you control.

How do I check if my organization schema works?

Run the page through Google’s Rich Results Test and the Schema Markup Validator, fix any errors, then use URL Inspection in Search Console on the live page. Make sure robots.txt, noindex or a login isn’t blocking the page.


Can AI engines read your site?

Check any page for free: crawler access for ChatGPT, Perplexity, Claude and Google AI Overviews, plus the fixes that matter most.

Run the free checker

More guides

All articles