LIVE MONITORING · 11 ENGINESChatGPT · Claude · Gemini · Grok · DeepSeek · Mistral · Perplexity · AI Overviews · AI Mode · Copilot · Meta AILisbon
Technical standards12 min read

Schema.org for B2B SaaS: the minimum viable in JSON-LD

The five schema types every B2B SaaS company needs, with JSON-LD snippets ready to paste: Organization, Service, FAQPage, BreadcrumbList and Article.

PTLer em português →

Photo by Nangialai Stoman on Unsplash

Does Schema.org improve AI visibility?

By Eduardo Mendonça, founder of destaque.ai. Reviewed on 13 November 2026.

In the public studies, adding schema to a page showed no gain in citations in AI answers. It helps the page be read and the brand be identified, and it makes pages eligible for Google's rich results, but it is not a way to be cited more.

What Ahrefs measured

Ahrefs, which sells SEO tools, published the study We Tracked 1,885 Pages Adding Schema. AI Citations Barely Moved. on 11 May 2026, written by Louise Linehan and revised on 9 June. It followed 1,885 pages that added JSON-LD between August 2025 and March 2026 and compared them with 4,000 pages that did not. It counted each page's citations in the 30 days before and the 30 days after, in Google's AI Overviews and AI Mode and in ChatGPT.

The authors conclude that “adding schema produced no major uplift in citations on any platform”. Citations rose 2.4% in AI Mode and 2.2% in ChatGPT, both indistinguishable from zero. In AI Overviews they fell 4.6% against the comparison pages, a small but statistically significant difference that the authors do not attribute to schema: “we don't know why”.

The study has limits, and the authors state them. Every page already had more than 100 AI Overview citations before adding schema. For pages that AI systems are not seeing at all, they write that schema “might still play a role” and that the study “can't speak to that directly”. They also grouped all schema types together, measured only 30 days, and counted only schema written in the HTML, not schema injected by JavaScript.

What Google and Microsoft say

On the Search Central page AI features and your website, updated on 10 December 2025, Google says there are no additional requirements to appear in AI Overviews or AI Mode. On schema, it writes that “there's also no special schema.org structured data that you need to add”. Among its best practices, it lists “making sure your structured data matches the visible text on the page”.

The guide Optimizing your website for generative AI features on Google Search, updated on 10 July 2026, repeats that structured data is not required and gives the reason to keep it: “it helps with being eligible for rich results on Google Search”.

Microsoft goes further than Google, in two posts on the Bing Webmaster Blog. In the post of 20 November 2025, it writes that structured content “helps AI systems interpret and summarize your content more effectively”. Its examples are schema-marked product pages, FAQs and comparison tables, and it speaks of AI systems in general, not of Copilot by name. In the post of 19 May 2025, on IndexNow and shopping, it says product schema helps surface a product accurately. The words are “in search results, shopping experiences, and AI-driven assistants”. Interpreting and summarising a page is not the same as citing it.

Where schema still counts

Study or documentSampleWhat it saysDateSource
Ahrefs study on schema and citations1,885 pages with new JSON-LD and 4,000 comparison pages, 30 days before and afterNo major uplift in citations. AI Mode +2.4% and ChatGPT +2.2%, indistinguishable from zero. AI Overviews -4.6%, cause not attributed11 May 2026 (revised 9 June)Ahrefs
AI features and your websiteDocumentation, no sampleNo special schema for AI Overviews and AI Mode. Structured data should match the visible text10 December 2025Google Search Central
Optimizing your website for generative AI features on Google SearchDocumentation, no sampleStructured data is not required and helps with eligibility for rich results10 July 2026Google Search Central
How AI Search Is Changing the Way Conversions are MeasuredBlog post, no sampleStructured content helps AI systems interpret and summarise20 November 2025Bing Webmaster Blog
Post on IndexNow and shoppingBlog post, no sampleProduct schema helps surface a product in search results, shopping and AI assistants19 May 2025Bing Webmaster Blog

The guide below, with the five schema types and the code for each, was published on 8 May 2026, before the Ahrefs study, and still holds for the three purposes above. Where it says schema makes a page citable by AI, read it in the light of what the studies measured.


For a B2B SaaS company, there are five schema types worth more than all the others combined: Organization, Service, FAQPage, BreadcrumbList and Article. Implemented in JSON-LD, with stable @ids and links between them, they are the minimum viable for the page to be read without ambiguity and the brand identified; on their own they are not a citation lever. This piece has the snippet for each one, ready to adapt.

Key takeaways

Why schema matters for GEO

Schema.org is the standard vocabulary for structured data. In HTML, describing something as an organisation is implicit (from tags like header, from CSS classes, from context). In schema, it is explicit: @type: Organization.

For traditional engines, schema unlocks rich results (stars, expanded FAQ, visible breadcrumbs). For LLMs, schema is the only reliable way to know, without ambiguity, what each thing is. When ChatGPT cites "Acme is a cybersecurity consultancy in Lisbon", it is inferring three things, what it is, what it does, where, and schema narrows the room for error.

The five types, one per tab

The @graph idea (and why it matters)

If you have several entities on the same page, you can wrap them in a @graph instead of scattering multiple application/ld+json script blocks:

{
  "@context": "https://schema.org",
  "@graph": [
    { "@type": "Organization", "@id": "https://acme.com/#organization", ... },
    { "@type": "WebSite",      "@id": "https://acme.com/#website",     ... },
    { "@type": "WebPage",      "@id": "https://acme.com/#webpage",     ... },
    { "@type": "Service",      "@id": "https://acme.com/#service-inv", ... },
    { "@type": "FAQPage",      "@id": "https://acme.com/#faq",         ... }
  ]
}

The advantage: less parsing, shared context, explicit links through @id. For LLMs, a coherent graph is significantly more legible than five loose scripts.

How the five link up through @id

Type@idLinks to
Organization#organizationReferenced by the others as provider, author, publisher
Service#service-inventoryprovider → #organization
FAQPage#faqisPartOf → #website
BreadcrumbList/product/inventory#breadcrumbNone in the example
BlogPosting/blog/integrate-sap#articleauthor, publisher → #organization; mainEntityOfPage → /blog/integrate-sap#webpage

Validation is not optional

Schema without validation is a trap. Before deploying, three tools:

Typical mistakes we see

The minimum viable, before deploying

Frequently asked questions

Microdata, RDFa or JSON-LD?

JSON-LD. It is the only one Google explicitly recommends, it is the cleanest to maintain (it separates semantic markup from presentation HTML), and it is what LLMs extract with the highest fidelity. Microdata and RDFa are still supported for compatibility, but they are not worth starting with in 2026.

Where should the JSON-LD go: head or body?

Either works, the specification does not require one. In the Next.js App Router, the typical pattern is to inject it with a JsonLd component inside the page's return (in the body, before the content). In static sites, the head is cleaner. In both cases, one script tag per semantic block avoids duplication.

Do I have to have @id on every entity?

It is not mandatory, but it is the difference between having a set of loose entities and having a coherent graph. With stable @ids (like https://example.com/#organization) you can reference the same entity from several pages without duplicating it. Engines and LLMs strongly prefer linked graphs.

How much schema is too much?

Irrelevant or invented schema is worse than no schema. Each type should correspond to something real on the page. Marking a pricing page as Recipe is plainly wrong; marking it as AggregateOffer makes sense. Rule: if you cannot defend why you put it there, take it out.

Sources