Stack

Trust / Security Stack

Trust & security center pages with WebPage context, Organization identity, FAQs, and breadcrumb navigation.

Open generator Validate in Rich Results Test

When to use this stack

Trust/security center pages that outline policies, certifications, and contacts
Security/compliance hubs that link to SOC 2/ISO, pen tests, and incident response
Pages where FAQs address data handling, encryption, and responsible disclosure

What's included

Web Page
Open generator
Declares the page as the trust/security hub.
Organization
Open generator
Anchors the brand identity, contact, and logo for trust context.
Frequently Asked Questions
Open generator
Answers top trust/compliance questions.
Breadcrumb
Open generator
Provides navigation context within the security/compliance section.

Required properties (stack union)

Ensure every applicable required property is present in your implementation. Nested props reference their parent objects (for example, `offers.priceCurrency`).

description

itemListElement[].name

logo

mainEntity[].@type=Question

mainEntity[].acceptedAnswer.text

name

url

Recommended properties (stack union)

contactPoint.contactType

contactPoint.telephone

dateModified

inLanguage

itemListElement[].item

mainEntity[].acceptedAnswer.text

mainEntity[].author.name

mainEntity[].name

sameAs

Combined JSON-LD

Paste as a single script tag. Keep product details, offer data, shipping/returns, and FAQ answers in sync with the page.

Validate

[
  {
    "@context": "https://schema.org",
    "@type": "WebPage",
    "@id": "https://www.example.com/trust#page",
    "name": "Trust & Security — Example Corp",
    "description": "Security, privacy, compliance, and incident response at Example Corp.",
    "url": "https://www.example.com/trust",
    "inLanguage": "en",
    "dateModified": "2025-02-10"
  },
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "@id": "https://www.example.com/#org",
    "name": "Example Corp",
    "url": "https://www.example.com",
    "logo": "https://www.example.com/assets/logo.svg",
    "sameAs": [
      "https://www.linkedin.com/company/example-corp"
    ],
    "contactPoint": [
      {
        "@type": "ContactPoint",
        "telephone": "+1-415-555-0100",
        "contactType": "security"
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Do you have SOC 2 or ISO certifications?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. We maintain SOC 2 Type II and ISO 27001. Request the latest reports from our security team."
        }
      },
      {
        "@type": "Question",
        "name": "How do you handle encryption?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Data is encrypted in transit with TLS 1.2+ and at rest with AES-256. Keys are managed via a hardened KMS."
        }
      },
      {
        "@type": "Question",
        "name": "How do I report a vulnerability?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Email security@example.com with reproduction steps. We follow a 48-hour acknowledgement SLA and prioritize remediation based on severity."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Trust & Security", "item": "https://www.example.com/trust" }
    ]
  }
]

Implementation steps

Start from your live product detail page content; ensure titles, prices, and availability match the page.
Embed one JSON-LD script in the head or just before the closing body tag using the combined example as a template.
Fill shipping details for each region you serve and keep them aligned with on-page shipping tables.
Attach your canonical MerchantReturnPolicy URL and keep the policy text in sync with Merchant Center.
Add 3–6 FAQs that address purchase blockers (shipping, returns, compatibility) and keep answers consistent with visible content.
Validate in the Rich Results Test and revalidate after price/availability/policy changes.

Common errors and fixes

Missing currency or availability: ensure `offers.priceCurrency` and `offers.availability` use ISO currency codes and schema URLs.
ShippingDetails missing destination or transit time: include `shippingDestination.addressCountry` and `deliveryTime.transitTime` with units.
MerchantReturnPolicy not linked: reference it from the Offer via `hasMerchantReturnPolicy` and provide a stable policy URL.
FAQ answers don't match the page: keep FAQ content identical to visible answers to avoid review or manual actions.

FAQs

Should I include every certification?

List only certifications you actually hold and keep report links gated if needed; ensure on-page content matches the JSON-LD.

Where do I link incident status?

Link your status page from the WebPage body and FAQ answers; keep URLs stable and use https.

SwiftSchema

Intuitive Schema Generation at Your Fingertips