Should You Still Add FAQ Schema in Webflow in 2026?

Should you still add FAQ schema in Webflow in 2026?

Usually no, if your only goal was rich results in Google. Google dropped FAQ rich results from Search on May 7, 2026, so the star treatment that made FAQ schema popular is gone. There are still narrow reasons to add it, but the old payoff no longer exists, and you should know that before you spend an hour on it.

I get asked to add FAQ schema constantly, and my answer changed this year because Google changed the rules. Chasing a feature that no longer appears is exactly the kind of wasted effort I try to save clients from. So let me give you the honest state of play and the steps, if you still decide it fits.

Here is what actually happened and what I would do now.

What is FAQ schema, and what changed?

FAQ schema is structured data, written in a format called JSON-LD, that labels a list of questions and answers on a page. It uses the FAQPage type from schema.org so search engines can read your questions and answers as clean, machine-readable data instead of guessing from the layout.

For years, adding valid FAQPage markup could earn you an expandable FAQ block right in Google's results, which took up more space and pushed competitors down. That visual reward is why so many people, including me, added it to service and pricing pages. It was one of the highest-value schema types you could ship.

What changed is that Google removed the reward. The markup format still exists and is still valid. Google just stopped turning it into anything you can see in Search, which flips the whole cost-benefit math on its head.

Did Google really drop FAQ rich results?

Yes, and Google announced it plainly. According to Google Search Central, FAQ rich results stopped appearing in Google Search as of May 7, 2026. This finished a rollback that started back in 2023, when Google first limited FAQ rich results to well-known, authoritative government and health sites.

Google is also removing the supporting tools. Per its own documentation, the FAQ search appearance, the rich result report in Search Console, and support in the Rich Results Test are being dropped in June 2026, and support for the FAQ rich result in the Search Console API is being removed in August 2026. That is a full retirement, not a quiet tweak.

So if a tutorial or agency still promises you FAQ rich snippets in Google today, they are working from old information. The feature is gone for everyone, and no amount of perfect markup brings it back.

So is FAQ schema worth adding at all now?

Only for reasons beyond Google rich results. Valid FAQPage markup does not hurt your site, and it still gives any machine reading your page a clean, labeled set of questions and answers. If you already have it, there is no urgent need to rip it out, since it does no harm.

The honest catch is that I cannot promise structured data alone earns you citations in AI answer engines. That link is not something Google or the AI vendors have confirmed, so I treat it as unproven rather than a selling point. What I do trust is the underlying habit: writing clear questions and direct answers is good for readers and good for any engine parsing your page.

My rule now is simple. Do not add FAQ schema chasing a Google feature that no longer exists. Add clear question-and-answer content because it genuinely helps people, and treat the markup as a small, optional extra rather than the goal.

How do you add FAQ schema in Webflow, step by step?

The method is the same as any custom structured data in Webflow. You write the JSON-LD by hand and drop it into an Embed element on the page. Webflow does not generate FAQPage markup for you, so this is a copy, edit, and paste job that takes about ten minutes once you have done it once.

Start by writing your real questions and answers as normal text on the page, inside your CMS or a rich text block, so visitors actually see them. Then open the Webflow Designer, drag an Embed element onto that same page, and inside it write a script tag whose type is the JSON-LD content type. Fill it with a FAQPage object whose mainEntity is your list of Question items, each holding a Question name and an acceptedAnswer with the answer text.

Match every question and answer in the markup to the exact wording shown on the page, then publish. That mirror between visible content and markup is not optional, and it is the rule most people break. I walk through the same embed technique for another type in my Webflow event schema JSON-LD tutorial, and the mechanics carry straight over.

How do you match the markup to visible content?

Every question and answer in your JSON-LD must appear as real, visible text on the same page. Google's structured data guidelines have always required that the marked-up content be present for the user, not hidden or invented for the crawler. Break that rule and you risk a manual action, not a reward.

In Webflow, the cleanest way is to bind both the visible FAQ and the schema to the same CMS fields, so they can never drift apart. When an editor updates an answer, both the on-page text and the markup update together. If you hand-code the JSON-LD in an Embed instead, you have to remember to edit it every time the copy changes, which people forget.

This matching discipline matters more than the schema itself. Clean, honest structure is the whole point. If your markup describes questions a visitor cannot find on the page, you have built a liability, not an asset.

How do you check your FAQ schema now that the tools are going away?

Lean on schema.org and general validators, not the FAQ-specific report. Since Google is removing the FAQ rich result report and its Rich Results Test support in June 2026, the old habit of pasting a URL into the Rich Results Test to confirm your FAQ no longer applies to this type. You need a different check.

Use the schema.org validator or a generic JSON-LD linter to confirm your syntax is valid and your types are correct. That tells you the markup is well-formed, which is all you can meaningfully verify now that the visible feature is gone. It will not show you a preview, because there is no preview left to show.

While you are auditing, check the rest of your structured data too, since broken schema elsewhere can cause real problems. I wrote a full guide on how to audit structured data errors in Webflow that covers the types still worth getting right.

What should you use instead for AI search?

Spend the effort on clear answers and the schema types that still earn features. Article, Product, Breadcrumb, and Organization markup still power real results, and plain, well-written answers still help you show up in AI engines like ChatGPT, Perplexity, and Google's AI experiences. The content beats the markup every time.

My whole approach to answer engine optimization is to write the way people ask and answer the way they want, then support it with the structured data that Google still rewards. I laid out that playbook in my guide on how to get cited by ChatGPT, Perplexity, and Google AI, and none of it depends on a feature Google just retired.

The lesson from the FAQ rollback is bigger than FAQ. Never build your strategy on one search feature, because platforms remove features. Build it on being genuinely clear and useful, which no algorithm change can take away.

What should you do next?

Audit where you already use FAQ schema and stop adding it for Google rich results, because they are gone. Keep your clear question-and-answer content, since that still serves readers and AI engines, and move your schema effort to types that still earn visible features.

I help clients cut work that no longer pays off and double down on what still ranks and gets cited. If you want a quick review of your structured data and where your effort should actually go in 2026, reach out through pravinkumar.co and let us take a look together.