Google's Structured Data Recommendations for Service Businesses Diverge from Schema.org
Google's John Mueller answer about which structured data to use for a business that offers a service with a range of prices shows how Google's recommendations on how to use structured data sometimes diverges from official Schema.org documentation. Roger Montti — February 13, 2023
If you run a service business and you have stared at your structured data markup wondering whether to follow Schema.org's broad type definitions or Google's tighter guidelines, you are not alone. The question comes up repeatedly in SEO office hours and forum threads. A website owner asked John Mueller how to handle invalid item errors when using product structured data for a service site with variable pricing. Mueller's answer assumed a local service provider and pointed to local business markup. At the same time, Schema.org's Product type definition technically includes services such as a haircut or a concert ticket. The result is a practical disconnect: what works in theory does not always work in Google Search results.
John Mueller's recommendation leans local
The question was straightforward: "Our website is a service, not a product. The price will vary on the estimate. How do I fix the invalid item for a service like ours when I use product structured data?" Mueller answered with the assumption that the business was a local service provider. His answer:
"For local business, like the one that you mentioned, I'd recommend looking at the local business structured data. This also lets you specify a price range for your services. We have more information about this markup in the search developer documentation."
Mueller's recommendation carries weight because it comes directly from Google's search advocate. He is not repeating Schema.org's type hierarchy; he is responding to what Google Search actually supports for enhanced SERP listings. Local business markup includes a price range property that product markup does not reliably surface for service contexts. If you want Google to display your service prices in rich results, Mueller's path is the one Google engineers have validated.
Schema.org's Product type technically covers services
Schema.org's official description of the Product type is broad:
"Any offered product or service. For example: a pair of shoes; a concert ticket; the rental of a car; a haircut; or an episode of a TV show streamed online."
On its face, this means you can mark up a haircut as Product. The vocabulary does not prohibit it. However, vocabulary breadth does not equal search engine support. Schema.org is a collaborative effort among Google, Microsoft, Yahoo, and Yandex. It is not a standards body like the W3C, which creates HTML standards. Search engines are free to ignore parts of the schema that do not fit their feature sets. What Schema.org permits, Google may not use.
Google's product structured data documentation focuses on products
Google's Search Central documentation on product structured data is explicit about its scope. The page states:
"When you add structured data to your product pages, Google search results (including Google Images and Google Lens) can show product information in richer ways."
The documentation describes two main classes of product structured data: product snippets for pages where people cannot directly purchase, and merchant listings for pages where customers can purchase. Both are framed around product content — price, availability, review ratings, shipping information. Nowhere does the documentation provide provisions for service businesses with estimate-based pricing. Google's guidance repeatedly references product pages, not service pages. When Google's own documentation has no provision for something, using it will not generate enhanced listings, even if the underlying schema type allows it.
The practical decision: follow Google or follow Schema.org
The SEJ article distills the core tension:
"Using structured data that's unsupported by Google won't harm a site. The markup won't be used for enhanced SERP listings."
This is the practical takeaway. You can validate your pages with Schema.org Product markup and Google will not reject the code. But if your goal is rich results that display price, availability, or review ratings, Google will not draw from that markup for service pages. The search engine simply does not have the mapping for it.
When in doubt, the article advises going with what Google recommends. Mueller's suggestion to use local business structured data gives you a property — price range — that Google can and does use for local services. If you instead keep product markup, you may have technically valid code that never appears in a rich result.
What this means for your service business
If you offer services with a range of prices — consultations, estimates, tiered packages — local business markup is the pragmatic choice. It lets you specify a price range, and Google has confirmed it will surface that information in relevant contexts. Product markup is not forbidden, but it is not optimized for Google's search features. The divergence is not a technical error; it is a feature-gap decision on Google's part.
For businesses that already have product markup in place, switching requires an audit of each page. If the page describes a tangible good, product markup stays. If the page describes a service with variable pricing, replacing or supplementing with local business markup is the safer route for rich result eligibility.
Conclusion
The Google versus Schema.org divergence on structured data for service businesses comes down to this: Schema.org defines what is possible in the abstract; Google decides what actually appears in its search results. John Mueller's recommendation to use local business structured data for services with price ranges is the path Google engineers have validated. Using product markup will not break your site, but it will not earn you rich results either. If you want your service prices to appear in Google Search, follow Google's guidance. If you are unbothered by invisible markup, Schema.org's broader types are yours to use.
Sources: Search Engine Journal article "Google On Use Of Product Structured Data For A Services Business" (https://www.searchenginejournal.com/google-on-use-of-product-structured-data-for-a-services-business/479159/); Google Search Central product structured data documentation (https://developers.google.com/search/docs/appearance/structured-data/product)
