Free to explore: filter winning sites by DR, traffic and niche  ·  Try the live explorer →

Hidden content in tabs: does Google count it?

An accordion FAQ on a mobile phone

Hidden content SEO used to come with a firm rule: if users cannot see it on load, Google discounts it. Tabbed product descriptions, collapsed FAQs and “read more” sections were all thought to carry less weight than text on the open page. On mobile, where screen space forces designers to collapse almost everything, that rule stopped making sense, and Google said so.

There are two very different things called “hidden content”, though. One is a design pattern that helps users. The other is a spam technique. Treating them as the same leads to bad decisions in both directions.

What Google said about content in tabs

The clearest statements were collected by Barry Schwartz at Search Engine Roundtable on 1 May 2018, in a post on content hidden in tabs under mobile-first indexing. A summary of John Mueller’s comments at BrightonSEO put it tersely: “during mobile-first hidden content on site == okay (may change if abusing)”.

Tabbed product details

The same post quoted Google’s Aaseesh, who was more explicit: “Google’ll be treating content that’s hidden under, say a tab similar to content that’s seen on the first glance.” That is the position in plain terms. Text in a tab or accordion that a user can open is not second-class content.

Note the qualifier in Mueller’s version: “may change if abusing”. The tolerance is for genuine interface patterns, not a licence to stuff collapsed panels with text nobody is meant to read. The reasoning is tied to how Google now indexes pages, covered in our guide to mobile-first indexing: the mobile version is the one that counts, and mobile layouts collapse content as a matter of course.

Hidden content SEO: tabs versus hidden text

What is hidden text in SEO, then, if tabs are fine? It is text placed on a page so that search engines read it while users cannot: white text on a white background, text positioned off screen, a font size of zero, keyword blocks behind an element with no way to reveal them. Google’s spam policies treat this as “hidden text and link abuse”.

An expandable menu on mobile
PatternCan a user reveal it?Who is it for?How Google treats it
Product details in tabsYes, by tapping the tabUsersSimilar to content seen at first glance (Aaseesh, 2018)
FAQ answers in an accordionYes, by expanding the questionUsersOkay under mobile-first, per Mueller, unless abused
Text the same colour as the backgroundNoSearch engines“Hidden text and link abuse” under the spam policies
Keyword block positioned off screenNoSearch engines“Hidden text and link abuse” under the spam policies

The test is simple. If a user can reach the content through a normal interaction, and it is there because it helps them, it is a design choice. If no interaction will ever show it, and its only audience is a crawler, it is spam. Hidden text is usually a vehicle for keyword stuffing, and when the page shown to crawlers differs from the one shown to users in a more systematic way, it shades into cloaking.

How the code differs

Both patterns can use the same CSS, which is why crawlers and audit tools cannot judge intent from markup alone. A tab panel is often hidden with display: none until the user selects it:

Text hidden against its background

The abusive version looks different in one key respect: there is no control that reveals it.

The first is a working interface with a button, an ARIA relationship and useful text inside. The second exists only to be read by a machine. A reviewer looking at either page would tell them apart in seconds, and that is roughly the standard to hold yourself to.

Practical rules for tabs and accordions

Put the content in the HTML that loads with the page. A tab whose content is fetched only when clicked may never be seen by a crawler, which is a different problem from being hidden. Use real buttons with ARIA attributes so the panels are usable with a keyboard and a screen reader, not just with a mouse.

A mobile page layout

Keep the content that answers the main query visible. Google may treat tabbed text much like visible text, but a user who lands from search wants the answer straight away. If the core of the page sits behind three taps, the experience suffers even if the indexing does not. Tabs work best for secondary detail: specifications, delivery terms, reviews.

Check the mobile and desktop versions carry the same text. A common slip is a desktop page that shows a full description while the mobile template drops it altogether rather than collapsing it. Under mobile-first indexing, content missing from the mobile page is a far bigger risk than content sitting inside a closed tab.

FAQ accordions are a common case worth checking. Collapsed answers are fine, and they pair naturally with structured data, covered in our guide to FAQ schema. The markup and the visible answers should match, word for word ideally.

CSS that hides content

Auditing a site for hidden text

Most crawlers report elements with display: none or zero size, and most of what they flag will be ordinary interface: menus, modals, tab panels, cookie banners. Do not try to clear that report. Instead, sample the flagged elements and ask one question of each: is there a way for a user to see this, and would they want to?

The things worth fixing are text with no reveal control, text matching the background colour, legacy keyword blocks from an old theme, and links hidden in footers or behind single characters. These often arrive through templates, plugins or a previous agency, and the site owner may not know they are there.

A designer arranging a layout

One limitation applies. Google’s statements describe how it treats tabbed content in principle; they do not say whether expanded and collapsed text carry exactly equal weight in every case, and nobody outside Google can measure that. Aaseesh’s word was “similar”, not “identical”. If a piece of text is central to why the page should rank, the cautious choice is to show it on load rather than test the edge of the policy.

The practical position is straightforward. Use tabs and accordions where they help users, put the content in the initial HTML, keep the main answer visible, and remove anything hidden that no user could ever reach.

Frequently asked questions

Does Google index content hidden in tabs?

Yes. Google’s Aaseesh said in 2018 that content hidden under a tab is treated similar to content seen at first glance, as long as it is in the page and users can reveal it.

What is hidden text in SEO?

Text placed on a page for search engines but not users, such as white text on a white background or keywords positioned off screen. Google’s spam policies call it hidden text and link abuse.

Are accordions bad for SEO?

No. Collapsed content in an accordion is fine under mobile-first indexing, provided it loads with the page and users can expand it.

Should important content go in a tab?

Better not. Google may count it, but users arriving from search want the main answer immediately. Keep tabs for secondary detail.

The takeaway Content in tabs and accordions counts much like visible text, as long as users can open it and it loads with the page. Text that no user can ever reach is hidden text abuse. Keep the main answer visible either way.