Person Schema for Author Pages: The Complete 2026 Guide

Person schema is a structured data vocabulary that describes an individual including their name, bio, affiliations, and social profiles. When implemented on author pages and contributor profiles, it helps search engines understand authorship, enables knowledge panel integration, and strengthens the entity relationship between authors and their published content. This guide covers the on-page application of Person schema specifically for author and contributor pages, distinguishing it from general organizational schema strategies.

Person schema establishes a structured identity for each author on your site. When linked from Article schema via the author property, it creates a clear author-to-content relationship that Google uses for authorship attribution and knowledge graph understanding. This can lead to author pages appearing in knowledge panels and helps establish topical authority for individual writers.

Google's documentation on authorship and structured data confirms that Person schema used in conjunction with Article schema helps Google understand who created the content. The sameAs property also allows you to link author pages to external social profiles, strengthening the entity's digital footprint.

The core properties for Person schema on author pages include:

• @type: Use Person.
• name: The full name of the person.
• givenName: The first name.
• familyName: The last name.
• description: A short bio or description.
• url: The URL of the author's profile page.
• sameAs: An array of URLs to social profiles (Twitter, LinkedIn, GitHub, etc.).
• image: A photo of the person.
• jobTitle: The person's role or position.
• worksFor: The organization they work for (optional).
• knowsAbout: An array of topics or skills.

Below is a complete JSON-LD block for an author page. Place it inside a <script type="application/ld+json"> tag.

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Alex Rivera",
  "givenName": "Alex",
  "familyName": "Rivera",
  "description": "Senior technical writer specializing in structured data, SEO, and web development. 10+ years of experience in content engineering.",
  "url": "https://example.com/author/alex-rivera",
  "image": "https://example.com/images/author/alex-rivera.jpg",
  "jobTitle": "Senior Technical Writer",
  "worksFor": {
    "@type": "Organization",
    "name": "Example Media"
  },
  "sameAs": [
    "https://twitter.com/alexrivera",
    "https://linkedin.com/in/alexrivera",
    "https://github.com/alexrivera"
  ],
  "knowsAbout": [
    "Structured Data",
    "Schema.org",
    "SEO",
    "Web Development",
    "JSON-LD"
  ],
  "birthDate": "1985-04-12"
}

Link Person schema from your Article schema. Each blog post's author property should reference a Person object that matches the author page's markup. Use the same name and url values in both locations to ensure consistency.

Use sameAs to claim external profiles. Google uses this property to connect the person entity across the web. Include profiles on Twitter, LinkedIn, GitHub, Mastodon, or other platforms where the author maintains an active presence. Each URL should be a full, valid URL.

Validate every author page's Person schema with Google's Rich Results Test. Confirm that name is present and matches the visible page content. Check that sameAs URLs resolve to valid profiles and that no URLs are broken or redirected. Verify that every blog post's Article schema author property references a Person object that matches the author page schema. Run a site-wide audit to identify pages with missing or incomplete Person schema.

1. Schema.org. "Person type definition." https://schema.org/Person
2. Google Search Central. "Understanding authorship with structured data." https://developers.google.com/search/docs/appearance/structured-data/article
3. Google Developers. "Rich results test." https://search.google.com/test/rich-results