SEO by Subham

Posted on Sep 8 Originally published at dev.to

The FAQ Rich Result You're Chasing Doesn't Exist Anymore

#webdev #seo #json #javascript

If you added FAQ schema to a page hoping for those little question dropdowns under your Google listing, I have some old news for you. That feature is gone.

Not "harder to get." Not "restricted." Gone.

Google first cut back FAQ rich results in August 2023, keeping them mostly for big government and health sites. Then on May 7, 2026, Google removed FAQ rich results from Search completely. Every site. No exceptions.

A lot of SEO guides and plugin pages still haven't caught up on this. I kept seeing "FAQ schema shows extra answers in search results and boosts your click rate" written as if it's still true. It isn't. So before I wrote anything else, I wanted to figure out what FAQ schema actually does now, and if it's even worth using anymore.

Short answer: yes, but not for the reason most people still think.

What FAQ Schema Actually Is

FAQ schema is a small piece of code that tells search engines and other systems "this part of the page is a question, and this part right under it is the answer." It uses FAQPage, Question, and Answer from Schema.org, written as JSON-LD. It sits in your page's <head> and doesn't change anything visitors see.

Say your page shows this on screen:

How long does SEO take to show results?

SEO results depend on your website, your competition, content quality, technical health, and how established your site already is. Some small changes show up fast. Bigger, more competitive changes take longer.

The matching JSON-LD looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does SEO take to show results?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "SEO results depend on your website, your competition, content quality, technical health, and how established your site already is. Some small changes show up fast. Bigger, more competitive changes take longer."
      }
    }
  ]
}
</script>

Quick breakdown of what each part does:

@context tells the parser which vocabulary to use (Schema.org)
@type: FAQPage marks this page as having FAQ content
mainEntity is the list of questions
Each Question has a name (the question itself) and an acceptedAnswer (the Answer with the real text)

Writing this by hand for one question is fine. Do it for ten questions and it gets messy fast. Missed commas and mismatched brackets are the usual problem.

So Why Bother If the Rich Result Is Gone?

This is the part I had to actually think about instead of assuming.

Google has said more than once that structured data helps it understand a page, even after a specific visual feature built on top of that data gets dropped. The rich result was just how that understanding showed up on screen. The information underneath it, "these questions and answers actually go together on this page", is still useful.

And that matters more now than it did a few years ago. Search is moving toward AI summaries and answer tools that need to read and understand content, not just crawl it and rank it. Clean, clearly labeled Q&A helps with that. It's not a promise you'll get picked up anywhere. There's no code that buys you that. But clear structure removes guesswork, and guesswork is exactly what these systems struggle with.

So the honest reason to still use FAQ schema in 2026 is this: it makes your page easier for machines to read correctly. It's not a shortcut to a Google feature that doesn't exist anymore.

I Built a Free Generator, and Left Out Auto-Extraction on Purpose

Once I understood what FAQ schema is actually good for now, I built a small tool for it. You type in your questions and answers, watch a live preview update, then copy or download the finished code.

One thing I chose not to add: auto-extraction from your page. I thought about it and decided against it, for the same reason my last two tools stayed manual.

The most common way FAQ schema goes wrong is a mismatch. The code says one thing, the page shows another. A tool that guesses which headings are "questions" is a good way to create that mismatch without noticing. Typing in the exact questions and answers that are already on your page keeps things honest, since there's no guessing involved.

The tool handles the fiddly part, the brackets, quotes, and correct JSON-LD formatting. The part that actually matters, whether this matches your real page, is still on you.

The Mistake That Matters More Than Getting the Code Right

Perfectly formatted code can still describe something false.

The biggest mistake isn't a missing comma. It's adding schema for questions that aren't really visible and answered on the page, usually to stuff in more keywords. Google's own guidelines say structured data should match real, visible content. Fake or hidden FAQ schema isn't just risky, it also doesn't get you anything anymore, since the reward it used to chase is gone.

A smaller but common problem: duplicate schema. If your SEO plugin or theme already adds FAQPage markup, adding a second block by hand creates two conflicting pieces of code on the same page. Worth checking your page source before adding anything manually.

Where the Code Actually Goes

The generated <script type="application/ld+json"> block goes in the <head> of the same page that shows the FAQ, not a different page, and not a global template unless that FAQ is genuinely on every page.

A few notes depending on your platform:

WordPress: use your SEO plugin's custom schema field if it has one, or a trusted header tool. Don't paste raw JSON-LD into a normal text block, the visual editor can break it.
Shopify: add it through the theme template's <head> with Liquid, only on the specific page, not site-wide.
Wix: use the custom code option to add it to that page's head, and check first that Wix hasn't already added its own FAQ markup.
Plain HTML: drop the script tag straight into the <head>, with the FAQ still showing normally as regular text on the page.

Try It

If you have a page with a real FAQ section, the free FAQ Schema Generator turns it into clean FAQPage code with a live preview. No signup needed.

Just don't add it expecting a fancy snippet in Google Search. That's gone. Add it because it helps machines read your content correctly. That's a smaller win than before, but it's a real one.

If you've run into other SEO advice that's still stuck in the past, I'd like to hear about it. Drop it in the comments.

DEV Community