Local Service Schema Stack
LocalBusiness + Service + FAQPage + Review for service-area businesses. Clarify NAP, service offering, policies, and proof.
When to use this stack
- Local service pages (plumbers, HVAC, electricians) serving a metro or region
- Lead-gen pages that need NAP, service description, and social proof
- Pages where FAQs handle pricing, arrival windows, and emergency support
What is included
Anchor NAP, coverage area, and contact points for the business.
Describe the specific service offering, provider, and area served.
Address blockers like pricing, arrival windows, guarantees, and coverage.
Provide social proof tied to the business.
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
- areaServed.name
- author.name
- itemReviewed.@id
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- offers.price
- offers.priceCurrency
- provider.@id
- reviewBody
- reviewRating.ratingValue
- telephone
- url
Recommended properties
- aggregateRating.ratingValue
- aggregateRating.reviewCount
- datePublished
- description
- geo.latitude
- geo.longitude
- image
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- name
- offers.availability
- offers.url
- priceRange
- reviewRating.bestRating
- serviceType
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": "LocalBusiness",
"@id": "https://www.example.com/services/drain-cleaning#business",
"name": "RapidRooter Plumbing",
"url": "https://www.example.com/services/drain-cleaning",
"image": [
"https://www.example.com/images/rapidrooter-van.webp"
],
"telephone": "+1-512-555-1212",
"priceRange": "$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main St",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 30.2672,
"longitude": -97.7431
},
"areaServed": {
"@type": "AdministrativeArea",
"name": "Austin, TX"
},
"sameAs": [
"https://www.facebook.com/rapidrooter",
"https://www.instagram.com/rapidrooter"
],
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.8,
"reviewCount": 215
}
},
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://www.example.com/services/drain-cleaning#service",
"name": "Emergency drain cleaning",
"description": "24/7 hydro-jetting and clog removal for residential drains in Austin.",
"serviceType": "Plumbing",
"provider": {
"@id": "https://www.example.com/services/drain-cleaning#business"
},
"areaServed": {
"@type": "AdministrativeArea",
"name": "Austin, TX"
},
"offers": {
"@type": "Offer",
"price": "189.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/services/drain-cleaning#booking"
}
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Do you offer same-day service?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. We offer same-day appointments in Austin and Round Rock. Call before 3pm for same-day arrival windows."
}
},
{
"@type": "Question",
"name": "Is there an emergency fee?",
"acceptedAnswer": {
"@type": "Answer",
"text": "After-hours visits include a $79 emergency dispatch fee, waived if we complete the repair."
}
},
{
"@type": "Question",
"name": "What if the clog comes back?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We warranty drain clearings for 14 days. If the same line clogs again in that window, we return at no labor charge."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "Review",
"@id": "https://www.example.com/reviews/123#review",
"name": "Kitchen drain cleared fast",
"reviewBody": "RapidRooter cleared our kitchen line in under an hour and left everything clean.",
"datePublished": "2026-02-10",
"reviewRating": {
"@type": "Rating",
"ratingValue": 5,
"bestRating": 5
},
"author": {
"@type": "Person",
"name": "Jordan B."
},
"itemReviewed": {
"@id": "https://www.example.com/services/drain-cleaning#business"
}
}
]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 reuse this for multiple service pages?
Yes. Use unique URLs, titles, and FAQs per service. Keep `provider` pointing to the correct LocalBusiness for that city/service.