SEO & Marketing

FAQ Schema: Why Google's Rich Result Isn't Displayed

If you've placed the FAQ markup correctly but don't see a rich result in the SERP, the problem usually isn't the schema itself. Here you'll see the real conditions for display and the reasons for rejection.

SEO & Marketing

You've placed the FAQPage markup on the page, the Rich Results Test confirms "FAQ" with a green checkmark, but for two weeks now no accordion has been opening under your link in the search results. This is exactly where most teams start fiddling with the JSON-LD, while the problem lies elsewhere. Since 2023, FAQ schema is no longer a public key; Google has restricted it to a limited set of sites and, for everyone else, won't display a rich result even with flawless markup.

So the first thing you should do is distinguish between "valid markup" and "eligible for display." These two are not the same, and Google's testing tool only tells you about the former.

Why FAQ schema gets validated but you see nothing in the SERP

In its own documentation, Google states plainly that it displays FAQPage and HowTo broadly only for "authoritative government and health sites." That means an online store or a corporate blog can have perfectly correct markup and still get no rich result. This limitation is a product policy, not a bug. As long as your page isn't in that limited category, further optimizing the JSON-LD is just a waste of time.

The diagnostic sign is simple: open the "Enhancements" section in Search Console. If the FAQ item isn't there at all but the Rich Results Test validates the markup, it means Google has seen the markup and deliberately chosen not to display it. If the FAQ item is there but has errors, the problem is technical and must be fixed.

The difference between a technical error and a policy rejection

A technical error shows itself like this: the number of "Invalid items" rises in Search Console and you get a specific message such as Missing field "acceptedAnswer" or Missing field "text". A policy rejection has no message; it's just silence. If more than four to six weeks have passed since the page was indexed and you see no change in display, assume it's policy.

Content that is actually eligible

Even on sites that Google permits to display, FAQ content must meet conditions that many overlook. The question must genuinely be a question, not a marketing headline with a question mark slapped on. "Why is site speed important?" is a question; "The best hosting in Iran!" is not, and if it's marked up as a question, the likelihood of a manual penalty is higher than that of display.

  • The answer must appear directly beneath that same question in the visible page. Hidden content with display:none that only appears in the JSON-LD is a violation.
  • Each question and answer must be unique. Repeating the same FAQ across ten different pages with different URLs is a negative signal.
  • The answer should be short. Multi-paragraph answers with numerous internal links get truncated in the display and destroy the click value.
  • The page must be a real page with standalone content, not an FAQ aggregation page for the whole site.

A technical point that's less often seen: if you use a content management system that renders the FAQ as a JavaScript widget after load, make sure the JSON-LD is in the initial HTML. Google does render JavaScript, but a delay in rendering means a delay in discovering the markup. With curl -s https://example.com/page | grep -c FAQPage you can quickly check whether the markup is in the server response or not.

How to write correct markup

The basic structure is fixed and doesn't need a heavy library. One JSON-LD block in the <head> is enough:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Is FAQ schema displayed in Google results?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Only for eligible sites; valid markup is a necessary condition but not sufficient."
    }
  }]
}
</script>

Three common mistakes in this same small block:

  1. Using "@type": "Answer" without the text field and putting the text in the wrong field. Result: the Missing field "text" error.
  2. Placing several separate FAQPage blocks on one page. There should be one FAQPage with a mainEntity array.
  3. Forgetting @context in the second block when you merge two schema types (e.g., Organization and FAQPage) into one script.

After every change, validate with SEO and webmaster tools or Google's Rich Results Test. If you have a structural error, close it before doing anything else; incomplete markup is worse than none because it creates a signal of untrustworthiness.

This is where they go wrong

The error I've seen most: the SEO team adds the markup to the page, it turns green in the test, and then because no rich result appears, they start adding more FAQs, changing the question text, and even duplicating the markup on other pages. Three months later the site has hundreds of duplicate FAQ blocks and no rich result, and in the worst case a "Spammy Structured Markup" manual action in Search Console. The sign is this: in the "Manual actions" section there's a red message saying your site's structured data doesn't match the page content. At that point you have to remove all the markup, not fix it.

So what actually works

If your site isn't in Google's restricted category, spend your time on something with a more guaranteed outcome. Keep the FAQ schema because it costs nothing and maybe one day the policy will change, but don't expect display. Instead, focus on things that work independently of Google's policy: real page speed, heading structure, and content that answers a real user question.

A practical alternative: instead of FAQPage, use Article and BreadcrumbList. These two are essentially open to everyone and show the page path in the SERP. For product pages, Product with offers and aggregateRating (if you genuinely have reviews) is far more effective than FAQ.

Schema typeDisplay for everyoneMaintenance costRecommendation
FAQPageNo, restrictedMediumKeep it, don't expect display
ArticleYesLowTop priority for the blog
BreadcrumbListYesLowAlways enabled
Product + offersYesHigh (in sync with inventory)Only if you have accurate data
HowToNo, restrictedMediumLike FAQ, keep it but don't expect

The real cost of this decision is this: if you keep the FAQ, every time the page content changes you must sync the markup too, otherwise you create the risk of a manual action. If you remove it entirely, on the day Google's policy opens up, you'll be behind your competitors. I prefer to keep it, provided the syncing is automatic rather than manual.

Technical check before any change

Before touching the markup, make sure the problem isn't elsewhere. If the page is served with a redirect chain or a wrong canonical, Google may index a different version and never see your markup at all. Use the domain and DNS technical check to check the status of records and redirects. If the site is hosted on a dedicated server or ServerNet's hosting service, you can start these checks right there.

To see what Google actually sees, use URL Inspection in Search Console and click "Test Live URL." If the FAQPage block isn't in the rendered HTML but was in the source, the problem is client-side rendering. If it wasn't in the source either, the problem is the template or the cache.

A practical point: after every change, wait at least 48 hours and then check the "Enhancements" section in Search Console. Structured data changes don't appear in reports immediately, and rushing only leads to a series of consecutive, fruitless changes.

Frequently asked questions

Does FAQ schema still work in Google?

FAQPage markup is still valid and won't produce a technical error, but its rich result is displayed only for eligible sites. Google has enforced this restriction since 2023, and for most commercial sites and corporate blogs, the FAQ rich result isn't displayed.

Why does the Rich Results Test validate my markup but I don't get a rich result?

The Rich Results Test only checks the structural validity of the JSON-LD, not policy eligibility. This tool's confirmation means the markup is technically correct, but the display decision is Google's and depends on your site's category.

Can I put FAQ schema on all pages of the site?

Yes, but only if each page has its own dedicated FAQ. Repeating one FAQ block across dozens of pages with identical content carries the risk of a "Spammy Structured Markup" manual action and, at best, is ineffective.

What's the alternative to FAQ schema for getting a rich result?

For articles, use Article and BreadcrumbList, which are essentially open to almost all sites. For product pages, Product with accurate offers and genuine aggregateRating is more effective than FAQ. These two work independently of Google's restrictive policy.

Next step: right now, open the "Enhancements" section in Search Console and see whether the FAQ item exists at all. If it doesn't, your problem isn't technical and you should spend your time somewhere better.

ServerNet Support

ServerNet engineering & editorial team — specialists in infrastructure, networking and web hosting.

SEO Services
Share:

Comments 0

No comments yet — be the first!

Leave a comment

Related service

SEO Services

SEO is not a cost, it's an investment. With technical SEO, content strategy and principled link building, ServerNet raises your ranking on Google and builds real, lasting organic traffic.