Real Estate Community Stack
Community/HOA pages with Place + Offer context, FAQs, and breadcrumb navigation.
When to use this stack
- Master-planned community pages with amenities and pricing
- HOA/community landing pages for prospective buyers
- Pages where FAQs clarify fees, rules, and availability
What is included
Anchors the community location, identity, and address.
Represents community pricing or availability with a CTA URL.
Answers questions about HOA fees, amenities, and rules.
Provides navigation context to the community page.
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
- url
Recommended properties
- category
- description
- geo.latitude
- geo.longitude
- image
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- priceValidUntil
- telephone
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": "Place",
"@id": "https://www.example.com/communities/oak-ridge#place",
"name": "Oak Ridge Community",
"url": "https://www.example.com/communities/oak-ridge",
"image": "https://www.example.com/images/oak-ridge.webp",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Oak Ridge Pkwy",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78748",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": "30.1705",
"longitude": "-97.8225"
}
},
{
"@context": "https://schema.org",
"@type": "Offer",
"@id": "https://www.example.com/communities/oak-ridge#offer",
"name": "Homes from $425,000",
"price": "425000",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/communities/oak-ridge#availability",
"itemOffered": { "@id": "https://www.example.com/communities/oak-ridge#place" },
"category": "NewHomeCommunity",
"description": "Single-family homes with access to parks, trails, and community pool."
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What are the HOA fees?",
"acceptedAnswer": {
"@type": "Answer",
"text": "HOA fees are $85/month and include amenity maintenance and community events."
}
},
{
"@type": "Question",
"name": "What amenities are included?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Residents have access to a pool, fitness center, playgrounds, and walking trails."
}
},
{
"@type": "Question",
"name": "Are there move-in ready homes?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Move-in ready inventory is listed in the Availability section on this page."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Communities", "item": "https://www.example.com/communities" },
{ "@type": "ListItem", "position": 3, "name": "Oak Ridge", "item": "https://www.example.com/communities/oak-ridge" }
]
}
]Implement and verify
- 01
Start with the live page
Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.
- 02
Add one JSON-LD script
Use the combined example as a template in the document head or before the closing body tag.
- 03
Complete regional details
Fill shipping destinations and timing for every region the page actually serves.
- 04
Link the return policy
Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.
- 05
Match visible answers
Add only FAQs that users can read on the same page, with identical answers.
- 06
Validate after changes
Run Rich Results Test after implementation and whenever price, availability, or policy data changes.
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.
Stack FAQs
Can I list multiple price ranges?
Yes. Use one Offer per range or home type, each pointing to the same Place @id.
What if prices change frequently?
Use priceValidUntil for time-bound prices and keep the Offer aligned to what is visible on the page.