Customer Impact

SEO & GEO

Product and Service Schema for B2B in AI Results

Copy for AI

For B2B service providers, Service schema almost always beats Product schema.

Product markup is built for purchasable items with a price, stock and a checkout button. That rarely fits a service you deliver to order.

The verdict: use schema.org/Service to make your offering machine-readable, and don’t expect stars or price labels in return. The gain is clarity for AI systems, not a flashy search result.

New to structured data? Our explainer on schema markup covers the basics first.

What is the difference between Product and Service schema?

Product schema describes a purchasable item. Service schema describes a service you perform.

That sounds subtle, but the consequences for B2B are significant.

Product: a thing someone buys

schema.org/Product is designed around a tangible or digital product: a name, a price, stock, delivery time and reviews.

Google ties its richest Product features to shop pages where a visitor can buy the item directly. Without a product, Product markup has nothing to describe.

Service: work you carry out

schema.org/Service describes a service that an organization delivers, for example advice, maintenance or implementation.

The type leans on other fields: who offers the service, what kind of service it is and where you deliver it.

For a consultant, agency or installer, that matches reality far better than a product page with a price tag.

Rule of thumb: if you sell a thing, use Product. If you carry something out for a client, use Service.

Here’s the difference side by side:

ProductService
DescribesAn item you buyWork someone performs
Key fieldsname, offers, price, availability, reviewprovider, serviceType, areaServed, offers
Rich result in GoogleMerchant listings, product snippetsNone of its own
Typical B2B fitSoftware license, spare partsConsultancy, agency work, installation

Which type do you choose as a B2B service provider?

Choose Service if you deliver a service. Keep Product only for concrete, purchasable items you sell alongside your services.

Most B2B companies sit entirely in the Service camp.

Four common B2B cases

A few practical cases make it concrete:

  • Pure service delivery (consultancy, marketing, legal advice): Service
  • A productized service with fixed scope and rate: still Service, optionally with offers
  • Software or a license sold as a defined product: Product, or a more specific type
  • Physical products plus installation: Product for the items, Service for the work

A productized service is still a service. You deliver an assignment, not a stock item, so the offers field just holds the price indication.

Software is different. There’s a clearly purchasable item with a price, so Product (or SoftwareApplication) can be right.

Don’t chase the “Product earns stars” myth

If you’re in doubt, ask whether a visitor “buys” something or “has something done”. That answer points you to the right type.

Avoid the temptation to mark everything as Product because you read somewhere that Product schema earns rich results.

For B2B services that usually doesn’t hold up, as you’ll read further on.

Which fields make your offering truly machine-readable?

The value lies in a handful of fields that state who you are, what you do and for whom.

Schema.org/Service lists 22 properties directly on the type. You need four of them in most cases.

The four fields that matter

Here’s what each one does:

  • provider: the organization that delivers the service, tied to your brand
  • serviceType: the kind of service, such as “GEO optimization”
  • areaServed: where you deliver, from a city to a country
  • offers: an optional price indication, handy for a fixed-rate package

provider is the basis of a recognizable entity. It links the service to the same organization you describe elsewhere, which is the core of entity SEO.

serviceType places your offering in an understandable category. areaServed prevents confusion about your reach when you work regionally or nationally.

Tip: connect your Organization to its profiles elsewhere with sameAs schema, so provider points to one clear entity.

A minimal JSON-LD example

JSON-LD is the recommended way to add schema. A minimal Service block looks like this:

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "GEO optimization for B2B",
  "serviceType": "Generative Engine Optimization",
  "provider": {
    "@type": "Organization",
    "name": "Customer Impact"
  },
  "areaServed": "BE"
}

Step-by-step placement on your pages is covered in how to implement schema markup.

Only mark up what’s visible

The golden rule: only mark up what’s also visible on the page.

Google’s structured data guidelines say it plainly: “Don’t mark up content that is not visible to readers of the page.”

A field that doesn’t match your text works against you.

You can check what a page really outputs in a validator. Here’s the result for our own English homepage:

Schema Markup Validator result for the customerimpact.be English homepage listing the detected structured data types, a check on product schema and service schema markup The Schema Markup Validator on our own English homepage, October 2026. Check that each detected type matches what the page visibly says.

Each detected type should match a visible claim on the page. More checks are in our guide to schema markup testing.

Do AI systems read your Product and Service schema?

The answer is nuanced. How much AI systems use your markup directly differs per platform and is partly unconfirmed.

So we don’t adopt hard percentages that nobody has firmly substantiated.

What Google says

Google has consistently said that structured data helps it understand content, and AI Overviews build on that same index.

But Google also states that there’s no special schema.org structured data you need to add to appear in AI Overviews or AI Mode.

It does advise making sure your structured data matches the visible text on the page.

ChatGPT and Perplexity

Pure language models such as ChatGPT and Perplexity work mainly with the visible, rendered text of a page.

They don’t necessarily read the invisible markup beneath it. Schema there is at best an extra signal, not a decisive factor.

What schema does do

