Coworking Space Stack
Coworking/location pages with Place + Offer context, FAQs, and breadcrumb navigation.
When to use this stack
- Coworking location pages with amenities and pricing
- Workspace landing pages with day pass or membership offers
- Pages where FAQs clarify access, hours, and policies
What is included
Anchors the coworking location, address, and contact details.
Describes the workspace offer (day pass or membership).
Answers questions about access, amenities, and guest policies.
Provides navigation context to the location 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
- telephone
- url
Recommended properties
- category
- description
- geo.latitude
- geo.longitude
- image
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- openingHoursSpecification
- 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": "Northwind Coworking — Downtown",
"url": "https://www.example.com/coworking/downtown",
"telephone": "+1-512-555-0190",
"image": "https://www.example.com/images/coworking-downtown.webp",
"address": {
"@type": "PostalAddress",
"streetAddress": "500 Congress Ave",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701",
"addressCountry": "US"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "08:00",
"closes": "18:00"
}
]
},
{
"@context": "https://schema.org",
"@type": "Offer",
"@id": "https://www.example.com/coworking/downtown#offer",
"name": "Day Pass",
"price": "35.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/coworking/downtown#book",
"itemOffered": { "@id": "https://www.example.com/coworking/downtown#place" },
"category": "CoworkingDayPass",
"description": "Access to open seating, Wi-Fi, coffee bar, and phone booths."
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is included with a day pass?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Open seating, high-speed Wi-Fi, coffee/tea, and access to phone booths."
}
},
{
"@type": "Question",
"name": "Can I bring a guest?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Guests are welcome with a guest pass. Please check in at the front desk."
}
},
{
"@type": "Question",
"name": "Do you have meeting rooms?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Meeting rooms can be booked by the hour through the member portal."
}
}
]
},
{
"@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
Can I list multiple membership tiers?
Yes. Use one Offer per tier with unique @id values and URLs aligned to the visible pricing table.
What if pricing changes frequently?
Use priceValidUntil and keep the Offer aligned with the current price shown on the page.