SwiftSchemaGenerate
    Schema stack

    Transcript Stack

    Transcript pages tying an Article to the source media (audio/video), with FAQs and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Article
    Audio Object
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Podcast or video episode transcript pages
    • Accessibility transcripts for audio/video content
    • Pages where FAQs clarify availability, licensing, and sharing
    Composition

    What is included

    • Article

      Represents the transcript page content with dates and authorship.

    • Audio Object

      Anchors the source media with URL, format, and transcript text.

    • Frequently Asked Questions

      Answers common questions about availability, licensing, and downloads.

    • Breadcrumb

      Provides navigation context to the transcript page.

    Data contract

    Properties across the bundle

    Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.

    Required properties

    • author.name
    • contentUrl
    • datePublished
    • description
    • duration
    • headline
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • transcript
    • url

    Recommended properties

    • associatedMedia.@id
    • dateModified
    • encodingFormat
    • inLanguage
    • itemListElement[].item
    • mainEntityOfPage
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • uploadDate
    Copy-ready example

    Combined JSON-LD

    Paste this as one script tag, then replace every example value with data from the live page.

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "@id": "https://www.example.com/podcast/episode-12/transcript#article",
    "headline": "Episode 12 Transcript — Scaling APIs",
    "description": "Full transcript for Episode 12 covering API scaling patterns.",
    "datePublished": "2025-02-18",
    "dateModified": "2025-02-18",
    "url": "https://www.example.com/podcast/episode-12/transcript",
    "author": { "@type": "Person", "name": "Alex Kim" },
    "mainEntityOfPage": "https://www.example.com/podcast/episode-12/transcript",
    "associatedMedia": { "@id": "https://www.example.com/podcast/episode-12/audio#media" }
  },
  {
    "@context": "https://schema.org",
    "@type": "AudioObject",
    "@id": "https://www.example.com/podcast/episode-12/audio#media",
    "name": "Episode 12 — Scaling APIs",
    "description": "Podcast episode discussing API scaling patterns.",
    "contentUrl": "https://cdn.example.com/audio/episode-12.mp3",
    "encodingFormat": "audio/mpeg",
    "duration": "PT42M10S",
    "inLanguage": "en",
    "uploadDate": "2025-02-18",
    "transcript": "In this episode, we explore API scaling patterns including rate limiting, caching, and fan-out controls..."
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Can I download the audio?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Use the download link on the episode page. The transcript remains available for on-site viewing."
        }
      },
      {
        "@type": "Question",
        "name": "Is this transcript licensed for reuse?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "You may quote short excerpts with attribution. For full reuse, contact us for permission."
        }
      },
      {
        "@type": "Question",
        "name": "Do you support other languages?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We publish transcripts in English. Machine-translated versions are planned for a future release."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Podcast", "item": "https://www.example.com/podcast" },
      { "@type": "ListItem", "position": 3, "name": "Episode 12 Transcript", "item": "https://www.example.com/podcast/episode-12/transcript" }
    ]
  }
]
    Workflow

    Implement and verify

    1. 01

      Start with the live page

      Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.

    2. 02

      Add one JSON-LD script

      Use the combined example as a template in the document head or before the closing body tag.

    3. 03

      Complete regional details

      Fill shipping destinations and timing for every region the page actually serves.

    4. 04

      Link the return policy

      Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.

    5. 05

      Match visible answers

      Add only FAQs that users can read on the same page, with identical answers.

    6. 06

      Validate after changes

      Run Rich Results Test after implementation and whenever price, availability, or policy data changes.

    Quality check

    Common errors and fixes

    • Missing currency or availability

      Use ISO currency codes and complete schema.org availability URLs in Offer data.

    • Incomplete shipping details

      Include shippingDestination.addressCountry and deliveryTime.transitTime with units.

    • Return policy is not connected

      Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.

    • FAQ answers differ from the page

      Keep structured FAQ answers identical to visible answers.

    Questions

    Stack FAQs

    Do I need both Article and AudioObject?

    Yes. Article represents the transcript page; AudioObject anchors the source media and includes the transcript text.

    What if the source is video?

    Swap AudioObject for VideoObject when the transcript is for video content, and align required fields accordingly.

    Primary sources

    References