Get found & cited

Audio is invisible to the systems people ask questions to. Search engines can't rank what has no page; answer engines can't cite what they can't quote. PodHood's core job is turning each episode into surfaces those systems can actually use — automatically, on every indexing.

What every episode publishes

For search engines — a fast, canonical episode page with real text: the summary, chapters, and full transcript, listed in the host's sitemap.xml. Structured data rides along as Schema.org JSON-LD: a PodcastEpisode with chapters and key moments as deep-linked Clip nodes, plus speakers and entities. That's what makes an episode eligible for rich results, not just a bare link.

For answer engines — the same content in the forms ChatGPT, Perplexity, and AI Overviews prefer to consume:

• A Markdown twin of every page: append .md to any episode URL (or send Accept: text/markdown) for the clean-text version.
• llms.txt on every Library host — the machine-readable index of the whole show, listing episodes and the channel's MCP endpoint.
• An open robots.txt: AI crawlers are welcome by default.

For citation precision — everything is timestamped. Chapters, key moments, and search results resolve to URLs that deep-link the exact second, so a citation lands on the moment something was said, not a 2-hour file.

Why this beats show notes

A typical episode's web presence is a paragraph of show notes on a platform page. An answer engine deciding what to cite is choosing between that paragraph and a structured page with the full transcript, entities, and quotable timestamped moments. The structure is the pitch: the same graph that powers your Library is what makes you citable.

How to check it's working

1. Look at your machine surfaces. Open yourshow.podhood.com/llms.txt in a browser — your episodes should be listed. Append .md to any episode URL and you'll see the clean-text twin, exactly as an AI crawler does.
2. Inspect the structured data. Run an episode URL through Google's Rich Results Test; the PodcastEpisode and its Clip nodes should validate.
3. Watch Google. Add your Library host (or custom domain) to Search Console and watch indexed pages grow as you backfill.
4. Ask the engines. Ask ChatGPT or Perplexity a question your show answered squarely — with browsing on — and see whether your episode page appears among the sources. Fresh indexes take time to be crawled; the back catalog compounds.