By Junaid Ahmed
Here is something that bothered me about the public pages we launched a few months ago.
A guest page shows your appearances. Good. But if a listener found the episode first and wanted to know more about the guest, there was nothing. No link. No name card. Just the episode, floating on its own.
An episode page had the audio, the description, the artwork. But the guest who showed up and made that conversation worth listening to? Invisible.
A podcast directory page listed the shows. But if you wanted to see who had been on a show before booking a guest slot, you had to go somewhere else. We had three surfaces with the same underlying information, and none of them talked to each other.
That is fixed now.
Every public episode page on podglue.com shows a card for the featured guest: their photo, their headline, and a link straight to their portfolio at /@handle. Below that, a row of other episodes they have appeared on across PodGlue podcasts. So if a listener is halfway through an interview and wants more, they can follow the guest, not just the show.
Every guest portfolio page now shows a verified "On PodGlue" appearances section. Not self-reported. Pulled from the actual episodes tied to their profile.
Every public podcast directory page shows the guests who have been on that show. If someone is deciding whether to pitch a show as a guest, they can see who else the host has talked to. That is real signal.
There is a part of this that matters more than the design.
All three page types now emit structured JSON-LD data. Person schema on guest pages. PodcastEpisode schema on episode pages. PodcastSeries schema on show pages. With the cross-links built in.
That means search engines do not just see a page. They see a graph. A guest, their appearances, the shows they appeared on, all connected in a format search engines actually read.
It is quiet infrastructure. Nobody tweets about JSON-LD. But it is the kind of thing that compounds over months.
This was the part of the guest portfolio project I could not get to in the first release. We built the addresses for guest appearances: podglue.com/@you. But an address is not much on its own if no one can find their way there from the episodes themselves.
Now they can.
If you have a guest portfolio on PodGlue, check your appearances section. If you host a show, open a public episode page and scroll down. The graph was always there in the data. We just made it visible.
What is next: topics pulled from transcript text, a quote bank, and appearance search for guests who want to find moments across everything they have recorded. The more episodes you have on PodGlue, the more useful that gets.
PodGlue is built around the idea that your best content is what you have already made. You just need the right place to surface it. This is another step in that direction.
Ready to make every episode compound?
PodGlue is the operating system for relationship-driven podcasters.
Get Started FreeRelated reading
Your Guest Appearances Deserve an Address
You've been on twelve podcasts. Maybe thirty. Where do they live? A LinkedIn post that scrolled away. A link in a bio somewhere. We just gave every guest a single address for all of it: podglue.com/@you.
The Blank Box Problem
Every press release needs an 'about the show' paragraph. We added a field for it and then watched everyone leave it empty. So we taught PodGlue to write the first draft.
600 Episodes and Nobody Got Credit
I imported my entire back catalog into PodGlue and discovered something embarrassing: hundreds of episodes with guest names right there in the title, and not one of them linked to an actual guest. Here's what we fixed.