How does Google actually treat hidden content in tabs or click-to-expand?

What Google used to say about hidden content

Back in 2014 and 2015, Google's guidance was cautious and a bit contradictory. John Mueller said hidden content "may not" get indexed or ranked the same way as visible text. Gary Illyes later added that this kind of content would carry less weight in rankings. Between the two, most SEOs walked away thinking that anything tucked behind a click was a liability.

That advice aged badly, mostly because mobile design moved on. Once phones became the primary way people browsed the web, hiding secondary content behind a tap stopped being a workaround and became standard practice. Google's position had to catch up with that shift.

What changed in Google's approach to hidden content

The turning point came with mobile-first indexing. In 2016, Gary Illyes was asked directly on social media whether content hidden in things like accordions was devalued on mobile. His answer was blunt: no, in a mobile-first world, content hidden for user experience reasons should carry full weight.

John Mueller reinforced this during a Google Search Central office hours session in March 2020. Asked whether hidden content behind tabs and accordions would still be devalued because a user might never click to reveal it, he confirmed that Google takes into account anything present in the page's HTML, tabbed or not.

What Google's Current Documentation Says About Hidden Content

This isn't just office-hours chat anymore. Google's own spam policies page, last updated in May 2026, spells it out in black and white. It lists accordion and tabbed content that toggles between hiding and showing more detail as one of several dynamic design patterns that do not violate Google's policies on hidden text or links. Slideshows, tooltips, and content aimed at screen readers get the same pass.

So the framing has genuinely flipped. What was once treated as a grey area, tolerated at best, is now named explicitly as acceptable UX. You can read the current guidance yourself on the Google Search Central spam policies page.

A few things are still worth flagging:

• This protection only applies if the content actually exists in the page's HTML on load. If it's injected later via AJAX and never rendered for Google, that's a different problem, and one worth checking with your dev team.

• The distinction Google draws is about intent and mechanism. White text on a white background, text pushed off-screen with CSS, or font sizes set to zero are still treated as hidden text abuse. An accordion panel is not the same thing, even though both are technically "not visible" at first glance.

• Google still won't pull a hidden section into a search snippet by default. So a page might rank for a phrase buried in an FAQ accordion, but the snippet shown in results probably won't quote that section, which can affect click-through even if ranking itself is fine.

• One area Google hasn't spelled out in as much detail is content revealed purely through a :hover event, rather than a click. It's reasonable to assume this gets treated the same as a standard accordion, since the mechanism and intent are similar, but there's no explicit confirmation either way. Worth bearing in mind if a design leans heavily on hover states for anything important.

What this means for hidden content on your website

The core principle from the old advice still holds up reasonably well, even if the ranking risk has eased. Ask yourself:

• Would a visitor expect to see this the moment the page loads?

• Does it answer a key question about the page's main topic?

• Would hiding it get in the way of someone making a decision, like a purchase?

• Could it happily live on its own page instead, if it's genuinely secondary?

Take an e-commerce product page. Core product details, the kind that inform whether someone buys, should sit in view by default. Burying that in an accordion won't tank your rankings the way it might have a decade ago, but it can still cost you conversions if a shopper leaves before clicking to reveal it. Delivery information or a returns policy, on the other hand, is a reasonable candidate for a tab. It's useful, but it's not usually what someone came to the page to read first.

The short version: Google's position on hidden content today

Google's stance has moved from "we'll index it, but it counts for less" to something closer to "if it's genuinely in your HTML and used for good UX, we treat it like any other content." Mueller and Illyes have both said as much publicly, and Google's own documentation backs it up now rather than leaving it to guesswork.

That said, ranking eligibility isn't the same as good UX. Just because Google won't penalise an accordion doesn't mean it's always the right call to hide something a visitor is actively looking for. Treat each page on its own merits, and if you're not sure where a piece of content should sit, our technical SEO team is happy to take a look.