SwiftSchemaGenerate
    Schema stack

    HOA Dues / Payment Stack

    HOA dues payment 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

    • HOA payment portals with dues schedules
    • Resident portals for recurring assessments
    • Pages where FAQs clarify payment methods, late fees, and receipts
    Composition

    What is included

    • Organization

      Defines the HOA or management company collecting dues.

    • Offer

      Describes the dues payment offer and payment URL.

    • Frequently Asked Questions

      Answers questions about billing cycles, methods, and late fees.

    • Breadcrumb

      Provides navigation context for the payment 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.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.

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "@id": "https://www.example.com/hoa#org",
    "name": "Northwind HOA",
    "url": "https://www.example.com/hoa",
    "logo": "https://www.example.com/assets/logo.svg",
    "contactPoint": {
      "@type": "ContactPoint",
      "telephone": "+1-512-555-0151",
      "contactType": "HOA Billing"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "Offer",
    "@id": "https://www.example.com/hoa#dues",
    "name": "Quarterly HOA Dues",
    "price": "325.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/hoa/pay",
    "description": "Quarterly assessment due on the 1st of January, April, July, and October."
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What payment methods are accepted?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "We accept ACH, credit card, and mailed checks."
        }
      },
      {
        "@type": "Question",
        "name": "When are dues late?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Payments are late after the 10th and may incur a late fee."
        }
      },
      {
        "@type": "Question",
        "name": "Can I set up autopay?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. Enable autopay in the portal to avoid missed payments."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "HOA", "item": "https://www.example.com/hoa" },
      { "@type": "ListItem", "position": 3, "name": "Payments", "item": "https://www.example.com/hoa/pay" }
    ]
  }
]
    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 fee types?

    If multiple fees exist (dues, assessments, fines), add separate Offer entries for each.

    Do I need to show due dates?

    Yes. Include due dates in the page content and Offer description to avoid confusion.

    Primary sources

    References