SwiftSchemaGenerate
    Schema stack

    Influencer Sponsorship Offer Stack

    Creator sponsorship offer pages with Person + Offer context, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Influencer sponsorship rate card pages
    • Creator brand partnership inquiry pages
    • Pages where FAQs clarify deliverables, timelines, and usage rights
    Composition

    What is included

    • Person

      Defines the creator identity and profile URL.

    • Offer

      Describes sponsorship packages, pricing, and inquiry URL.

    • Frequently Asked Questions

      Answers questions about deliverables, usage rights, and timelines.

    • Breadcrumb

      Provides navigation context for the sponsorship offer 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
    • itemOffered.@id
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • price
    • priceCurrency
    • url

    Recommended properties

    • description
    • eligibleRegion
    • image
    • itemListElement[].item
    • jobTitle
    • 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": "Person",
    "@id": "https://www.example.com/creators/ava-lee#person",
    "name": "Ava Lee",
    "url": "https://www.example.com/creators/ava-lee",
    "image": "https://www.example.com/images/ava-lee.webp",
    "jobTitle": "Lifestyle Creator",
    "sameAs": [
      "https://www.instagram.com/ava",
      "https://www.youtube.com/@ava"
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/creators/ava-lee#offer",
    "name": "Sponsored Instagram Reel Package",
    "price": "1800.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/creators/ava-lee/sponsor",
    "itemOffered": { "@id": "https://www.example.com/creators/ava-lee#person" },
    "description": "One 30-60s Reel, 3 story frames, and usage rights for 30 days.",
    "eligibleRegion": "Worldwide"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What deliverables are included?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Packages include agreed deliverables such as a Reel, story frames, and a link in bio."
        }
      },
      {
        "@type": "Question",
        "name": "How long is the turnaround time?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Typical turnaround is 2–3 weeks from contract signature to posting."
        }
      },
      {
        "@type": "Question",
        "name": "Do you offer usage rights?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Usage rights are included for 30 days, with extensions available."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Creators", "item": "https://www.example.com/creators" },
      { "@type": "ListItem", "position": 3, "name": "Ava Lee", "item": "https://www.example.com/creators/ava-lee" }
    ]
  }
]
    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 sponsorship tiers?

    Yes. Add one Offer entry per package with its own price and deliverables.

    How do I represent campaign exclusivity?

    Mention exclusivity windows in the Offer description and ensure they match contract terms.

    Primary sources

    References