SwiftSchemaGenerate
    Schema stack

    Loyalty Tier Upgrade Stack

    Loyalty tier upgrade pages with Organization and Offer context, FAQs, and breadcrumbs.

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

    When to use this stack

    • Loyalty program tier upgrade landing pages
    • Status match or tier boost offers
    • Membership upgrade pages with benefits and thresholds
    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

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

    Recommended properties

    • category
    • contactPoint
    • description
    • itemListElement[].item
    • legalName
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • priceValidUntil
    • 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/loyalty#org",
    "name": "Northwind Loyalty",
    "url": "https://www.example.com/loyalty",
    "contactPoint": {
      "@type": "ContactPoint",
      "contactType": "Loyalty Support",
      "email": "loyalty@example.com"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/loyalty/tier-upgrade#offer",
    "name": "Gold Tier Upgrade",
    "description": "Upgrade to Gold tier after spending $1,500 in 90 days.",
    "price": "0.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/loyalty/tier-upgrade#apply",
    "priceValidUntil": "2025-12-31"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Who can apply for a tier upgrade?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Active members with a verified account can apply for a tier upgrade."
        }
      },
      {
        "@type": "Question",
        "name": "How long does the upgrade take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Upgrades are typically processed within 3 to 5 business days."
        }
      },
      {
        "@type": "Question",
        "name": "What benefits are included?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Gold members receive bonus points, priority support, and early access to offers."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Loyalty", "item": "https://www.example.com/loyalty" },
      { "@type": "ListItem", "position": 3, "name": "Tier Upgrade", "item": "https://www.example.com/loyalty/tier-upgrade" }
    ]
  }
]
    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 spend thresholds?

    If thresholds are shown, include them in the Offer description or FAQ answers.

    How do I show limited-time upgrades?

    Use priceValidUntil to reflect the offer end date and match it to the page copy.

    Primary sources

    References