ProfilePage markup is designed for any site where creators, either people or organizations, share first-hand perspectives. Adding this markup helps Google Search understand the creators that post in an online community and show better content from that community in search results, including the Discussions and Forums feature. The sameAs property connects the Person entity to external profiles Google uses for Knowledge Graph resolution.
What Is ProfilePage Structured Data in Google Search Central?
Google Search documentation covers the official details in Structured data markup that Google Search supports.
ProfilePage is a Schema.org structured data type that tells Google which page on a site represents a specific creator. Other structured data features can link to pages with ProfilePage markup too. For example, Article and Recipe structured data have authors, and there are often several authors present in discussion forum and Q&A page structured data.
The ProfilePage type uses 3 core schema objects:
The 11 Deadly Sins of Search Engine Optimization and How to Fix Each One
Common SEO Mistakes in Digital Content Production: 10 Errors and How to Fix Each One
- ProfilePage: the wrapper describing the page itself
- Person: the individual the page is about
- Organization: used when the profile represents a brand or company rather than an individual
What Pages Qualify as a ProfilePage?
Valid use cases include a user profile page on a forum or social media site, an author page on a news site, an About Me page on a blog site, and an employee page on a company website. Invalid use cases include the main home page of a store and an organization review site where the organization is not associated with the website.
What Are the Required and Recommended Properties for Person Schema?
The ProfilePage type has 1 required property: mainEntity, which must be a Person or Organization. This indicates that the primary focus of the page is information about this entity.
The Person type inside mainEntity has its own required and recommended properties:
Property | Status | Type | Description name | Required | Text | The primary name of the person alternateName | Recommended | Text | A social media handle or alternate public identifier description | Recommended | Text | The user's byline or applicable credential identifier | Recommended | Text | A unique internal site ID for the user image | Recommended | URL or ImageObject | Profile image URL sameAs | Recommended | URL | Links to external profiles or home pages interactionStatistic | Recommended | InteractionCounter | Follower, like, or friend counts agentInteractionStatistic | Recommended | InteractionCounter | Post, share, or like counts by the creator
For recommended properties, dateCreated and dateModified on the ProfilePage itself represent the date and time the profile was created or last modified, in ISO 8601 date format.
What Is the sameAs Property in Person Structured Data?
The sameAs property is a URL that declares a Person or Organization entity on one page is the same entity described at an external URL. sameAs is used to declare that the subject of the schema, such as a Person or Organization, is the same as another entity described at an external URL, typically a social profile, Wikidata, or Wikipedia page. It links to authoritative profiles or references that define the same identity and is common for Google's Knowledge Graph reconciliation.
sameAs links are one of the strongest trust signals in ProfilePage markup. They act as evidence that different profiles across the web refer to the same person or organization.
Which URLs Should You Include in sameAs?
sameAs should list official profiles you control, such as LinkedIn, GitHub, Crunchbase, or a Wikipedia page if one exists. Always use official and active links only. If a link changes, update it quickly. Each sameAs link should strengthen, not weaken, Google's understanding of your identity.
Accepted sameAs URL types for a Person schema include:
- LinkedIn profile URL
- Wikipedia or Wikidata page URL
- GitHub profile URL
- Crunchbase profile URL
- Official personal website URL
- Other verified social media profile URLs the person controls
How Do You Implement ProfilePage Structured Data with Person and sameAs?
Add the required properties based on the format you are using. Using a CMS? It may be easier to use a plugin integrated into your CMS. Using JavaScript? Learn how to generate structured data with JavaScript.
Follow these 5 implementation steps:
- Identify the page that represents the person (author page, About page, or user profile)
- Add a JSON-LD script block in the page head with @type set to ProfilePage
- Add the mainEntity object with @type set to Person and all required and recommended properties
- Add the sameAs array with all verified external profile URLs
- Validate the markup using the Google Rich Results Test before deployment
What Does a Complete ProfilePage JSON-LD Example Look Like?
{ "@context": "https://schema.org", "@type": "ProfilePage", "dateCreated": "2024-12-23T12:34:00-05:00", "dateModified": "2024-12-26T14:53:00-05:00", "mainEntity": { "@type": "Person", "name": "Angelo Huff", "alternateName": "ahuff23", "identifier": "123475623", "description": "Defender of Truth", "image": "https://example.com/avatars/ahuff23.jpg", "sameAs": [ "https://www.example.com/real-angelo", "https://example.com/profile/therealangelohuff" ] } }
If the profile page also includes the creator's recent activity, include markup using URLs on those objects to reference the page with the full content. The hasPart property links Article or other content types back to the Person entity using an @id reference.
How Does sameAs Affect Google Knowledge Graph and E-E-A-T?
Organization and Person schema with sameAs identifiers enables AI to resolve the publishing entity against Knowledge Graph records. Resolved entities receive higher trust scores in AI answer generation.
Entity clarity through sameAs ties a website, its authors, and their profiles together so Google can confirm they are the same entities. This provides a better fit for E-E-A-T and Generative Engine Optimization, as a connected entity graph makes it easier for search and AI systems to understand and recommend the content creator.
What Is the Difference Between sameAs and knowsAbout in Schema?
Use sameAs for primary entities and knowsAbout for related, less salient entities. sameAs communicates identity: this schema subject is the same real-world entity as the one at this external URL. knowsAbout communicates topical association: this person has expertise or knowledge about this subject, place, or concept.
How Do You Validate and Monitor ProfilePage Structured Data?
Validate code using the Rich Results Test and fix any critical errors. Consider also fixing any non-critical issues flagged in the tool, as they can help improve the quality of the structured data.
3 monitoring checkpoints apply after implementation:
- After first deployment: check the Rich Results status report in Google Search Console for invalid items
- After template updates: monitor for increases in invalid structured data items
- Periodically: review the Performance Report in Search Console to track rich result impressions and click-through rate
What Errors Does Google Flag in ProfilePage Markup?
Update the schema whenever the person's details or employment change, and ensure that the on-page text, metadata, and structured data all match. Every entity, whether a person, organization, or profile page, should have a unique, stable identifier using the @id property. Without it, Google might treat references to the same person on different pages as separate individuals.
Accurate markup helps; inflated markup creates contradictions. Add only what the page can support. sameAs links pointing to inactive URLs, unrelated accounts, or placeholder profiles reduce entity trust scores rather than improving them.
Waleed Qamar holds a BSc in Computer Science from Purdue University and has spent the years since turning that technical foundation into something the curriculum never covered: figuring out why websites rank, why they fall, and why most businesses never find out until it is too late.
Pakistan-born and based between the United States and South Asia, he has managed search visibility for e-commerce stores, local service businesses, and SaaS startups across two continents. He started in SEO when guest posting still worked, survived the Penguin update, and has rebuilt client sites from scratch after algorithm hits more than once.
He has watched good businesses get sold packages that looked like progress and delivered nothing lasting. He has also seen the right approach quietly double a site’s traffic without a single press release about it.
His writing on SEO By Highsoftware99 covers Google algorithm updates, autocomplete optimization, semantic SEO structure, and the widening gap between what agencies promise and what Google actually rewards in 2026.
He knows what a traffic cliff looks like in Search Console on the morning you discover it.