Person Schema

People Are Entities Too

Every organization is run by people. Google knows this, and it looks for Person entities associated with Organization entities. When Google can identify a connection between a recognized Person (a founder, CEO, or key expert) and your Organization, both entities become stronger. The person lends credibility to the organization, and the organization provides context for the person.

This matters especially for E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), Google's quality framework. Content published by a recognized Person entity with established expertise ranks better than anonymous content, even if the text is identical.

Core Person Properties

The Person-Organization Relationship

The most powerful aspect of Person schema is the bidirectional relationship it creates with your Organization:

On the Organization schema (homepage), you reference the founder using the founder property. On the Person schema (bio page), you reference the organization using the worksFor property. Google follows both links and confirms the relationship from both sides.

The @id Pattern for Cross-Page Linking

When your Person schema and Organization schema are on different pages, use the @id property to link them. The @id is a unique identifier (typically a URL with a fragment) that lets Google know two schema blocks on different pages refer to the same entity.

// On homepage (Organization schema):
"founder": {
  "@type": "Person",
  "@id": "https://yoursite.com/about/#founder",
  "name": "Ahmad Hidayat"
}

// On bio page (Person schema):
{
  "@type": "Person",
  "@id": "https://yoursite.com/about/#founder",
  "name": "Ahmad Hidayat",
  "jobTitle": "Founder & Director",
  "worksFor": {
    "@type": "Organization",
    "@id": "https://yoursite.com/#organization",
    "name": "PT Arsindo Perkasa"
  }
}

The matching @id values tell Google: the "founder" referenced in the Organization schema is the same person described in detail on the bio page.

Complete Person Schema Example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://yoursite.com/about/#founder",
  "name": "Ahmad Hidayat",
  "jobTitle": "Founder and Director",
  "description": "Industrial pump specialist with 20 years of experience in manufacturing and distribution across Indonesia.",
  "url": "https://yoursite.com/about/",
  "image": "https://yoursite.com/images/ahmad-hidayat.jpg",
  "worksFor": {
    "@type": "Organization",
    "@id": "https://yoursite.com/#organization",
    "name": "PT Arsindo Perkasa"
  },
  "alumniOf": {
    "@type": "EducationalOrganization",
    "name": "Institut Teknologi Bandung"
  },
  "knowsAbout": [
    "industrial pumps",
    "fluid mechanics",
    "pump system design",
    "water infrastructure"
  ],
  "sameAs": [
    "https://www.linkedin.com/in/ahmadhidayat",
    "https://twitter.com/ahmadhidayat"
  ]
}
</script>

Where to Place Person Schema

Person schema goes on the page that is about that person. This could be:

Do not place Person schema on every page of the site. Place it once, on the person's canonical page. Reference it from other pages using the @id pattern.

Further Reading

• Person - Schema.org Type - The complete property list for Person in the Schema.org vocabulary.
• Organization Structured Data - Google's documentation, including the founder property linking to Person entities.
• JSON-LD Schema Markup: Complete Implementation Guide - Includes Person schema patterns and cross-entity linking.
• LocalBusiness Schema Guide - Schema App's guide covering Person entities within business schema contexts.