Skip to content
Kuraib Ali

Schema types that still get rich results

Not every schema type Google once supported still produces a visible rich result. What still works, and what happened to FAQ schema.

By Kuraib AliPublished Updated 11 min read

A single jigsaw puzzle piece separated from the rest, representing the FAQ schema type Google removed from search results
Photo: Unsplash

Google's current structured data documentation lists rich results for articles, breadcrumbs, discussion forums, events, job postings, videos, local businesses, movies, organisations, products, profiles, Q&As, recipes, reviews, software apps, and several more. But a type being listed as supported doesn't mean it is worth your time. And one type that used to be on that list, FAQ, is a special case: the markup remains valid, but the visible rich result itself was retired for every site, including the government and health sites previously exempted, as of 7 May 2026.

What is schema markup?

Schema markup is the common name for structured data written with the schema.org vocabulary. Google describes structured data as a standardised format for giving information about a page and classifying its content, and uses it to understand the page and the people, books or companies it mentions. Google recommends JSON-LD, and says Microdata and RDFa are equally fine when the markup is valid and implemented as the feature documentation says.

Which schema types does Google still support in 2026?

Per Google's own Search Central documentation (last updated 16 October 2026), implementing structured data can make a page eligible for these result types:

CategoryTypes
Content & mediaArticles, books, videos, image metadata, math solvers, movies, speakable content
Commerce & localProducts, local businesses, vacation rentals
Structure & navigationBreadcrumbs, carousels, organisations, profile pages
Q&A & communityQ&As, discussion forums, reviews
JobsJob postings, employer ratings
Events & otherEvents, fact checks, recipes, software apps, subscriptions

Several types that used to appear here are gone from the current gallery: FAQ (documentation removed 15 June 2026), practice problems (removed January 2026), and course info, estimated salary, and vehicle listings (removed 9 September 2025). Dataset markup is now only used by Dataset Search.

This list changes over time. Google has retired specific types before (HowTo, retired on mobile and then desktop in 2023, and several lower-usage types since) when usage data showed a feature wasn't adding meaningful value. Treat any static list, including this one, as a snapshot rather than a permanent reference, and check Google's documentation directly before building a long-term content strategy around a specific type.

What happened to FAQ schema?

This is the one confusing entry on the list. Google restricted FAQ rich results in August 2023 to "well-known, authoritative government and health websites." Everyone else stopped seeing the feature regularly from that point on. Then, as of 7 May 2026, Google removed the FAQ rich result entirely, for every site, including the government and health sites that had kept it since 2023. Google then removed its FAQ structured data documentation on 15 June 2026.

What did not change: FAQPage remains a valid Schema.org type. When Google retired seven other types in June 2025, it said the change "won't affect how pages are ranked," and the same holds for markup that no longer triggers a rich result. The markup won't throw an error, won't trigger a manual action, and won't hurt rankings if it's left on a page. What ended is the visible dropdown on the search engine results page (SERP), not the schema type itself.

Is FAQ schema still worth using?

For the SERP dropdown specifically, no. That feature is gone for everyone. But that's a narrower question than "should I keep FAQ content on my page," and the answer to that one hasn't changed: useful question-and-answer content still helps readers. Keeping FAQPage markup does no harm, but it no longer earns a rich result. Remove it if maintaining it has become overhead, not out of a belief that it now causes harm.

A brief history of other retired rich results

FAQ and HowTo aren't isolated incidents. Google has been trimming this list steadily, and knowing the pattern matters more than memorising any single removal, since the next one will follow the same shape.

The sitelinks search box, a search bar Google could show directly under a site's result, was removed globally starting 21 November 2024. Google's own announcement on the Search Central blog was direct about why: "It's been over ten years since we initially announced the sitelinks search box in Google Search, and over time, we've noticed that usage has dropped. With that, and to help simplify the search results, we'll be removing this visual element." Google's guidance at the time was the same as for FAQ: there's no need to remove the underlying structured data, since unsupported markup doesn't cause errors or ranking problems, it just stops rendering.

A larger batch followed on 12 June 2025, when Google's search product manager, Henry Hsu, announced the retirement of seven structured data types at once: Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement, and Vehicle Listing. Search Console's reports and the Rich Results Test's support for six of them were removed on 9 September 2025, with Book Actions excluded. The stated reasoning matched every other removal: usage had dropped so low that the feature wasn't adding enough value to justify maintaining it. One complication: Google reversed part of that decision for Book Actions in November 2025. It restored the documentation and confirmed the markup still powers an active Search feature. So "retired" announcements aren't always final. Check current documentation, not an old removal notice, before assuming a type is gone.

The pattern across all of these is consistent. A type gets removed when Google's usage data shows it isn't earning its space. The underlying schema.org markup is never declared invalid. And Google states that removal doesn't affect rankings, because these visual features were never ranking inputs. Building a content strategy around a niche rich-result type that could plausibly follow the same path (something powering a small, specific visual element rather than broad content structure) carries a real maintenance risk worth weighing against the payoff.

A labelled file cabinet, representing the handful of schema types still worth prioritising on most sites

The schema types worth prioritising

