Do you really need to display all FAQ schema questions visibly on your page?

Why does Google require questions to be visible?

Google's position is clear: schema.org markup must reflect what the user actually sees. If you mark up a question in FAQ schema, it must be present in the visible DOM without requiring a click or interaction to display.

This rule is part of the fight against manipulative hidden content. Google has always been wary of techniques that involve marking up invisible content to trick the algorithm — and FAQ schema is no exception to this principle.

What's the difference between questions and answers in this directive?

That's where it gets interesting. Google makes a clear distinction: the question must be visible, but the answer can be hidden behind an accordion system or dropdown menu.

Concretely? You can structure your page with questions displayed permanently and answers that expand on click. It's even a common UX practice that doesn't conflict with Google's guidelines.

Does this rule apply to all types of FAQ?

Mueller's directive specifically targets pages that use FAQ schema markup to get rich snippets in the SERPs. If you have a FAQ section without structured markup, this constraint doesn't apply — but you also won't benefit from visibility advantages in the search results.

However, be careful: even without schema, completely hiding key questions in tabs or accordions closed by default can dilute their SEO weight. Google indexes hidden content, but values it less than immediately visible content.

• Questions marked up in FAQ schema must be displayed directly on the page
• The answer can be hidden in an accordion or dropdown menu
• This rule only concerns pages using schema.org FAQ markup
• Hidden content remains indexable but is valued less by Google

Is this requirement consistent with practices observed in the field?

Yes, and it's even applied quite strictly. We regularly observe removal of FAQ rich snippets on pages that hide questions in tabs or complex navigation systems.

Google likely uses automated detection that verifies the visible presence of marked-up text. If your question is in a `display:none` on page load, or requires a click to appear, you risk losing rich snippet eligibility — even if the technical markup is perfect.

What nuances should be applied to this directive?

Let's be honest: Mueller's wording leaves a gray area about what exactly constitutes "visible". A question that appears after light scrolling? A question in a lazy-loaded block? [To be verified] — Google has never provided precise guidelines on these edge cases.

Furthermore, this rule says nothing about the quality or relevance of the questions. We still see too many pages displaying artificial questions just to grab rich snippets, without providing real value. Google tolerates it for now, but it remains a risky practice long-term.

In what cases does this rule cause problems?

The main conflict arises with UX and mobile constraints. On mobile, displaying 15 expanded questions permanently creates an endless page. Designers naturally prefer accordions closed by default — which directly contradicts Google's directive.

Result? Many sites compromise by displaying questions but not answers, which remains compliant. But this sometimes creates awkward user experiences, with question lists that look like titles without context.

What should you do concretely to stay compliant?

First step: audit your existing FAQ pages. Review each page using FAQ schema and verify that questions are displayed in the viewport without requiring user interaction.

If you use accordions, make sure that the accordion title contains the marked-up question, and that it's visible on load. The answer can remain hidden until click — that's acceptable.

What errors should you avoid when implementing?

Never mark up a question that doesn't exist visually on the page. It seems obvious, but we still see sites automatically generating FAQ schema from content hidden in databases or CMS systems.

Also avoid multi-tab systems where questions are distributed across different tabs. Google generally considers that only the content of the first active tab is "visible" on load — the rest is treated as hidden.

How do you verify that your implementation is correct?

• Use Google's Rich Results Test to validate technical markup
• Inspect the page with Search Console and verify the version rendered by Googlebot
• Test in private browsing without JavaScript — if questions don't display, that's a red flag
• Verify that each marked-up question matches exactly the visible text on the page
• Monitor the appearance of rich snippets in the SERPs — their disappearance may signal a compliance issue