Stack

Support / Help Center Stack

Support/help pages with FAQs, speakable selectors, and breadcrumb navigation for clarity and discoverability.

Open generator Validate in Rich Results Test

When to use this stack

Help center articles and support pages
FAQ hubs that need voice-friendly selectors and navigation
Pages where structured FAQs improve self-serve resolution

What's included

Frequently Asked Questions
Open generator
Primary structure for support answers.
Speakable
Open generator
Optional voice-friendly selectors for key parts of the page.
Breadcrumb
Open generator
Navigation context within the help center.

Required properties (stack union)

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

itemListElement[].name

mainEntity[].@type=Question

mainEntity[].acceptedAnswer.text

speakable.cssSelector

Recommended properties (stack union)

itemListElement[].item

mainEntity[].acceptedAnswer.text

mainEntity[].author.name

mainEntity[].name

speakable.xpath

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": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How do I reset my password?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Go to Settings → Security → Reset Password. We’ll email you a reset link."
        }
      },
      {
        "@type": "Question",
        "name": "How do I contact support?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Email support@example.com or use the in-app chat. We respond within one business day."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "WebPage",
    "speakable": {
      "@type": "SpeakableSpecification",
      "cssSelector": [
        "h1",
        ".faq-question"
      ]
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Help Center", "item": "https://www.example.com/help" },
      { "@type": "ListItem", "position": 3, "name": "Account Access", "item": "https://www.example.com/help/account-access" }
    ]
  }
]

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

Do I need Speakable?

Use it if you want voice surfaces to highlight key parts of the help page. Otherwise omit that object.

Should I use multiple FAQPages?

Keep one FAQPage object per page with multiple questions in mainEntity. Use multiple pages for different topics.

SwiftSchema

Intuitive Schema Generation at Your Fingertips