Playbook · AI search and GEO

Updated

Which schema markup matters for search and AI answers?

The schema markup that matters is the kind Google lists in its search gallery for your type of page, such as Article, Product, Organization or Breadcrumb, written in JSON-LD and matching what the page shows. Google says AI search needs no special schema, so markup helps rich results and understanding, not a separate AI ranking.

Rotten Tomatoes added structured data to 100,000 pages and measured a 25% higher click-through rate than on pages without it.
Source: Google Search Central, updated 10 Dec 2025

What Google says about schema markup

  • JSON-LD is the recommended format, if your setup allows it.
  • Do not mark up information the user cannot see on the page, even if it is accurate.
  • Required properties make a page eligible for a rich result. Google does not guarantee it will show one. Eligible is as far as markup gets you.
  • Structured data is not required for generative AI search, and there is no special schema.org markup for it.

Markup that no longer shows anything

FAQ rich results stopped appearing in Google Search on 7 May 2026, and Google removed the FAQ documentation on 15 June 2026. How-to rich results went in September 2023. Leaving the markup in place does no harm, but it no longer earns extra space in results. Any checklist that still counts FAQ schema as a quick win was written before May 2026.

Types worth checking for a company site

  • Organization: name, logo, contact and profiles.
  • Article: headline, author and date modified on guides and posts.
  • Breadcrumb: where the page sits in the site.
  • Product and Review snippet, for stores. Software app, for apps.
  • Profile page, for a person or a team member.

This site’s JSON-LD, as a worked example

ProfessionalService and Service do not earn a rich result in Google’s gallery. I keep them because they describe the business in a form machines can read, and they cost nothing once they come from the same data.

  • Every page: a ProfessionalService node for badii.studio with an OfferCatalog of priced offers, a Person node for me, and a WebSite node.
  • The offers are built from the same data as the pricing table, so the prices in the markup cannot drift from the prices on the page.
  • Every guide: an Article with the question as the headline and the same updated date the page shows, linked to the Person and the business by id.
  • Every service page: a Service with its offers and prices.

How to check yours

Run your main templates through Google’s Rich Results Test, then compare each field with what a visitor sees. Missing markup is rarely the bug I find. The usual one is markup that says one price, date or author while the page says another, because someone updated the page and nobody remembered the JSON.

Read next

Sources

Start

Tell me where the product is stuck.

In 30 minutes we look at where things stand, what you need from a CTO right now, and which option fits. Either way, you leave with a clear next step.

How the call goes

  1. 01You tell me about the product, the team and the next 6 months.
  2. 02I ask about the code, the stack and what keeps breaking.
  3. 03We pick the option that fits, or agree that none does.

09:00 to 20:00 CET

Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.