SwiftSchemaGenerate
    Schema stack

    Subscription Pause / Cancel Stack

    Subscription pause/cancel policy pages with Offer + WebPage context, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Subscription pause or cancel pages with policy details
    • Account management pages explaining plan changes
    • Pages where FAQs clarify refunds, proration, and reactivation
    Composition

    What is included

    • Web Page

      Defines the policy page and its purpose.

    • Offer

      Describes the subscription change offer and action URL.

    • Frequently Asked Questions

      Answers questions about proration, refunds, and reactivation.

    • Breadcrumb

      Provides navigation context for the policy page.

    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

    • availability
    • description
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • price
    • priceCurrency
    • url

    Recommended properties

    • dateModified
    • description
    • eligibleRegion
    • inLanguage
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • priceValidUntil
    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": "WebPage",
    "@id": "https://www.example.com/account/subscription#page",
    "name": "Pause or Cancel Subscription",
    "url": "https://www.example.com/account/subscription",
    "description": "Manage your subscription status, including pausing or canceling your plan."
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/account/subscription#offer",
    "name": "Subscription Pause or Cancel",
    "price": "0.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/account/subscription/manage",
    "description": "Pause billing for up to 3 months or cancel your plan anytime."
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Will I receive a refund if I cancel?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Refunds are not issued for partial months. You retain access until the end of your billing period."
        }
      },
      {
        "@type": "Question",
        "name": "Can I reactivate after pausing?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. You can resume your subscription at any time from the account portal."
        }
      },
      {
        "@type": "Question",
        "name": "What happens to my data?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Your data is retained during a pause and remains available upon reactivation."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Account", "item": "https://www.example.com/account" },
      { "@type": "ListItem", "position": 3, "name": "Subscription", "item": "https://www.example.com/account/subscription" }
    ]
  }
]
    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 multiple plans?

    If pause/cancel terms differ by plan, add separate Offer entries for each plan’s policy.

    Do I need to mention proration?

    Yes. Document proration or refund rules in the page content and FAQ answers.

    Primary sources

    References