SwiftSchemaGenerate
    Schema stack

    Security Advisory Stack

    Security advisories with Article + SoftwareApplication context, FAQs, and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Article
    Software App
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Security vulnerability advisories tied to a product or app
    • CVE-style posts that need affected product/version context
    • Pages where FAQs address impact, remediation, and timeline
    Composition

    What is included

    • Article

      Represents the advisory content with headline, dates, and author/publisher.

    • Software App

      Anchors the affected product/application with version details.

    • Frequently Asked Questions

      Answers remediation, impact, and upgrade guidance.

    • Breadcrumb

      Provides navigation context from the security hub.

    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

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

    Recommended properties

    • about.@id
    • dateModified
    • inLanguage
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.url
    • publisher.name
    • softwareVersion
    • url
    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/security/advisories/2025-01-sso-bypass#article",
    "headline": "Security Advisory: SSO Bypass in Legacy SAML Flow",
    "description": "We identified and fixed an SSO bypass affecting legacy SAML configs. Update to v5.12.3 or apply the mitigation.",
    "datePublished": "2025-01-20",
    "dateModified": "2025-01-21",
    "inLanguage": "en",
    "url": "https://www.example.com/security/advisories/2025-01-sso-bypass",
    "author": { "@type": "Organization", "name": "Example Security Team" },
    "publisher": { "@type": "Organization", "name": "Example Corp" },
    "about": { "@id": "https://www.example.com/security/advisories/2025-01-sso-bypass#app" }
  },
  {
    "@context": "https://schema.org",
    "@type": "SoftwareApplication",
    "@id": "https://www.example.com/security/advisories/2025-01-sso-bypass#app",
    "name": "Example Identity Suite",
    "applicationCategory": "Security",
    "operatingSystem": "SaaS",
    "softwareVersion": "5.12.2",
    "offers": {
      "@type": "Offer",
      "url": "https://www.example.com/security/releases/5.12.3"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Which versions are affected?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Versions 5.10.0 through 5.12.2 with legacy SAML enabled are affected. Versions 5.12.3+ are patched."
        }
      },
      {
        "@type": "Question",
        "name": "What is the fix?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Upgrade to 5.12.3 or later. As a temporary mitigation, disable legacy SAML and enforce modern SSO policies."
        }
      },
      {
        "@type": "Question",
        "name": "Is there any evidence of exploitation?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We have no evidence of exploitation. Logs and IDS rules have been updated to detect attempts. Contact security@example.com with questions."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Security Advisories", "item": "https://www.example.com/security/advisories" },
      { "@type": "ListItem", "position": 3, "name": "SSO Bypass (2025-01)", "item": "https://www.example.com/security/advisories/2025-01-sso-bypass" }
    ]
  }
]
    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 include CVE IDs?

    Include the CVE in the Article body and headline if assigned. Keep JSON-LD aligned with what’s visible on the page.

    How do I show multiple affected products?

    Add one SoftwareApplication object per affected product/version and link them from the Article via about.@id.

    Primary sources

    References