What Structured Data Actually Does (And What It Does Not)

This post used to be called "Structured Data Is a Lead Generation Tool." That title was wrong, and the argument under it was wrong in a way that is worth explaining rather than quietly deleting.

Structured data does not generate leads. It does not earn you the map pack. It does not make Google rank you higher. What it does is narrow and real: it states the facts about your page in a format a machine can read without inferring anything, and it can make a page eligible for a search feature that Google supports. Eligible. Not entitled.

We are rewriting this because we found ourselves recommending schema types to clients that Google had already stopped showing.

What structured data actually is

Schema.org vocabulary, expressed as JSON-LD in your page, that says in plain key-value terms: this is an Organization, its name is X, its address is Y, this page is an Article published on this date by this author, this is a Product with this price and this availability.

Without it, a search engine or a language model has to infer those facts from your prose and your HTML layout. Sometimes it infers correctly. Sometimes it decides your phone number is a fax number, or that the author of your article is the name in your cookie banner. Structured data removes the inference step. That is the entire mechanism. It is a strong and unglamorous benefit and it is enough of a reason to do the work.

What it does not do

It does not earn the map pack. Google's local ranking comes down to relevance, distance, and prominence. Your Google Business Profile drives that surface, not the JSON-LD on your website. We have said otherwise in the past and that was not correct.

It does not get you a star rating in search. Google's structured data policy excludes self-serving review content, meaning reviews about your own business that live on your own site. Marking up an AggregateRating you assigned to yourself is not a growth hack, it is a policy violation, and it is also just a lie printed in machine-readable form. We have a house rule against it and we do not run one on our own site.

FAQ markup no longer produces an FAQ rich result for you. In August 2023 Google restricted FAQ rich results to well known, authoritative government and health sites. In 2026 Google dropped the FAQ appearance entirely. HowTo rich results were deprecated in the same 2023 change. An earlier version of this post called FAQ schema "absurdly powerful" and told you to mark up your sales objections. That advice is dead. It was accurate when it was written and it is not accurate now, which is the ordinary condition of SEO advice and a good argument for dating everything you read.

It does not guarantee any feature at all. Google's own documentation says that valid structured data makes a page eligible for a rich result and that Google does not guarantee the feature will appear. Eligibility is a gate, not a promise.

What it can do, with the evidence stated plainly

Google publishes case studies on its structured data documentation. Rotten Tomatoes added structured data to 100,000 pages and reported a 25 percent higher click-through rate on pages with markup than on those without. Nestle reported an 82 percent higher click-through rate on pages that appeared as rich results.

Read those carefully. They are vendor-reported before-and-after numbers published by the platform that benefits from adoption, not controlled experiments, and they come from very large publishers with content types that Google supports rich results for. They are evidence that rich results can lift click-through when you qualify for one. They are not evidence that adding LocalBusiness schema to a five-page plumbing site will lift anything, because there is no rich result for that site to win.

That is the question to ask before you write a single line of JSON-LD: does Google currently support a visible feature for this content type? If yes, markup makes you eligible for it. If no, the markup is still worth adding for machine-readable clarity, and you should expect no visible change in the search results whatsoever. Anyone who tells you differently is selling schema.

The types that still map to a supported feature

Check Google's search gallery for the current list before you build anything, because it changes. As of this writing, the types that reliably matter for a small business are:

Organization or LocalBusiness. Name, address, phone, hours, sameAs links to your real profiles. This is your identity record. It is what makes your business a resolvable entity rather than a string of text, and it is what keeps a machine from guessing.

Product, with real offers. If you sell things, price and availability are eligible for product rich results.

Article and BreadcrumbList. Modest, but supported, and they clarify authorship and site structure.

Event, JobPosting, Recipe, Video. Supported, if you actually have that content.

Everything else you can mark up, and most of it will produce no visible feature. That is fine. Add it for accuracy, not for a payoff.

Structured data and AI answers

Some AI systems parse JSON-LD. Some do not. The honest position is that we do not have a controlled measurement showing that adding schema causes an assistant to recommend a business, and neither does anyone else who is confidently telling you it does.

What we can say from our own work is narrower and better supported. In our 368-site study, 92 of 368 sites lost at least one answer-critical element (body text, links, or name-address-phone) between the rendered DOM and the raw HTML. A crawler that does not execute JavaScript sees nothing on those pages. If your facts only exist after hydration, structured data in the initial HTML is one of the few things a non-rendering crawler can still read. That is a real, checkable reason to serve JSON-LD server-side. It is not the same claim as "schema makes ChatGPT recommend you."

How to do it without wasting a week

1. Write Organization or LocalBusiness JSON-LD for your homepage. Real name, real address, real phone, real hours, real sameAs profile links.
2. Serve it in the initial HTML, not injected by client-side JavaScript.
3. Run the page through Google's Rich Results Test and the Schema Markup Validator. The first tells you what feature you are eligible for. The second tells you whether the syntax is valid at all. They are different tools and you want both.
4. Make sure the marked-up facts match what a human reads on the page. Mismatch is a manual action risk and, again, it is just false.
5. Do not mark up reviews of yourself.

Our DeepAudit AI checks for structured data as part of its 60-plus checks across 9 categories and will tell you what is present and what is malformed. It will not tell you that schema is going to make your phone ring, because it will not.

The honest bottom line

Structured data makes your facts explicit and makes you eligible for the features Google currently supports. Both of those are worth an afternoon. Neither of them is lead generation. If your leads are not coming, the problem is almost never your JSON-LD, and we would rather tell you that than sell you the markup.

Run the free audit and see what your site actually declares about itself.