Schema markup generator for speakers and authors
Speakers and authors should use the Person type, since you are the brand. Fill in the form and I’ll build valid JSON-LD you can paste into your site’s head.
Person JSON-LD
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://jordanashby.example/#person",
"name": "Jordan Ashby",
"jobTitle": "Keynote speaker and author",
"description": "A Calgary keynote speaker and author who writes and speaks about resilient leadership and workplace change.",
"url": "https://jordanashby.example/",
"email": "hello@jordanashby.example",
"image": "https://jordanashby.example/images/photo.jpg",
"knowsAbout": [
"Resilient leadership",
"Workplace change",
"Team culture",
"Remote work"
],
"alumniOf": "University of Calgary",
"knowsLanguage": [
"English",
"French"
],
"sameAs": [
"https://www.instagram.com/jordanashby",
"https://www.linkedin.com/company/jordanashby"
]
}
</script>Paste this into your page’s head, then test it with Google’s Rich Results Test and validator.schema.org. The example values are made up: replace every one.
Want this added to your personal brand’s website?
Send me your site and I’ll check your current structured data and send back corrected JSON-LD for it. Free.
The properties that matter for speakers and authors
Type: Person. Every property below is a real schema.org property.
| Property | Why it matters |
|---|---|
@type | Person tells search tools the site is about you, not a company, and helps them connect your profiles to one identity. |
sameAs | Link LinkedIn, your publisher page and any Wikipedia or Wikidata entry. It’s how search tools confirm you’re one person. |
knowsAbout | Event planners and AI tools look for speakers by topic. Name the topics you’re actually booked for. |
jobTitle | “Keynote speaker and author” is clearer than a creative title. It helps search tools categorise you. |
image | Use a real, current headshot. It’s often what shows next to your name in search. |
Common mistakes
Using Organization for a personal brand. If you are the brand, Person is the right main entity.
Adding a fake award or unverifiable credential. Keep every claim true and visible on the page.
Marking up books as Product on the home page. Use Book markup on each book’s own page.
How to add it to your site
- Replace every example value in the form with your own details. They should match your Google Business Profile exactly.
- Copy the code and paste it into your page’s
<head>. Most site builders have a custom code field. On a hand-built site, it goes in the template. - Test the live page with Google’s Rich Results Test and validator.schema.org, and fix anything they flag.
- Add the same facts to the visible page. Structured data should describe what visitors can see. My website checklist for speakers and authors covers the rest.
Schema for speakers and authors: questions
Person, when you are the brand. If you run a speaking business with staff under a company name, add an Organization too, but keep Person as the main entity on your home page.
Give each book its own page with Book markup: name, author, ISBN and publisher. Link back to your Person entity as author.
It helps, but it doesn’t guarantee one. Consistent sameAs links, press coverage and a clear about page all play a part.
Keep reading
- nick@tavro.ca
- 587-439-9994
- Calgary, Alberta