Why AI Search Engines Struggle to Attribute Expertise
When someone asks ChatGPT or Perplexity "who is the best nutritionist in London?" or "what does [expert name] recommend for gut health?", the AI has to make a judgement call about who counts as a credible source. It does that by piecing together signals from crawled web pages, structured data, and third-party mentions. If your website does not explicitly tell AI crawlers who you are, what you know, and where you have been cited, you are essentially an anonymous contributor to the web.
That is where Person schema comes in. It is a specific type of structured data from Schema.org that lets you formally describe a person, their credentials, their affiliations, and their online presence in a machine-readable format. Done well, it becomes one of the clearest signals you can send to AI systems about why they should attribute knowledge to you rather than someone else.
What Person Schema Actually Contains
Person schema is a JSON-LD object you embed in a web page that describes a human being. It sits within a <script type="application/ld+json"> tag and can include a wide range of properties. Here are the most useful ones for AI authority building:
- name - Your full name, exactly as you want it to appear in citations.
- jobTitle - Your primary professional role, e.g. "Registered Nutritionist" or "E-commerce Growth Strategist".
- url - The canonical URL of your profile or about page.
- image - A URL to a professional headshot. AI systems increasingly cross-reference this with other databases.
- sameAs - An array of URLs to your verified profiles elsewhere: LinkedIn, Twitter/X, Wikipedia, Wikidata, your Google Scholar profile, podcast appearances, and so on.
- knowsAbout - A list of topics you have expertise in. This is underused but genuinely valuable for AI topic modelling.
- alumniOf - Universities or institutions you attended, which adds credibility signals.
- worksFor - The organisation you are associated with, ideally one that also has its own Organisation schema on the web.
- award - Any industry awards or recognitions.
- description - A short bio written in plain language. Think of this as the paragraph you want AI to quote when summarising who you are.
Not every property applies to every person. Pick the ones that are genuinely accurate. Inflating or fabricating credentials in schema is not just unhelpful, it actively erodes trust if an AI cross-references your claims against other sources and finds inconsistencies.
A Practical JSON-LD Example
Here is a realistic Person schema implementation for a freelance e-commerce consultant. You would drop this into the <head> of your about page or author profile page:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Sarah Flinn",
"jobTitle": "E-commerce SEO Consultant",
"url": "https://example.com/about",
"image": "https://example.com/images/sarah-flinn.jpg",
"description": "Sarah Flinn is an e-commerce SEO consultant specialising in structured data and AI search visibility for Shopify brands.",
"knowsAbout": [
"Schema markup",
"Shopify SEO",
"AI search optimisation",
"JSON-LD implementation",
"Structured data strategy"
],
"alumniOf": {
"@type": "EducationalOrganization",
"name": "University of Edinburgh"
},
"worksFor": {
"@type": "Organization",
"name": "FlinnSchema",
"url": "https://flinnschema.com"
},
"sameAs": [
"https://www.linkedin.com/in/sarahflinn",
"https://twitter.com/sarahflinn",
"https://www.wikidata.org/wiki/Q12345678"
]
}
</script>A few things worth noting here. The description field is written in third person, present tense. That is intentional. AI language models are trained to extract and reuse biographical text, and third-person descriptions are far easier for them to cite verbatim. First-person bios ("I am an SEO consultant…") tend to get ignored or awkwardly rewritten.
The sameAs array is probably the most important section for AI authority. Every URL you list there is an additional data point that helps AI systems triangulate who you are and verify that you are a real, established professional. Wikidata entries are particularly powerful because many AI models were trained on Wikipedia and Wikidata dumps.
Where to Place Person Schema on Your Site
The page you place Person schema on matters. Here are the most effective locations, in order of priority:
Your About Page
This is the strongest option. Your about page is typically the most-linked internal page on a personal or business site, and it is the natural destination for anyone (human or AI) researching who you are. Place the full Person schema block in the <head> of this page.
Author Profile Pages
If you have a blog, each author should have a dedicated profile page with their own Person schema. This is how you connect individual articles back to a credible human author. Article schema has an author property that should reference the same Person entity. When you link the two together, AI systems can follow that thread from a piece of content back to a verified, credentialed person.
You can read more about this in our guide on how to use Article schema to get your blog posts cited by AI.
Homepage (for Personal Brands)
If you are a solopreneur or consultant and the site is essentially your personal brand, adding a lightweight Person schema to the homepage is reasonable. Do not duplicate the full schema across every page though. One canonical location is best, with other pages referencing it via the author or founder properties on other schema types.
Connecting Person Schema to the Rest of Your Structured Data
Person schema does not work in isolation. Its real power comes from being part of an interconnected web of structured data across your site. Think of it like a knowledge graph in miniature.
Linking to Organisation Schema
If your business has Organisation schema (which it absolutely should), the Person schema can reference it via the worksFor property, and the Organisation schema can reference you via the founder or employee properties. This creates a two-way link that gives AI systems more confidence that both entities are real and related.
Connecting to Article Schema
Every article or blog post you publish should have Article schema with an author property pointing back to your Person entity. Over time, as you publish more content, AI crawlers accumulate more evidence that you are an active, knowledgeable contributor on specific topics. This is essentially building a citation record, similar to how academic systems work.
Using sameAs Strategically
The sameAs property is worth treating as an ongoing project rather than a one-time task. Every time you get a new credible mention or profile, add it. Think: your Google Business Profile, your Crunchbase listing, your podcast guest appearances (if the show has a guest page), your contributions to publications with author pages, and any industry directories where you are listed. The more authoritative the domain, the more weight it carries.
Person Schema for E-commerce Store Owners
Most advice about Person schema focuses on journalists, academics, or consultants. But e-commerce brand founders can benefit from it too, particularly as AI shopping assistants like ChatGPT's shopping features and Perplexity's product recommendations start attributing brand authority to founding stories and expertise claims.
If you sell handmade ceramics and you are a trained ceramicist, your Person schema should say so. If you built a skincare brand after 10 years working as a cosmetic formulator, that credential belongs in your schema. AI systems are increasingly looking for the "why" behind a brand, and Person schema is one of the cleanest ways to communicate it.
For Shopify store owners specifically, Person schema is best added via a custom JSON-LD block in the theme's theme.liquid file or through a dedicated schema app, scoped to the about page template. If you are unsure where to start, our free AI visibility audit can flag exactly what structured data is missing from your site and where it should go.
Common Mistakes to Avoid
A few patterns come up repeatedly when auditing sites for Person schema errors:
- Using a first-person description. As mentioned above, third-person is far more useful for AI citation. Rewrite your bio accordingly.
- Listing dead or inconsistent sameAs URLs. If your LinkedIn URL has changed or your old Twitter profile is deleted, remove it. Broken links in sameAs arrays signal unreliability.
- Duplicating Person schema across every page. Pick one canonical page and stick to it. Duplication confuses crawlers about which version to trust.
- Leaving knowsAbout empty. This is a missed opportunity. Be specific. "Nutrition" is vague. "Sports nutrition for endurance athletes" is a real signal to AI topic models.
- Mismatching the name field with how you appear elsewhere. If your LinkedIn says "Jonathan Smith" and your schema says "Jon Smith", that looks like two different people to an entity-resolution system. Consistency matters.
At FlinnSchema, we regularly spot these issues during audits. They are easy to fix but often invisible to site owners who have not looked at their structured data critically.
Testing and Validating Your Person Schema
Once you have implemented Person schema, run it through Google's Rich Results Test and Schema.org's own validator. Neither tool will confirm whether AI systems will use your schema, but they will catch syntax errors and missing required fields before they become a problem.
Beyond validation, the real test is whether AI systems start attributing content to you more consistently. Search for your name or brand in ChatGPT, Perplexity, and Gemini. Note what they say, where they pull information from, and whether your expertise is accurately described. If the answers are vague or incorrect, that is a signal that your entity data needs strengthening, not just your schema.
If you want a structured approach to the whole process, take a look at what we do differently at FlinnSchema. The methodology goes well beyond schema placement and looks at the full picture of how AI systems perceive and cite your brand.
Frequently Asked Questions
Does Person schema directly affect Google search rankings?
Not directly in the traditional sense. Google does not offer a rich result type specifically for Person schema. However, it contributes to entity understanding in the Knowledge Graph, which can influence how Google presents your brand in knowledge panels and AI Overviews. The more immediate benefit is in AI-powered search engines like Perplexity and ChatGPT, which rely heavily on structured data to attribute expertise.
Do I need a Wikipedia page for Person schema to work?
No. A Wikipedia page is helpful because AI models were heavily trained on Wikipedia data, but it is not required. A Wikidata entry (which is easier to create and maintain) can serve a similar purpose. The key is having multiple credible, consistent mentions of your name and credentials across authoritative domains, whether or not Wikipedia is one of them.
Can I use Person schema for multiple people on the same site?
Yes. If you have a team or multiple authors, each person should have their own profile page with their own Person schema block. Do not bundle multiple people into one schema object. Each person is a distinct entity and should be described separately, with their individual sameAs arrays, knowsAbout lists, and credentials.
How long does it take for AI search engines to reflect updated Person schema?
It varies. AI systems like Perplexity that use live web crawling can pick up changes relatively quickly, sometimes within days of a re-crawl. Models like ChatGPT that rely on periodic training data updates may take much longer to reflect changes, potentially months. That is why it is worth getting your Person schema right from the start rather than iterating on it repeatedly. You can learn more about how different AI systems crawl and index content in our post on whether ChatGPT uses Google's index or its own crawl.