FAQ, review and breadcrumb schema: what still works in 2026

FAQ schema in 2026: the short version

If you added FAQ schema to get those expandable questions under your Google listing, that feature is gone. Google’s documentation changelog has an entry dated May 8, 2026 that says the FAQ rich result “will no longer appear in Google Search starting May 7, 2026”. A second entry on June 15, 2026 removed the documentation and says the feature “is no longer shown in Google Search results.”

Before that, the feature was already narrow. A September 2023 entry limited FAQ rich results to well-known, authoritative government and health websites. A local service business was not going to see them.

This article covers what the three schema types you probably hear about (FAQ, review and breadcrumb) do now, with markup examples and the rules Google sets. It sits under AI search optimization, because the question most owners have is whether schema helps them be found by AI assistants. The answer is more modest than most vendors say.

What changed with FAQ schema

Google removed its FAQ rich result documentation in June 2026, so there are no longer any published rules or limits for the feature: it no longer exists in Search. What the changelog does not say matters too.

• FAQPage is still part of schema.org. Google dropped the display, not the vocabulary.
• The changelog entries we read do not mention Search Console or the Rich Results Test. Some outlets report that the Search Console FAQ report and Rich Results Test support were dropped around June 2026. Google’s changelog entries do not say so, so check your own Search Console to see what is still reported.
• Google did not tell site owners to remove existing markup. The entries we read give no such instruction.

What to do with your FAQ now

1. Keep the questions on the page. A visible FAQ still answers real customer questions, and the page text is what search engines and assistants read.
2. Write answers that stand alone. Two or three sentences, with the price, area or condition included, so the answer makes sense if quoted by itself.
3. Leave existing markup if it is accurate. Google’s general guidelines say not to mark up content that is not visible to readers. If you delete a question from the page, delete it from the markup.
4. Do not add FAQ schema to every page. Put it on pages where the questions are real and answered.

A matching example, for a page that really shows these two questions:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you offer free estimates?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. We quote in writing after a site visit. The estimate is free for jobs in the Boston area."
      }
    },
    {
      "@type": "Question",
      "name": "How soon can you come?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most requests get a reply the same business day. Emergency availability is listed on our contact page."
      }
    }
  ]
}

The questions and answers above are placeholders. Use your own, and make them match the page word for word.

Does FAQ schema help with AI answers?

You will see claims that FAQ markup makes pages several times more likely to be cited by AI assistants. Treat them carefully. Google’s AI features documentation says there are no additional requirements to appear in AI Overviews or AI Mode, and that there is “no special schema.org structured data that you need to add”. It also says structured data should match the visible text.

We searched for independent evidence that FAQ markup raises AI citations and found vendor blogs with conflicting numbers and no controlled study that isolates the markup from the content. That is not proof that it has no effect. It means you should not pay for FAQ schema as a growth plan. A clear FAQ on the page is the part with a plain reason behind it: customers ask those questions.

Nobody controls what Google AI Overviews, ChatGPT or Perplexity recommend, and no markup can promise a placement. We work on structure and facts, and we measure what the tools say before and after.

Review schema: what is allowed for a local business

Review snippets can show star ratings in Search. Google’s review snippet documentation lists LocalBusiness and Organization among the types that can carry Review and AggregateRating markup. Then it adds the rule that decides most local cases.

Self-serving reviews. If a LocalBusiness or Organization controls the reviews about itself, its pages are ineligible for the star review feature. This covers reviews embedded through third-party widgets, such as Google Business or Facebook reviews. Google says ratings for local businesses must come directly from users, and human editors should not create or compile them.

In plain terms: if you run an HVAC company and paste your Google reviews into markup on your own service page, Google will not use it for stars. Other rules in the same documentation:

• Reviews and ratings must be visible to users on the marked-up page.
• Do not combine reviews or ratings gathered from other websites.
• Reviews must be about a specific item, not a category or a list.
• Fake reviews and undisclosed incentivized reviews are prohibited.
• Review needs an author, an itemReviewed (unless nested), and a reviewRating with a ratingValue. AggregateRating needs ratingValue and at least one of ratingCount or reviewCount.
• Google recommends accepting only ratings that include a review comment and an author name.

So what should a service business do about reviews? Collect them on Google Business Profile and other independent platforms, and show a few real quotes on your pages with the reviewer’s name and the platform. Do not mark them up for stars on your own pages. The wider trust picture is in E-E-A-T for service businesses.

Breadcrumb schema: still supported, worth a few minutes

Google’s breadcrumb documentation describes BreadcrumbList markup as showing a page’s position in the site hierarchy, and Google uses it to categorize the page in results. It is documented as available on desktop in all regions and languages where Google Search is available. The page does not mention mobile.

The rules are short:

• At least two ListItem entries, each with a position.
• item (the URL) and name for each entry. The last item can omit item, and Google then uses the page’s own URL.
• The trail should reflect a typical path a visitor takes, not just copy the URL structure.
• The home page item and the current page item are not required.
• Old data-vocabulary.org markup no longer qualifies.

A service page example:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Plumbing", "item": "https://www.example.com/plumbing/" },
    { "@type": "ListItem", "position": 3, "name": "Water heater replacement" }
  ]
}

Breadcrumbs also help visitors and make your hierarchy clear. Add a visible breadcrumb trail on the page to match the markup.

Rules that apply to all three

Google’s general structured data guidelines apply to everything above:

• Markup must match what visitors can see. Do not mark up content that is hidden or not on the page.
• JSON-LD is the recommended format. Microdata and RDFa also work.
• Valid markup does not guarantee a rich result. Google decides what to show for each search.
• Misleading markup can trigger a manual action, which removes rich result eligibility but does not change web ranking.
• Include all required properties. A few complete properties beat many incomplete ones.

What to prioritize instead of FAQ schema

For a local service business, the schema that earns its place is the one that states business facts: Organization or a specific LocalBusiness subtype with name, address, phone, hours and sameAs links. Google’s local business documentation requires address and name and recommends hours, telephone, url and geo, and it asks for the most specific subtype possible. Our guide to schema markup for local service businesses walks through it, and how to test schema markup shows how to check it before you publish.

Google’s AI features page also lists what matters more than any markup: crawlable pages, important content in text, internal links, a good page experience, and current Business Profile data.

How we use these at Magnet Mint

On the sites we build, we add schema that matches the visible page: business details, service information and breadcrumbs, plus FAQPage markup where a page shows real questions, because it is valid and costs little. We do not promise a rich result from any of it. If you want a written list of what your site is missing, the GEO/AEO audit is from $750. You can also start with a free demo. Prices are as of October 2026.

Published October 25, 2026. Updated October 25, 2026.