What it does in practice
Entity grounding: Organisation markup is how a machine knows, without guessing, that this page speaks about a specific company, what it does and where its official channels are. LLMs' entity knowledge has to attach to something — structured facts are the anchor; without markup, an engine can only guess which namesake a name refers to.
Understandable content units: Service, FAQPage and Article markup declare in machine terms what a page is and which section answers which question, instead of forcing the engine to infer it from prose.
Verifiable facts: dates, authors, sources and issuing organisations in markup are extractable at crawl time — verifiable facts are what answers prefer to cite.
On format, Google's official documentation lists JSON-LD as the recommended format: it sits in its own script tag, separate from the visible text, and is the easiest to implement and maintain. Google also requires markup to match the visible page content — marking up claims nobody can see is worse than no markup.
What it cannot do
Structured data is not a citation switch. Without third-party mentions it will not lift mention rates; it raises two different things: the probability that facts get read correctly, and the probability of being quoted correctly once you are in scope. Google's official docs are explicit that no AI-specific structured data is needed for AI Overviews and AI Mode — structured data is not a requirement for AI search. What it does is make the citations that do happen more accurate.
One change from 2026 is worth knowing: Google stopped showing FAQ rich results in Search in May 2026. FAQPage remains a valid schema.org type with real value for AI engines and other parsers, but do not build it as a Google Search display play; the reason to add FAQPage is machine readability, not a search feature.
The cost of the work is low and the effect is testable — in our sample of 30 Chinese exporter websites (Negency Flagship Report 2026, Issue 1, sampled 30 October 2026), missing JSON-LD was the single most common major gap (17 of 30), and the machine-readable dimension averaged only 69.2 (median 68.5). That profile — cheap to fix, most people have not, fixes a real error class — is exactly what should be done first. (Sampling note: the sample is the global homepages of 30 Chinese exporter websites, measured in a single-day sweep on 30 October 2026 with the Negency audit engine — about 30 signals in five groups. The report measures technical visibility only — whether AI can reach and read the site — not brand mention rates in AI answers.)
Order of work
Organisation entity first, then FAQPage for FAQ content, then Service for offerings, then Article for news and reports. Cross-check names, dates and URLs against the visible page text: markup that contradicts the page makes things worse, not better. Accept the work in two steps: validate the syntax with a checking tool such as Google's Rich Results Test, then hand-check that the names, dates and links in the markup match what a human can see on the page, item by item.
The four types to do first, in order
- Organization: pin down who you are — legal name, website, logo, public contact and founding facts — so engines stop confusing you with namesakes;
- WebSite: declare the site's name and how its language versions relate, so multilingual pages roll up to one entity;
- FAQPage / Article: structure the title, author, publication and update dates of Q&A and article pages, so engines can extract and attribute them cleanly;
- Service / Product: state each service and product's name, description and audience as structured entries, so "who offers what" can be read directly.
The figure above this article shows a JSON-LD skeleton for Organization + FAQPage, using Negency's own public facts as the example; every field comes from the schema.org specification, so you can write against it directly.
When structured data "does nothing", the usual cause
When structured data "does nothing", the cause is usually not format but mismatch: the structured facts disagree with what humans can see on the page, only the homepage has it while inner pages do not, or a plugin's default output conflicts with the company's real facts. A typical case: the markup says the company was founded in 2014 while the About page says 2016 — faced with two versions, the engine trusts neither. Engines trust cross-consistent information; structured data only states consistent information more clearly — it is not a pass for inconsistent information. Reconcile before you mark up, and re-check page by page afterwards; only then is the markup actually in place.
Not sure which markup your site is missing? A free AI visibility audit checks JSON-LD item by item — look at the result before you start fixing.