Founder, expert and author profile pages for AI search: get people's roles, credentials and expertise read correctly
Whether an AI answers a question about a person correctly depends on whether that person's profile page states, in plain text, who they are, where they work and what they are an expert in. Put the name, role, organization, credentials, areas of expertise and career on one page; link to it from article bylines and from the leadership line of your About page; and publish the same values as Person structured data. Those three steps are the core. Inflating credentials or inventing authors backfires: Google calls fabricated creator profiles deception.
Written November 16, 2026 (JST). Google's "Creating helpful, reliable, people-first content" (last updated October 5, 2026) and "Profile page (ProfilePage) structured data" were checked the same day. This guide is for companies, shops and practices with pages about their founder, director, practitioners, teachers or writers, and for the agencies that build those sites. The company itself is covered in About page AI search optimization.
AI answers change by day and by wording. These steps make the information AI reads accurate; they do not guarantee that a person will appear in an answer or that rankings will rise.
What AI uses profile pages for
ChatGPT search, Perplexity and Google's AI Overviews read web pages when they answer and show them as sources. For a question about a person, the profile page on the site of the organization they belong to is the most direct material. When there is no such page, when it is only a photo and a name, or when the job title differs from page to page, the AI may build its answer from an old article or from someone else with the same name.
Questions about people tend to fall into a few patterns.
- "Who runs Sample Ltd and what is their background?" (the founder or CEO)
- "What is the director of Sample Clinic a specialist in?" (an expert's credentials and field)
- "Which accountant in Leeds is good with inheritance tax?" (found by expertise; no name in the question)
- "Who wrote this article, and can I trust it?" (the author)
- "How is Jane Doe connected to Sample Ltd?" (role, other positions, previous jobs)
- "How do I book a consultation with Dr Doe?" (contact and booking)
In a question like the third one, with no name in it, the AI first looks for a practice or shop and then adds who would handle the work. A profile page is material not only when someone asks by name but also when they search by expertise.
What Google itself says (as far as we could check)
A lot of what circulates about authorship and E-E-A-T is guesswork. Start from what Google writes itself.
| What Google says | Source | What this guide takes from it |
|---|---|---|
| It strongly encourages accurate authorship information, such as bylines, where readers might expect it | Creating helpful content | Show the author's name on articles and link it to a profile |
| Fabricating creator profiles with AI-generated headshots, made-up names or false credentials is deception and a sign of a low-quality page | Same | No invented authors and no inflated credentials |
| E-E-A-T itself is not a specific ranking factor; of its parts, trust matters most; E-E-A-T carries more weight on health, financial and safety topics (YMYL) | Same | Treat E-E-A-T as a way to publish trustworthy facts, not as a score |
| ProfilePage is for pages whose main subject is one person or organization tied to the site (author pages, a blog's about-me page, a company's employee pages); a store's home page does not qualify | ProfilePage structured data | Use it on founder, expert and author pages, not on the company home page |
| Required on ProfilePage: mainEntity (Person or Organization) and its name; dateModified should reflect only human edits | Same | Start small and use the date someone actually edited the profile |
| There are no additional requirements or special markup for AI Overviews or AI Mode | AI features and your website | Markup is the answer key to the text; the text comes first |
The places Google says ProfilePage markup can show up are features such as Discussions and forums. It says nothing about an effect on AI answers. This guide treats markup as a way to publish the same facts as the text in a form machines can read.
Claims you will see in top articles, and how well they hold up
We read ten of the top Japanese and English articles for queries like "author E-E-A-T AI search". Many have useful steps and checklists, but the claims below could not be traced to a primary source. Use the table as a reading guide.
| Common claim | What we found |
|---|---|
| Percentages such as "author credentials carry 16% of the weight in AI citation decisions" | None of the articles links the original study, and none defines what the "weight" measures |
| "Person schema is mandatory" | Google lists required properties only for ProfilePage to appear in its search features; it never says markup is required for AI answers |
| "The more sameAs links, the better" | No evidence. Listing only profiles the person controls, and that clearly belong to them, is the safer choice |
| "Adding a medical or legal reviewer raises your E-E-A-T" | No evidence for a name-only reviewer line, and Google calls misrepresenting creators deception. State what was reviewed and when |
| "The ideal bio length is N words" | The number differs from article to article and none gives a source. Length matters less than whether the facts are there |
Whose page, and where
Sort the people on your site into four roles. Not everyone needs a long page; start with the people an AI is most likely to be asked about.
| Role | Where | Minimum content | How to connect it |
|---|---|---|---|
| Founder or CEO | Inside the About page, or a page such as /about/name/ | Name, role, career, what they do in the company | Link from the leadership line on the About page; in markup, point the company's founder or employee at the same @id |
| Expert (director, practitioner, teacher) | A staff list plus one page per person | Credentials, registration number, field, which services they handle | Link from the "who you'll see" line on service pages |
| Article author | The WordPress author archive or a regular page | Name, organization, topics, list of articles | Link from the byline |
| Outside reviewer | A reviewer page with a link to their own organization | Name, credential, affiliation, what they reviewed | On the article: "Reviewed by Name (credential), date", linked to the page |
When the same person appears as founder, author and reviewer, keep one page and spell the name and title the same way everywhere. An AI may take two spellings for two people.
What to write, and the matching structured data
The table lists what a profile page should carry, the mistakes AI answers tend to make, and the matching schema.org properties, chosen from the Person and ProfilePage definitions (types checked in schema-dts 2.1.0).
| Item | How to write it | Typical AI mistake | Structured data |
|---|---|---|---|
| Name | One spelling across the site; give other scripts or a romanized form once | Mixed up with someone of the same name | name, alternateName |
| Role and organization | Always with the company name, e.g. "Founder, Sample Ltd" | Introduced with a previous or side job title | jobTitle, worksFor |
| Credentials | Full official name, registration number (if it may be public), issuing body, year | The type of credential is confused | hasCredential (EducationalOccupationalCredential) |
| Areas of expertise | Three to five specific areas, not "everything" | Recommended for things outside their field | knowsAbout |
| Career | One line per year and event: education, previous jobs, when they set up | Dates mixed up | Text (alumniOf for schools) |
| Track record | Numbers with a date and how they were counted | Old or inflated numbers get quoted | Text only |
| Awards and coverage | Name, year, organizer; link where possible | Awards confused with mentions | award (awards only) |
| Other profiles | Only accounts the person controls | Linked to impostors or namesakes | sameAs |
| Photo | A real photo; no AI-generated headshots | — | image |
| Articles and services | A list or links | Unclear what field the person works in | Text |
| Last updated | At the end of the page; fix titles as soon as they change | Introduced with a former role | dateModified (ProfilePage) |
schema.org describes knowsAbout as "suggesting possible expertise but not implying it" (schema.org: knowsAbout). Listing areas in markup proves nothing on its own, so back them up in the text with cases handled and articles written.
Writing the page: say who the person is in the first sentence
- Put the name, role, organization and field in the first sentence, e.g. "Jane Doe is the founder of Sample Ltd in Leeds and a chartered accountant specialising in small-business accounts and inheritance tax."
- Use the second sentence for facts that tell her apart from others: the year she qualified, the bodies she belongs to, the area she covers.
- Write credentials in full. Where a credential can be checked in a public register, you can say so, so readers can verify it.
- Put the career in a table or timeline, not an image or a PDF.
- Replace claims nobody can compare, such as "the industry's number one", with facts: years, numbers, fields.
- In regulated fields such as medicine and law, there are rules on how titles and qualifications may be advertised. For healthcare, see also AI search for clinics.
Bylines and reviewers
Show the author's name at the start or end of each article and link it to the profile page. A team byline is fine, but then the team page should say who writes and how.
When an outside expert checks the content, call it a review, separate from authorship, and state what was reviewed (for example "the tax calculations") and when. schema.org has reviewedBy for people who reviewed a page for accuracy, a different property from author. Do not list the author and reviewer together under author.
Google recommends telling readers how content was produced, including whether automation or AI was used. If an article was drafted with AI, say so where readers would expect it, along with the fact that a person checked it.
Markup example: ProfilePage and Person
A minimal example. Every value must also be in the text. Pointing worksFor at the same @id as your company node lets the person and the company be read as one pair.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"dateModified": "2026-11-16",
"mainEntity": {
"@type": "Person",
"@id": "https://example.com/about/jane-doe/#person",
"name": "Jane Doe",
"jobTitle": "Founder and Chartered Accountant",
"worksFor": { "@id": "https://example.com/#organization" },
"description": "Chartered accountant specialising in small-business accounts and inheritance tax in Leeds.",
"knowsAbout": ["Inheritance tax", "Small-business accounting"],
"hasCredential": {
"@type": "EducationalOccupationalCredential",
"name": "Chartered Accountant",
"credentialCategory": "Professional qualification"
},
"image": "https://example.com/images/jane-doe.jpg",
"sameAs": ["https://www.linkedin.com/in/example"]
}
}
</script>The credential type EducationalOccupationalCredential can also carry the kind of credential (credentialCategory) and the body that recognizes it (recognizedBy). Put in sameAs only profiles the person controls and that clearly belong to them.
On WordPress (with Nurevo AEO)
With Nurevo AEO (free), people are handled as follows.
- First, under Users > Profile, set each writer's "Display name publicly as" to their real name (or the name the site uses). When Nurevo publishes its own graph, posts become BlogPosting with the author as a Person carrying that display name. Pages get no author.
- With Yoast SEO, Rank Math, All in One SEO or Slim SEO, the Article and its author stay exactly as that plugin publishes them; Nurevo does not change them. Set authors up in that plugin's user settings. The author on VK All in One Expansion Unit's Article is not changed either.
- To add the founder to the company's markup, or a ProfilePage to a profile page, use the developer filters below (there are no input fields for these in Nurevo). With an SEO plugin, the company node's values from that plugin still win.
- Check the page source to make sure your SEO plugin does not already publish a ProfilePage for that author, so nothing is duplicated.
- Open /llms.txt and check that the profile page is listed. llms.txt lists the 30 most recently modified pages and posts; if it is missing, add a line with the webmcp_canary_llms_txt_lines filter.
// 1) Add the founder to the business node (only someone your About page names)
add_filter('webmcp_canary_business_node', function ($org, $settings) {
$org['founder'] = array(
'@type' => 'Person',
'@id' => home_url('/about/jane-doe/#person'),
'name' => 'Jane Doe',
);
return $org;
}, 10, 2);
// 2) Add a ProfilePage only on the profile page (slug jane-doe)
add_filter('webmcp_canary_schema_graph', function (array $bundle) {
if (!is_page('jane-doe')) {
return $bundle;
}
$bundle['extra'][] = array(
'@type' => 'ProfilePage',
'url' => get_permalink(),
'mainEntity' => array(
'@type' => 'Person',
'@id' => home_url('/about/jane-doe/#person'),
'name' => 'Jane Doe',
'jobTitle' => 'Founder and Chartered Accountant',
'worksFor' => array('@id' => $bundle['org_id']),
'knowsAbout'=> array('Inheritance tax', 'Small-business accounting'),
),
);
return $bundle;
});On other platforms the checks are the same. The free check needs no sign-up: enter a URL to see the state of structured data, llms.txt and AI crawler access.
How to check: questions with the person's name
Check profile pages with questions that include the person's name. Ask the same question to the same AI on different days and record the answers; do not judge from one answer.
| What to record | Example |
|---|---|
| Date, AI, question | 16 Nov, Perplexity, "What is the background of Jane Doe, founder of Sample Ltd?" |
| Facts in the answer | Role, credentials, field and career: right or wrong, one by one |
| Sources | Was your profile page cited, or someone else's page? |
| Mix-ups | Any namesake or former title in the answer? |
Nurevo's free AI check (once a month on connected Free and Standard sites) asks questions built from your business type and area, never a name, so questions about people are checked by hand with the table above. Pro visibility measurement (beta) currently covers Perplexity. The full method is in how to measure AI visibility.
Profile page checklist
- The first sentence has the name, role, organization and field.
- Name and title are written the same way on the About page, bylines and staff pages.
- Credentials are written in full with the year or issuing body.
- Areas of expertise are specific and backed by cases or articles.
- Numbers have a date and say how they were counted.
- No invented people, AI-generated headshots or inflated credentials.
- Bylines link to the profile; reviews are separate from authorship, with scope and date.
- ProfilePage and Person markup match the text and are not duplicated.
- sameAs lists only accounts the person controls.
- Titles are fixed as soon as they change, and the last-updated date follows.
- You checked with questions that include the name, on different days, and recorded the results.
FAQ
Does a small company need a founder page?
A few lines with the name, role and background in the About page are often enough. If the founder writes articles, speaks or gets interviewed, or people search for them by name, a separate page keeps the facts in one place.
Are articles by people without formal credentials less likely to be used by AI?
Google does not say that lacking a credential is a problem in itself. What it says matters most is trust, and real experience (how many years, what kind of work) written as fact is good material. For health or money topics, you can also have an expert review the content and say so.
Can we publish under a pen name?
Yes, as long as you do not attach an invented background or credentials, and the pen name's page states in what capacity the person writes. Google calls fabricated creator profiles deception.
Which comes first, the author page or the ProfilePage markup?
The page. Markup puts the same facts as the text in a machine-readable form; do not put facts in markup that the text does not state.
Should a reviewer go under author?
Keep authors and reviewers apart. schema.org has reviewedBy for people who checked a page for accuracy. In the text, too, write "written by" and "reviewed by" separately.
Our CEO has changed. What should we update?
The About page, the CEO's profile page, founder or employee in the markup, bylines, and profiles elsewhere (social accounts, industry directories). Keep the former CEO's page with their role and dates, or point it to the new page. There is no fixed time for AI answers to catch up.
If we follow these steps, will AI always describe our people correctly?
That cannot be guaranteed; AI answers change by day and wording. These steps make the information AI reads accurate and consistent, so mix-ups are less likely.