Insights / Visibility & Authority
Structured data: the nutrition label of your website
What structured data clarifies, what it can’t guarantee, and why the label has to match what’s in the box.
Pick up a box of crackers and the front tells you a story. Whole grain. Hearty. Made with real something.
The back tells you what’s inside. Serving size, ingredients, the numbers. Same product, two jobs. The front persuades. The label clarifies.
Your website works the same way. The page people read is the front of the box. Structured data is the label underneath: a standard format that tells machines, plainly, what the page is about. This is a business. This is its address. This person wrote this article. This is a service, and this is where it’s offered.
Search engines and AI tools don’t read your site the way a person does. They parse it, classify it and try to work out what they’re looking at. A clear label helps them get it right.
The question isn’t whether you have structured data. It’s whether your label is accurate, and what you expect it to do.
What the label clarifies
Structured data uses a shared vocabulary, called schema, to describe things on your pages. It removes guesswork. Is “Halton” a place you serve or a person on your team? Is that page an article or a service? Is the phone number in the footer the main office or a branch?
When the answers are explicit, machines are less likely to misread you. That matters for search, and it matters for the wider picture AI tools build about your business, because a clear, consistent identity is easier to recognize across sources.
That’s the job: clarity. Not persuasion, not ranking magic.
What it can’t guarantee
A lot of older advice, including some we published, made bigger promises. Here’s where things stand.
It isn’t required for AI features. Google states that no special schema or new markup is needed to appear in its AI features. Pages that are crawlable, useful and clear are the foundation. Markup can help machines read a page accurately. It doesn’t earn you a place in an AI answer, and nobody can show it reliably does across tools.
FAQ rich results are gone. Google ended FAQ rich results in May 2026. FAQ content can still help your readers. The expandable questions under a search result are no longer something markup gets you.
HowTo rich results were deprecated in 2023. The vocabulary still exists. The search feature doesn’t. Valid markup and a supported search feature are different things.
It doesn’t guarantee anything else either. Not featured snippets, not stars, not clicks, not rankings. Eligibility for a feature is not the feature.
A nutrition label doesn’t make the food healthier. It makes it easier to understand.
Why the label has to match the box
A label that lists ingredients the product doesn’t contain is worse than no label. Same here.
Structured data should describe what a visitor can see on the page. If your markup says you serve six cities and the page mentions two, or claims reviews nobody can find, or carries last year’s address, you’re sending conflicting signals. Google’s guidelines treat markup that misrepresents visible content as a problem, and it can cost you eligibility for features altogether.
Mismatch usually isn’t deliberate. A plugin adds markup automatically. Someone changes the hours on the site and nobody updates the profile data. A theme update quietly duplicates the organization details. That’s why the label needs an owner, not just an installer. If you’re not sure who that is, start with who controls your website.
The types most businesses need
You don’t need every type in the vocabulary. You need the ones that describe what’s actually on your pages.
Organization.
Who you are: legal and trading name, logo, website, contact details, and the official profiles that belong to you. This is the core of your identity.
LocalBusiness.
For firms with a physical location or defined service area: address, hours, phone, area served. Pick the most specific type that fits, and keep it matched to your business profiles.
Person.
For the people whose expertise you’re asking buyers to trust: name, role, credentials, and the articles or services they’re connected to. Useful only if the page itself shows that information.
Service.
What you offer, to whom, and where. Mark up services that have their own clear page, not a list of everything you’ve ever done.
Article.
For insights and resources: headline, author, publication and update dates. It connects your content to the people who wrote it.
BreadcrumbList.
How a page sits in your site’s structure. Simple, low risk, and it helps search engines understand your hierarchy.
Review, only where policy allows.
Google doesn’t show review stars for testimonials a business collects and publishes about itself. Review markup has legitimate uses, but your own testimonials page usually isn’t one. Display genuine testimonials as content and let independent reviews live where they belong.
Two more you may see recommended: QAPage is meant for pages where many people answer one question, like a forum. Speakable was built for news publishers. Neither is a general fix for conversational search.
Check it, then keep it current
Validate your markup with Google’s Rich Results Test and the Schema Markup Validator. Then compare it, line by line, with what the page says. Validation tells you the syntax is right. Only a person can tell you the facts are.
Recheck whenever something real changes: a move, a new service, a new partner, a rebrand. And when you want to know whether the bigger picture is landing, test what AI tools actually say about you. Structured data is one input to AI visibility, not the whole of it.
Make the label accurate.
Make it match the box.
Then make sure the box is worth buying.