FAQ Schema Just Got Restricted — Here's What Still Qualifies

For a few years, FAQPage schema was close to a free lunch. Bolt an accordion onto the bottom of any landing page, mark it up, and Google would sometimes hand you extra real estate in the SERP — expandable snippets stacked under your blue link, pushing competitors further down the page. It cost almost nothing to implement and the downside was basically zero. So agencies added it everywhere, on every template, whether the FAQ was three lines of genuine substance or five throwaway questions written purely to have something to mark up.

That era is over. Google has tightened FAQ rich results to pages where the FAQ is actually the primary content of the page — not a courtesy section stapled onto a service page, a product page, or a homepage. The practical result was a sharp drop in FAQ rich-result impressions across the board once the change rolled out, reported by digitalapplied.com in March 2026. If your FAQ markup was living on pages built around something else — a service description, a product listing, a pricing table — it likely stopped earning anything the moment the update landed.

What “primary content” actually means

The distinction Google is drawing isn’t subtle once you look at it from their side. A page qualifies when the FAQ is the page: a dedicated FAQ page, a support article structured entirely as question-and-answer, a policy page where every section is a question someone would type into a search bar. It doesn’t qualify when the FAQ is decoration — three or four questions tacked onto the bottom of a landing page that’s really about a product, a service, or a pitch, added mainly because someone once read that FAQ schema helps rankings.

The tell is usually obvious if you’re honest about it: does the page exist because of the FAQ, or does the FAQ exist because the page needed to feel more complete? If it’s the second one, that markup was never going to survive a tightening like this, and it probably shouldn’t have been added in the first place.

The markup nobody notices until it stops working

Here’s the part that trips people up: FAQPage schema that no longer qualifies doesn’t throw an error. It doesn’t get flagged in Search Console as broken. It just quietly stops producing rich results, and because most sites never went back to check whether the accordion at the bottom of their pricing page was actually earning anything, nobody notices the schema is now inert. It sits there — extra JSON-LD, extra page weight, one more thing that has to stay in sync with content that changes — doing nothing.

That’s worse than useless. It’s not neutral; it’s a small tax on every page that carries it, for zero return. And unused schema that no longer matches Google’s current interpretation of what it’s for is exactly the kind of thing that looks sloppy in an audit — the digital equivalent of a filing cabinet nobody’s opened in three years.

How we handled this on our own site

We didn’t wait for this update to make the call, because the logic was already obvious before Google formalized it. Our homepage has a visual FAQ accordion — the kind of thing every SaaS and agency site runs, answering the handful of questions a first-time visitor is likely to have. There’s no FAQPage schema on it. The FAQ there is genuinely a supporting element on a page whose primary job is something else entirely: introducing what we do and moving people toward a service page. Marking it up as if it were the main event would have been exactly the kind of noise this update is now penalizing.

Our individual service pages — /services/full-cycle-seo, /services/seo-audit, and the rest — are a different case. Each one is built around a single service, and the FAQ section on those pages is doing real work: it’s answering the specific, substantive questions a buyer has about that service before they commit — scope, timeline, what’s included, what isn’t. That FAQ isn’t decoration bolted onto a generic template; it’s a meaningful part of what the page is for. Those pages carry FAQPage schema, and they still should.

The rule we’d apply to any client site is the same one that drove that split: ask what the page is fundamentally about, then decide whether the FAQ markup is describing the page’s actual purpose or just riding along on top of it.

What to actually do about it

Go through your site’s templates — not just individual URLs, templates — and separate them into two piles. Pages where the FAQ is genuinely the reason the page exists keep the schema. Pages where the FAQ is a nice-to-have addition on top of a landing page, a product page, or a service overview should lose the FAQPage markup, even if the visible accordion stays for users. The content can survive; the structured data claiming it’s the main event shouldn’t.

This isn’t a huge project, but it’s an easy one to never get around to, because the markup isn’t breaking anything visibly — it’s just sitting there, inert. An SEO Audit is where this kind of thing gets caught: a look through your templates for schema that’s stopped matching what the page is actually for, ours included. If you haven’t checked, it’s worth fifteen minutes to find out where you stand — SEO Audit.