SwiftSchemaGenerate
    Schema stack

    Resource Library Stack

    Resource/library hubs with a CollectionPage of articles, FAQs, and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Collection Page
    Article
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Content hubs aggregating guides, reports, and tutorials
    • Marketing resource centers that need structured navigation
    • Pages where FAQs clarify what’s included and how often it updates
    Composition

    What is included

    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

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

    Recommended properties

    • author.name
    • dateModified
    • description
    • inLanguage
    • itemListElement[].item
    • mainEntity.@id
    • mainEntityOfPage
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    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": "CollectionPage",
    "@id": "https://www.example.com/resources#page",
    "name": "Resource Library",
    "description": "Guides, tutorials, and reports to help you get more from Example Platform.",
    "url": "https://www.example.com/resources",
    "inLanguage": "en",
    "mainEntity": {
      "@type": "Article",
      "@id": "https://www.example.com/resources/guide-to-migration#article"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "Article",
    "@id": "https://www.example.com/resources/guide-to-migration#article",
    "headline": "Migration Guide for Teams",
    "description": "Step-by-step guidance to migrate from LegacyApp to Example Platform.",
    "datePublished": "2025-01-10",
    "dateModified": "2025-01-10",
    "url": "https://www.example.com/resources/guide-to-migration",
    "author": { "@type": "Organization", "name": "Example Platform" }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Do I need an account to access resources?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most resources are public. Some premium reports require a free account to download."
        }
      },
      {
        "@type": "Question",
        "name": "How often is the library updated?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We add new guides weekly and refresh key reports at least once per quarter."
        }
      },
      {
        "@type": "Question",
        "name": "Can I share the guides?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "You may share links freely. Do not host the files elsewhere; link back to this page."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Resources", "item": "https://www.example.com/resources" }
    ]
  }
]
    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

    How many Articles should I list?

    Include at least one Article object that’s visible on the page; for multiple items, add one Article per visible resource.

    Can this work for mixed media?

    Yes. Swap Article for VideoObject or CreativeWork for other media types that are actually on the page.

    Primary sources

    References