Person schema: author pages that prove expertise

Why author information is crucial for AI

In a world where AI models increasingly determine which content gets cited and recommended, the question "who wrote this?" has become at least as important as "what is written?" AI models evaluate the trustworthiness of content not only based on the content itself, but also based on the authority and expertise of the author. This is the core of the E-E-A-T philosophy: Experience, Expertise, Authoritativeness and Trustworthiness.

Person schema from Schema.org is the means by which you make author information machine-readable. By adding structured data about your authors, you give search engines and AI models the information they need to verify the expertise behind your content. This closely aligns with the E-E-A-T strategy we discussed extensively earlier.

Without Person schema, your author information is unstructured text that machines have to interpret. With Person schema, it is an unambiguous dataset that can be directly processed, linked and verified.

Person schema: the basics

The Person schema describes an individual with properties such as name, job title, employer, social profiles and expertise. For author pages, you focus on the properties that communicate expertise and authority.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jan de Vries",
  "jobTitle": "Senior AEO Consultant",
  "worksFor": {
    "@type": "Organization",
    "name": "Kobalt",
    "url": "https://kobaltdigital.nl"
  },
  "url": "https://aeo-expert.nl/team/jan-de-vries",
  "image": "https://aeo-expert.nl/images/team/jan-de-vries.jpg",
  "description": "Jan de Vries is a Senior AEO Consultant at Kobalt with over 10 years of experience in SEO and content strategy.",
  "sameAs": [
    "https://www.linkedin.com/in/jandevries",
    "https://twitter.com/jandevries",
    "https://github.com/jandevries"
  ],
  "knowsAbout": [
    "Answer Engine Optimization",
    "Schema.org Markup",
    "E-E-A-T Optimization",
    "Technical SEO",
    "Content Strategy"
  ],
  "alumniOf": {
    "@type": "EducationalOrganization",
    "name": "University of Amsterdam"
  }
}
</script>

Let us break down the most important properties. The "name" and "jobTitle" are fundamental for identification. The "worksFor" links the author to an organization, which lends authority. The "sameAs" links are crucial: they connect the Person schema with external profiles, allowing AI models to verify the identity.

The power of knowsAbout

The "knowsAbout" property is particularly valuable for AI models. It is an explicit declaration of the author's areas of expertise. When an AI model encounters an article about Schema.org markup and the author has "Schema.org Markup" in their knowsAbout, this strengthens the relevance and trustworthiness of the article for that specific topic.

• Use specific, industry-recognized terms in knowsAbout. "SEO" is too broad; "Technical SEO" or "Schema.org Implementation" is more targeted.
• Limit yourself to 5 to 10 core areas. A list of 50 expertise areas dilutes the signal and looks unreliable.
• Align knowsAbout with the content the author actually publishes. Inconsistencies between claimed expertise and published content undermine trust.
• Update knowsAbout regularly as the author's expertise areas evolve.

Linking Person schema to articles

The Person schema on the author page is only half the story. The other half is linking the author to individual articles via the Article schema.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Person Schema: author pages that prove expertise",
  "author": {
    "@type": "Person",
    "@id": "https://aeo-expert.nl/team/jan-de-vries#person",
    "name": "Jan de Vries",
    "url": "https://aeo-expert.nl/team/jan-de-vries"
  },
  "datePublished": "2026-04-24",
  "publisher": {
    "@type": "Organization",
    "name": "AEO Expert",
    "url": "https://aeo-expert.nl"
  }
}
</script>

By using an @id in the Person object, you create a machine-readable link between the article and the full author page. AI models can follow this link to learn more about the author, including their expertise, work experience and sameAs profiles. This network of connections strengthens the entire trust profile of your content.

Building the ideal author page

An author page is more than a bio with a photo. It is a landing page for trust. Every element on the page should contribute to proving expertise and building authority.

1. Professional headshot and biography. Start with a clear photo and a bio that describes the relevant experience and expertise of the author. Mention specific results and projects, not just job titles.
2. List of publications on the site. Show all articles the author has written, preferably with date and category. This demonstrates that the expertise is not incidental but consistent.
3. External publications and speaking engagements. Mention articles on other platforms, conference presentations, podcasts and other public appearances. This strengthens external authority.
4. Social profiles and professional links. Link to LinkedIn, Twitter/X, GitHub and other relevant profiles. Ensure these match the sameAs links in the Person schema.
5. Qualifications and certifications. Mention relevant education, certifications and memberships of industry organizations.

