Campground / RV Park Stack
Campground/RV park pages with Campground + Offer context, FAQs, and breadcrumb navigation.
When to use this stack
- Campground or RV park landing pages with rates
- Locations with amenities and booking CTAs
- Pages where FAQs clarify policies and availability
What is included
Anchors the campground location and amenities.
Represents campsite or RV site pricing and booking URL.
Answers questions about hookups, check-in, and policies.
Provides navigation context to the campground 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.addressLocality
- address.addressRegion
- address.streetAddress
- availability
- itemListElement[].name
- itemOffered.@id
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- price
- priceCurrency
- telephone
- url
Recommended properties
- amenityFeature
- category
- description
- geo.latitude
- geo.longitude
- image
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- priceValidUntil
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": "Campground",
"@id": "https://www.example.com/campgrounds/pine-ridge#campground",
"name": "Pine Ridge Campground",
"url": "https://www.example.com/campgrounds/pine-ridge",
"telephone": "+1-406-555-0182",
"image": "https://www.example.com/images/pine-ridge.webp",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Forest Rd",
"addressLocality": "Bozeman",
"addressRegion": "MT",
"postalCode": "59715",
"addressCountry": "US"
},
"amenityFeature": [
{ "@type": "LocationFeatureSpecification", "name": "Electric Hookups", "value": true },
{ "@type": "LocationFeatureSpecification", "name": "Shower Facilities", "value": true }
]
},
{
"@context": "https://schema.org",
"@type": "Offer",
"@id": "https://www.example.com/campgrounds/pine-ridge#offer",
"name": "RV Site Nightly Rate",
"price": "45.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/campgrounds/pine-ridge#book",
"itemOffered": { "@id": "https://www.example.com/campgrounds/pine-ridge#campground" },
"category": "RVSite",
"description": "Full hookup RV sites with 30/50 amp power and water."
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What time is check-in?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Check-in begins at 2 PM. Late arrivals should contact the office in advance."
}
},
{
"@type": "Question",
"name": "Are pets allowed?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Pets are welcome on leash. Please clean up after your pet."
}
},
{
"@type": "Question",
"name": "Do you offer tent sites?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Tent sites are available and can be reserved online."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Campgrounds", "item": "https://www.example.com/campgrounds" },
{ "@type": "ListItem", "position": 3, "name": "Pine Ridge", "item": "https://www.example.com/campgrounds/pine-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 site types?
Yes. Use one Offer per site type with unique @id values and matching pricing.
What if availability is seasonal?
Use priceValidUntil and update availability to match the visible booking calendar.