Speaker Hub uses necessary cookies for secure accounts. With your permission, first party analytics help us improve signup and onboarding. We do not use advertising or cross site tracking cookies. Read the Cookie Policy.
Speaker schema markup: what Google actually does with it · Speaker Hub
Speaker schema markup: what Google actually does with it
Person markup earns you no rich result, and it is still worth adding. The reason is what happens after a search engine reads it.
•6 min read
Structured data advice for speakers usually promises a rich result. Add Person markup, get a fancy box in Google.
That is not what happens, and the real reason to do it is better than the promised one.
What Google says it does
Google's introduction to structured data describes the purpose plainly. Google uses structured data to understand the content of a page and to gather information about the web and the world, including about people.
Note the two halves. Understanding the page, and gathering information about entities. Only some of that surfaces as a visual feature.
The features that do produce a visible result are listed in the search gallery. Work through it and you will notice that a standalone Person entry is not among them. Articles, events, recipes, products, job postings, video, and a number of others are. A speaker's biography is not.
Google is also explicit that markup does not guarantee a rich result even for the types that support one.
So why bother
Because the alternative to telling a machine what a page means is letting it guess.
Your speaker page probably contains several names. Yours, the companies you have worked with, the person who wrote a testimonial, the conferences you have spoken at. A crawler reading prose has to work out which of those the page is about.
Markup removes the guess. This name is the subject. This is their job title. These are the organisations they are affiliated with. This is the same person as the one behind these other profiles.
That last one is the part most speakers miss, and it is the most valuable.
sameAs is the field that matters
Inside Person markup, sameAs takes a list of URLs that refer to the same person. Your LinkedIn, your YouTube channel, your author page at a publication, your profile on a conference site.
This is how you tell a search engine that the Jane Doe speaking about healthcare burnout on your site is the Jane Doe with 40,000 LinkedIn followers and the Jane Doe who wrote that piece in a trade journal. Without it, those are three unconnected strings that happen to match.
Entity consolidation is unglamorous and it is doing more for you than any visual feature would. It is also directly relevant to getting cited by AI, because an answer engine deciding whether you are a credible source on a topic benefits from the same connections.
A working example
Here is a minimal Person block. Put it in a script tag with type="application/ld+json" in the head of your about or speaking page.
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Jane Doe",
"url": "https://janedoe.com",
"image": "https://janedoe.com/headshot.jpg",
"jobTitle": "Keynote speaker and former ICU nurse",
"description": "Speaks on burnout and staff retention in healthcare.",
"knowsAbout": ["healthcare burnout", "clinical staff retention", "shift handover"],
"sameAs": [
"https://www.linkedin.com/in/janedoe",
"https://www.youtube.com/@janedoe"
]
}
Three notes on that.
knowsAbout is where your topics go, and it should match what your page actually says. Listing twelve topics you have never spoken about is the structured data version of keyword stuffing.
jobTitle is a good place to be specific. "Keynote speaker" alone describes thousands of people. The version above says what the talks are about.
sameAs should only list profiles you control or that genuinely refer to you. It is a claim of identity, not a link list.
ProfilePage on top
Google does document ProfilePage markup, which marks a page as being about one person or organisation.
If you have a dedicated speaker page, wrap it. It is a small addition and it says something Person alone does not: that this URL exists to describe this person, rather than merely mentioning them.
Where speakers get Event markup wrong
The common mistake is adding Event markup for every conference you have spoken at.
Event markup describes an event. If you did not organise it, do not control the listing, and are not selling tickets to it, marking it up on your own site is describing somebody else's event on your page. Google's event documentation is aimed at the organiser.
If you run your own workshops or ticketed sessions, that is a genuine use. A speaking history is not.
List past appearances as ordinary content. They still work, because a crawler reading "spoken at" alongside real conference names is getting a clear signal without any markup at all.
Check it worked
Two tools, both free, and they answer different questions.
The Rich Results Test tells you whether Google can read your markup and whether it is eligible for a feature. For Person it will often report valid markup and no eligible rich result, which is the expected outcome.
The Schema Markup Validator checks your markup against the schema.org vocabulary rather than against Google's feature list, which is the right test for markup whose value is not a visual feature.
Where this sits
Markup is one line item on a longer list, and it is not the first one. If your site is still blocking crawlers or has no indexed pages, structured data changes nothing. Work through the six checks first.
Does Person schema get you a rich result in Google?
No. Google's search gallery lists the features that produce a visual rich result, and a standalone Person entry is not one of them. Google's own documentation says it uses structured data to understand page content and gather information about people and organizations, which is a different job from drawing a box in the results.
If it earns no rich result, why add it?
Because the alternative to explicit markup is inference. Without it a search engine has to guess from your prose whether the name on the page is the subject, the author, or someone you quoted. Markup answers that unambiguously, and the same machine readable claims are what an answer engine reads when it summarises who you are.
Which schema type should a speaker page use?
Person for you, and ProfilePage on the page that is about you, which Google does document. Add Event markup only for talks you are actually hosting or that you control the listing for, since Event markup describes an event rather than a speaker's appearance at somebody else's.
Google deleted FAQ rich results in 2026, and it never read llms.txt at all. Here is what survives once you strip out the advice that stopped being true.
The bio that impresses a programme chair and the bio a search engine can use are not the same paragraph. You need both, and most speakers write neither.
