How to implement schema markup: the types a B2B website actually needs

For a B2B website, you only truly need a small number of schema types: Organization (your company details), Service or WebSite for your service pages, BreadcrumbList for your navigation trail and Article for your knowledge base. The rest is unnecessary for most B2B sites. In this article you will read which types matter, why it is best to build schema in during development rather than afterwards, and how to go about it in a CMS like Webflow, WordPress or a headless setup.

Want to know first what schema markup exactly is and how it works? Then read our explanation of schema markup. This article goes one step further: from understanding to implementation.

What does implementing schema markup mean exactly?

Implementing schema markup means adding an invisible piece of code to your pages that tells Google and AI models what is on that page. The recommended form is JSON-LD, a block of structured data in the source code that you place separately from your visible text. Google explicitly prefers JSON-LD over older formats like Microdata, because it is easier to manage and test.

The difference between “quickly adding” and “implementing” lies in the approach. A standalone block of code on a single page is quickly pasted in. But a B2B site grows: you add service pages, write knowledge articles and change your company details. Implementing means you set the schema up structurally, fed from your CMS, so the data stays automatically correct and grows along. That is the difference between a one-off fix and a part of your website architecture.

Which schema types does a B2B website actually need?

A B2B service company needs a limited but important set. You do not have to use every conceivable type; focus on what your pages actually describe.

• Organization. The foundation. With it you record your company name, logo, address, contact details and social profiles. This helps Google recognise your brand as an entity and links all your pages to one clearly identified company.
• LocalBusiness. A more specific variant of Organization, handy if you work from a physical location or are regionally active. Strong for local SEO, because it passes along opening hours and location.
• Service. For your service pages. With it you describe which service you offer, for whom and in which area. For a B2B service provider often more relevant than Product, which is intended more for physical or clearly priced products.
• BreadcrumbList. Marks up your navigation trail so Google understands the structure of your site and sometimes shows it in the search result. Simple to build in and widely supported.
• Article or BlogPosting. For your knowledge base and blog pages. Passes along author, publication date and topic, which helps in correctly understanding and dating your content.
• WebSite. A basic type on your homepage that describes your site as a whole and links it to your Organization.

What you can skip for most B2B sites: Product and the associated Review and AggregateRating markup. These are meant for concrete products with prices and ratings, and Google enforces strict rules around review markup. Do not invent stars that do not match your real page.

A point of attention about FAQPage: this type was long popular for expandable questions in the search results, but Google no longer shows those FAQ rich results as of May 2026. Google still uses the data to understand your page better, but you no longer get a more prominent search result out of it. So no longer build FAQPage in for the rich result, at most for the understanding.

Why do you build schema in during development?

Schema markup belongs in the construction of your site, not as a loose plug-and-play layer on top. The reason is simple: if you feed schema from your CMS fields, the data is always correct and stays automatically up to date.

Imagine: you record the author, date and title of a knowledge article in CMS fields. During construction you link those fields to your Article schema. If you then write a new article, the schema fills itself in correctly, without anyone having to adjust code manually. Do it the other way around, with loose code blocks per page, and you are guaranteed to get stuck: a date you forget to update, a title that no longer matches, a service you rename. Incorrect structured data works against you, so that error-proneness is what you want to avoid.

This is also where the choice of your platform and CMS comes into play. How your content is structured determines how easily you link schema to it. A well-considered setup of your content model, as with a headless CMS, makes building schema in a good deal simpler. More about how structured and unstructured content relate, you can read in our explanation of structured data.

How do you implement schema in your CMS?

The method differs per platform, but the principle stays the same: generate JSON-LD from your content and place it in the source code. We are platform-agnostic and choose the system that fits your case, so here below are the honest differences.

• WordPress. SEO plugins like Yoast or Rank Math already generate basic schema by default (Organization, Article, BreadcrumbList) and let you control types per page type. For custom work you link custom fields to your markup. The advantage: a lot works automatically. The disadvantage: default schema is generic, so for your service pages you often want to go further than what the plugin does out of the box. More about this in WordPress SEO.
• Webflow. Webflow does not automatically generate schema, but does give you full control. You place JSON-LD via a custom code embed and can insert fields from a CMS collection, so an article or service receives its own data. It takes a bit more setup work, but you keep precise control over what gets marked up.
• Headless or custom. Here you generate the JSON-LD server-side from your content model and render it along with the page. Maximum flexibility and scalability, at the cost of more development work up front. For sites with many pages or complex content, often the cleanest solution.

Whichever route fits, the approach is always: determine which types are needed per page type, link them to the right fields, and test each page with Google’s Rich Results Test or the Schema Markup Validator before you go live. Test before you publish, not after. If you would rather outsource this, read what having schema markup implemented concretely involves in terms of approach and costs.

Does schema markup generate more leads?

Honestly: no, not directly, and schema is also not a ranking factor. It does not automatically lift you to position one and it does not fill your inbox with inquiries. What it does do is help Google and AI models understand your pages faster and more correctly, and in some cases enrich your search result with a breadcrumb or brand recognition.

At Customer Impact we always steer on the outcome, not on the technique itself. A neat schema implementation that yields no extra visibility or clicks is wasted energy. And extra clicks that your site does not turn into inquiries are a vanity number. Schema is a hygiene measure: you lay the foundations well so that search engines and AI do not misunderstand you, and the real gain lies in a site that convinces visitors and turns them into leads. That whole chain, from technique to conversion, we keep an eye on in our website development.

The short summary

Implementing schema markup on a B2B website comes down to a limited set of types that truly matter: Organization, Service, BreadcrumbList and Article for the vast majority of cases, supplemented with LocalBusiness and WebSite where that fits. Build them in during development, fed from your CMS fields, so the data is automatically correct and grows along. Only mark up what actually appears on the page, test every implementation, and remember that schema is not a goal in itself: it helps machines understand you, your site has to bring in the leads. Want your whole website approach in one well-considered whole? Start with our guide to having a B2B website built. Do not forget the basic pages along the way: our checklist of mandatory pages a B2B website needs makes sure your site is also formally in order.

Doubting which schema your site truly needs and which you can safely leave out? We are happy to take a look with honest advice. Plan your free intake.