ProfilePage schema: describing the person or brand behind a profile

JSON-LD example

Copy this into a <script type="application/ld+json"> tag and replace the values with your own.

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "dateCreated": "2021-03-09T11:00:00-06:00",
  "dateModified": "2026-07-18T08:30:00-05:00",
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman",
    "alternateName": "priyacooks",
    "identifier": "1047",
    "description": "Recipe developer and former pastry chef. Writes about laminated doughs and home baking.",
    "image": "https://example.com/wp-content/uploads/2024/05/priya-raman-portrait.jpg",
    "sameAs": [
      "https://www.instagram.com/priyacooks",
      "https://www.youtube.com/@priyacooks"
    ],
    "agentInteractionStatistic": {
      "@type": "InteractionCounter",
      "interactionType": "https://schema.org/WriteAction",
      "userInteractionCount": 186
    }
  }
}

Properties

Which pages are profile pages

Google's test is that the page's main focus is a single person or organization affiliated with the site.

• Valid: a user profile on a forum or social site, an author page on a news site, an "About me" page on a blog, an employee page on a company site.
• Not valid: a store's home page, which carries plenty besides profile information, or a review site's page about a company that has nothing to do with the site.

A WordPress author archive fits when it leads with the author's bio and photo. An archive that is just a list of post titles under a name is a weaker candidate; add the bio first.

Two kinds of stats

The two statistics properties are easy to mix up.

• interactionStatistic describes what others do toward the creator: how many follow them, how many likes their content has collected.
• agentInteractionStatistic describes the creator's own activity: how many posts they have written, how many accounts they follow.

Count only activity on your platform. Google's own warning is not to claim that the creator has 100,000 followers on some other site. On a blog, the natural statistic is posts written, which WordPress counts for you.

Author archives in WordPress

Author archives are the obvious place for this markup on most WordPress sites. Hydrogen SEO's Schema screen covers the Organization or Person behind the site; for per-author profiles, append a block on author archives with the hydrogen_seo_schemas filter:

add_filter( 'hydrogen_seo_schemas', function ( $schemas ) {
    if ( ! is_author() ) {
        return $schemas;
    }
    $user = get_queried_object();
    $schemas[] = [
        '@context'   => 'https://schema.org',
        '@type'      => 'ProfilePage',
        'mainEntity' => [
            '@type'       => 'Person',
            'name'        => $user->display_name,
            'identifier'  => (string) $user->ID,
            'description' => get_the_author_meta( 'description', $user->ID ),
            'image'       => get_avatar_url( $user->ID, [ 'size' => 512 ] ),
            'agentInteractionStatistic' => [
                '@type'                => 'InteractionCounter',
                'interactionType'      => 'https://schema.org/WriteAction',
                'userInteractionCount' => (int) count_user_posts( $user->ID ),
            ],
        ],
    ];
    return $schemas;
} );

One catch: get_avatar_url() returns a Gravatar default image for users who never uploaded a photo. Google asks you to omit placeholder images, so skip image for those users.

Pointing content at the profile

A profile does the most good when other markup links to it. Set author.url in Article, DiscussionForumPosting and QAPage to the exact profile URL, trailing slash included, so every signal lands on one address. Google also recommends images of at least 50,000 pixels (width times height), ideally in 16x9, 4x3 and 1x1 versions, and they must be crawlable, so check that your media folder isn't blocked in robots.txt.