What Is ProfilePage Schema? The Complete Guide (2026)

Why ProfilePage Schema Matters for AI Visibility

Profile pages are critical for entity disambiguation — the process by which AI systems identify that "Jane Smith the software engineer" is a different entity from "Jane Smith the journalist." ProfilePage schema, combined with sameAs links to external profiles, gives AI systems the identity signals they need to correctly attribute content and avoid entity confusion.

For publishers and content platforms, properly marked-up author profile pages increase the likelihood that AI assistants correctly credit articles, posts, and videos to the right creator. This is especially important as AI-generated content summaries increasingly include author attribution.

ProfilePage Schema Structure

ProfilePage schema wraps the page-level information around a mainEntity object that describes the Person or Organization being profiled. Think of it as two nested layers:

1. Outer layer (ProfilePage): Describes the page itself — dateCreated, dateModified, and optionally hasPart (links to recent content published by this user).
2. Inner layer (mainEntity): Describes the person or organization — their name, image, biography, external profiles, and engagement statistics.

Required Properties

Recommended Properties

interactionStatistic vs. agentInteractionStatistic

These two properties record different directions of interaction and require different valid interactionType values:

Each stat must be an InteractionCounter with @type, interactionType, and userInteractionCount. Using the wrong interactionType for the wrong property is a Greadme warning.

ProfilePage Schema Code Example

A complete author profile page with engagement statistics:

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "dateCreated": "2022-01-15T00:00:00+00:00",
  "dateModified": "2026-04-01T09:00:00+00:00",
  "mainEntity": {
    "@type": "Person",
    "name": "Jane Smith",
    "alternateName": "@janesmith_dev",
    "identifier": "user-7821",
    "description": "Senior software engineer specializing in distributed systems.",
    "image": "https://example.com/avatars/jane-smith.jpg",
    "sameAs": [
      "https://twitter.com/janesmith_dev",
      "https://linkedin.com/in/janesmith",
      "https://github.com/janesmith"
    ],
    "interactionStatistic": [
      {
        "@type": "InteractionCounter",
        "interactionType": "https://schema.org/FollowAction",
        "userInteractionCount": 3200
      }
    ],
    "agentInteractionStatistic": [
      {
        "@type": "InteractionCounter",
        "interactionType": "https://schema.org/WriteAction",
        "userInteractionCount": 142
      }
    ]
  }
}

Common Mistakes to Avoid

• Missing both name and alternateName: At least one is required — Google explicitly states that alternateName can substitute for name when the name is unavailable. On platforms where users have handles but no real names, using the handle in alternateName alone satisfies the requirement.
• Using placeholder images: Greadme warns against placeholder image URLs. Use the actual profile photo — a real image URL that resolves to the user's avatar.
• Wrong interactionType for the context: WriteAction and ShareAction represent things a user does — they belong in agentInteractionStatistic. BefriendAction represents something received — Greadme places it in interactionStatistic. Greadme warns on types that do not semantically fit their context.
• Missing userInteractionCount: Every InteractionCounter must have this field. Greadme warns and deducts points if it is absent.
• hasPart items without @type or url: Greadme warns on each hasPart item missing a @type or URL reference.

How Greadme Validates ProfilePage Schema

Greadme runs a dedicated ProfilePage validator. The score starts at 100 with these key deductions:

Frequently Asked Questions