It makes your core facts unambiguous. A system that sees in fixed fields who delivers the service and where doesn’t have to distill that from a paragraph.

That lowers the chance your offering is summarized wrongly or attributed to another party.

It connects to grounding, the process by which AI determines what is true. It also supports entity consistency, which keeps your brand separate from a similarly named player.

Schema is thus part of GEO, becoming visible in AI answers, and not a standalone trick.

Does Product or Service schema earn a rich result in B2B?

Usually not, and that’s important to know before you invest a lot of time in it.

Google’s rich results are stricter than what schema.org allows, and Service misses out.

Product has 2 rich result types

Google’s Product structured data splits into 2 kinds:

  • Merchant listings: pages where customers can buy from you
  • Product snippets: pages that describe or review a product without selling it

Both are about a product. A typical B2B service page doesn’t fit either.

Service has none

The Service type has no rich result of its own in Google Search.

Service is also missing from the item types that qualify for review snippets, even though every validator approves the markup. Google lists 16 eligible types there, from Book to Software App.

And reviews a business controls about itself on LocalBusiness or Organization markup aren’t eligible for stars either.

So expect no stars or price labels under your service page. Our guide to review and rating schema explains where stars still apply.

So is schema pointless for B2B?

No. The value merely shifts from a visible rich result to machine readability.

You make your offering clear and consistent for systems that process your facts, even without an eye-catching search result in return.

At Customer Impact we’re deliberately clear about this: we don’t promise rich results that simply don’t exist for your type of page.

How does schema fit into a broader GEO approach for B2B?

Schema is one layer, and almost never the first one to invest in.

The order that works in practice:

  1. Content: make it accurate and clearly structured
  2. Brand: get mentioned beyond your own site
  3. Schema: make the whole sharper and machine-readable

Here’s that order as a picture:

GEO ORDER Where schema belongs 01 Strong content Accurate and clearly built 02 Recognizable brand Mentioned beyond your site 03 Schema Machine-readable finishing touch Schema strengthens strong content, it does not replace it.
Build in this order: schema is the finishing touch, not the starting point.

Why the order matters

If you start with the markup, you polish a page whose content isn’t yet strong enough to be cited. That’s wasted effort.

The biggest lever remains content that’s crystal clear even without schema. That’s the core of content architecture for AI extraction.

Where to start on your own site

For example, say you run an industrial maintenance firm with 3 service pages. Check each page first: does the H1 and first paragraph say what you do, for whom and where?

Only then add a Service block that repeats exactly those facts. An AI visibility audit shows which pages need the content fix first.

How to approach these choices for your sector is in our guide on GEO for B2B.

How do you test and maintain your Service schema?

Test it once after launch, then every time the visible page changes.

Markup that drifts away from the text is the most common problem we see. It’s also the easiest to prevent.

Step 1: Validate the output

Run the live URL through a validator, not the code in your CMS. Plugins and templates often add or overwrite types you didn’t expect.

Look for 3 things:

  • Duplicates: two Organization blocks with different names
  • Wrong type: Product on a page that sells a service
  • Empty fields: areaServed or provider left blank

Step 2: Compare fields with the page

Put the markup next to the visible text. Every value in serviceType, areaServed and offers should appear in a heading or paragraph.

Watch out: an old price in offers after a rate change is exactly the mismatch Google’s guidelines warn about.

Step 3: Keep one source of truth

Generate the markup from the same fields that fill the page, such as the service name and region in your CMS.

Then one edit updates both. Hand-pasted JSON-LD is the version that falls out of sync.

Which types sit next to Service?

A B2B service page rarely needs more than a few types:

  • Organization: who you are, linked to provider
  • BreadcrumbList: where the page sits, see breadcrumb schema
  • FAQPage: only for a real FAQ, see FAQPage schema

More types don’t make a page more citable. Clean, consistent ones do.

Frequently asked questions

Should a B2B agency use Product or Service schema?

Service. An agency carries out work for a client, so provider, serviceType and areaServed describe it far better than Product fields such as stock and availability.

Can I add a price to Service schema?

Yes, through the offers field. It suits a productized service with a fixed rate. Only add it if the same price is visible on the page.

Does Service schema give my page review stars?

No. Service isn’t among the item types Google supports for review snippets, and reviews a business controls about itself aren’t eligible for stars.

Do I need schema to appear in AI Overviews?

No. Google says no special structured data is needed. Schema helps make your facts unambiguous, but clear visible content matters more.

The short summary

For B2B service providers, Service schema almost always fits better than Product.

The fields that really matter are provider, serviceType and areaServed, and they must match the visible text on your page.

Rarely expect a rich result: Product experiences are for e-commerce and Service has none of its own.

The gain lies in machine readability, which raises the chance of a correct mention. Steer on the leads that extra AI visibility produces.

Want to know which schema and steps make the difference on your site? Our generative engine optimization (GEO) team starts with a page-by-page check, even if the biggest gain turns out to lie elsewhere.

Contact us and we’ll go through your current markup with you.

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.