SwiftSchemaGenerate
    Schema stack

    Partner Program Stack

    Partner/affiliate program pages with Organization + Offer, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Partner/affiliate program enrollment pages
    • Program overview pages that highlight benefits and terms
    • Pages where FAQs clarify eligibility, payouts, and onboarding
    Composition

    What is included

    • Organization

      Anchors the brand offering the partner program.

    • Offer

      Expresses the partner/affiliate program benefits and terms.

    • Frequently Asked Questions

      Answers eligibility, payout, and onboarding questions.

    • Breadcrumb

      Provides navigation context to the partner program 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
    • itemListElement[].name
    • logo
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • price
    • priceCurrency
    • url

    Recommended properties

    • contactPoint.contactType
    • description
    • eligibleRegion
    • itemListElement[].item
    • 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/partners#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"
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/partners#offer",
    "name": "Example Partner Program",
    "description": "Earn recurring commissions and get co-marketing resources as an Example partner.",
    "price": "0.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/partners/apply",
    "eligibleRegion": "Worldwide"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Who can apply?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Agencies, consultants, and creators with relevant audiences can apply. We review applications within 5 business days."
        }
      },
      {
        "@type": "Question",
        "name": "How are commissions paid?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We pay monthly via ACH or PayPal once you reach the minimum payout threshold. See program terms for details."
        }
      },
      {
        "@type": "Question",
        "name": "Do you provide co-marketing materials?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Partners get access to a content kit, product updates, and joint webinar opportunities."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Partners", "item": "https://www.example.com/partners" }
    ]
  }
]
    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 the Offer be $0.00?

    Yes for a free partner/affiliate program. If you charge a fee, reflect the real price and currency.

    Can I add multiple offer tiers?

    Add one Offer per tier visible on the page, each with its own URL and eligibility details.

    Primary sources

    References