Google Is Treating Your Tabs as Hidden Content

Whether Google treats your tabs as hidden content turns on one question first: whether the text is already in the page when it loads. Google’s spam policies list “accordion or tabbed content that toggle between hiding and showing additional content” among the design elements that don’t violate its policies. Its mobile-first guidance suggests moving content into accordions or tabs instead of removing it. The same guidance says Google won’t load content that requires a user interaction to load. A tab whose text is in the HTML is ordinary page content. A tab that fetches its text only when someone clicks it may hold content Google never sees.

What Google’s documentation says

Three statements carry the argument.

• Tabs are not hidden text abuse. Google’s spam policies define hidden text or link abuse as placing content on a page solely to manipulate search engines and not to be easily viewable by visitors. Their examples are white text on a white background, text behind an image, text positioned off-screen with CSS, and a font size or opacity of zero. The same section then says that many design elements show and hide content dynamically to improve user experience, and that these don’t violate the policies. Accordion and tabbed content comes first on that list.
• Google suggests tabs for dense content. Google’s mobile-first indexing guidance says a mobile design can differ from desktop, for example by moving content into accordions or tabs, as long as the content is equivalent. It also says: “Instead of removing content, consider moving content into accordions or tabs to save space.”
• Google doesn’t click. The same guidance says Google won’t load content that requires user interactions, such as swiping, clicking or typing, to load.

What these documents don’t say matters too. They say nothing about how collapsed text is weighted against visible text, in either direction. Claims that tabbed content counts “fully” and claims that it counts “less” both go beyond what Google has written in them.

How “hidden content is devalued” can spread

The phrase “hidden content” has two meanings, and confusion can start between them. In Google’s spam policies it means text hidden to manipulate search engines, the white-on-white kind. In a product template it means a specifications table behind a tab. The first is a violation; Google explicitly says the second is not. Advice that treats them as one thing can get copied forward, and “hidden” turns into “penalized”.

The test that matters: in the page, or loaded on click

The classification that matters for whether Google sees the text:

• In the page, collapsed by CSS. The tab’s text is in the HTML, and a style such as display: none keeps the panel closed until someone opens it. Google receives the text with the page.
• Loaded on click. The tab’s text is fetched from an API or inserted by JavaScript only when a user opens the tab. Google doesn’t click, so the text may never be in the page it indexes.

The same rule covers content that loads as the user scrolls: Google’s lazy-loading guidance asks that content load whenever it is visible in the viewport, without relying on user actions such as scrolling or clicking.

So the risky pattern is an accordion whose content exists only after a click.

Check each tab, not each page

You can tell which case you have without guessing:

1. Open a representative page in the URL Inspection tool, run a live test and click View tested page to see the HTML Google received.
2. Search that HTML for text that lives inside a closed tab: a line from the specifications, a review, an answer.
3. If the text is there while the tab is closed, Google has it. If it appears in your browser only after you click, and is missing from the tested HTML, it is loaded on click and at risk.
4. Repeat for each tab type. One template can mix both: specifications rendered on the server, reviews loaded on click.

Because one template stamps the same structure onto every product or article page, one misconfigured tab becomes a gap on every page that uses the template, and one fix closes it on all of them.

When the content is indexed but still doesn’t rank

If the text is in the tested HTML and a page still doesn’t rank for a question its accordion answers, the tab is not the first suspect. Compare your page with the one that ranks for that query:

• If the ranking page shows the answer openly and yours collapses it, surfacing yours is a reasonable test.
• If the ranking page also collapses the answer and still ranks, presentation isn’t the gap. Look at depth, how directly the page answers the query, and the page’s standing overall.

The comparison tells you whether changing the accordion is justified before you rebuild the template. It is a practical test, not a Google rule.

Decide what should be visible for readers

Separate from indexing, there is a design question: what does a visitor need to see without clicking? One pattern for product pages is a visible summary of the specifications, reviews and questions people use to decide, with the long tail kept in tabs. Search Console’s query data shows which attributes and questions bring searchers to the page, and those are the candidates for the visible summary.

Two reflexes to avoid:

• Removing every accordion. On mobile, accordions are a normal way to present dense information, and Google’s own guidance suggests them.
• Serving a different layout to Googlebot. A script that expands everything for the crawler and collapses it for users adds a moving part without a documented benefit. Build one page for everyone, with the content in the HTML.

FAQ markup won’t add a rich result

According to Google’s list of documentation updates, FAQ rich results stopped appearing in Google Search on May 7, 2026. FAQPage markup on an accordion of questions won’t produce one. Keep the questions and answers on the page because they help readers, and make sure the answers are in the HTML.

Frequently asked questions

Does Google treat content in tabs as hidden text?

Not when the content is in the page. Google’s spam policies list accordion and tabbed content among design elements that don’t violate its policies. Hidden text abuse means text concealed to manipulate search engines, such as white text on a white background.

If my accordion content loads only when clicked, will Google index it?

It may not. Google says it won’t load content that requires user interactions to load. Check the tested HTML in URL Inspection while the panel is closed. If the text is missing, move it into the initial HTML.

Is collapsed text ranked lower than visible text?

Google’s documentation on these points doesn’t say. It suggests accordions and tabs, and it doesn’t describe a weighting difference. If an indexed answer doesn’t rank, compare with the page that does before changing the design.

Should I add FAQPage markup to my accordion?

Not for a rich result. FAQ rich results stopped appearing in Google Search on May 7, 2026.