Professional Services Stack
Consulting/pro services pages with Organization + Service + Offer context, FAQs, and breadcrumbs.
When to use this stack
- Consulting, agency, or advisory service pages
- Services where price/terms are shown or quoted
- Pages needing FAQs about scope, process, and billing
What is included
Anchors the service provider identity (name, URL, logo).
Describes the service offering, provider, scope, and service area.
Answers common questions on scope, process, and billing.
Provides navigation context to the service 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
- areaServed.name
- itemListElement[].name
- logo
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- offers.price
- offers.priceCurrency
- provider.@id
- serviceType
- url
Recommended properties
- address.addressCountry
- contactPoint.telephone
- description
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- offers.availability
- offers.url
- 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/services/strategy#org",
"name": "Northwind Strategy",
"url": "https://www.example.com",
"logo": "https://www.example.com/assets/logo.svg",
"sameAs": [
"https://www.linkedin.com/company/northwind-strategy"
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+1-415-555-0123",
"contactType": "sales"
}
},
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://www.example.com/services/strategy#service",
"name": "Go-To-Market Advisory",
"description": "Research, positioning, pricing, and launch planning for B2B products.",
"serviceType": "Consulting",
"provider": { "@id": "https://www.example.com/services/strategy#org" },
"areaServed": { "@type": "AdministrativeArea", "name": "North America" },
"offers": {
"@type": "Offer",
"price": "12000.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/services/strategy#contact"
}
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is included in the engagement?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Discovery, market research, messaging framework, pricing guidance, and a 90-day GTM plan."
}
},
{
"@type": "Question",
"name": "How long do projects take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Typical engagements run 6–8 weeks with weekly checkpoints."
}
},
{
"@type": "Question",
"name": "Do you offer fixed-fee pricing?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Fixed-fee is available for defined scopes; custom projects are quoted after discovery."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Services", "item": "https://www.example.com/services" },
{ "@type": "ListItem", "position": 3, "name": "Go-To-Market Advisory", "item": "https://www.example.com/services/strategy" }
]
}
]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 services?
Yes. Use one Service per offering with unique @id values, all pointing to the same Organization provider.
What if pricing is by quote?
Keep offers.url and availability aligned to the visible CTA; if price isn’t shown, omit price fields but retain Offer where applicable.