In 2026 there are two kinds of websites with schema: those that have it out of obligation — because a plugin added it — and those that have it by design. The first group gets nothing from it. The second group receives consistent AI-driven traffic. The files look similar. The results don't.
Schema JSON-LD is, technically, structured data: a small code fragment that tells search engines and AI models what kind of thing each page is. But reducing it to "that's technical SEO" misses the point entirely. Schema is, in 2026, the native language AI models use to read your website. If you don't speak it fluently, they hear you — they just don't understand you.
Why schema is critical for LLMs
When a language model crawls your page, it tries to understand it like a human but with superpowers — and with blind spots. It can process text at impossible speeds, but it regularly stumbles on basics: what kind of business you are, your address, your most important products, your review scores.
Schema JSON-LD fixes that. It hands the model labeled data, unambiguously. "This is the product name. This is the price. This is the average rating. This is the physical address. This is the opening hours." When schema is properly implemented, AI models cite you with precision. When it's wrong — or generic from a template — they cite someone else, make up data, or move on.
The most expensive mistake: template schema
This deserves its own section because we see it every day. A small business installs an SEO plugin, the plugin adds default schema, and the business relaxes thinking it's covered. The problem is that schema is generic: it works for almost everything and excels at nothing.
A restaurant without a properly configured Restaurant schema — with opening hours, menu, cuisine type, price range, reservation schema — is giving up the right to be cited by ChatGPT on specific queries. An architecture practice without an appropriate ProfessionalService schema, with projects marked as CreativeWork entities, gets left out of answers about "architects specializing in…". An e-commerce without a Product schema that includes offers, aggregateRating and brand is invisible in product recommendation responses.
We won't list every critical field here because it varies dramatically by sector — and honestly, that analysis is exactly what we do in an audit. But we can say what's already public: out of all the schema types that exist, there are roughly ten that AI models almost always ignore, and three or four that, when properly implemented, change the entire conversation.
Having schema vs. having the schema AI models actually read
That's the line we repeat in every audit. Having schema is checking a box. Having the schema AI models read is earning real visibility. The difference between the two isn't technically complex — it's a matter of judgment. Knowing, for your sector, which fields carry weight, which properties models are increasingly using, which structures are replacing the older ones.
And knowing what not to include. Because schema crammed with irrelevant data — or worse, data that contradicts the rest of your site — is a negative signal. AI models prefer a short, coherent schema to a long, contradictory one.
A concrete case: Menorca Studio
With the architecture practice Menorca Studio, the schema work was probably the single most important factor in their AI positioning. This isn't a case where we published fifty articles; it's a case where the site is relatively small but the schema is meticulous.
Each project — Santa Margarita, Mar i Cel, Sant Tomàs — has its own entity record with its own metadata. The practice has its Organization and ProfessionalService schema with declared specializations, services, and area served. Together, they give ChatGPT everything it needs to answer with authority when someone asks about architecture in Menorca. And it does: first position.
Had we installed a generic plugin and trusted its output, they'd be mid-table. That's the real difference.
How to tell if your schema is working
Not by running it through Google's validator — that only tells you if it's technically valid, not if it's effective. The real test is running prompts in ChatGPT and Perplexity about your sector and location, and checking whether you're cited with the right data. If you're cited vaguely ("there are some architecture practices in Mahón…") or incorrectly (old address, services you no longer offer), your schema has a problem. If you're cited with name, correct address and precise specializations, it's doing its job.
At A-Digital we've spent years refining this type of audit, for clients in Menorca and companies across Spain and Europe. What we consistently find: almost every site, large or small, has something improvable in schema. And the return on fixing it — in citations, traffic, and conversion — is usually greater than the return on producing new content.
We'll tell you which schema you're missing, which you have wrong, and which is just noise. Free audit, specific diagnosis.
Request your free audit →