Complete Guide to Organization + Person Schema (E-E-A-T Foundation)

What Is Organization + Person Schema

Organization schema reports the identity of companies, brands, and organizations as structured data. Person schema specifies the identity and expertise of content authors, founders, and experts. E-E-A-T signals are maximized when both schemas are used together rather than alone.

In E-E-A-T quality assessment, Google heavily weighs "who operates the site and who wrote this content." Organization and Person schemas answer these questions in a machine-readable form.

TL;DR

Organization + Person schema summary: ① No official required properties → start with available information ② sameAs is key — connect authority via external verification such as Wikipedia, Wikidata, LinkedIn, and X ③ Specify expertise areas with Person knowsAbout → AI category trust signal ④ Referencing both as author and publisher in Article and BlogPosting doubles the effect.

When to Use

Organization: Sites operated by companies, brands, institutions, or nonprofits. Insert once on the homepage or About page as the default, referenced as the site-wide publisher.

Person: Blog author pages, expert profile pages, team introduction pages. Referenced as author in each Article and BlogPosting.

Not applicable: Simple landing pages with no operating entity, auto-generated catalog pages.

Significance from an AEO and AI Citation Perspective

AI answer engines implicitly evaluate "can the entity providing this information be trusted?" when selecting sources. Organization + Person schemas provide structural evidence for this judgment.

External authority sources linked via sameAs (Wikipedia, Wikidata, LinkedIn) strengthen the signal that the entity is already recognized in data the AI model was trained on. Content from entities known in the knowledge graph tends to receive higher citation priority than unverified anonymous sources.

Organization Property Reference

Recommended properties per Google official documentation (verified June 2026). All properties are optional.

Person Property Reference

Minimal Example (Organization)

No required properties, but start with at least name, url, logo, and sameAs.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://kroffle.com/#organization",
  "name": "Kroffle",
  "url": "https://kroffle.com",
  "logo": "https://kroffle.com/images/logo.png"
}

Recommended Example (Organization + Person Linked)

A practical example including sameAs, address, contactPoint, and Person references.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://kroffle.com/#organization",
      "name": "Kroffle",
      "legalName": "Kroffle Inc.",
      "url": "https://kroffle.com",
      "logo": {
        "@type": "ImageObject",
        "url": "https://kroffle.com/images/logo.png",
        "width": 200,
        "height": 200
      },
      "foundingDate": "2022",
      "taxID": "000-00-00000",
      "telephone": "+82-2-0000-0000",
      "email": "hello@kroffle.com",
      "address": {
        "@type": "PostalAddress",
        "addressCountry": "KR",
        "addressRegion": "Seoul",
        "addressLocality": "Gangnam-gu",
        "streetAddress": "123 Teheran-ro"
      },
      "sameAs": [
        "https://www.linkedin.com/company/kroffle",
        "https://x.com/kroffle",
        "https://www.wikidata.org/wiki/Q000000"
      ],
      "founder": { "@id": "https://kroffle.com/team/ceo#person" }
    },
    {
      "@type": "Person",
      "@id": "https://kroffle.com/team/ceo#person",
      "name": "Jane Smith",
      "familyName": "Smith",
      "givenName": "Jane",
      "jobTitle": "CEO",
      "worksFor": { "@id": "https://kroffle.com/#organization" },
      "url": "https://kroffle.com/team/ceo",
      "image": "https://kroffle.com/images/team/ceo.jpg",
      "sameAs": [
        "https://www.linkedin.com/in/hobeom-im",
        "https://x.com/hobeom"
      ],
      "knowsAbout": ["SEO", "AEO", "AI search optimization", "content marketing"],
      "knowsLanguage": "ko"
    }
  ]
}

Using @graph bundles multiple schema objects in a single <script> tag and enables cross-referencing via @id.

Adaptation for the Korean Market

Name notation: Korean names work with name: "Hong Gildong", but specifying familyName: "Hong" and givenName: "Gildong" separately is recommended for compatibility with English systems. Mixing Korean order (family + given) and Western order (given + family) can make same-person mapping in the knowledge graph difficult.

Business registration number: Insert the business registration number in the taxID property. Google official documentation recommends this as a trust signal.

Address format: Write Korean addresses in reverse order within PostalAddress. addressCountry: "KR", addressRegion: "Seoul" (province/city), addressLocality: "Gangnam-gu" (district), streetAddress: "123 Teheran-ro" (street address).

Wikidata: If a Korean company has a Wikidata entry, include it in sameAs. It is one of the strongest external authority signals for entity recognition in AI models.

Common Mistakes

Wrong example: Including job title in Person name

"name": "CEO Jane Smith"

Correct example: Pure name in name, job title in separate jobTitle

"name": "Jane Smith",
"jobTitle": "CEO"

Wrong example: Entering sameAs as a single URL

"sameAs": "https://www.linkedin.com/in/hobeom-im"

Correct example: sameAs as an array with multiple external profiles

"sameAs": [
  "https://www.linkedin.com/in/hobeom-im",
  "https://x.com/hobeom"
]

Combination with Other Schemas

Organization + Person is more effective when linked to other schemas than used alone.

• Article · BlogPosting: Reference Person @id in author, Organization @id in publisher
• LocalBusiness: Extend as a subtype of Organization
• ProfilePage: Wrap Person schema as mainEntity

Validation Methods

1. Google Rich Results Test: https://search.google.com/test/rich-results — enter URL or code snippet directly
2. Schema Markup Validator: https://validator.schema.org — verify Schema.org standard compliance
3. Google Search Console: Monitor recognition in the "Enhancements" tab after implementation

Frequently Asked Questions

Q. Must Organization schema be placed only on the homepage?
A. Google official documentation recommends placement on the homepage or About page. The standard approach is a single Organization schema representing the entire site, referenced via @id. You do not need to duplicate it on every page.

Q. Which URLs should I put in sameAs?
A. Priority order: ① Wikidata entry ② Wikipedia page ③ LinkedIn company or personal page ④ Official X and Instagram accounts. The URL must be accessible and contain organization or person information.

Q. Must I use @graph?
A. No. A single schema can be written directly without @graph. However, when cross-referencing multiple schemas such as Organization + Person via @id, @graph provides clearer structure.

Q. Must I add Person schema to every blog post?
A. Referencing a Person object in the Article/BlogPosting author field is sufficient. Referencing via @id is recommended rather than repeating the full Person schema on every page.

References

• Google official Organization documentation: https://developers.google.com/search/docs/appearance/structured-data/organization (verified June 2026)
• Google official ProfilePage documentation: https://developers.google.com/search/docs/appearance/structured-data/profile-page (verified June 2026)
• Schema.org Organization: https://schema.org/Organization
• Schema.org Person: https://schema.org/Person