SwiftSchemaGenerate
    Schema stack

    Safety / Trust & Safety Stack

    Trust & safety policy pages with WebPage + Organization context, FAQs, and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Web Page
    Organization
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Trust & safety policy pages for marketplaces or communities
    • Safety guidelines pages with reporting and enforcement details
    • Pages where FAQs clarify enforcement and appeal steps
    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

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

    Recommended properties

    • contactPoint.contactType
    • dateModified
    • inLanguage
    • itemListElement[].item
    • 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.

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "@id": "https://www.example.com/about#org",
    "name": "Example Marketplace",
    "url": "https://www.example.com",
    "logo": "https://www.example.com/assets/logo.svg"
  },
  {
    "@context": "https://schema.org",
    "@type": "WebPage",
    "@id": "https://www.example.com/trust-safety#page",
    "name": "Trust & Safety Policy",
    "description": "Policies and enforcement guidelines to keep the marketplace safe.",
    "url": "https://www.example.com/trust-safety",
    "inLanguage": "en-US",
    "dateModified": "2025-08-10"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How do I report a safety issue?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Report concerns through the Help Center or the in-app report feature."
        }
      },
      {
        "@type": "Question",
        "name": "What actions are taken on violations?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We investigate reports and may remove listings, suspend accounts, or escalate to authorities."
        }
      },
      {
        "@type": "Question",
        "name": "Can I appeal a decision?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Appeals can be submitted within 14 days through the support portal."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Trust & Safety", "item": "https://www.example.com/trust-safety" }
    ]
  }
]
    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 list emergency resources?

    Yes. If emergency resources are provided, include them in the page content and FAQs.

    Do I need separate pages for buyer and seller policies?

    If policies differ, split them into separate pages with their own WebPage entries.

    Primary sources

    References