Choosing between Article schema and ProfilePage schema depends on the page’s primary signal. Use Article when the page represents a content asset with a clear byline and publication date, such as a blog post or news article, where the main subject is the content itself and the author can be linked via the author property. Use ProfilePage when the page primarily conveys identity for a person or organization, anchored by a mainEntity that is a Person or Organization, and enhanced with byline, image, description, and social identifiers. If a page hosts both strong identity signals and publishable content, start with ProfilePage for identity and attach related Article items via hasPart, or use the graph approach to map both types. Validate markup with RichResultsTest and verify crawl status with URL Inspection after publishing.
TLDR:
- Use Article for content assets with bylines and dates; main signal is the article itself.
- Use ProfilePage for identity anchored by a mainEntity; include name, image, description, sameAs.
- If both signals exist, connect related Articles to a ProfilePage via hasPart to reflect ownership of the content.
- Validate with RichResultsTest and verify crawl status after changes using URL Inspection.
- Link related content and identities carefully to maximize clarity in search results.
Article schema vs ProfilePage schema at a glance
The table compares Article and ProfilePage based on how they describe content versus identity signals. It draws on the evidence set that positions Article as content centric with bylines and dates, and ProfilePage as an identity centric page anchored by a mainEntity. Additional related types such as Person, Organization, and supporting objects like ImageObject and FAQPage help complete the landscape. The aim is to guide practical choices for pages that mix content and author identity signals and to show where tradeoffs arise in implementation and validation.
| Option | Best for | Main strength | Main tradeoff | Pricing |
|---|---|---|---|---|
| ProfilePage | Describing author or profile oriented pages | Anchors identity to a mainEntity that is a Person or Organization and supports identity signals | May require linking to related content via hasPart to reflect author portfolios | Not stated |
| Article | Content centric posts such as articles and news items | Emphasizes the content as the primary subject with byline and datePublished | Identity signals may be weaker unless complemented by a profile structure | Not stated |
| Person | Representing an individual inside a profile payload | Specifies an individual as part of the profile structure | Not a standalone identity page; relies on mainEntity context | Not stated |
| Organization | Representing a corporate or institutional profile | Supports corporate identity with external links | Less emphasis on individual authorship | Not stated |
| ImageObject | Providing crawlable imagery tied to profiles or articles | Provides image metadata and crawlable URLs | Needs association with a main entity; not a standalone identity | Not stated |
| FAQPage | Pages that contain a list of questions and answers | Supports a structured Q and A section for rich results | Not used for identity or full profile data | Not stated |
| WebPage | General page context or fallback type | Flexible container context for page level data | Less specificity may reduce rich result signals | Not stated |
| RichResultsTest | Validating structured data readiness before live deployment | Validation tooling to gauge eligibility | Not a content type; tool oriented | Not stated |
| URL Inspection Tool | Validating live reachability and recrawl status after changes | Post publish recrawl status verification | Post deployment monitoring rather than content type | Not stated |
How to read this table:
- Type correctness matters for setting Article or ProfilePage as the main type
- MainEntity anchoring identity signals to Person or Organization
- Identity details such as name and alternateName improve recognition
- Freshness signals from dateCreated and dateModified influence recrawls
- Image identity via ImageObject enhances visual identity
- SameAs links external profiles to consolidate signals
- HasPart connects related content to a profile page when appropriate
- Validation and crawl checks via RichResultsTest and URL Inspection Tool confirm readiness
Option by option comparison: article schema vs profile page schema in practice
ProfilePage
Best for: Describing author or profile oriented pages. It centers identity signals around a mainEntity that is a Person or Organization.
What it does well:
- Anchors identity to a mainEntity that is a Person or Organization
- Supports identity signals such as name description image and sameAs
- Allows linking related content via hasPart to reflect author portfolios
- Uses dateCreated and dateModified to reflect freshness of the profile data
Watch-outs:
- May require linking related content to reflect a portfolio of Articles
- Identity signals depend on a proper mainEntity anchor
- Untethered profiles may underperform for content discovery unless paired with Articles
Notable features: ProfilePage provides a structured identity surface that can tie a person or organization to multiple articles and social identifiers, supporting knowledge graph signals and author credibility. It emphasizes mainEntity as the anchor and allows inclusion of social and descriptive details to establish trust.
Setup or workflow notes: Declare ProfilePage as the main type and assign mainEntity to a Person or Organization. Include key identity fields such as name and image, add description and sameAs where applicable, and track changes with dateCreated/dateModified. Validate with available testing tools and verify recrawl status after publishing.
Article
Best for: Content centric posts such as articles and news items. The article type treats the content itself as the primary subject.
What it does well:
- Emphasizes the content as the primary subject with a clear byline and datePublished
- Supports author linkage via the author property
- Works with image data to provide a thumbnail or featured image
- Fits well for news and blog style content with clear publication signals
Watch-outs:
- Identity signals may be weaker unless paired with a ProfilePage or similar identity surface
- Not a standalone identity page; designed around the article content itself
Notable features: Article centers on the content asset, supported by headline, author, datePublished, and image fields that convey topical authority and recency. It integrates well with publication workflows and content management systems.
Setup or workflow notes: Use Article as the main type for content assets; include headline, author, and datePublished; attach an image and optional publisher data. Validate markup prior to publication and revalidate after changes, ensuring crawlability and eligibility in tests.
Person
Best for: Representing an individual inside a profile payload. Serves as a granular identity element within a larger ProfilePage.
What it does well:
- Specifies an individual as part of the profile structure
- Supports identity attributes such as name and description
- Contributes to knowledge graph signals when used with ProfilePage
Watch-outs:
- Not a standalone identity surface; relies on a surrounding ProfilePage or similar context
- On its own, it may lack the broader identity and content signals needed for discovery
Notable features: The Person type is designed to be embedded within a profile structure, enabling detailed biographical or credential data to accompany a broader identity page.
Setup or workflow notes: Associate a Person as the mainEntity within a ProfilePage when representing an individual. Include relevant identifiers and descriptive text, and ensure linkage to external profiles if applicable. Validate and monitor recrawl as part of the update process.
Organization
Best for: Representing a corporate or institutional profile within a profile page context.
What it does well:
- Supports organizational identity with external links via sameAs
- Provides a structured identity surface for institutions linked to content
- Enables credential and affiliation signals tied to the entity
Watch-outs:
- Less emphasis on individual authorship unless paired with Person and Article signals
- Requires careful linking to related content to maximize discoverability
Notable features: Organization type anchors a corporate or institutional profile, enabling broader identity signals and cross-site references that support trust signals and context around content creation.
Setup or workflow notes: Include Organization as the mainEntity in ProfilePage when appropriate; populate name, sameAs, and related identifiers. Integrate external references and validate markup before going live, then recheck after updates.
ImageObject
Best for: Providing crawlable imagery tied to profiles or articles to support visual identity.
What it does well:
- Provides image metadata with a crawlable URL
- Supports dimensions and captions to improve context
- Enhances visual identity signals associated with a profile or content
Watch-outs:
- Needs association with a main entity to add value
- On its own, it does not convey who or what the page is about without linkage
Notable features: ImageObject offers structured image data that can be used across profiles and articles to improve visual recognition and crawlability.
Setup or workflow notes: Attach ImageObject to the relevant mainEntity or content item; ensure the URL is accessible and appropriately sized. Validate the image payload as part of the page's overall structured data validation workflow.
FAQPage
Best for: Pages that contain a list of questions and answers to surface in FAQ rich results.
What it does well:
- Supports a structured Q and A surface that can appear in rich results
- Provides a clear content pattern for user intent and quick answers
Watch-outs:
- Not used for identity or full profile data; best as an adjunct to content or profiles
- Requires a list of questions with accurate answers to be effective
Notable features: FAQPage centers on mainEntity containing Question and acceptedAnswer constructs, enabling direct answer snippets in search results.
Setup or workflow notes: Implement FAQPage when appropriate and ensure questions align with the content. Validate the markup and monitor performance in search results after publishing.
WebPage
Best for: General page context or a flexible fallback type when a more specific type does not fit.
What it does well:
- Provides a broad container for page level data
- Supports signaling context when other types are not a perfect fit
- Easy to implement as a baseline structure
Watch-outs:
- Less specificity may reduce rich result signals compared to targeted types
- Should not replace a more precise type where appropriate
Notable features: WebPage acts as a generic frame for page level information, enabling flexible structuring when a page does not map neatly to Article or ProfilePage.
Setup or workflow notes: Use WebPage when needed as a default; ensure other types are preferred where applicable. Validate and monitor crawlability after updates to ensure search engines understand the page context.
VideoObject
Best for: Representing video content with metadata such as title, description, and URLs for hosting and embedding.
What it does well:
- Includes fields like name description thumbnailUrl uploadDate duration contentUrl and embedUrl
- Helps search engines understand multimedia assets and where to retrieve them
- Useful for video heavy pages or author video portfolios tied to content
Watch-outs:
- Needs careful mapping to the main entity to reinforce identity signals
- May complicate markup when multiple videos and content types are present
Notable features: VideoObject provides a robust set of video specific fields, enabling richer presentation in search results and potential video search surfaces.
Setup or workflow notes: Include VideoObject alongside the primary schema type if videos are a key element. Validate the video payload and ensure contentUrl and embedUrl are accurate; test recrawl after publishing changes.
Decision help for choosing between Article and ProfilePage schemas
The core decision centers on what the page primarily conveys. If the page is a content asset with a byline and publication date, Article is the appropriate main type because the content itself is the focal point. If the page primarily communicates identity for a person or organization anchored by a mainEntity, ProfilePage becomes the stronger choice to surface identity signals. When both content and identity signals are strong, starting with ProfilePage and linking related Articles via hasPart can reflect ownership while preserving content signals. Validate markup with RichResultsTest and confirm recrawl status after publishing using URL Inspection.
- If the page is primarily a content asset with a byline and publication date, choose Article because the main subject is the content itself.
- If the page mainly conveys identity for a person or organization anchored by a mainEntity that is a Person or Organization, choose ProfilePage.
- If a page contains both strong identity signals and publishable content, start with ProfilePage for identity and attach related Article items via hasPart.
- If a page serves as a hub linking author identity to multiple articles, use ProfilePage with hasPart for related Articles.
- If the page centers on a list of articles by an author, ProfilePage with hasPart linking to Articles is suitable.
- If the page surfaces brief author details and a single article, you might still use Article but link identity signals in sameAs or author fields.
- When validating, run RichResultsTest before live publish to check eligibility.
- Use URL Inspection after changes to confirm recrawl status and visibility.
- Use sameAs and optionally ImageObject to strengthen signals for identity and visual context.
People usually ask next
- What is the difference between Article and ProfilePage in practice? In practice, Article targets content assets with a byline and date, while ProfilePage centers identity signals anchored by a mainEntity.
- Can a page carry both Article and ProfilePage semantics? Yes, by combining a ProfilePage with related Articles via hasPart to reflect ownership of content.
- How does mainEntity influence identity and knowledge graph signals? The mainEntity anchors the primary subject to a Person or Organization, enabling explicit connections to the entity in search results.
- What fields are essential for a ProfilePage payload? Key fields include mainEntity, name, image, description, dateCreated, dateModified, and sameAs where applicable.
- When should I validate markup and recrawl after changes? Validate with RichResultsTest before publishing and use URL Inspection to confirm recrawl after updates.
- Should I use WebPage as a fallback type? WebPage can be a flexible fallback when a page does not neatly fit a more specific type, though it offers less rich result potential.
Practical questions and quick decisions on Article vs ProfilePage
What is the difference between Article and ProfilePage in practice
Article is designed to describe a content asset with a byline and publication date, making the content itself the main subject. ProfilePage centers identity signals anchored by a mainEntity that is a Person or Organization, linking identity attributes such as name image and sameAs. When both signals exist, ProfilePage can host related Articles via hasPart to reflect ownership while keeping content signals. Validating with RichResultsTest and confirming recrawl after publishing is advised.
Can a page carry both Article and ProfilePage semantics
Yes, by using ProfilePage as the primary type and attaching related Article items via hasPart; this setup describes both identity and content ownership. Alternatively, you can use Article for the content and attach identity signals within the article's author field, but this provides less explicit identity surface.
How does mainEntity influence identity and knowledge graph signals
MainEntity anchors the primary subject to a Person or Organization, enabling knowledge graph connections and identity resolution across pages. In ProfilePage, mainEntity drives credibility by tying content and author identity; in Article, mainEntity is weaker unless identity data is extended via author or a linked profile.
What fields are essential for a ProfilePage payload
Key fields include mainEntity, name, image, description, dateCreated, dateModified, and sameAs where applicable. These fields establish identity and context and help search engines connect to external profiles. Additional signals like internal identifiers and hasPart relationships can link related content to a profile, clarifying ownership and building a richer identity surface that supports Knowledge Graph connections.
When should I validate markup and recrawl after changes?
Validate markup with RichResultsTest before publishing to confirm eligibility and syntax correctness. After publishing or updating, use URL Inspection to verify crawl status and detect recrawl events. Schedule recrawls after significant changes such as adding a profile image or linking new articles to ensure search engines reflect the latest signals.
Should I use WebPage as a fallback type?
WebPage can serve as a flexible fallback when a page does not neatly fit Article or ProfilePage, but it offers less specificity for rich results. Prefer a more precise type when signals exist, and reserve WebPage for general pages that act as containers rather than identity or content signals.