The Person schema on the author page should reflect all these elements. The visible content and the structured data must tell a consistent story.

Advanced Person schema with @graph

For maximum effect, you combine the Person schema with other schema types in a @graph structure on the author page.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Person",
      "@id": "https://aeo-expert.nl/team/jan-de-vries#person",
      "name": "Jan de Vries",
      "jobTitle": "Senior AEO Consultant",
      "worksFor": { "@id": "https://aeo-expert.nl/#organization" },
      "url": "https://aeo-expert.nl/team/jan-de-vries",
      "image": "https://aeo-expert.nl/images/team/jan-de-vries.jpg",
      "sameAs": [
        "https://www.linkedin.com/in/jandevries",
        "https://twitter.com/jandevries"
      ],
      "knowsAbout": ["AEO", "Schema.org", "E-E-A-T", "Technical SEO"]
    },
    {
      "@type": "ProfilePage",
      "mainEntity": { "@id": "https://aeo-expert.nl/team/jan-de-vries#person" },
      "name": "Jan de Vries - AEO Expert",
      "url": "https://aeo-expert.nl/team/jan-de-vries",
      "breadcrumb": {
        "@type": "BreadcrumbList",
        "itemListElement": [
          { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://aeo-expert.nl/" },
          { "@type": "ListItem", "position": 2, "name": "Team", "item": "https://aeo-expert.nl/team" },
          { "@type": "ListItem", "position": 3, "name": "Jan de Vries" }
        ]
      }
    }
  ]
}
</script>

The @graph combines the Person schema with a ProfilePage type. The ProfilePage tells machines that this page is primarily about a person, via the "mainEntity" property. The BreadcrumbList places the author page in the site hierarchy.

Person schema and Google Knowledge Panel

A well-implemented Person schema can contribute to obtaining a Google Knowledge Panel for the author. The Knowledge Panel is the information block that appears on the right side of Google search results when you search for a person.

Google uses multiple signals to generate a Knowledge Panel, including Wikipedia/Wikidata entries, consistent sameAs links and structured Person data. The Person schema on your author page is one of those signals. Combined with strong sameAs links to verified profiles, you significantly increase the chance of a Knowledge Panel.

Although a Knowledge Panel is not guaranteed, every correctly implemented signal contributes. The combination of Person schema, consistent sameAs links, external publications and an active online presence forms the strongest case.

In the AI era, the author is just as important as the content. Person schema is the means by which you prove the expertise behind your words to machines that read increasingly critically.

Common mistakes with Person schema

• Not including sameAs links. Without external profile links, an AI model cannot verify the author's identity. Always add links to LinkedIn, Twitter/X and other relevant profiles.
• Using generic job titles. "Employee" or "Writer" says little. Use specific titles like "Senior SEO Consultant" or "Head of Content Strategy" that communicate expertise.
• Person schema only on articles, not on an author page. The schema on an article is a reference; the author page is the source. Without a dedicated author page with comprehensive Person schema, the foundation is missing.
• Inconsistent names between schema and visual content. If the schema says "J. de Vries" but the page shows "Jan de Vries", you create an inconsistency that can confuse machines.
• Overloading knowsAbout with irrelevant terms. Limit yourself to actual areas of expertise that are supported by published content.

Key takeaways

• Person schema makes author information machine-readable, allowing AI models to verify the expertise and trustworthiness behind your content.
• The knowsAbout property is particularly valuable: it explicitly declares the author's areas of expertise, strengthening the relevance of related articles.
• Link Person schema to articles via an @id reference, so AI models can follow the connection between author and content.
• Build a complete author page with bio, publications, external references and social profiles that are consistent with the Person schema.
• The combination of Person schema, sameAs links and consistently linked content contributes to the possibility of a Google Knowledge Panel.

Frequently asked questions

Every article is only as strong as the reputation of the author behind it. Person schema makes that reputation visible to the machines that increasingly determine who gets read.