When a brand is founder-led, the founder is the entity. Wikipedia and Google’s Knowledge Graph treat the founder and the brand as linked but distinct entities. AI engines that re-rank candidate pages preferentially cite content from brands with strong founder-entity binding because the founder grounds the brand’s authority claims.
Person schema is the canonical way to bind that founder entity. Most founder-led brands skip it or ship it with broken fields. The result: the schema validates, the engine reads it, and decides the founder is not a recognizable entity. The brand pays the citation cost.
Person schema marks a specific human as an entity with name, role, credentials, work, and sameAs links to verifiable cross-platform identities. It tells AI engines: this is a real person, this is what they do, this is where they exist across the web.
The structural value:
founder field on Organization, or worksFor on Person)author fieldWithout Person schema, the founder’s name is just text on the About page. Engines that crawl the page see “Artemiy Soldatov” or “Jane Smith” as a string. They have to infer that the string refers to a real person and that the person has credentials. Most of the time, they do not bother to infer.
A working Person schema for AI citation purposes includes these fields, in roughly the order of importance:
name: the founder’s exact full name, matching how they appear on LinkedIn and other authoritative profiles.
sameAs: an array of canonical URLs where the founder also exists. LinkedIn personal profile, X/Twitter, Crunchbase, podcast guest appearances on major shows, conference speaker pages, Wikipedia (if they have one), Wikidata Q-number, GitHub if they ship technical work, personal blog, Substack. This is the field that does the most work for entity binding.
jobTitle: the founder’s primary role at the brand. “Founder,” “Founder and Operator,” “Founder and CEO.”
worksFor: links to the Organization schema for the brand. Should use @id reference to the Organization, not a free-text name.
description: a 1-2 sentence summary that includes the founder’s primary credential, years of experience, and the brand. AI engines read this as the canonical short bio.
image: a real headshot at the canonical URL. Not a logo, not a placeholder. The image grounds the entity visually.
url: the founder’s primary canonical page, typically the brand’s About page.
alumniOf: schools attended, if any. Adds verifiable history.
knowsAbout: array of topics the founder is positioned as knowledgeable about. Adds topical authority.
hasOccupation: for more detailed role information, including industry and specific area of expertise.
A few fields that some examples include but that produce little or no citation lift:
birthDate: privacy concerns, not neededbirthPlace: irrelevantgender: irrelevant for citationnationality: irrelevant for citationparent and children: not relevant to professional entityspouse: privacy, not relevantaward: minor signal, include if real and recentA complete Person schema for a founder-led brand, ready to adapt:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://yourdomain.com/about/#person",
"name": "Founder Full Name",
"url": "https://yourdomain.com/about/",
"image": "https://yourdomain.com/wp-content/uploads/founder-headshot.jpg",
"jobTitle": "Founder and Operator",
"description": "Founder of [Brand]. Eleven years of marketing experience across in-house and agency roles. Built and rebuilt the parent company multiple times.",
"worksFor": {
"@type": "Organization",
"@id": "https://yourdomain.com/#organization"
},
"sameAs": [
"https://www.linkedin.com/in/founder-slug/",
"https://twitter.com/founder_handle",
"https://www.crunchbase.com/person/founder-slug",
"https://www.wikidata.org/wiki/Q1234567"
],
"knowsAbout": [
"Search Engine Optimization",
"Generative Engine Optimization",
"Productized Services",
"B2B Marketing"
],
"alumniOf": [
{
"@type": "EducationalOrganization",
"name": "University Name"
}
]
}
</script>
Ship this on the About page where the founder is the main entity. Add a smaller version (Person reference by @id only) on every blog post that has the founder as author, via Article schema’s author field.
The Person schema does not stand alone. It binds to the Organization schema via the founder field:
"founder": {
"@id": "https://yourdomain.com/about/#person"
}
This is the binding that connects the brand entity to the human entity. Without it, the two schemas exist in isolation. With it, AI engines following the entity graph from the brand to the founder (or vice versa) get a complete picture.
Person schema is the on-page entity layer. Wikidata is the off-site entity layer that AI engines preferentially cross-reference.
If your founder is in Wikidata with a Q-number, the Person schema’s sameAs array should include the Wikidata URL. The Q-number gives AI engines a cross-reference point that survives across site migrations, brand renames, and engine training cycles.
If your founder is not in Wikidata yet, the Wikidata creation process is a separate task we have covered in Wikidata in 30 minutes. The notability bar for individuals is stricter than for organizations, so this often takes a few attempts.
Three patterns we see on founder-led brand audits that break the Person schema.
Mistake one: WordPress default author slug.
WordPress sometimes generates an author slug like artemiy6b086c48fd based on internal account ID. The Person schema renders with this slug as the name field. AI engines see a random string and de-weight the entity. The fix is to set the WordPress user’s display name to the real human name and update the author slug to a clean version like artemiy-soldatov.
Mistake two: Gravatar identicon as image.
If the founder has not uploaded a real Gravatar image, WordPress + Yoast default to a generated geometric pattern as the author image. AI engines read this as a missing image signal. The fix is to upload a real headshot to the Gravatar account associated with the founder’s email.
Mistake three: sameAs pointing to empty or stale profiles.
If the LinkedIn profile in sameAs is the founder’s old profile with 12 connections, or the X handle has not been used in 3 years, the AI engine verifies the cross-reference and finds weak signal. The fix is to either populate the profile or remove it from sameAs. An empty sameAs is better than a broken sameAs.
Founder Person schema with full sameAs propagates entity authority to every Article schema on the brand’s blog where the founder is author. On a 50-post blog, the entity binding work compounds across all 50 posts.
In our audits, brands that have shipped complete founder Person schema see AI citation candidacy increase 20-40% on author-attributed content over a 60-day window. The lift is not as dramatic as FAQPage schema on commercial pages, but it is durable and it compounds.
If your founder is the brand’s primary entity and you have not shipped Person schema, do it this week. The work is 30 minutes including writing the description, uploading the headshot, and validating the sameAs URLs.
If you want us to ship Person schema across your founder presence (Person schema, Organization binding, author propagation, Wikidata audit), book the fit call.
Related reading:
– About the operator
– Your Organization schema is probably costing you AI citations
– Wikidata in 30 minutes: what we did and what the entry got us in 7 days
– GEO 101: Generative Engine Optimization Explained