Structured data for AI search: the schema types that matter in 2026

Key takeaways

Structured data helps Google understand a page and qualifies it for rich results; it is not a ranking signal, and a manual action for bad markup removes rich result eligibility without affecting ranking (Google).
FAQ rich results stopped appearing in Google Search on May 7, 2026, and HowTo rich results are gone on every device, so neither type earns visibility any more (Google).
Organization, Article, ProfilePage, Product and LocalBusiness are the types that map to entities an AI answer has to identify: who you are, who wrote this, what it costs, where you are.
Google recommends JSON-LD, and every property must describe content a visitor can actually see on the page (Google).
Keep deprecated markup if you like, Google's docs say it can stay for other engines, but do not spend another hour on it.

Structured data is not a requirement for AI search: Google's own guide states "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add" (Google). What still matters in 2026 is a small set of types that keep your company, authors, products and locations unambiguous for the systems that feed AI answers: Organization, Article with a real author, ProfilePage, Product, LocalBusiness, Breadcrumb and Video. FAQPage and HowTo no longer produce anything visible in Google.

Does structured data help you get cited by AI?

Indirectly. Google's stated purpose for structured data is to provide "explicit clues about the meaning of a page", and its main visible effect is eligibility for rich results (Google). AI Overviews and AI Mode are built on the same index and the same quality systems as the ten blue links, so anything that helps Google understand a page cleanly also helps there, without being required.

The larger benefit is entity clarity. An AI answer has to decide that "Qubba" is a marketing and automation company with a specific website, address and people, and not a similarly named brand. Consistent Organization and author markup, matching the visible page and your public profiles, is the cheapest way to settle that. Google also cautions that structured data "must be a true representation of the page content" and that you should not "mark up content that is not visible to readers of the page" (Google).

Which schema types still earn something in Google in 2026?

Google's search gallery currently lists 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 (Google). For most companies, seven of those do the work.

Type	What it does in 2026	Who needs it
Organization	Feeds the logo, knowledge panel and merchant details; anchors your entity (Google)	Every site, on the home or about page
Article	Better title, image and date handling; ties content to a named author (Google)	Blogs, news, guides
ProfilePage	Identifies the person or organization behind first-hand content (Google)	Author and team pages
Product	Product snippets and merchant listings with price, availability and reviews (Google)	Anyone selling online
LocalBusiness	Knowledge panel and business carousels in Search and Maps (Google)	Physical locations
Breadcrumb	Shows site hierarchy in results	Any site deeper than one level
Video	Video rich results and key moments	Sites hosting their own video

What happened to FAQ and HowTo markup?

Google's FAQPage documentation now carries a deprecation notice: "This feature will no longer appear in Google Search starting May 7, 2026", with the search appearance filter, report and Rich Results Test support removed in June 2026. HowTo "is no longer shown in search results, on both desktop and mobile devices", and Practice problem rich results ended in January 2026 (Google). The 2026 removal completed a rollback that began in August 2023, when Google limited FAQ rich results to government and health sites (Search Engine Journal).

The markup itself is still valid schema.org: FAQPage is defined simply as "a WebPage presenting one or more Frequently asked questions" (schema.org). Google's pattern across these deprecations is to say the markup can stay because other search engines and services may use it. So leave existing FAQPage blocks in place if they mirror visible questions, and stop adding them in the hope of a Google rich result.

Which types matter most for AI answer engines?

Start with the entity. Google recommends placing Organization markup "on your home page, or a single page that describes your organization", with name, url, logo, sameAs, address, contactPoint, telephone, email and description (Google). Use the same name everywhere, and point sameAs at profiles you control.

Then authorship. Article markup should carry author.name and author.url, where the URL is "a web page that uniquely identifies the author", plus datePublished and dateModified in ISO 8601 (Google). Give each author a bio page with ProfilePage markup naming the person as mainEntity, with a real name, image and sameAs links (Google).

If you sell, add Product with price, availability and reviews, and pair it with a Merchant Center feed: Google says providing both "maximizes your eligibility to experiences and helps Google correctly understand and verify your data" (Google). If you have premises, add LocalBusiness with the required name and address, plus telephone, openingHoursSpecification, geo and url (Google). Google's generative AI guide points product and local businesses to Merchant Center and Business Profiles for exactly these features (Google).

How should you implement it?

Use JSON-LD. Google recommends it "as it's the easiest solution for website owners to implement and maintain at scale" (Google). A minimal Organization block looks like this:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://qubba.ai/marketing#org";,
  "name": "Qubba Marketing",
  "url": "https://qubba.ai/marketing/";,
  "logo": "https://qubba.ai/marketing/assets/shared/logo/lockup.svg";,
  "email": "hello@qubba.ai",
  "sameAs": ["https://qubba.ai/";]
}

Three rules keep it safe. Every value must match something visible on the page, because Google will not accept "structured data about information that is not visible to the user, even if the information is accurate" (Google). Dates must be true, so wire dateModified to your publishing system rather than typing it. And validate with the Rich Results Test after every template change, since one broken block silently disables the whole graph.

What should you stop doing?

Stop adding FAQPage and HowTo for Google, for the reasons above. Stop publishing llms.txt as if it were markup: Google says such files "neither harm nor help your site's visibility or rankings" (Google). Stop marking up reviews or ratings that are not shown on the page, and stop stamping every page with the same generic Organization block instead of one canonical one.

At Qubba Marketing the standard site graph is one Organization, one ProfilePage per author, Article on every post, Breadcrumb everywhere, and Product or LocalBusiness only where the page really sells or really has a door. It is small on purpose: fewer types, all accurate, all visible.

Frequently asked questions

Should I remove FAQPage markup now that Google dropped FAQ rich results?

You do not have to.
Google's deprecation notices say the feature has stopped showing, not that the markup is invalid, and its documentation for retired features consistently notes the markup can stay for other search engines and services.
Keep it only where it mirrors questions and answers visible on the page, and do not add new blocks expecting a Google rich result.

Does structured data improve rankings?

No.
Google describes structured data as a way to give explicit clues about a page's meaning and to qualify for rich results, and its policy states that a manual action for markup problems removes rich result eligibility while it "doesn't affect how the page ranks".
Treat markup as clarity and presentation, and put ranking effort into content, links and page quality.

Is JSON-LD better than microdata or RDFa?

Google supports all three but recommends JSON-LD because it is the easiest to implement and maintain at scale.
JSON-LD lives in one script block, so it can be generated from your CMS without touching page templates, and it is simple to validate.
Use microdata only when a platform forces it, and never mix formats for the same entity on one page.

Which single type should a small business add first?

Organization on the home page if you sell online or nationally, LocalBusiness if customers visit a physical location.
Both need a consistent name, address, phone and URL that match your public profiles.
That one block settles who you are for search engines and AI answer engines alike, and every other type you add later links back to it.