Short answer: structured data tells a search system which string on your page is your telephone number and which is your address. It does not add anything your page does not already say, it is not a ranking boost, and it cannot earn you an AI citation. It is still worth doing properly, because it removes ambiguity — and the only thing to be careful about is keeping it true.
What structured data actually does
A search system reading your contact page sees a mixture of things: a heading that says “Contact”, a telephone number, an email address, a postal address, opening hours, and a paragraph about how to get in touch. All of it is text, and none of it is labelled.
Structured data adds the labels. One block of JSON-LD says: this string is the telephone, this one is the postal address, these are the opening hours for that location, and this is the business they all belong to.
That is the entire mechanism. Google’s introduction to structured data is worth reading because it is unusually clear about it — structured data describes content on a page, in a format a machine can process. [1] Moz’s explainer covers the same ground from the vocabulary side, including why a schema type exists for almost every noun you would think to mark up. [2] Moz’s explainer covers the same ground from the vocabulary side, including why a schema type exists for almost every noun you would think to mark up. [2]
Key takeaway: markup removes ambiguity. It does not create information, and it cannot compensate for a page that is thin, inaccurate or unrankable.
The rule that gets people in trouble
Structured data must describe content that is actually visible on the page.
This is not a technicality. Google’s guidelines are explicit that it must represent the main content of the page and be something a user could read there. There was a specific incident where a site used markup for reviews that were not rendered on the page, and the markup was being shown as a rich result for something a visitor could not see — which is precisely the behaviour the rules exist to prevent.
So if you are about to add Review markup, check that the review text is on the page. If you are adding Product markup, check the price is on the page. The test is simple: would a visitor pointing at their screen find the thing you are claiming?
Where to start, and it is not complicated
If you serve a local area, start with LocalBusiness. If not, start with Organisation. Both describe your business rather than your page, both are short, and both are the ones most often absent or wrong.
LocalBusiness documentation sets out the properties Google expects and which are required versus recommended — name, address, telephone, opening hours, geo coordinates, and a URL that matches the page it appears on. [4] Organisation is the same shape without the location-specific properties. [5]
After that, BreadcrumbList, which is the most under-used and most useful because it describes your site structure rather than your content. Most sites display breadcrumbs visibly and mark up none of them. [3]
Then FAQPage, if you have genuine questions and answers. Worth adding structurally; note that Google restricted the FAQ rich result to government and health sites, so on a commercial site the markup helps comprehension and does not produce the badge.
Drift is the real failure mode
Almost nobody gets markup syntax wrong. What happens is that it goes stale.
Somebody updates the phone number in the header. The footer keeps the old one. The JSON-LD block in the template still carries last year’s number, because it was hand-written once and nobody has looked at it since. Now you have a machine-readable statement that your business can be reached on a disconnected number — and a search system or assistant reading your markup has no way to know that is wrong.
The fix is not more care. The fix is generation: store your business facts once, render the visible page and the structured data from the same record, so they cannot disagree. That is the argument in automated entities, and it is the single highest-value thing on this page.
For a site where that is not practical, at minimum review the markup whenever you change a business detail — not whenever you publish.
What to check after you add it
- Syntax. Google’s Rich Results Test reports parse errors and missing required properties.
- It actually rendered. A very common failure is markup in a template that never reaches the page source, particularly on client-side rendered sites. The Rich Results Test will show absence rather than error, which is easy to misread as “fine”.
- The values are true. Neither test can tell you this. Open the rendered page and compare against the visible content.
That last one is the only one that really matters, and it is the one nobody automates.
A note on AI, briefly
There is no citation mechanism attached to markup. No evidence suggests marked-up pages are cited more often by assistants, and anyone selling a tool that reports an “AI schema score” is selling a number they generated.
What is true is much smaller: an unambiguous business is easier to summarise accurately than an ambiguous one. That is the same argument as entity SEO, and it is why the direct-dispatch benefit of good markup has more to do with your own site than with anyone else’s model.
| Markup type | Describes | Worth doing on a small site |
|---|---|---|
| LocalBusiness | Your business and location | Yes, first |
| Organisation | Your business | Yes, first |
| BreadcrumbList | Your site structure | Yes, usually missing |
| FAQPage | Questions on the page | Structurally; no rich result |
| Article | A long-form post | Optional |
| Review | Reviews on the page | Only if visible |
| Product | An item for sale | Only if you sell one |
What to do first
- Add LocalBusiness or Organisation markup to your site template, once.
- Fill in the properties from a single source you already trust.
- Run the Rich Results Test, then confirm it rendered.
- Compare every value against the visible page.
- Put a reminder in when your business details change, so the markup is checked with them.
That is most of the available value, and it fits in an afternoon.
How this connects
- Automated entities covers generating markup so it cannot drift.
- Entity SEO covers why an unambiguous business matters.
- Modern search covers where this sits in the wider foundation.
- Local search versus AI answers covers the same ground for a local business.
