Multi-Location Local Stack
HQ + branch pages with organization identity, local locations, reviews, FAQs, and breadcrumb context.
When to use this stack
- Company pages listing multiple local branches
- HQ pages that need org identity plus location context
- Pages where FAQs cover service areas, hours, and contact
What is included
HQ identity with brand and contact.
Branch/location details (NAP, geo, hours).
Social proof for a representative branch or the org.
Answer service area, hours, and contact questions.
Navigation context.
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
- author.name
- itemListElement[].name
- itemReviewed.@id
- logo
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- reviewBody
- reviewRating.ratingValue
- telephone
- url
Recommended properties
- contactPoint.contactType
- contactPoint.telephone
- datePublished
- geo.latitude
- geo.longitude
- image
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- name
- openingHours
- priceRange
- reviewRating.bestRating
- sameAs[]
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": "Organization",
"@id": "https://www.example.com/#org",
"name": "BrightCare Clinics",
"url": "https://www.example.com",
"logo": "https://www.example.com/images/logo-120x60.png",
"sameAs": [
"https://www.facebook.com/brightcare",
"https://www.linkedin.com/company/brightcare"
]
},
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"@id": "https://www.example.com/locations/downtown#location",
"name": "BrightCare Clinic — Downtown",
"url": "https://www.example.com/locations/downtown",
"telephone": "+1-512-555-0101",
"address": {
"@type": "PostalAddress",
"streetAddress": "500 Main St",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 30.2672,
"longitude": -97.7431
},
"openingHours": "Mo-Fr 08:00-18:00",
"priceRange": "$$"
},
{
"@context": "https://schema.org",
"@type": "Review",
"@id": "https://www.example.com/reviews/brightcare-1#review",
"name": "Great experience at the downtown clinic",
"reviewBody": "Friendly staff and quick check-in. Doctor was thorough and answered all questions.",
"datePublished": "2026-02-19",
"reviewRating": {
"@type": "Rating",
"ratingValue": 5,
"bestRating": 5
},
"author": { "@type": "Person", "name": "Pat R." },
"itemReviewed": { "@id": "https://www.example.com/locations/downtown#location" }
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Do all locations offer the same services?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Most services are available at every clinic. Check each location page for specific offerings."
}
},
{
"@type": "Question",
"name": "Can I book online?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Book through each location page; phone scheduling is also available."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Locations", "item": "https://www.example.com/locations" },
{ "@type": "ListItem", "position": 3, "name": "Downtown", "item": "https://www.example.com/locations/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 add multiple LocalBusiness objects?
Yes if you list multiple locations on one page. Ensure each has unique @id/URL and correct NAP.
Do I need Organization for every location page?
Include the Organization for brand identity; each location gets its own LocalBusiness entry.
Related schema stacks
Bundles that share schema types with this one.
- B2B SaaS Lead-Gen Stack
Feature/solution landing pages for SaaS with app identity, org trust, reviews, FAQs, and breadcrumb context.
- SaaS / Software Schema Stack
Software application pages with organization identity, reviews, FAQs, and breadcrumb context. Works for web and mobile apps.
- Legal Services Stack
Practice-area pages with Attorney + Service + LocalBusiness, reviews, FAQs, and breadcrumb context.
- Finance / Insurance Stack
Finance or insurance service pages with local presence, service details, reviews, FAQs, and breadcrumb context.
- Local Service Schema Stack
LocalBusiness + Service + FAQPage + Review for service-area businesses. Clarify NAP, service offering, policies, and proof.
- Public RFP / Bid Stack
Public RFP or bid pages with CreativeWork + Organization context, FAQs, and breadcrumb navigation.