AI search engines do not discover brands the way traditional search engines do. Google crawls links and measures signals like PageRank. ChatGPT, Perplexity, and Gemini draw on structured, entity-based understanding of the web. They are looking for clear, consistent, machine-readable signals that tell them who you are, what you do, and whether you can be trusted. ProfilePage schema is one of the most underused tools for providing exactly those signals.
Most brands put effort into Product, FAQ, or Article schema and completely skip ProfilePage. That is a missed opportunity, especially if you want AI engines to reliably identify your brand as a distinct entity rather than a vague concept floating somewhere in their training data.
What ProfilePage Schema Actually Does
ProfilePage is a schema.org type designed to describe a web page that represents a person or organisation. Think of it as a structured business card baked into your HTML. When you mark up your About page, founder bio, or team page using ProfilePage schema, you are telling AI crawlers: "This page is authoritative, entity-level information about this specific person or brand."
The schema.org definition positions ProfilePage as a subtype of WebPage. That means it inherits all the standard WebPage properties but adds meaningful context for entity representation. The key properties that matter most for AI visibility are:
- mainEntity - points to a Person or Organisation entity, which is the heart of the whole thing
- name - the canonical name for the brand or individual
- description - a clear, factual summary of who the entity is
- url - the canonical URL of the page itself
- sameAs - an array of external profile URLs (LinkedIn, Twitter/X, Crunchbase, Wikipedia, Wikidata, etc.)
- image - a branded image, ideally a logo or headshot
- foundingDate / dateCreated - when the entity was established
- knowsAbout - a list of topics the entity has genuine expertise in
The sameAs property deserves particular attention. It is the structured data equivalent of a citation network. When you list your LinkedIn, your Crunchbase profile, your Wikidata entry, and your Google Knowledge Panel URL in a sameAs array, you are giving AI engines a web of corroborating signals that confirm your entity is real, consistent, and trustworthy across the web.
Setting Up a Basic ProfilePage Implementation
Here is a minimal but solid JSON-LD implementation you can drop into the <head> of your About page. This example covers an e-commerce brand.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"url": "https://www.yourbrand.com/about",
"name": "About YourBrand",
"description": "The official About page for YourBrand, a UK-based e-commerce brand specialising in sustainable homeware.",
"mainEntity": {
"@type": "Organization",
"name": "YourBrand",
"url": "https://www.yourbrand.com",
"logo": "https://www.yourbrand.com/images/logo.png",
"description": "YourBrand sells sustainable homeware products to eco-conscious households across the UK and Europe.",
"foundingDate": "2018",
"sameAs": [
"https://www.linkedin.com/company/yourbrand",
"https://www.instagram.com/yourbrand",
"https://en.wikipedia.org/wiki/YourBrand",
"https://www.wikidata.org/wiki/Q12345678",
"https://www.crunchbase.com/organization/yourbrand"
],
"knowsAbout": [
"Sustainable homeware",
"Eco-friendly packaging",
"Zero-waste living",
"Ethical supply chains"
]
}
}
</script>
A few notes on this implementation. First, your description fields should read like factual reference text, not marketing copy. AI engines extract descriptions to include in answers. If your description says "We are passionate about revolutionising the homeware space," that is useless to a language model trying to summarise who you are. Write it like an encyclopaedia entry. Clear, specific, direct.
Second, the sameAs URLs should all be live, accurate, and consistent with the name used in the schema. If your LinkedIn company page uses a slightly different brand name, fix that first. Inconsistency across external profiles is one of the main reasons AI engines fail to consolidate an entity's information reliably.
ProfilePage for Personal Brands and Founder Profiles
ProfilePage schema is especially powerful for founder-led brands. If you are the face of the company, your personal authority transfers to the brand. Marking up your founder bio or team page with ProfilePage schema using a Person mainEntity rather than an Organization builds a separate but connected knowledge entity.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"url": "https://www.yourbrand.com/about/founder",
"name": "About Jane Smith, Founder of YourBrand",
"mainEntity": {
"@type": "Person",
"name": "Jane Smith",
"jobTitle": "Founder and CEO",
"worksFor": {
"@type": "Organization",
"name": "YourBrand",
"url": "https://www.yourbrand.com"
},
"description": "Jane Smith is a UK entrepreneur and founder of YourBrand, with 10 years of experience in sustainable product design.",
"sameAs": [
"https://www.linkedin.com/in/janesmith",
"https://twitter.com/janesmith",
"https://www.wikidata.org/wiki/Q87654321"
],
"knowsAbout": [
"Sustainable product design",
"E-commerce operations",
"Circular economy"
]
}
}
</script>
By linking the Person entity back to the Organisation entity via worksFor, you are building a semantic graph. AI engines can then associate Jane's expertise and credibility with the YourBrand entity. This is how you start appearing in responses like "Who are the leading sustainable homeware founders in the UK?" rather than just product searches.
Connecting ProfilePage to Your Broader Schema Strategy
ProfilePage does not work in isolation. It is most effective when it sits within a connected schema architecture. On your About page, link the Organisation entity to your WebSite schema on the homepage. Reference the same Organisation entity in your Product schema, your Article schema bylines, and your BreadcrumbList markup.
The principle here is entity consistency. Every schema block that mentions your brand should reference the same canonical name, the same URL, and ideally the same @id identifier. If your Product schema says the brand is "Your Brand Ltd" but your ProfilePage says "YourBrand," you are introducing ambiguity that AI engines will struggle to resolve.
At FlinnSchema, we see this inconsistency constantly when we run AI visibility audits. Brands spend time implementing schema across their site but use slightly different names, different URLs, or different descriptions in each block. The result is a fragmented entity signal rather than a strong, coherent one. Getting a free AI visibility audit is one of the fastest ways to spot these gaps before they cost you citations.
If you want to understand more about how WebSite schema contributes to this connected entity picture, this post on WebSite schema and brand identification covers the complementary layer in detail.
Common ProfilePage Mistakes to Avoid
Putting it on the wrong page
ProfilePage schema belongs on pages that are genuinely about an entity. Your About page, your founder bio, your team page. Do not add it to your homepage, blog posts, or product pages. The schema type signals "this is a profile," and if Google's crawlers or AI engines see it on a product listing, it creates a type mismatch that undermines your markup credibility.
Leaving sameAs empty
An Organisation entity with no sameAs links is significantly weaker than one with five or six corroborating external URLs. If you have not yet built profiles on Wikidata, LinkedIn, and Crunchbase, do that first. Wikidata in particular is worth prioritising because it is a structured, open-source knowledge graph that many AI systems use as a reference. Creating a Wikidata entry for your brand takes about 30 minutes and pays dividends in entity recognition.
Writing marketing descriptions
As mentioned above, the description field is not a strapline. Write it in the third person, factually, without superlatives. "FlinnSchema is a UK-based structured data agency specialising in AI visibility for e-commerce brands" is useful to an AI engine. "We are the UK's most innovative schema solution" is noise.
Skipping the image property
Including a logo or headshot via the image property strengthens the entity signal. AI systems that surface visual context, such as Perplexity's answer pages, can use this. More importantly, it rounds out the entity description and makes the markup feel complete rather than partial.
How AI Engines Use This Data
When ChatGPT or Perplexity generates a response that includes your brand, they are drawing on their training data and, for models with live search, on real-time index signals. ProfilePage schema improves your chances at both levels.
For training data: clear, structured entity descriptions in schema markup contribute to the information that gets associated with your brand name in large language model training. The more consistent and authoritative that information is, the more confidently a model can describe or recommend you.
For live search: tools like Perplexity's online mode actively crawl pages and extract structured data. A well-formed ProfilePage block gives the crawler a clean, unambiguous entity summary that can be quoted directly in an answer.
This is closely related to how E-E-A-T signals interact with AI engines. If you want to understand that connection more deeply, this post on E-E-A-T and AI search covers the relationship between expertise signals and AI citation rates.
Testing Your ProfilePage Implementation
Once you have added the JSON-LD to your About page, run it through Google's Rich Results Test at search.google.com/test/rich-results. It will not validate ProfilePage as a "rich result" type specifically, but it will confirm your JSON-LD is syntactically valid and that the schema.org types are recognised correctly.
Also check it in the Schema Markup Validator at validator.schema.org. Paste in your URL and look for any warnings about missing recommended properties. If sameAs or description are flagged as missing, add them before moving on.
For AI-specific testing, search for your brand name in Perplexity and note what it says. Run the same search a few weeks after implementing the schema and see if the description of your brand has become more accurate or detailed. That is the clearest real-world signal that your entity markup is working. Tracking AI visibility over time requires a consistent testing routine, and ProfilePage is a key variable to monitor.
Frequently Asked Questions
Does ProfilePage schema directly improve Google search rankings?
Not directly in the traditional sense. Google does not currently show a rich result for ProfilePage the way it does for FAQ or Product schema. However, it does contribute to Knowledge Panel eligibility and entity recognition, which can improve how your brand appears in Google's AI Overviews and Knowledge Graph. The primary benefit is AI engine visibility rather than classic blue-link rankings.
Should I use ProfilePage on my homepage as well as my About page?
No. ProfilePage should go on the page that is specifically about the entity, typically your About page or a dedicated founder/team page. Your homepage should use WebSite schema and potentially Organization schema, but ProfilePage is semantically tied to "a page that describes a person or organisation" and works best when the page content clearly matches that intent.
How many sameAs URLs should I include?
There is no hard limit, but quality matters more than quantity. Three to eight well-chosen, accurate, live URLs are better than fifteen that include broken links or outdated profiles. Prioritise Wikidata, LinkedIn, Crunchbase, and any major industry directories that carry genuine authority. Avoid linking to social media profiles that are inactive or have inconsistent naming.
Can I use ProfilePage schema on Shopify or WordPress without a developer?
Yes, on both platforms. On WordPress, plugins like Yoast SEO Premium or Rank Math Pro allow you to add custom JSON-LD blocks to specific pages. On Shopify, you can add JSON-LD directly to your theme's layout/theme.liquid file or use a schema app. If you want the implementation handled end-to-end without touching code, FlinnSchema's automations service covers this as part of a full AI visibility build.