Table of contents
- Author text vs Person entity — the real difference
- All Person schema fields — priority levels
- Full JSON-LD Person schema for a founder
- Guide to creating a Wikidata entry — the most important step
- Connecting Person — Article — Organization
- Priority platforms for the sameAs network
- Checklist for building a Person entity
When AI answers a question about a particular field, it is not just searching for information — it is searching for a trustworthy person in that field. If you are the founder of a SaaS company, a marketing expert, or a personal finance blogger, Person schema is how you tell AI: "I am real, I have expertise, and here is the proof."
Without a complete Person schema, you are just a name in a paragraph. With a properly structured Person schema and entity graph, you become a node in the knowledge graph — one that AI can connect, cite, and recommend.
Author text vs Person entity — the real difference
| Plain text author | Person entity with schema | |
|---|---|---|
| Can AI link it? | No — just a string of characters | Yes — @id connects sources |
| AI confidence level | Low — cannot be verified | High — cross-references exist |
| Authority accumulation | No — each article stands alone | Yes — all articles accumulate into the entity |
| Appears in Knowledge Graph | Rarely | Likely if sameAs is complete |
| AI mentions the name in answers | Very rarely | More frequently when entity is strong |
| Time to build | Immediate (just add a name) | 3–6 months for the entity to be recognized |
The most important difference: when multiple articles point to the same Person entity via author: \{"@id": ...\}, they accumulate topical authority into the same person. AI understands this is a consistent expert in the field, not many scattered authors.
All Person schema fields — priority levels
| Field | Description | Priority |
|---|---|---|
@id | Author page URL (canonical) | Required |
name | Full name | Required |
jobTitle | Current title | High |
description | Short bio ~160 characters | High |
image | Photo (ImageObject with url, width, height) | High |
sameAs | Array of profile URLs on other platforms | Very high |
knowsAbout | Array of areas of expertise | High |
worksFor | Current organization (@id) | High |
url | Personal website or author page | High |
givenName / familyName | First and last name separately | Medium |
email | Public email (optional) | Low |
nationality | Nationality | Low |
alumniOf | University attended | Medium |
hasCredential | Professional certifications | High (for YMYL) |
memberOf | Organizations/associations the person belongs to | Medium |
award | Awards received | Low |
Full JSON-LD Person schema for a founder
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://example.vn/tac-gia/tran-minh-duc",
"name": "Trần Minh Đức",
"givenName": "Đức",
"familyName": "Trần",
"jobTitle": "Founder & CEO",
"description": "Founder AEO Saigon, 8 năm kinh nghiệm SEO/AEO cho thị trường Việt Nam. Đã tư vấn cho 200+ doanh nghiệp SME về chiến lược nội dung và tối ưu AI visibility.",
"url": "https://example.vn/tac-gia/tran-minh-duc",
"image": {
"@type": "ImageObject",
"url": "https://example.vn/images/tran-minh-duc.jpg",
"width": 400,
"height": 400
},
"sameAs": [
"https://www.wikidata.org/wiki/Q123456789",
"https://www.linkedin.com/in/tranminhduc-aeo",
"https://twitter.com/tranminhduc_seo",
"https://scholar.google.com/citations?user=XXXX"
],
"knowsAbout": [
"Answer Engine Optimization",
"Structured Data / Schema Markup",
"AI Search Optimization",
"Content Strategy",
"Technical SEO"
],
"worksFor": {
"@type": "Organization",
"@id": "https://example.vn",
"name": "AEO Saigon"
},
"nationality": {
"@type": "Country",
"name": "Vietnam"
},
"alumniOf": {
"@type": "CollegeOrUniversity",
"name": "Đại học Kinh tế TP. Hồ Chí Minh"
},
"memberOf": {
"@type": "Organization",
"name": "Vietnam Digital Marketing Association"
}
}
Guide to creating a Wikidata entry — the most important step
Wikidata is a data source that Google Knowledge Graph and many AI models reference. Creating a Wikidata entry is free and open to everyone — no Wikipedia-level fame is required.
Minimum conditions for a valid Wikidata entry:
- At least 1 external reference source (news article, company website, LinkedIn)
- A real person with a real name and verifiable activities
- Documented achievements/activities (founding a company, writing a book, being interviewed in the press)
Process for creating a Wikidata entry:
- Register an account at wikidata.org (using your email)
- Create a new item: click "Create a new item"
- Enter the Label (full name), Description (brief occupation), Aliases (other names if any)
- Add important statements: P31 (instance of: human), P106 (occupation), P27 (country of citizenship), P569 (date of birth — optional)
- Add external identifiers: P214 (VIAF), P4003 (LinkedIn), P2002 (Twitter/X)
- Add references (verification sources) for each statement
Once created, the Wikidata URL takes the form https://www.wikidata.org/wiki/QXXXXXXX — this is the value you add to sameAs in the Person schema.
Connecting Person — Article — Organization
The entity graph works when schemas are linked to each other via @id. Here is how 3 entities connect:
| Connection | Source schema | Field | Target schema |
|---|---|---|---|
| Author writes article | Article | author: { "@id": "..." } | Person |
| Company founder | Organization | founder: { "@id": "..." } | Person |
| Employee of organization | Organization | employee: { "@id": "..." } | Person |
| Person works at | Person | worksFor: { "@id": "..." } | Organization |
| Member of | Person | memberOf: { "@id": "..." } | Organization |
A practical example in Article schema:
{
"@type": "Article",
"@id": "https://example.vn/blog/aeo-la-gi",
"headline": "AEO là gì?",
"author": {
"@type": "Person",
"@id": "https://example.vn/tac-gia/tran-minh-duc"
},
"publisher": {
"@type": "Organization",
"@id": "https://example.vn"
},
"datePublished": "2026-08-09",
"dateModified": "2026-08-09"
}
When AI sees the same @id appearing in 20 Article entries, 1 Organization, and confirmed by Wikidata via sameAs — confidence about that Person entity increases noticeably.
Priority platforms for the sameAs network
| Platform | Value for AI | Suitable for | How to optimize |
|---|---|---|---|
| Wikidata | ★★★★★ | Everyone | Create a Q-item, add complete statements |
| ★★★★★ | Experts, founders | Enable Creator mode, complete About, post regularly | |
| Wikipedia | ★★★★ | Well-known individuals | Requires notable criteria — difficult to self-create |
| Google Scholar | ★★★★ | Researchers | Add complete publications, citations |
| Crunchbase | ★★★★ | Founders, startups | Create founder profile on the company page |
| X (Twitter) | ★★★ | Thought leaders | Verified account, post about expertise |
| GitHub | ★★★ | Developers | Contribution history, repositories |
| Podcast guest | ★★★ | All industries | Be invited as a guest, link the episode |
Checklist for building a Person entity
- Dedicated author page at a fixed URL (/author/[name-slug])
- Professional real photo (not a logo, not AI-generated)
- Bio of 150–200 words with specific experience and numbers
- Complete Person schema with @id, name, jobTitle, description
- sameAs includes at least Wikidata + LinkedIn
- knowsAbout lists 5–8 specific areas of expertise
- worksFor points to Organization @id
- Every article on the site uses
author: \{"@id": author_page_URL\} - Consistent name and photo across all platforms in sameAs
- Update jobTitle and worksFor when changing positions
Building a Person entity is not a one-time task. It is a continuous accumulation process — every new article, every press mention, every new profile in the sameAs network contributes to your entity. After 6–12 months of consistent effort, your name will start appearing when AI is asked about the field you are building authority in — not by luck, but because you have created enough signals for AI to recognize you as a genuine expert.
Frequently asked questions
How is Person schema different from simply writing the author's name in an article?
Writing an author name as plain text — AI can read it but cannot link it to an entity. Person schema with an @id (author page URL) creates a 'node' in the knowledge graph that AI can connect to multiple other sources: LinkedIn, Wikipedia, Wikidata, newspaper articles. This is the difference between 'a name in text' and 'a real person in the AI knowledge graph'.
How important is the sameAs field in Person schema?
sameAs is the most important field after @id. It tells AI: 'this person on our website is the same person on LinkedIn, Wikidata, and X/Twitter'. AI uses sameAs to merge information from multiple sources and increase confidence about the entity. Priority order: Wikidata (★★★★★), LinkedIn (★★★★★), Wikipedia (★★★★), Google Scholar (★★★★), X/Twitter (★★★).
Can an SME website without Wikipedia still build a Person entity?
Yes — Wikipedia is not a prerequisite. Effective alternatives: (1) Create a Wikidata entry for the founder (free, anyone can do it); (2) Complete LinkedIn profile with Creator mode enabled; (3) Be mentioned in a newspaper article or podcast (even local press); (4) A complete author page on the website connected with Article schema. These 4 points are sufficient for AI to recognize the entity in most industries.
Should we create Person schema for regular employees?
Only when: the employee is a frequent blog author (≥5 articles), or is an expert cited in content (doctor, lawyer, accountant), or is the company's spokesperson in the press. For ordinary employees — declaring them in Organization schema via employee is sufficient; a separate author page is not needed since there is no topical authority for AI to connect.
AEO Saigon
An Answer Engine Optimization agency in Ho Chi Minh City — helping business websites get cited by AI. About AEO Saigon →
Want your website to be cited by AI like this?
Free Audit