{"id":7062204,"date":"2026-09-20T15:55:55","date_gmt":"2026-09-20T15:55:55","guid":{"rendered":"https:\/\/peraltafinancing.com\/uncategorized\/8-important-schema-for-better-ai-search-visibility-in-2026\/"},"modified":"2026-09-20T15:55:55","modified_gmt":"2026-09-20T15:55:55","slug":"8-important-schema-for-better-ai-search-visibility-in-2026","status":"publish","type":"post","link":"https:\/\/fivemor.com\/?p=7062204","title":{"rendered":"8 Important Schema for Better AI Search Visibility in 2026"},"content":{"rendered":"


\n<\/p>\n

\n

I run structured data across a publishing operation with a news site, seven content hubs, a shop, a mobile app, fifteen free browser tools and seven language subdomains. That is a lot of surface area, and most of it needs different markup. Over the past two years I have cut my list of schema for better AI search visibility down to eight types. The rest either stopped working or never earned the maintenance.<\/strong><\/p>\n

One thing first, because it shapes everything below. Google has never published a schema requirement for AI Overviews or AI Mode. There is no AI-specific markup. Anyone selling you a special block of JSON-LD that gets you cited is overstating it. What structured data actually does is remove ambiguity.<\/p>\n

It tells a machine who you are, who wrote this, what it costs and when it changed, without asking it to guess. That is a trust and clarity job, not a ranking switch, and it is worth doing for exactly that reason. We cover the rest of the overclaiming in our piece on AI search myths in SEO<\/a>.<\/p>\n

1. Organization: The Anchor for Any Schema Built for Better AI Search Visibility<\/strong><\/span><\/h2>\n

If you implement one thing, implement this one. Every other type on the list points back at it.<\/p>\n

The organization schema states who publishes the site. Name, URL, logo, and sameAs<\/code> links to the profiles you actually control. For a publisher, it NewsMediaOrganization<\/code> is the sharper choice, because it accepts properties that matter for trust.<\/p>\n

We publish a corrections policy and a fact-checking policy as real pages. For a long time they sat in the footer and nowhere else. Pointing the markup at them costs nothing and turns two links into a stated claim about how the operation runs.<\/p>\n

Put the block in your site-wide template, give it an @id<\/code>, and reference that @id<\/code> everywhere else instead of repeating the details. Consistency beats completeness here. If your organization name appears three different ways across your site, social profiles and app listing, fix that before you add another property.<\/p>\n

2. Person: Who Wrote This, in a Form a Machine Can Check<\/strong><\/span><\/h2>\n

Author markup is the second half of the same job. The organization says who published it. The person says who wrote it.<\/p>\n

Give each writer a real bio page. Mark that page up as a Person<\/code> \u201cwith,\u201d\u00a0then have every article reference the @id<\/code> rather than repeating a name string. Add jobTitle<\/code>, knowsAbout<\/code> for their actual subjects, and sameAs<\/code> point to a LinkedIn profile or equivalent that exists.<\/p>\n

The trap is inflation. knowsAbout<\/code> is not a wish list. If the page says someone is an authority on six subjects and they have written about one, you have created a mismatch that is easy to check and embarrassing when checked.<\/p>\n

Our own author pages carry the founder, the editor and the CTO. Each writes in a narrow lane. That narrowness is the point.<\/p>\n

3. Article and News Article: Dates That Are Actually True<\/strong><\/span><\/h2>\n

\"sample\"sample<\/p>\n

Article markup is still one of the few types that produces a visible rich result, and it carries the freshness signal.<\/p>\n

The required work is small: headline<\/code>,author<\/code> referencing your person,publisher<\/code> referencing your organization,and dateModified<\/code>.<\/p>\n

dateModified<\/code> is where most sites quietly cheat. Bumping the date without changing the content is the fastest way to teach a system that your timestamps mean nothing. I only move it when something on the page actually changes, and I try to make the change visible on the page itself. If an AI system is choosing between two sources on a moving topic, the one whose dates match its content history is the safer cite. More on how that plays out in how AI Overviews are changing SEO strategy<\/a>.<\/p>\n

4. BreadcrumbList: Cheap Structure That Machines Read<\/strong><\/span><\/h2>\n

Breadcrumbs are the least glamorous type here and one of the easiest wins. They still produce a rich result, and they state where a page sits without requiring anyone to reverse-engineer your URLs.<\/p>\n

This mattered more on our site than I expected. Our articles sit under hub categories, but our fifteen tool pages sit at the root, because they were built as standalone products. From the outside, nothing connects a calculator to the hub that owns it. Breadcrumbs are the cheapest way to say it out loud.<\/p>\n

Keep them matching the visible navigation. If the breadcrumb trail in your markup does not exist anywhere on the page, you have created a second mismatch for no benefit.<\/p>\n

5. FAQPage: The Honest One<\/strong><\/span><\/h2>\n

This is the type people argue about, so here is the current position, plainly.<\/p>\n

FAQ-rich results no longer appear in Google Search<\/a> as of May 7, 2026. The Search Console report and Rich Results Test support were removed in June 2026, and API support ended in August. For most sites the practical loss happened back in August 2023, when eligibility was narrowed to well-known government and health sites.<\/p>\n

The rich result is gone. The schema type is not deprecated, and the markup still describes your content accurately to anything that parses it. That is the entire remaining case for it, and I think it is still a decent one, because a question with a direct answer under it is the easiest shape for a machine to lift.<\/p>\n

What I stopped doing is bolting FAQ blocks onto pages that had no questions in them. That was always a rich-result play, and the rich result is what died. Write the questions because readers ask them, then mark them up.<\/p>\n

HowTo sits in the same place, one deprecation cycle earlier. Restricted in 2023, no rich result on any surface now, still a valid schema.<\/p>\n

6. Product, Offer and AggregateRating: For Better AI Search Visibility Still Pays Directly<\/strong><\/span><\/h2>\n

\"Product,\"Product,<\/p>\n

Product markup is one of the types that kept its rich results, and it is the one with the clearest commercial return.<\/p>\n

The combination that matters is Product<\/code> plus Offer<\/code> with price, currency and availability, plus AggregateRating<\/code> if you have real ratings. AI answers about what to buy lean hard on this, because price and stock are facts that cannot be inferred from prose.<\/p>\n

Two rules I do not bend. The rating has to be genuine, and it has to be visible on the page. Invisible or invented review markup is one of the few structured data errors that can earn a manual action rather than just being ignored. Keep availability current. A tool can be wrong about your price; you should not be.<\/p>\n

7. SoftwareApplication and WebApplication: For Tools and Apps<\/strong><\/span><\/h2>\n

If you ship software, this one is underused.<\/p>\n

We run fifteen free browser tools and a mobile app for children learning letters. Both categories answer questions that get asked in plain language: a free freelance rate calculator and an alphabet tracing app for a five-year-old. SoftwareApplication<\/code> lets you state, and aaoffers<\/code> block with a price of zero.<\/p>\n

Free is worth stating explicitly. A machine cannot tell that a tool is free by looking at a page that simply has no pricing on it. Silence reads as unknown, and unknown is not what gets recommended. This is the same logic behind using generative AI for SEO<\/a> work at all: state things plainly instead of hoping they are inferred.<\/p>\n

8. VideoObject: The Transcript Is the Point<\/strong><\/span><\/h2>\n

\"VideoObject\"VideoObject<\/p>\n

Video markup takes,\u00a0and a contentUrl<\/code> or embedUrl<\/code>.<\/p>\n

The property people skip is transcript<\/code>, and it is the one that matters most here. A language model cannot watch your video. It can read the transcript. A page with an embedded video and no text is close to empty as far as these systems are concerned, no matter how good the video is.<\/p>\n

Latest Google Update to Be Taken<\/strong><\/span><\/h3>\n

Pruning matters as much as adding. Google has said that structured data, which is not being used, does not cause problems, but it also has no visible effect, so it is pure maintenance cost.<\/p>\n

The seven types retired in June 2025, including Course Info, Claim Review, Estimated Salary and Special Announcement. Dataset markup, which only feeds Dataset Search rather than Google Search. And any markup describing something a reader cannot see on the page.<\/p>\n

\n\n\n\n\n\n\n\n\n\n\n\n\n
Schema type<\/th>\nStill a rich result?<\/th>\nWorth keeping?<\/th>\n<\/tr>\n<\/thead>\n
Organization \/ NewsMediaOrganization<\/td>\nNo<\/td>\nYes, it anchors everything.<\/td>\n<\/tr>\n
Person (author)<\/td>\nNo<\/td>\nYes<\/td>\n<\/tr>\n
Article \/ NewsArticle<\/td>\nYes<\/td>\nYes<\/td>\n<\/tr>\n
BreadcrumbList<\/td>\nYes<\/td>\nYes<\/td>\n<\/tr>\n
FAQPage<\/td>\nNo, retired May 2026<\/td>\nYes, for machine readability only<\/td>\n<\/tr>\n
Product + Offer + AggregateRating<\/td>\nYes<\/td>\nYes<\/td>\n<\/tr>\n
SoftwareApplication<\/td>\nNo<\/td>\nYes, if you ship software<\/td>\n<\/tr>\n
VideoObject<\/td>\nYes<\/td>\nYes, with a transcript.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

Final Thoughts<\/strong><\/span><\/h2>\n

None of this is a shortcut, and anyone promising that structured data alone gets you cited is selling something. Schema for better AI search visibility works by making facts explicit that a machine would otherwise have to infer, and inference is where you lose.<\/p>\n

If you are starting today, do it in this order. Organization first, once, site-wide. Author pages next. Article markup with dates you can defend. Then breadcrumbs. Those four cover most pages on most sites and take an afternoon.<\/p>\n

Then go back and check one thing that is easy to skip: does every claim in your markup appear somewhere a reader can see it? If the answer is no anywhere, fix the page before you touch the JSON-LD.<\/p>\n

\t\t\t\t<\/div>\n