Is the hidden content behind an accordion or tab really taken into account by Google?

Why can't Google 'click' on interactive elements?

Googlebot operates like a headless browser: it loads the HTML, executes the JavaScript, but simulates no user actions. No scrolling, no hovering, and especially no clicking a button to reveal hidden content.

If your content is hidden by default — in a closed accordion, an inactive tab, or behind a 'See more' button — Googlebot technically sees this content in the DOM. It indexes it. But it does not know that this content is meant to be 'discovered' by a user click. To it, it's secondary content by default.

What's the difference between 'ignored' and 'weighted differently'?

Google does not say that hidden content is invisible. It says it can be considered less important. A crucial nuance. This means that this content counts for indexing, it may even contribute to the semantic understanding of the page, but it probably weighs less in the relevance calculation for a given keyword.

If you put your FAQ answers in closed accordions, they will be indexed — but their ranking weight will be lower than that of content visible right from the loading. The risk? Losing positions on specific long-tail queries that match this hidden content.

How does Google determine if content is 'visible by default'?

Google looks at the initial rendered DOM after executing JavaScript. If an element has a display:none, visibility:hidden, or height:0 when loading, it is considered not visible. The hidden or aria-hidden="true" attributes also play a role.

What complicates things: some JS frameworks load all visible content in the DOM, then hide it via CSS. Google then sees the content, but detects that it is not displayed to the user by default. Thus the reduced weighting.

• Content visible at loading: maximum SEO weight, strong relevance signal.
• Content hidden by default: indexed, but weighted as secondary, risk of semantic dilution.
• Content loaded in lazy-load: if visible in the initial viewport, treated as main content; otherwise, same logic as hidden content.
• Accordions and tabs: non-active content by default incurs a weighting penalty, even if it remains technically indexable.
• Popups and modals: if they only display after user interaction, their content is considered tertiary by Google.

Is this statement consistent with field observations?

Yes, and it’s even a strong signal that confirms what many have suspected. For years, SEOs have seen that pages with content visible 'above the fold' perform better than those hiding everything in accordions. But Google remained vague on the subject, leading to the belief that 'as long as it's in the DOM, it's OK'.

Now the line is clear: visible by default = maximum weight. Hidden by default = reduced weighting. This explains why some content-rich FAQs do not rank on their specific keywords: they are indexed, but Google does not assign them the same weight as directly displayed content.

What nuances should be added to this rule?

First point: this weighting is not binary. It's not '100% weight if visible, 0% if hidden'. It’s a continuum. Hidden content in an accordion counts more than absent content, but less than displayed content.

Second nuance: [To be verified] — Google provides no figures. It is unknown whether it's a reduction of 10%, 50%, or variable depending on context. The A/B tests I’ve conducted show varying impacts depending on the type of page: on a product page, moving specs from an accordion to a visible display resulted in a +15% increase in organic traffic on specific technical queries. On other sites, the impact was negligible. This likely depends on the competition on the query and the semantic richness of the rest of the page.

In what cases might this rule not necessarily apply?

On mobile, accordions are almost a UX necessity. Google knows this. It is likely that the algorithm applies different logic on mobile: hidden content for ergonomic necessity should not be penalized the same way as content hidden to stuff a page with keywords.

But beware — [To be verified] — Google has never officially confirmed this mobile nuance. It’s a reasonable assumption but not a certainty. If you are optimizing for mobile-first index, it’s wise to test versions with visible content and measure the real impact.

What should you concretely do with existing accordions and tabs?

First step: audit your strategic pages. Identify those that hide important content behind accordions or tabs. Ask yourself: does this hidden content contain keywords I want to rank for? If yes, you likely have a problem.

Next, test a version where this content is visible by default. You can style it with a 'Read less' option to avoid degrading the UX. Monitor positions and traffic on targeted queries. If you gain, it means the reduced weighting was costing you ranking.

What mistakes should you absolutely avoid?

Classic mistake: thinking that because Google 'indexes' hidden content, everything is fine. No. Indexing ≠ weighting. You can be indexed on 10,000 keywords and rank on none if all your content is hidden.

Another trap: using aggressive lazy-loads that load content only after interaction. If this content is not in the initial DOM, Googlebot doesn't even see it. Result: zero indexing, zero weighting. It's worse than hiding it in an accordion.

How to check that my site meets Google's expectations?

Use the URL inspection tool in Search Console. Look at the version rendered by Google: is all the content you consider strategic visible by default? If not, it's a red flag.

Supplement with a JavaScript rendering test (tools like Screaming Frog or Oncrawl). Compare the initial DOM and the DOM after user interaction. If content blocks only appear after a click, you know they are undervalued.

• Audit pages with accordions/tabs targeting strategic keywords
• Test a version with content visible by default and measure the impact on organic traffic
• Check the Googlebot rendering via Search Console (URL inspection tool)
• Avoid lazy-loads that prevent content from being in the initial DOM
• Prioritize the visible display of strategic content, even if it means adding a 'Reduce' button for UX
• Analyze server logs to identify pages where Googlebot loads only a partial DOM