SwiftSchemaGenerate
    Schema stack

    Wedding Venue Stack

    Wedding venue landing pages with Place + Offer context, FAQs, and breadcrumb navigation.

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

    When to use this stack

    • Wedding venue pages listing packages, capacity, and pricing
    • Venue location pages that need clear NAP + offer signals
    • Pages where FAQs cover availability, policies, and inclusions
    Composition

    What is included

    • Place

      Anchors the venue’s identity, location, and contact details.

    • Offer

      Describes the booking offer/package with price and CTA URL.

    • Frequently Asked Questions

      Answers questions about capacity, policies, and availability.

    • Breadcrumb

      Provides navigation context to the venue 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

    • address.addressCountry
    • address.addressLocality
    • address.addressRegion
    • address.postalCode
    • address.streetAddress
    • availability
    • itemListElement[].name
    • itemOffered.@id
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • price
    • priceCurrency
    • telephone
    • url

    Recommended properties

    • aggregateRating.ratingValue
    • aggregateRating.reviewCount
    • category
    • description
    • geo.latitude
    • geo.longitude
    • image
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • priceValidUntil
    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": "Place",
    "@id": "https://www.example.com/venues/riverhouse#venue",
    "name": "Riverhouse Wedding Venue",
    "url": "https://www.example.com/venues/riverhouse",
    "telephone": "+1-503-555-0147",
    "image": "https://www.example.com/images/riverhouse.webp",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "200 Riverside Dr",
      "addressLocality": "Portland",
      "addressRegion": "OR",
      "postalCode": "97204",
      "addressCountry": "US"
    },
    "aggregateRating": {
      "@type": "AggregateRating",
      "ratingValue": "4.7",
      "reviewCount": "128"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/venues/riverhouse#offer",
    "name": "Riverhouse Wedding Package",
    "price": "5800.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/venues/riverhouse#book",
    "category": "WeddingVenuePackage",
    "itemOffered": { "@id": "https://www.example.com/venues/riverhouse#venue" },
    "description": "Full-day venue rental, on-site coordination, tables/chairs, and bridal suite access."
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What is the capacity?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Up to 180 seated guests indoors and 220 with tented outdoor space."
        }
      },
      {
        "@type": "Question",
        "name": "Can we bring our own catering?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Choose from our preferred list or bring your own licensed caterer with proof of insurance."
        }
      },
      {
        "@type": "Question",
        "name": "Is there on-site parking?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes, 80 on-site spaces plus valet options for larger parties."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Venues", "item": "https://www.example.com/venues" },
      { "@type": "ListItem", "position": 3, "name": "Riverhouse", "item": "https://www.example.com/venues/riverhouse" }
    ]
  }
]
    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

    Can I show multiple packages?

    Yes. Use one Offer per package, each pointing to the same Place via itemOffered.@id and unique @id values.

    What if pricing is by quote?

    If no price is shown, omit price fields and keep availability/url aligned to the visible CTA for quote requests.

    Primary sources

    References