Schema stack

    Franchise Opportunity Stack

    Franchise opportunity pages with Organization + Offer, FAQs, and breadcrumb navigation.

    Included schema
    Organization
    Offer
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Franchise landing pages outlining investment and requirements
    • Pages describing territory availability and onboarding process
    • Pages where FAQs cover fees, timelines, and support
    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

    • category
    • contactPoint.contactType
    • contactPoint.telephone
    • 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.

    [
      {
        "@context": "https://schema.org",
        "@type": "Organization",
        "@id": "https://www.example.com/franchise#org",
        "name": "FreshBowl",
        "url": "https://www.example.com/franchise",
        "logo": "https://www.example.com/assets/freshbowl-logo.png",
        "sameAs": [
          "https://www.linkedin.com/company/freshbowl",
          "https://www.instagram.com/freshbowl"
        ]
      },
      {
        "@context": "https://schema.org",
        "@type": "Offer",
        "@id": "https://www.example.com/franchise#offer",
        "name": "FreshBowl Franchise Fee",
        "description": "Initial franchise fee for a single unit location.",
        "price": "35000.00",
        "priceCurrency": "USD",
        "availability": "https://schema.org/InStock",
        "url": "https://www.example.com/franchise#apply",
        "category": "FranchiseFee",
        "eligibleRegion": "United States"
      },
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          {
            "@type": "Question",
            "name": "What is the total investment?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Total investment ranges from $250k to $450k depending on location and build-out."
            }
          },
          {
            "@type": "Question",
            "name": "Do you provide training?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Yes. New franchisees receive 4 weeks of onboarding plus ongoing operations support."
            }
          },
          {
            "@type": "Question",
            "name": "How long does it take to open?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Most locations open within 6-9 months after signing the franchise agreement."
            }
          }
        ]
      },
      {
        "@context": "https://schema.org",
        "@type": "BreadcrumbList",
        "itemListElement": [
          { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
          { "@type": "ListItem", "position": 2, "name": "Franchise", "item": "https://www.example.com/franchise" },
          { "@type": "ListItem", "position": 3, "name": "Apply", "item": "https://www.example.com/franchise#apply" }
        ]
      }
    ]
    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 territories?

    Yes. Add eligibleRegion details on the Offer or create separate Offers for each territory.

    Do I need to include royalties?

    If royalties are disclosed on the page, add them in the Offer description or in FAQ answers.

    Primary sources

    References