Schema markup in 2026: what still works for Google and AI search?
Short answer: Structured data still matters in 2026, but for fewer visual features. Google stopped showing HowTo rich results in 2023, removed the sitelinks search box in 2024, phased out several lesser-used types in 2025 (including ClaimReview) and stopped showing FAQ rich results from 7 May 2026. Organization, Article, Breadcrumb, Product, Local business, Event and other features remain. For AI Overviews and AI Mode, Google says no special schema is needed, only that your markup matches the visible page. Schema does not automatically win AI citations.
A lot of schema advice online was written for a results page that no longer exists. If a guide promises FAQ dropdowns or a search box under your listing, it’s out of date. Every Google claim below comes from Google Search Central’s own documentation, blog or changelog, checked on 12 November 2026. Where nobody has published anything, we say so.
Which rich results has Google retired?
Oldest first:
| Feature | What Google said | When |
|---|---|---|
| HowTo rich results | Limited to desktop in August 2023; “As of September 13, Google Search no longer shows How-to rich results on desktop, which means this result type is now deprecated.” Documentation removed. | August to September 2023 |
| FAQ rich results (first change) | “Will only be shown for well-known, authoritative government and health websites” | August 2023 |
| Sitelinks search box | “We’ll be removing this visual element starting on November 21, 2024.” Documentation removed 29 November 2024. | Announced 21 October 2024 |
| Course info, estimated salary, learning video, special announcement, vehicle listing | Named in the June 2025 phase-out; “no longer shown in Google Search results”, documentation removed 9 September 2025 | Announced 12 June 2025 |
| ClaimReview (fact check) | Named in the June 2025 phase-out and listed in September 2025 as “phased out from Search results”. Its documentation page still exists with the note “We’re phasing out support for ClaimReview markup in Google Search. However, this markup remains supported by the Factcheck Explorer Tool.” | 2025 |
| Practice problem | Deprecation notice 5 November 2025; documentation removed 6 January 2026 because it “is no longer shown in Google Search results” | November 2025 to January 2026 |
| Dataset | Clarified on 5 November 2025 as “only used by Dataset Search, and not Google Search” | November 2025 |
| FAQ rich results (final change) | “This feature will no longer appear in Google Search starting May 7, 2026.” Documentation removed 15 June 2026. | May to June 2026 |
One reversal. Book actions were also named in the June 2025 phase-out. On 5 November 2025 Google removed the deprecation banner from the book actions documentation, “as there’s still a feature using the markup in Google Search”. Book actions are limited to book providers with a wide selection of available books, so they don’t apply to most sites.
None of this was a ranking change. Google said the HowTo and FAQ change “should not be considered a ranking change”, that the sitelinks search box removal “doesn’t affect rankings”, and that the June 2025 simplification “won’t affect how pages are ranked”. What changed is how results look.
Does old FAQ or HowTo markup hurt?
No, according to Google. In August 2023 it said: “While you can drop this structured data from your site, there’s no need to proactively remove it. Structured data that’s not being used does not cause problems for Search, but also has no visible effects in Google Search.” It said much the same about sitelinks search box markup in 2024: “Unsupported structured data like this won’t cause issues in Search.”
So there’s no emergency. The rule that matters is Google’s general one: “Don’t mark up content that is not visible to readers of the page.” If your FAQPage markup describes questions and answers people can see, it’s accurate. If it describes FAQs removed from the page years ago, take it out when you next edit that template.
What to stop is adding FAQ or HowTo markup to win a search feature. That feature no longer exists in Google Search, so “add FAQ schema for rich results” is expired advice.
QAPage isn’t a workaround. Google’s Q&A guidelines say: “Don’t use QAPage markup for FAQ pages or pages where there are multiple questions per page.” They list “an FAQ page written by the site itself with no way for users to submit alternative answers” as an invalid use. QAPage is for a page built around a single question with answers, such as a forum thread or a support community post. Our guide on FAQPage vs QAPage: what each is for covers the difference in detail.
Which structured data still earns a Google feature?
Google’s structured data search gallery lists these features (checked 12 November 2026; the gallery page was last updated 16 October 2026). The “documented AI effect” column describes what Google or any AI company has published about that type and AI answers.
| Type | Google feature or use | Who it’s for | Key requirement | Documented AI effect |
|---|---|---|---|---|
| Organization | Logo, legal name, address and contact details, which “can show up in knowledge panels and other visual elements” | Every business | No required properties; add the ones that apply | Not established |
| Article | Article title and larger images in rich result features | Publishers, blogs, guides | No required properties; add the ones that apply | Not established |
| Breadcrumb | Breadcrumb trail in the result | Any site with a hierarchy | itemListElement with ListItem entries |
Not established |
| Local business | Business details in the knowledge panel | Physical businesses | name and address |
Not established |
| Product | Price, availability and review details | Sellers of products | name, plus offers, review or aggregateRating |
Not established |
| Review snippet | Star ratings | Reviews of other things, not of your own business | See the self-serving rule below | Not established |
| Event | A list of events people may attend at a particular time and place | Venues, organisers | Per-feature guidelines | Not established |
| Recipe, Video, Image metadata, Movie, Carousel | Media and content features | Publishers of those formats | Per-feature guidelines | Not established |
| Job posting, Employer aggregate rating | Google’s job search experience | Employers, job boards | Per-feature guidelines | Not established |
| Course list, Education Q&A, Math solver, Q&A | Education and single-question pages | Education sites, forums | Per-feature guidelines | Not established |
| Discussion forum, Profile page | Forum threads; pages about one person or organisation | Communities, author pages | Per-feature guidelines | Not established |
| Software app, Vacation rental, Subscription and paywalled content | Specialist features | Those publishers | Per-feature guidelines | Not established |
| Speakable (beta) | Google Assistant reading news aloud | English-language news publishers, US users | Beta; see below | Not established |
| Dataset | Dataset Search only, not Google Search | Data publishers | Per-feature guidelines | Not established |
Valid markup never guarantees a feature. Google: “Using structured data enables a feature to be present, it does not guarantee that it will be present.” Our evidence note on structured data and rich result eligibility makes the same point: eligibility is not a guarantee of display.
Three conditions people often miss:
- Reviews of your own business. Google’s review snippet guidelines say: “If the entity that’s being reviewed controls the reviews about itself, their pages that use LocalBusiness or any other type of Organization structured data are ineligible for star review feature.” That includes reviews shown through an embedded third-party widget. The same guidelines say “Don’t aggregate reviews or ratings from other websites.” Since July 2026 they also cover fake and undisclosed incentivised reviews.
- Speakable is a beta feature. Google says it “works for users in the U.S. that have Google Home devices set to English, and publishers that publish content in English”, and that the Google Assistant uses it “to answer topical news queries on smart speaker devices”. It isn’t a general AI-search signal.
- WebSite markup still matters for site names. When Google retired the sitelinks search box it noted that “site names also uses a variation of WebSite structured data, which continues to be supported”. You don’t need a
SearchActionany more.
What does schema do for AI answers?
It’s worth separating what’s documented from what isn’t.
What Google documents. Its AI features guidance says: “There are no additional requirements to appear in AI Overviews or AI Mode”, “there’s also no special schema.org structured data that you need to add”, and lists “making sure your structured data matches the visible text on the page” among its recommendations. A page must be “indexed and eligible to be shown in Google Search with a snippet”. Google’s May 2026 guide to optimising for generative AI features goes further, listing “overfocusing on structured data” among things to ignore: “Structured data isn’t required for generative AI search, and there’s no special schema.org markup you need to add. However, it’s 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.”
What isn’t documented. We haven’t found public documentation from OpenAI, Anthropic, Perplexity or xAI describing how, or whether, schema markup affects which pages their assistants cite. Treat any claim that a schema type “makes ChatGPT cite you” as unproven unless it comes with a primary source.
What schema reliably does. It states facts about a page in a consistent, machine-readable form: who publishes it, what the business is called, where it is, what a product costs, who wrote an article and when. That reduces ambiguity for any system that reads it. It’s why the SearchScore audit checks structured data as one of its eight GEO categories, weighted at 12% of the GEO score. That weight reflects how we score website readiness. It isn’t a measurement of how much schema changes citations.
How common the gap is. In SearchScore’s own measurement (Q3 2026 SAVI index panel, 102,873 websites, weighted), 55.7% of websites published no JSON-LD, and 68.2% published no Organisation schema (SearchScore data). No JSON-LD isn’t the same as no structured data: some of those sites declare schema in microdata or RDFa, which the JSON-LD figure doesn’t count. Both figures describe SearchScore’s panel of audited websites, not the whole web.
Copyable JSON-LD examples
Fictional examples. Harbour Lane Accounts and example.co.uk are invented. Replace every value with your own, and only include properties whose values are visible on the page or true of your business.
Each block goes inside a <script type="application/ld+json"> tag. We checked that each one parses as JSON and that every property and type name exists in the Schema.org vocabulary. Run your own version through the Schema.org validator and, for features Google still supports, Google’s Rich Results Test.
Organization (home or about page):
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.co.uk/#organization",
"name": "Harbour Lane Accounts",
"url": "https://www.example.co.uk/",
"logo": "https://www.example.co.uk/images/logo.png",
"email": "[email protected]",
"telephone": "+44 20 7946 0000",
"sameAs": [
"https://www.linkedin.com/company/example-harbour-lane-accounts"
]
}
Article (guides and blog posts; the dates must match the dates shown on the page):
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How much does bookkeeping cost for a small business?",
"datePublished": "2026-10-01",
"dateModified": "2026-11-01",
"author": {
"@type": "Person",
"name": "Sam Example",
"url": "https://www.example.co.uk/team/sam-example/"
},
"publisher": {
"@id": "https://www.example.co.uk/#organization"
},
"image": "https://www.example.co.uk/images/bookkeeping-costs.jpg"
}
BreadcrumbList (must match the breadcrumb trail visible on the page):
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://www.example.co.uk/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Guides",
"item": "https://www.example.co.uk/guides/"
},
{
"@type": "ListItem",
"position": 3,
"name": "Bookkeeping costs"
}
]
}
Google’s breadcrumb documentation says the item URL isn’t required for the last breadcrumb; Google then uses the URL of the containing page.
LocalBusiness (a physical business; name and address are required for Google’s feature). Note there’s no aggregateRating here: Google treats ratings a business controls about itself as ineligible for stars.
{
"@context": "https://schema.org",
"@type": "AccountingService",
"name": "Harbour Lane Accounts",
"url": "https://www.example.co.uk/",
"telephone": "+44 20 7946 0000",
"address": {
"@type": "PostalAddress",
"streetAddress": "1 Harbour Lane",
"addressLocality": "Bristol",
"postalCode": "BS1 0AA",
"addressCountry": "GB"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "09:00",
"closes": "17:30"
}
],
"priceRange": "££"
}
AccountingService is a Schema.org subtype of LocalBusiness. Use the most specific subtype that is true of your business, or LocalBusiness if none fits.
A practical checklist for 2026
Every site:
- Organization (or the right LocalBusiness subtype) on the home or about page, with details that match your website and profiles.
- WebSite with your site name. No
SearchActionneeded. - BreadcrumbList that matches the visible breadcrumb trail.
By page type:
- Articles and guides: Article with a named author, and
datePublishedanddateModifiedthat match the dates shown. - Product pages: Product with an Offer carrying the visible price and currency.
- Local service pages: LocalBusiness details consistent with your Google Business Profile.
- Events, jobs, recipes, videos: the matching type, following that feature’s own guidelines.
Rules that apply everywhere:
- Mark up only what readers can see.
- Keep markup and visible text in step when either changes.
- Don’t add markup to win a feature that has been retired.
- Don’t mark up star ratings for reviews of your own business.
What to do this week
- List the schema types each page template outputs. View the page source and search for
application/ld+json, or use your CMS plugin’s settings. - Stop adding markup whose only purpose was a retired feature. Remove FAQ or HowTo markup where it describes content that’s no longer on the page.
- Check that your organisation details match everywhere they appear: site, profiles and directories.
- Run a free SearchScore audit to see how your structured data scores alongside the other seven GEO categories, then work through the findings it lists, highest priority first.
For pages built to help people choose, see comparison, alternatives and pricing pages. For the wider question of what schema can and can’t do for AI search, see schema markup for AI search.
Sources
Google sources checked 12 November 2026.
- Google Search Central blog, Changes to HowTo and FAQ rich results, 8 August 2023, updated 14 September 2023
- Google Search Central blog, Farewell, Sitelinks Search Box, 21 October 2024
- Google Search Central blog, Simplifying the search results page, 12 June 2025, updated 8 September 2025
- Google Search Central blog, An update on our efforts to simplify the search results page, 5 November 2025
- Google Search Central, Latest documentation updates (entries for 29 November 2024, 12 June 2025, 9 September 2025, 5 November 2025, 6 January 2026, 8 May 2026, 15 June 2026 and 24 July 2026)
- Google Search Central, AI features and your website
- Google Search Central, Optimizing your website for generative AI features on Google Search
- Google Search Central, Structured data search gallery
- Google Search Central, General structured data guidelines
- Google Search Central, Review snippet, Q&A, Speakable, Fact check, Book actions, Breadcrumb, Local business and Site names
- SearchScore, JSON-LD and Organisation schema figures (Q3 2026 SAVI index panel, 102,873 websites, weighted)
Frequently asked questions
Does Google still show FAQ rich results?
No. Google limited FAQ rich results to well-known, authoritative government and health websites in August 2023. Its documentation changelog then said the feature would no longer appear in Google Search starting 7 May 2026, and the FAQ documentation was removed in June 2026. FAQPage is still Schema.org vocabulary, but it no longer earns a Google search feature for anyone.
Should I remove old FAQ or HowTo markup?
There's no need to rush. When Google changed HowTo and FAQ results in 2023, it said there was no need to proactively remove the markup, and that structured data that isn't being used does not cause problems for Search. Remove it if it describes content that's no longer visible on the page; keep it if it accurately describes questions and answers readers can see.
Can I use QAPage markup instead of FAQPage?
Not on an ordinary FAQ. Google's Q&A guidelines say not to use QAPage markup for FAQ pages or pages with multiple questions, and list an FAQ written by the site itself, with no way for users to submit answers, as an invalid use. QAPage is for a page built around one question with answers, such as a forum thread.
Do I need schema to appear in Google AI Overviews or AI Mode?
No. Google's guidance on AI features says there's no special schema.org structured data you need to add, and no additional technical requirements beyond being indexed and eligible to show in Google Search with a snippet. It also says to make sure your structured data matches the visible text on the page.
Does schema help ChatGPT or Perplexity cite my site?
We haven't found public documentation from OpenAI, Anthropic, Perplexity or xAI saying that schema markup changes which pages their assistants cite. Treat that as an open question rather than a proven tactic. Schema reliably states facts about a page in a consistent format; what any assistant does with it is not documented.