Coworking Day Pass Stack
Coworking day-pass pages with Place + Offer context, FAQs, and breadcrumb navigation.
When to use this stack
- Coworking day-pass landing pages
- Workspace access pages with day pricing and amenities
- Pages where FAQs clarify hours, access, and guest policies
What is included
Defines the coworking location and address.
Describes the day-pass offer, price, and purchase URL.
Answers questions about access, hours, and amenities.
Provides navigation context for the day-pass 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.streetAddress
- availability
- itemListElement[].name
- itemOffered.@id
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- price
- priceCurrency
- url
Recommended properties
- description
- eligibleRegion
- 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": "Place",
"@id": "https://www.example.com/coworking/downtown#place",
"name": "Downtown Coworking Hub",
"url": "https://www.example.com/coworking/downtown",
"image": "https://www.example.com/images/coworking-downtown.webp",
"address": {
"@type": "PostalAddress",
"streetAddress": "300 Congress Ave",
"addressLocality": "Austin",
"addressRegion": "TX",
"addressCountry": "US"
}
},
{
"@context": "https://schema.org",
"@type": "Offer",
"@id": "https://www.example.com/coworking/downtown#day-pass",
"name": "Coworking Day Pass",
"price": "25.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/coworking/downtown/day-pass",
"itemOffered": { "@id": "https://www.example.com/coworking/downtown#place" },
"description": "Day pass access from 8 AM–6 PM with high-speed Wi-Fi and free coffee."
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What hours are included?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Day passes include access from 8 AM to 6 PM, Monday through Friday."
}
},
{
"@type": "Question",
"name": "Can I bring a guest?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Guests are welcome with advance notice; guest passes are available at the front desk."
}
},
{
"@type": "Question",
"name": "Is a reservation required?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Reservations are recommended for peak days but walk-ins are accepted when space allows."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Coworking", "item": "https://www.example.com/coworking" },
{ "@type": "ListItem", "position": 3, "name": "Downtown", "item": "https://www.example.com/coworking/downtown" }
]
}
]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
Should I list multiple locations?
If multiple locations are listed, add one Place and Offer per location with unique URLs.
Do I need to include amenity details?
Yes. Include amenities in the page content and align the Offer description with what’s provided.