SwiftSchemaGenerate
    Schema stack

    Affiliate Program Stack

    Affiliate signup 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

    • Affiliate program landing pages with commission details
    • Partner signup pages for referral programs
    • Pages where FAQs clarify payouts and tracking
    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
    • 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/affiliates#org",
    "name": "Example SaaS",
    "url": "https://www.example.com",
    "logo": "https://www.example.com/assets/logo.svg",
    "sameAs": [
      "https://www.linkedin.com/company/example-saas"
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/affiliates#offer",
    "name": "Example SaaS Affiliate Program",
    "description": "Earn 20% recurring commissions for referred customers.",
    "price": "0.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/affiliates/apply",
    "eligibleRegion": "Worldwide"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How do payouts work?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Payouts are issued monthly once you reach the minimum threshold."
        }
      },
      {
        "@type": "Question",
        "name": "How is referral tracking handled?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Each affiliate gets a unique tracking link with a 30-day cookie window."
        }
      },
      {
        "@type": "Question",
        "name": "Are there restrictions on promotion?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Paid search and coupon sites require prior approval."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Affiliates", "item": "https://www.example.com/affiliates" }
    ]
  }
]
    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 commission tiers?

    If you offer tiered commissions, add a separate Offer entry for each tier.

    Do I need a separate affiliate terms page?

    If terms are lengthy, link to a separate terms page and keep key points summarized here.

    Primary sources

    References