SwiftSchemaGenerate
    Schema stack

    Wedding Vendor Directory Stack

    Wedding vendor directories with ItemList + LocalBusiness, FAQs, and breadcrumb navigation.

    Open generatorValidate in Rich Results Test
    Included schema
    Item List
    Local Business
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Wedding vendor directories listing multiple providers
    • Category pages (photographers, florists, venues) with filters
    • Pages where FAQs clarify booking, pricing, and availability
    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

    • address.addressCountry
    • address.addressLocality
    • address.addressRegion
    • address.postalCode
    • address.streetAddress
    • itemListElement[].name
    • itemListElement[].url
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • url

    Recommended properties

    • image
    • itemListElement[].item
    • itemListOrder
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • numberOfItems
    • priceRange
    • servesCuisine
    • telephone
    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": "ItemList",
    "@id": "https://www.example.com/weddings/vendors#list",
    "name": "Austin Wedding Photographers",
    "itemListOrder": "https://schema.org/ItemListOrderAscending",
    "numberOfItems": 3,
    "itemListElement": [
      {
        "@type": "ListItem",
        "position": 1,
        "name": "Harbor Light Photography",
        "url": "https://www.example.com/weddings/vendors/harbor-light"
      },
      {
        "@type": "ListItem",
        "position": 2,
        "name": "Golden Hour Studio",
        "url": "https://www.example.com/weddings/vendors/golden-hour"
      },
      {
        "@type": "ListItem",
        "position": 3,
        "name": "Juniper Wedding Photos",
        "url": "https://www.example.com/weddings/vendors/juniper"
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "LocalBusiness",
    "@id": "https://www.example.com/weddings/vendors/harbor-light#business",
    "name": "Harbor Light Photography",
    "url": "https://www.example.com/weddings/vendors/harbor-light",
    "telephone": "+1-512-555-0194",
    "image": "https://www.example.com/images/harbor-light.webp",
    "priceRange": "$$$",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "210 Congress Ave",
      "addressLocality": "Austin",
      "addressRegion": "TX",
      "postalCode": "78701",
      "addressCountry": "US"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "How far in advance should we book?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Most vendors recommend booking 6–12 months in advance for peak season dates."
        }
      },
      {
        "@type": "Question",
        "name": "Do vendors require deposits?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. A signed contract and deposit are typically required to hold your date."
        }
      },
      {
        "@type": "Question",
        "name": "Can we schedule site visits?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Many vendors offer virtual or in-person consultations before booking."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Weddings", "item": "https://www.example.com/weddings" },
      { "@type": "ListItem", "position": 3, "name": "Vendors", "item": "https://www.example.com/weddings/vendors" }
    ]
  }
]
    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 each vendor also have its own page?

    Yes. Link each ListItem to a dedicated vendor page with its own LocalBusiness schema.

    Do I need one LocalBusiness per vendor?

    If you display multiple vendors, include a LocalBusiness entry for each vendor shown on the page.

    Primary sources

    References