Not every site needs every type on the list above. For most content and business sites, five types cover the large majority of practical value: Organization (homepage identity, sitelinks, and Knowledge Panel eligibility), Article or BlogPosting (author, publish date, and headline for blog and news content), Product (price, availability, and review stars for anything sold directly), LocalBusiness (map and local-pack eligibility for a physical location), and BreadcrumbList (near-universal, low-effort, applies to almost any interior page). Everything else on the full list is valuable for the specific content type it targets (recipes, events, job postings) but isn't worth implementing on a site that doesn't have that content.

Implementing the three highest-value types, with real markup

Reading a property list is one thing; seeing what a correct block looks like is another. Three of the five types above cover most of what a typical guide, product page, or local-business page needs. All three examples below follow Google's own current documentation for required and recommended properties, and all three use JSON-LD (JavaScript Object Notation for Linked Data) in a <script type="application/ld+json"> tag, which is Google's stated preferred format over Microdata or RDFa.

Article (or BlogPosting). Google's own documentation is unusual here: there are no strictly required properties, only recommended ones, but skipping the recommended set means skipping the information Google uses to build the rich result. A minimal correct block for a guide like this one:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Schema types that still get rich results",
  "image": ["https://example.com/images/schema-guide-1x1.jpg"],
  "datePublished": "2026-09-01T08:00:00+04:00",
  "dateModified": "2026-09-14T09:00:00+04:00",
  "author": [{ "@type": "Person", "name": "Kuraib Ali", "url": "https://kuraibseo.site/about" }]
}

headline, image, datePublished, dateModified, and author (with a name and, ideally, a url pointing to a page that identifies that author) are the properties Google's documentation recommends including whenever they apply. Google's own guidance for image recommends supplying multiple aspect ratios (16x9, 4x3, and 1x1) as an array when possible, since different surfaces crop differently.

LocalBusiness. This one does have two required properties per Google's documentation: name and address. Everything else is recommended but optional:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Example Consulting Dubai",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Business Bay",
    "addressLocality": "Dubai",
    "addressCountry": "AE"
  },
  "telephone": "+971-4-000-0000",
  "priceRange": "$$$",
  "url": "https://example.com/",
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Sunday"],
      "opens": "09:00",
      "closes": "18:00"
    }
  ]
}

priceRange has to stay under 100 characters per Google's documentation (a symbol string like $$$ or a range like $10-15 both qualify), and url needs to be a working link to the specific location's own page, not a generic homepage, when a business has more than one location.

Product. Google's documentation splits this type into two tracks: product snippets (for pages that describe a product without a direct purchase) and merchant listings (for pages where the product can be bought), with merchant listings supporting more detail (shipping and return information are recommended, not required). A page that sells directly needs, at minimum, a price and priceCurrency on an Offer, with availability recommended:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Product Name",
  "image": "https://example.com/images/product.jpg",
  "offers": {
    "@type": "Offer",
    "price": "149.00",
    "priceCurrency": "AED",
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/products/example-product"
  }
}

Leaving out a required property such as price or priceCurrency doesn't produce a partial rich result, it produces none, since Google's documentation is explicit that missing required merchant-listing properties disqualify the whole block rather than degrading gracefully. availability, shippingDetails, and hasMerchantReturnPolicy are recommended: leaving them out won't disqualify the page, but it gives Google less to show.

An abstract grid pattern in teal and pink, representing the structured, machine-readable format schema markup provides

Validating structured data with Google's Rich Results Test

Writing correct-looking JSON-LD isn't the same as confirming Google can parse it. Google's Rich Results Test (search.google.com/test/rich-results) is the official tool for that check, and it does two things a manual read-through of the code can't: it renders the page the way Googlebot does, JavaScript included, and it checks the result against the specific eligibility criteria for each rich-result type, not just against valid schema.org syntax.

It accepts either a live URL or a pasted code snippet. For a URL, the tool fetches and renders the page itself; for a snippet, it checks the markup in isolation without page context, which is faster for iterating on a template before it's live. The output lists every structured data type it detected, which rich results (if any) that markup is eligible for, and separates hard errors (which block eligibility entirely) from warnings (recommended properties that are missing but won't disqualify the page on their own).

A magnifying glass resting on a white surface, representing the validation step that confirms structured data parses the way it was written to

Two limitations worth knowing before treating a clean test result as the final word. First, passing the test confirms eligibility, not appearance: Google's own documentation is explicit that correct markup "does not guarantee" a rich result will show up in search results, since Google selects which features to display per query, device, and overall search experience. Second, the test validates against Google's current supported list, which, as the first section shows, keeps changing. A type the tool doesn't flag as eligible for a rich result might simply be one Google no longer supports, not one that's incorrectly marked up. Run the test after any template change that touches structured data, and again periodically on a spot-check basis, since Google's supported list and property requirements both change over time without necessarily breaking the markup itself.

What schema type should I use for my site?

  • Every site: Organization on the homepage, BreadcrumbList on interior pages.
  • Blog or news content: Article/BlogPosting on every post.
  • Selling anything directly: Product, matched exactly to what's visible on the page. Missing required properties like price or priceCurrency means no rich result at all, not a partial one.
  • Physical location: LocalBusiness.
  • Useful Q&A content: FAQPage markup does no harm if you keep it, but it no longer earns a rich result.

Whatever's implemented, validate it against what's visible on the page first. Google's own guidance is direct on this point: structured data must be a true representation of the page content, and mismatched or fabricated markup risks a manual action independent of any of the changes covered above.

Related: is structured data a ranking factor?, canonical tags and canonicalisation.