SwiftSchemaGenerate
    Schema stack

    Marketplace Seller Onboarding Stack

    Seller onboarding pages with Organization + Offer context, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Marketplace seller signup and onboarding pages
    • Seller requirements and verification pages
    • Pages where FAQs clarify fees, approval, and payout timing
    Composition

    What is included

    • Organization

      Defines the marketplace brand inviting sellers.

    • Offer

      Describes the seller program offer and signup URL.

    • Frequently Asked Questions

      Answers questions about requirements, fees, and approval timelines.

    • Breadcrumb

      Provides navigation context for the seller onboarding 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/sell#org",
    "name": "Northwind Marketplace",
    "url": "https://www.example.com/sell",
    "logo": "https://www.example.com/assets/logo.svg",
    "sameAs": [
      "https://www.linkedin.com/company/northwind-marketplace"
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/sell#offer",
    "name": "Seller Onboarding Program",
    "price": "0.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/sell/apply",
    "eligibleRegion": "US",
    "description": "Apply to sell on Northwind Marketplace with access to analytics and fulfillment support."
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What documents are required?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Provide a business license or tax ID, bank account details, and product catalog."
        }
      },
      {
        "@type": "Question",
        "name": "How long does approval take?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most applications are reviewed within 3-5 business days."
        }
      },
      {
        "@type": "Question",
        "name": "What fees do sellers pay?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Sellers pay a per-order commission and optional fulfillment fees listed in the program terms."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Sell", "item": "https://www.example.com/sell" },
      { "@type": "ListItem", "position": 3, "name": "Onboarding", "item": "https://www.example.com/sell/onboarding" }
    ]
  }
]
    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 seller tiers?

    If tiers exist, add separate Offer entries with tier-specific fees and benefits.

    Do I need to mention payout timing?

    Yes. Include payout timing in page content and FAQ answers to set expectations.

    Primary sources

    References