TL;DR
FAQ accordions on product pages suffer double deprioritization: FAQ content is already treated as supplementary, and hiding it behind click-to-expand compounds the effect. The same FAQ content on a dedicated FAQ page in accordions performs better because Google understands the page’s purpose. If you’re targeting long-tail queries with product page FAQ accordions, Google may index the content but weight it too low to rank.
The Conversation
Megan, content manager at a SaaS company, 200 blog posts, HubSpot CMS, intermediate SEO knowledge, accordion FAQs not generating traffic: We added FAQ accordions to all our product pages with really detailed answers targeting long-tail keywords. Six months later, none of those questions appear in search results. The content is there but it’s like Google doesn’t see it.
SDC SEO Brain: Google can see it, but it might not be giving it full ranking weight. Check if the content is indexed first. In Search Console, use URL Inspection on one of those pages and view the rendered HTML. Search for some of your FAQ text in that HTML.
Megan: Let me check… yes, the FAQ content is in the rendered HTML. Google definitely sees it.
SDC SEO Brain: So the content is indexed. The question is why it isn’t ranking. How are your accordions implemented? Pure CSS toggle, JavaScript, or specific library?
Megan: They’re JavaScript. Click to expand, click to collapse. Standard accordion pattern.
SDC SEO Brain: That’s actually fine for indexing. The issue is likely Google’s content weighting, not visibility. Google has historically given less ranking weight to content that requires user interaction to view. The rationale is that if you’re hiding content, it might be less central to the page’s purpose.
But here’s a nuance specific to FAQ accordions: Google treats FAQ content differently depending on context. An FAQ on a product page is supplementary. An FAQ on a dedicated FAQ page is the primary content. Same accordion, different weighting. Where are these accordions located?
Megan: On our product pages. Each product has an FAQ section with 5-10 questions.
SDC SEO Brain: That’s the worst-case scenario for accordion SEO. Product page FAQs are already considered supplementary, and then you’re hiding them behind interaction. Double deprioritization. A standalone FAQ page with the same content in accordions would fare better because Google understands FAQ as the page’s purpose.
Megan: But FAQs make sense as accordions on product pages. Nobody wants a wall of text.
SDC SEO Brain: From a UX perspective, you’re right. Accordions are good design for FAQs. But SEO and UX don’t always align. Google’s algorithm developed when hiding content was often used for keyword stuffing. The association between hidden content and lower quality persists, even when the hiding is legitimate.
Megan: Has Google said this explicitly?
SDC SEO Brain: Google’s John Mueller has addressed this in various ways over the years. The messaging has evolved from “hidden content may not be fully indexed” to “we can index it but may not give it as much weight.” It’s not a penalty, more like a reduced emphasis. But here’s what’s important: this is observed correlation, not confirmed mechanism. We see accordion content underperform visible content consistently. Google’s statements suggest why, but they haven’t published a weighting formula. The evidence is circumstantial but strong across thousands of sites.
Megan: So the content is indexed but treated as secondary?
SDC SEO Brain: That’s the likely explanation. Your main page content, visible immediately, gets full ranking weight. Your accordion content, requiring interaction to view, gets partial weight. For long-tail queries that match your FAQ content specifically, that partial weight might not be enough to rank when competitors have that content visible.
Megan: How do I know for sure this is the problem?
SDC SEO Brain: Compare performance. Pick a long-tail query you’re targeting in accordion content. Search for it. Look at the top results. Is their equivalent content in accordions, or is it visible? If competitors have similar content visible and ranking while your accordion content isn’t, that’s your answer.
Megan: I just checked one. Our competitors have FAQs but they’re just paragraphs with headers. No accordions. They rank; we don’t.
SDC SEO Brain: There’s your evidence. Same content, different presentation, different rankings. The competitors’ visible FAQs get full weight; your accordion FAQs get reduced weight. The content quality might be identical, but the presentation affects ranking.
Megan: Should we get rid of accordions entirely?
SDC SEO Brain: Not necessarily. There are middle-ground approaches. First, consider keeping the most important FAQ items expanded by default. The first 2-3 questions that target your primary long-tail keywords stay visible; the rest can collapse. Google sees the key content immediately.
Megan: So partially expanded?
SDC SEO Brain: Exactly. Or you can implement a hybrid: show full text content on page load, then initialize JavaScript to collapse them after render. Googlebot typically captures the initial render. If content is visible at render time before JavaScript collapses it, Google sees it as visible content.
Megan: That sounds complicated. Does it actually work?
SDC SEO Brain: It can work, but it’s fragile. Google’s rendering has improved and might capture the JavaScript-collapsed state. The cleaner solution is designing around the constraint. If FAQ content is important for SEO, keep critical answers visible. Use accordions for supplementary information that doesn’t need to rank.
Megan: What about FAQ schema? We have that implemented. Doesn’t that help?
SDC SEO Brain: FAQ schema can get you rich results in SERPs, the expandable FAQ snippets under your listing. But schema doesn’t affect regular organic ranking of the content. Your FAQ schema might appear in rich results while the underlying content still doesn’t rank for long-tail queries. They’re separate things.
Megan: So schema doesn’t overcome the accordion weighting issue?
SDC SEO Brain: Correct. Schema tells Google how to display information in rich results. It doesn’t tell Google to give hidden content more ranking weight. You could have beautiful FAQ rich results appearing when someone searches your brand name, while those same FAQ questions never rank organically for the actual questions.
Megan: This is frustrating. We spent a lot of time on these FAQs.
SDC SEO Brain: The content work isn’t wasted. Restructure the presentation and the same content can rank. Move your highest-value FAQ content to visible sections. Keep accordions for less critical questions. The investment in writing good answers pays off once Google can give that content proper weight.
Megan: What about mobile? Don’t accordions make more sense on mobile?
SDC SEO Brain: They do for user experience. But Google uses mobile-first indexing, meaning the mobile version of your site is what Google primarily sees. If your mobile site has content in accordions that your desktop site shows visible, Google sees the accordion version. Mobile-first makes this even more important to address.
Megan: Our mobile and desktop are the same. Responsive design.
SDC SEO Brain: Then whatever Google sees on mobile is what counts for indexing. If accordions are collapsed on mobile, that’s how Google experiences your content. The same accordion weighting issues apply regardless of which device view Google uses.
FAQ
Q: Can Google index content inside accordions and tabs?
A: Yes. Google renders JavaScript and can see content in accordions, tabs, and other collapsible elements. The issue isn’t indexation but ranking weight. Content requiring interaction to view may receive less ranking emphasis than immediately visible content.
Q: Does FAQ schema help accordion content rank better?
A: No. FAQ schema affects rich result display in search results, not organic ranking weight. You can have FAQ rich results showing while the underlying content still doesn’t rank for long-tail queries. Schema and ranking weight are separate mechanisms.
Q: Should I remove all accordions from my site?
A: Not necessarily. Accordions serve legitimate UX purposes. The solution is strategic: keep high-value SEO content visible, use accordions for supplementary content that doesn’t need to rank. Or expand key accordion items by default so Google sees them as visible.
Q: What’s the best way to make FAQ content rank for long-tail queries?
A: Make the content immediately visible without requiring interaction. Format FAQs as regular paragraphs with headers instead of accordions. Or expand the most important FAQ items by default. Google gives full ranking weight to content that’s visible on page load.
Summary
Google can index accordion and tabbed content, but historically gives less ranking weight to content requiring user interaction to view. This affects whether that content ranks for long-tail queries, not whether it’s indexed.
The solution isn’t eliminating accordions entirely but strategic presentation: keep high-value SEO content visible, use accordions for supplementary information that doesn’t need to rank independently.
FAQ schema affects rich results display, not ranking weight. You can have FAQ rich results while the underlying content fails to rank organically for the questions themselves.
Mobile-first indexing means Google sees your mobile presentation. If accordions are collapsed on mobile, that’s how Google evaluates your content regardless of desktop presentation.
Compare competitor presentation when diagnosing accordion ranking issues. If competitors rank with visible FAQs while your accordion FAQs don’t rank, presentation difference is likely the cause.
Sources
- Google Search Central: FAQ structured data
- Google Search Central: Mobile-first indexing