Does Content Hidden in Tabs or Accordions Hurt SEO?
Updated 4 November 2026
Jump to section
No. Under mobile-first indexing, content inside tabs, accordions, and "read more" expanders is indexed, as long as it sits in the page's HTML. According to Google's John Mueller, it is not devalued for being collapsed. Google's own guidance names accordions and tabs as an acceptable mobile design. The rule Google stresses is equivalence: on a site with a separate mobile version, the mobile content must match the desktop version, because Google indexes the mobile page.
What does Google actually say?
Google explicitly permits tabs and accordions in its mobile-first indexing guidance. The document, last updated December 2025, tells site owners they can move content into these controls for a better mobile layout.
Its wording is direct. You can, it says, "have a different design on mobile to maximize user experience (for example, moving content into accordions or tabs)". The catch follows at once: "just make sure that the content is equivalent to the desktop site, since indexing on your site comes from the mobile site". That is the core rule (Google Search Central).
The instruction is about equivalence, not visibility. Google is telling you the collapsed layout is fine, provided the same content exists on the version it indexes.
The guide applies to sites with dynamic serving or separate mobile URLs. On a responsive site, Google notes the content is already the same on mobile and desktop.
Does hidden content get less ranking weight?
No, content behind a tab or accordion is not discounted for being collapsed. Google's John Mueller addressed this directly. He said Google will "take into account anything that's in the HTML", and that content visible to users "at some point" is "completely normal". That comes from a Google Search Central office-hours session, reported April 2020.
The key phrase is "in the HTML". Google reads the full page source, not just the part on screen when it loads. A visitor taps to reveal the rest; the crawler already had it.
Where did the myth come from?
The belief that hidden content is ignored dates from the desktop-indexing era, before mobile-first indexing became the default. Search Engine Roundtable reported in December 2014 that, according to Google's John Mueller, Google had always discounted content hidden in tabs on desktop pages.
Mobile-first indexing changed the logic. On a phone, tabs and accordions are a normal, sensible way to fit a long page onto a small screen, so penalizing them would punish good mobile design. The old advice simply outlived the index it was written for.
This is why old SEO articles still warn against tabs. They are describing a rule that Google retired years ago.
The rule that still matters
Content must be in the initial HTML, and the mobile version must not drop what desktop shows. Those are the two real risks, and neither is about the tab itself.
- Content injected only on click. If text loads through JavaScript only after a user taps, Google's mobile-first guidance says it won't load content that requires a click, swipe, or typing to appear. This is the same indexing risk as any JavaScript-rendered content.
- A thinner mobile version. If your mobile layout quietly omits sections the desktop page has, you break equivalence, and Google indexes the shorter mobile page.
| Common claim | The reality |
|---|---|
| Tabbed content is ignored | Indexed, and not devalued for being collapsed |
| Accordions demote content | No demotion under mobile-first indexing |
| Hide weak content to rank better | No benefit; equivalence is what counts |
Tabs and accordions are good responsive design for long product and service pages, and they cost nothing in Search when the text ships in the HTML. In our experience, owners who lose rankings often suspect a design choice like this one, but we've more often traced ranking drops to slow or neglected sites.
An FAQ accordion raises one more question, about markup rather than layout. Google removed the FAQ rich result on 7 May 2026, so FAQ schema no longer earns a rich result. The visible FAQ content still helps readers and AI answer engines.
Frequently asked questions
Should I avoid tabs and accordions for SEO?
No. Tabs and accordions are an accepted, Google-endorsed way to organize a long page, especially on mobile. They do not reduce ranking weight as long as the content is in the HTML and matches the desktop version. Use them where they genuinely help readers, such as product specifications or a long FAQ.
Does a "read more" truncation hurt rankings?
No, provided the full text is in the page's HTML and only visually collapsed. A "read more" that hides existing text behind a click is fine. A "read more" that fetches the rest of the article from the server only when clicked is the risky kind, because the crawler may not trigger that fetch.
What if my tab content only loads when clicked?
That is the real problem to check. If the content is pulled in by JavaScript on click and is absent from the initial page source, Google won't load it, according to its mobile-first guidance. View the raw HTML, or use the URL Inspection tool in Search Console, to confirm the text is present before any interaction.
Do I need the same content on mobile and desktop?
Yes, and this is the rule Google's mobile-first guidance repeats. Because it indexes the mobile version, any content that exists only on desktop can effectively vanish from Search. Keep the mobile page equivalent, even if the layout differs, so nothing important is missing from the version Google reads.
Is hidden text in accordions the same as cloaking?
No. Cloaking shows Google different content from what users see, which breaks Google's spam policies. Unlike cloaking, an accordion shows the same content to both; the user just taps to expand it. Because the text is identical for crawler and visitor, there is no deception and no policy problem. Google's spam policies list "accordion or tabbed content that toggle between hiding and showing additional content" among design elements that do not violate them.
Making tabs work for both readers and search
Storming Solutions builds custom-coded websites and runs SEO, AEO, and GEO for Malaysian businesses from Kuala Lumpur. Our honest view is that every word should ship in the HTML first and be collapsed for layout second, never the other way around.
Worried your tabbed content is not being indexed? Send us the page on WhatsApp or through our contact page, and we will tell you what to check in the raw HTML.