Structured Data After AI Search: What Still Pays Off

Schema markup has picked up a new sales pitch: add the right structured data and AI will cite you. Google’s own documentation says otherwise. Its page on AI features and your website states: “There’s also no special schema.org structured data that you need to add.” Its guide to generative AI search lists “overfocusing on structured data” among the things you don’t need to do. So is structured data still worth the effort? Yes, but for the reason it always was.

What Google actually says

The same guide that tells you not to overfocus on structured data also says it is “a good idea to continue using it as part of your overall SEO strategy, as it helps with being eligible for rich results on Google Search.” That is the real job of structured data: it makes a page eligible for richer search result displays, such as review stars, product prices, event dates or breadcrumbs.

There is one AI-related rule worth knowing. Google’s AI features page includes, in its list of SEO basics, “making sure your structured data matches the visible text on the page.” Markup that claims things the page doesn’t show is a problem everywhere, and Google’s structured data policies have always required it to represent the visible content.

Two more points from Google’s introduction to structured data are worth keeping in mind. Google recommends JSON-LD where your setup allows it, as the easiest format for site owners to implement and maintain. And valid markup does not guarantee a rich result: the structured data policies page says Google “does not guarantee that your structured data will show up in search results, even if your page is marked up correctly”. Correct markup makes a page eligible, nothing more, so judge it by the Rich Results Test and Search Console reports rather than by what appears in a single search.

Which markup still earns rich results

Google keeps a list of every structured data feature it supports in its search gallery. As of this month it includes Article, Breadcrumb, Carousel, Course list, Dataset, Discussion forum, Education Q&A, Employer aggregate rating, Event, Image metadata, Job posting, Local business, Math solver, Movie, Organization, Product, Profile page, Q&A, Recipe, Review snippet, Software app, Speakable, Subscription and paywalled content, Vacation rental and Video.

Anything not on that list may still be valid schema.org vocabulary, but it won’t produce a Google rich result. That is the simplest filter for deciding what to add: if it is in the gallery and matches your content, it can pay off. If it is not, it is optional at best.

A shortlist by type of site

Most small sites only need a handful of types. Here is a practical starting point:

• Every site: Organization on the home page (name, logo, contact details), and Breadcrumb if your site has a clear hierarchy.
• Blogs and news sites: Article, with accurate dates and author information. Author details also support the trust signals covered in the earlier post on E-E-A-T for YMYL sites.
• Online shops: Product, with price, availability and shipping where you have them, plus Review snippet only for genuine reviews. The earlier post on sale duration markup covers fields stores often skip.
• Local businesses: Local business, with the same name, address and phone number as your Google Business Profile.
• Event organisers, recipe sites, job boards: Event, Recipe or Job posting respectively. These are among the rich results that change how a listing looks the most.
• Sites with video: Video, which helps Google understand and show your videos.

On WordPress, a plugin usually handles this so you don’t write JSON-LD by hand. Rank Math, for example, adds Organization or Person and Article markup by default and lets you choose a schema type per post. Whatever tool you use, the rules below still apply.

Five checks that prevent structured data problems

1. Test every template. Run one page of each type (a post, a product, the home page) through the Rich Results Test. It shows which rich results the page is eligible for and any errors.
2. Compare markup with the visible page. If the markup says 4.8 stars, the page must show the rating. If it lists a price, the price must be on the page and current.
3. Remove duplicates. A theme and a plugin both outputting Organization or Article markup creates conflicting data. Check the page source for more than one block of the same type.
4. Don’t mark up what isn’t there. FAQ markup on a page without visible questions and answers, or reviews written by the business itself, break Google’s policies. Google’s rules on incentivised reviews and review snippets are one example.
5. Watch the Enhancements reports. Search Console shows reports for detected structured data types, with errors and warnings. Check them after theme or plugin changes, which is when markup most often breaks. The earlier post on JSON-LD unescaping shows one less obvious way markup can fail.

The honest summary

Structured data won’t get you into AI Overviews, and Google has said so in two places. It still does what it always did: it helps Google understand a page and makes the page eligible for rich results, which can make a listing stand out in normal search. For most small sites that means a few accurate, well-tested types, not a page full of every schema available. Accuracy matters more than quantity, because the one firm AI-related rule Google gives is that markup must match what people actually see on the page.