Schema stack

    Multi-Author Blog Stack

    Blog hubs with CollectionPage + BlogPosting + Person context, FAQs, and breadcrumb navigation.

    Included schema
    Collection Page
    Blog Post
    Person
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Blog homepages with multiple authors and contributor bios
    • Editorial hubs highlighting posts and author pages
    • Pages where FAQs clarify submissions, editorial policy, and attribution
    Composition

    What is included

    • Defines the blog homepage and its content summary.

    • Represents featured blog posts with authors and publish dates.

    • Represents the authors contributing to the blog.

    • Answers submission, attribution, and editorial questions.

    • Provides navigation context to the blog homepage.

    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
    • datePublished
    • description
    • headline
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • url

    Recommended properties

    • author.@id
    • description
    • image
    • inLanguage
    • itemListElement[].item
    • jobTitle
    • mainEntity.@id
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • sameAs[]
    Copy-ready example

    Combined JSON-LD

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

    [
      {
        "@context": "https://schema.org",
        "@type": "CollectionPage",
        "@id": "https://www.example.com/blog#page",
        "name": "Example Blog",
        "description": "Insights, product updates, and growth strategy from the Example team.",
        "url": "https://www.example.com/blog",
        "inLanguage": "en",
        "mainEntity": { "@id": "https://www.example.com/blog#blog" }
      },
      {
        "@context": "https://schema.org",
        "@type": "BlogPosting",
        "@id": "https://www.example.com/blog/launch-week#post",
        "headline": "Launch Week Recap: What Shipped and What's Next",
        "description": "A recap of our biggest launches, roadmap updates, and lessons learned.",
        "datePublished": "2025-02-18",
        "url": "https://www.example.com/blog/launch-week",
        "image": "https://www.example.com/images/blog/launch-week.webp",
        "author": {
          "@id": "https://www.example.com/blog/authors/jordan-lee#author",
          "name": "Jordan Lee"
        }
      },
      {
        "@context": "https://schema.org",
        "@type": "BlogPosting",
        "@id": "https://www.example.com/blog/scaling-support#post",
        "headline": "Scaling Support Without Sacrificing Quality",
        "description": "How we restructured support workflows and doubled response speed.",
        "datePublished": "2025-03-03",
        "url": "https://www.example.com/blog/scaling-support",
        "image": "https://www.example.com/images/blog/scaling-support.webp",
        "author": {
          "@id": "https://www.example.com/blog/authors/amina-hassan#author",
          "name": "Amina Hassan"
        }
      },
      {
        "@context": "https://schema.org",
        "@type": "Person",
        "@id": "https://www.example.com/blog/authors/jordan-lee#author",
        "name": "Jordan Lee",
        "jobTitle": "Senior Product Manager",
        "url": "https://www.example.com/blog/authors/jordan-lee",
        "image": "https://www.example.com/images/authors/jordan-lee.webp"
      },
      {
        "@context": "https://schema.org",
        "@type": "Person",
        "@id": "https://www.example.com/blog/authors/amina-hassan#author",
        "name": "Amina Hassan",
        "jobTitle": "Staff Engineer",
        "url": "https://www.example.com/blog/authors/amina-hassan",
        "image": "https://www.example.com/images/authors/amina-hassan.webp"
      },
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          {
            "@type": "Question",
            "name": "Do you accept guest posts?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Yes. We review pitches monthly and prioritize original research and tactical guides."
            }
          },
          {
            "@type": "Question",
            "name": "How do you handle author attribution?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Each post includes a byline, author bio, and links to the author profile page."
            }
          },
          {
            "@type": "Question",
            "name": "Can I republish your content?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "You may quote with attribution and a canonical link. Full republication requires permission."
            }
          }
        ]
      },
      {
        "@context": "https://schema.org",
        "@type": "BreadcrumbList",
        "itemListElement": [
          { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
          { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://www.example.com/blog" }
        ]
      }
    ]
    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

    Should I add author pages separately?

    Yes. Link to author profile pages and include Person objects for each author shown on the blog homepage.

    Do I need BlogPosting or just CollectionPage?

    Include BlogPosting for the featured posts shown on the homepage; it clarifies post-level details and authorship.

    Primary sources

    References