Does the FAQ schema work if the answers are hidden in an accordion?

Why does Google require the visibility of FAQ questions?

John Mueller's position clarifies a sensitive point: Google does not require the answers to be expanded by default. The FAQ schema remains eligible for rich snippets even if the answers only appear on click — the essential factor is that the questions themselves are displayed immediately upon page load.

This requirement fits into Google's broader policy against hidden content. If the entire FAQ block is hidden (behind a tab, a "See more" button, or a collapsed section by default), Google considers that there is no visible value for the user — and therefore no legitimacy to display a rich snippet in the SERP.

What’s the difference between an accordion and completely hidden content?

A classic FAQ accordion always displays the questions. The user sees "What is the delivery time?", "How to return a product?" — and clicks to reveal the answer. This pattern is explicitly validated by Mueller: the questions are visible, the content is accessible with one click, thus the schema remains compliant.

Conversely, hiding the entire FAQ module — for instance under a "Frequently Asked Questions" tab that only opens upon interaction — would mean hiding both the questions and answers. Google cannot guarantee that the user will see this content, so the schema loses its relevance. Let's be honest: if you hide everything, you are trying to manipulate rich snippets without providing visible value — and Google knows it.

Do crawlers detect accordion content differently?

Googlebot interprets client-side JavaScript and renders pages like a modern browser. An accordion implemented in pure CSS (with :target or :checked) or in JS is analyzed without issue: the bot sees the visible questions, identifies the FAQPage schema markup, and associates each Question with its acceptedAnswer even if it is hidden by default.

The problem arises when the content is never loaded into the initial DOM — for example, if answers are called via AJAX on click. In this case, Googlebot may miss the answer text if the event listener is not triggered during the crawl. However, for a standard accordion where the answers exist in the HTML (simply hidden with CSS or aria-expanded="false"), there is no risk of non-indexation.

• FAQ questions must be visible upon page load — this is Google's only strict criterion.
• Answers can be in an accordion (expandable on click) without negatively impacting eligibility for the FAQ schema.
• Hiding the entire FAQ block (questions + answers) behind a tab or a button poses a problem and risks invalidating the schema.
• Modern crawlers (Googlebot) handle JavaScript and identify accordion content without difficulty as long as the HTML is present in the DOM.
• The FAQ schema JSON-LD must point to genuinely accessible content — not to permanently hidden elements.

Is this statement consistent with field observations?

Yes — and it is indeed one of the few positions from Google that is perfectly aligned with practice. Sites that use FAQ accordions retain their rich snippets in SERPs, provided the questions are displayed. I have tested dozens of pages with FAQ schema + CSS accordion: no loss of snippet as long as the <h3> or <dt> of the questions remain visible.

On the other hand, hiding the entire FAQ module behind a "Show Questions" button often leads to a removal of the rich snippet within 2-4 weeks after deployment. Google does not always report the error in Search Console — the snippet simply disappears. This aligns with Mueller's position: no visibility, no snippet.

What nuances should be made to this rule?

Mueller does not specify if Google analyzes the visible portion above the fold or if a FAQ at the bottom of the page is sufficient. [To be verified] on very long pages: if the FAQ only appears after 5 scroll depths, does Google consider it "visible"? Field experience suggests yes — as long as the HTML is loaded from the start, vertical position matters little. But no official data settles this point.

Another gray area: FAQs embedded in tabs ("Delivery", "Returns", "Warranty"). If the default tab contains a visible FAQ, is the schema for that tab valid? And what about FAQs in inactive tabs upon loading? Google says nothing. Practice shows that only the content of the first active tab generates rich snippets — other FAQs are often ignored.

In what cases does this rule not apply or pose problems?

E-commerce sites with product FAQs must choose between mobile UX (accordion to save space) and desktop readability (expanded answers). Mueller's statement validates the accordion but does not address the click-through rate of rich snippets based on the displayed format. Does a FAQ snippet with 6 visible questions perform better than a FAQ snippet with 3 questions + expanded answers? No public data.

Also be cautious of dynamically generated FAQs (for example, displayed based on geolocation or user history). If the FAQ does not exist in the DOM when Googlebot crawls, the schema will not be interpreted — even if the questions appear for a real user. In this case, ensure server-side rendering (SSR) or pre-rendering for bots.

What should be done to comply with this rule?

Ensure that FAQ questions are present in the HTML upon page load — not injected by asynchronous JavaScript. If you are using React, Vue, or a modern framework, ensure server-side rendering (SSR) or pre-rendering for bots. The <h3>, <dt> or <div class="question"> tags must be visible, even if the answers are hidden in CSS by display:none or aria-expanded="false".

Implement the FAQ schema JSON-LD by pointing each Question to the visible question text and each acceptedAnswer to the answer content (even if it is in an accordion). Use Google's Rich Results Test to validate the markup — but do not blindly rely on the "Valid" status, test in real SERPs.

What mistakes should be absolutely avoided?

Never place the entire FAQ block in a display:none or visibility:hidden element upon loading. Even if you display it later via JS on scroll, Google may crawl the page before the event is triggered — result: no visible FAQ content, schema ignored.

Also avoid duplicating FAQs across dozens of pages with the same schema. Google can detect duplicate content and may choose to display the rich snippet only on one URL — often not the one you want. Each FAQ must be unique and contextual to the page.

How to check if my implementation is compliant?

Use the URL Inspection tool in Search Console to analyze how your page renders as Googlebot sees it. If the FAQ questions appear in the rendered HTML, you are compliant. Otherwise, it means your JS is not executing correctly for the bot — or that the content is loading too late.

Monitor your rich snippet impressions in Search Console ("Rich Results" filter). If you have a valid FAQ schema but no rich snippet impressions after 2-3 weeks, it’s likely that Google judges the content as hidden or irrelevant. Test in incognito mode on mobile and desktop to see if the snippet displays in the SERP.

• Ensure FAQ questions are visible in the DOM upon page load (not injected later).
• Implement the FAQ schema JSON-LD by pointing to the actual questions and answers on the page.
• Use a CSS or JS accordion for the answers (acceptable), but never for the questions themselves.
• Test the rendering with URL Inspection in Search Console to validate that Googlebot sees the questions.
• Monitor rich snippet impressions in real SERPs — schema validation does not guarantee snippet display.
• Avoid duplicating the same FAQs across dozens of pages — Google may ignore multiple occurrences.