SwiftSchemaGenerate
    Schema stack

    SaaS Upgrade / Downgrade Stack

    Plan change pages with Offer + WebApplication context, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Plan upgrade or downgrade landing pages
    • Self-serve account management plan change flows
    • Billing pages explaining proration, trials, and limits
    Composition

    What is included

    • Offer

      Represents the plan change offer and pricing details.

    • Web Application

      Describes the account management UI used to change plans.

    • Frequently Asked Questions

      Answers proration, billing cycle, and feature access questions.

    • Breadcrumb

      Provides navigation context for the plan change 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

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

    Recommended properties

    • description
    • eligibleCustomerType
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.url
    • priceValidUntil
    • softwareVersion
    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": "Offer",
    "@id": "https://www.example.com/account/plan-change#offer",
    "name": "Upgrade to Pro Plan",
    "description": "Unlock advanced analytics, priority support, and team workflows.",
    "price": "99.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/account/plan-change"
  },
  {
    "@context": "https://schema.org",
    "@type": "WebApplication",
    "@id": "https://www.example.com/account/plan-change#app",
    "name": "Plan Management Console",
    "description": "Manage upgrades, downgrades, and billing settings.",
    "applicationCategory": "BusinessApplication",
    "operatingSystem": "Any",
    "url": "https://www.example.com/account/plan-change",
    "offers": {
      "@type": "Offer",
      "url": "https://www.example.com/account/plan-change"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How does proration work?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Upgrades are prorated immediately, and credits apply to your next invoice."
        }
      },
      {
        "@type": "Question",
        "name": "Will I lose features if I downgrade?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Downgrades take effect at the end of the billing cycle; premium features remain active until then."
        }
      },
      {
        "@type": "Question",
        "name": "Can I switch plans anytime?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. You can change plans at any time from the plan management page."
        }
      }
    ]
  },
  {
    "@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": "Plan Change", "item": "https://www.example.com/account/plan-change" }
    ]
  }
]
    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 multiple plan options?

    Yes. Add one Offer per plan tier and match each to the corresponding CTA.

    How do I handle annual plans?

    Use separate Offer entries for monthly vs annual pricing or describe the billing cadence in the offer description.

    Primary sources

    References