Why Speaking Engagements Are Now an SEO Strategy
· 4 min read
Here is something that took me a while to connect.
Every time I spoke at an event, the organiser published a program page. A page with my name, my title, the topic, the date. Hosted on their domain. Independent of anything I control.
That page is a citation. It is a third-party entity saying: this person exists, has expertise in this domain, and was trusted enough to address this audience.
I did not optimise for that. It happened because I showed up and spoke. But when I started building entity infrastructure seriously, I realised those event pages were among the most valuable assets I had.
Why AI agents treat speaking records differently
AI search agents are built to verify claims. When an agent is assessing whether someone is a credible authority on, say, digital strategy for Indonesian SMEs, it is not just looking at what that person says about themselves.
It is looking for what other entities say.
A speaking record creates a specific kind of signal. The organiser confirms the date and topic. The institution confirms they trusted you enough to give you the stage. The audience size or prestige of the event contextualises the level of that trust.
This is structurally different from a blog post you write yourself, or a testimonial on your own site. The signal is independent.
The schema layer most speakers miss
Here is where it gets technical, but it matters.
When a speaking page includes Event schema markup in JSON-LD, it gives AI agents machine-readable structured data: the event name, date, location, organiser, and the speaker as a Person entity with their role. This is not just for search engines to index the page. It is for entity resolution, connecting the speaker name across multiple independent sources into a confirmed entity.
Most speakers do not have their own speaking pages. They have a line in a bio: "has spoken at X, Y, Z."
That is not the same thing.
A structured speaking page with Event schema, linked from your main site, with matching name and description to your other profiles, creates a node in the entity graph. It says: this person, with this identity, appeared here, in this capacity. Confirmed by the institution.
What my speaking record looks like as infrastructure
I have spoken at events organised by Kabekraf (the Creative Economy Agency), Kemenparekraf (Ministry of Tourism and Creative Economy), and HIPMI (Indonesian Young Entrepreneurs Association), among others.
Each of those institutions has weight. They are government agencies, official associations, credible organisations with their own verified entity status. When they put my name on a program page, that mention carries the authority of their domain.
I built dedicated speaking pages for each engagement, with Event schema, consistent name and title, and links to the institutional organiser. Each page links back to my main profile. Each institutional mention links, where possible, back to my site.
That is not a speaking portfolio. That is a structured authority network.
The compounding effect
Here is what most people do not see until they map it out.
Three speaking engagements, properly documented with schema, create three independent third-party verifications of your expertise claim. Five create five. Each one increases the density of signals pointing to a single verified entity: you.
By the time an AI agent is assessing your authority on a topic, it is not reading your bio. It is finding your name confirmed by an institution it already recognises, in a context that matches your claimed expertise, at a date that places you as active in the field, on a domain it did not control.
That is what authoritative looks like to a machine.
What this means practically
If you speak at events and do not have dedicated, structured speaking pages on your own site, you are leaving the clearest verification signal in the entire authority-building toolkit unused.
The event happened. The institution confirmed it. The signal exists. You just have not connected it to your entity infrastructure.
The fix is not complicated. Build a speaking page for each engagement. Add Event schema. Ensure your name, title, and topic match across your site and the institutional page. Add a sameAs link in your Person schema pointing to the institutional program page if it is still live.
That is it. The infrastructure is already there. You just need to claim it.
A note on timing
AI authority is compounding and retrospective. Events from three years ago, properly documented now, still count. The signal is the independent third-party confirmation, not the recency.
Document everything you have. Start with the most prestigious institutions, work backwards. The window where this kind of structured documentation gives you a significant head start over your peers is probably 18 to 24 months from now.
After that, everyone will know about it and the advantage compresses.
Right now it is still early. For Indonesia especially.