Somebody has told you the FAQ boxes under your Google listing are gone and that you should strip the code out of your site. Half of that is true. Here is the verdict on FAQ schema in 2026, before any of the explanation: leave the markup exactly where it is, and spend the afternoon rewriting the answers instead.
Google did retire the FAQ rich result. It stopped showing on 7 May 2026, the reporting was pulled out of Search Console through June, and the API support followed in August. What it did not do was make FAQPage markup harmful, and there is no version of this where deleting valid code improves anything.
The useful question is not whether to keep the schema. It is whether the answers inside it are written well enough to be lifted and quoted by something. Most are not. That is the job this post gives you.
Key takeaways
- Google stopped showing FAQ rich results on 7 May 2026 and removed the reporting from Search Console in June, with API support ending in August.
- Google's own position is that structured data which is not being used causes no problems for Search, so valid FAQPage markup can stay in place.
- Most small business sites never saw the FAQ rich result anyway, because Google restricted it to authoritative government and health sites back in August 2023.
- The markup was never a ranking factor, so removing it will not lift rankings and keeping it will not lower them.
- The change worth making is to the writing: put the complete answer in the first sentence, with a real number or timescale, so it survives being quoted out of context.
What Google actually switched off, and when
FAQ rich results were the expandable list of questions that used to appear underneath a search listing, driven by FAQPage markup in the page code. They made one result take up the height of three. That was the whole appeal, and it is why so many agencies added the markup to client sites between 2019 and 2023.
The retirement was not sudden. Google restricted eligibility in August 2023 to well known, authoritative government and health websites, which quietly removed the feature from every hairdresser, builder and accountant in the country three years ago. What happened in May 2026 was the tidying up: the display went, then the search appearance filter, the dedicated rich result report and the support inside the Rich Results Test through June, then the API in August.
So if you are reading this and worrying about lost visibility, check the timing. Unless you run an NHS trust or a council website, you did not lose anything in May. You lost it in 2023 and probably never noticed.
Is FAQ schema still worth it in 2026?
Yes, in the specific sense that it is worth keeping and not worth panicking about. Google has been plain that structured data which is not being used does not cause problems in Search. It also has no visible effect, which is the honest other half of that sentence. Valid FAQPage markup on your pages is inert. Inert is not harmful.
Set against that, removing it is real work with real risk. Someone has to go into the template, take the block out, and not break the surrounding code while they are at it. On a Webflow site that is a careful ten minutes; on an older WordPress build with three plugins fighting over the head of the page it can be an afternoon and a broken layout. You are paying for that in order to achieve nothing.
When you should actually remove it
There are three cases, and only three:
- The markup fails validation. Broken structured data of any type is worth cleaning up, because it can confuse the parsing of the valid markup sitting next to it.
- It describes questions and answers that are no longer on the page. Markup has to match visible content. A page whose code claims six questions it does not display is misleading, and Google treats mismatched structured data as a spam issue regardless of type.
- It was generated automatically and says things you would not say. Plenty of plugins invented FAQ blocks from page headings. Read what yours actually claims before you decide it is harmless.
If none of those apply, close the tab. It is fine.
Does FAQ schema help AI Overviews and ChatGPT?
Be careful with anyone who answers this confidently. No major AI platform has published how it weights FAQPage markup, and any agency quoting you a percentage uplift is quoting a correlation study, not a documented mechanism.
What can be said honestly is narrower and still useful. The systems that read the live web, including Bing, Perplexity and ChatGPT's search behaviour, parse structured data as part of how they understand a page. FAQPage markup does one thing no prose can: it states unambiguously that this exact string is a question and this exact string is its answer. A model reading raw HTML has to infer that pairing from headings and layout, and inference goes wrong on badly built pages.
So the markup is a small, cheap clarity signal rather than a lever. The heavy lifting is done by the answer itself, which is the same conclusion the wider work on answer engine optimisation keeps arriving at, and it is why the practical tactics for getting cited by ChatGPT are about writing rather than code. If you want the broader picture of what structured data does across a whole site, that sits in the schema markup guide rather than here.
The change that actually matters: rewrite the answers
Here is the test. Take any answer from your FAQ section, paste it into a blank document with the question removed, and read it. If it no longer makes sense, or it says nothing a stranger could use, no machine is going to quote it and no customer was ever helped by it.
Most small business FAQ sections fail that test badly, because they were written to fill a section rather than to answer anything. This is a real example of the pattern, from a bathroom fitter's site.
The answer nothing can quote
How much does a new bathroom cost?
Every bathroom is different and there are many factors that affect the final price. We pride ourselves on offering competitive rates and a high quality finish. Get in touch today for a free, no obligation quotation and we will be happy to discuss your requirements.
Forty three words, no information. Remove the question above it and you cannot tell what trade it belongs to, let alone what a bathroom costs. It is a sales line wearing an answer's clothes.
The same answer, rewritten
A full bathroom refit in Bury St Edmunds usually costs between £4,500 and £9,000, with most jobs landing near £6,000. That covers the strip out, first and second fix plumbing, tiling and making good, over eight to twelve working days. Moving the soil stack or specifying large format tiles is what pushes a job to the top of the range.
Sixty words. It answers the question in the first sentence, it names the town, it gives a range and a typical figure, it says how long the work takes, and it explains what moves the price. Lift it out of the page and it still stands up. That is the difference between content that gets quoted and content that gets skipped.
The rules behind the rewrite
- Answer in the first sentence. No preamble, no restating the question. If the first sentence is not the answer, the rest will not be read.
- Name the subject inside the answer. Write "a full bathroom refit", not "it". The answer has to work with the heading stripped off.
- Put a number in it. A price, a range, a timescale, a distance, a quantity. Anything checkable beats anything reassuring.
- Keep it to 40 to 70 words. Shorter and it lacks substance, longer and it stops being a quotable unit.
- One question per heading. Two questions bundled together cannot be cleanly extracted by anything, human or machine.
- Answer the question customers actually ask. Not the one you wish they asked. The phone gives you the list for free; the research behind which questions are worth answering gives you the rest.
Which rich results survived, and which did not
FAQ is not the only feature Google has wound back, and it helps to see where the effort is now worth spending.
| Markup type | Status in 2026 | What to do about it |
|---|
| FAQPage | Rich result retired 7 May 2026 | Leave valid markup, rewrite the answers |
| HowTo | Retired in 2023, no lift on any surface | Leave it, but do not build new |
| Product and merchant listing | Active, price, availability and stars | Keep prices and stock accurate |
| Review and AggregateRating | Active on eligible page types | Only mark up reviews you genuinely hold |
| Event | Active | Keep dates, venues and ticket links current |
| LocalBusiness and Organization | No visual rich result, feeds entity matching | Match it exactly to your Google Business Profile |
| BreadcrumbList | Active, shows the path under your listing | Keep it on every page below the top level |
| Article and BlogPosting | Active as a supporting appearance | Include named author and published date |
The pattern is not hard to read. The features Google has kept are the ones describing verifiable facts about a thing: a price, a date, a rating, a location. The ones it has dropped were describing your writing back to it, and it no longer needs the help.
What to check on your own site this week
Half an hour, no developer required for the first four steps.
- Find out whether you have it. Open one of your pages, view the page source, and search the text for FAQPage. If it is not there, skip to step four.
- Validate it. Run the page through validator.schema.org, which still reports FAQPage properly now that Google's own Rich Results Test no longer covers it.
- Check it matches the page. Every question and answer in the code should be visible to a reader. Delete anything that is not.
- Read your answers cold. Copy them into a blank document without the questions. Rewrite everything that fails.
- Fix the worst three first. Usually price, timescale and coverage area. Those are the questions people ask before they call, and the ones an answer engine most often needs a source for.
On a site we build, the markup and the answer structure are shipped together as part of the standard website build, and the ongoing search work inside every plan keeps the answers current as prices and services change. That is the reason it is not a separate line on the invoice at our pricing.
Frequently asked questions
Did Google remove FAQ rich results?
Yes. Google stopped showing FAQ rich results in Search on 7 May 2026, then removed the FAQ search appearance, the rich result report and Rich Results Test support during June, with API support ending in August. The underlying FAQPage markup still validates and is still parsed by other systems; it simply no longer produces a visible feature in Google.
Should I remove FAQPage schema from my site?
No, in almost every case. Google has stated that structured data which is not being used causes no problems for Search, so valid FAQPage markup is inert rather than harmful. Remove it only if it fails validation, describes content that is not visible on the page, or was auto-generated and makes claims you would not stand behind.
Does FAQ schema help AI Overviews?
There is no documented answer, and anyone quoting you a figure is quoting correlation. What is defensible is that FAQPage markup states unambiguously which text is a question and which is its answer, which removes guesswork for any system parsing the page. Treat it as a small clarity signal and put your effort into the answers themselves.
Is it worth adding FAQ schema to a new page in 2026?
It is worth about ten minutes, not a project. On a platform where the markup is generated automatically, leave the setting on. If adding it means hand-writing JSON-LD for every page, that time is better spent writing the answers properly, because the answer quality drives every outcome the markup was supposed to deliver.
Will keeping FAQ schema hurt my Google rankings?
No. FAQ markup was never a ranking factor, only a display feature, so its presence or absence has no bearing on position. The only structured data that carries ranking risk is markup that is broken or that describes content the page does not contain, and that risk applies to every schema type, not just FAQPage.
How do I check whether my site has FAQ schema?
View the page source in your browser and search the text for FAQPage, or paste the page address into validator.schema.org, which lists every schema type it detects. Google's Rich Results Test no longer reports FAQ markup, so it will look absent there even when it is present. Many sites acquired it via a template or plugin without the owner knowing.
Where this leaves your FAQ page
The retirement of a search feature is a bad reason to change anything on a website, and a good prompt to look at something you have been ignoring. Nobody is going to notice the missing arrows under your listing. Plenty of people will notice that your site is the only one in Stowmarket that says what a job costs and how long it takes.
The businesses that come out of this well are the ones that treat the FAQ section as the most-read part of the site rather than an SEO afterthought, because that is usually what it is. A pub answering whether the garden is dog friendly, a clinic answering how long the appointment takes, a haulier answering what happens if the delivery slot is missed. Those answers do work whether or not any structured data is attached to them.
Leave the markup. Rewrite the answers, starting with price. If you want a second pair of eyes on which questions are missing entirely, send us your FAQ page and we will tell you what your customers are asking that it does not answer.
