**Content that's hidden with CSS or buried inside an iframe may not be credited to your page — and hiding text from users while showing it to engines is a serious violation.** This check looks for important content concealed via `display:none` and similar, or loaded in iframes that engines may treat as belonging elsewhere. Content you want to rank or be cited should be genuinely visible in the page.
It looks for content that may not count toward the page because it's concealed or embedded. Specifically:
- CSS-hidden content — meaningful text hidden with display:none, visibility:hidden, zero height, or off-screen positioning.
- Iframe content — key content loaded inside an <iframe>, which engines may attribute to the iframe's source rather than your page.
- Cloaking risk — differences between what users see and what's served to engines.
No important content hidden passes; some content hidden or in iframes (e.g. behind tabs) is a warning; key content concealed from users or engines is a fail.
GEObubbly checks for meaningful content hidden via CSS or embedded in iframes. It's an extended Security & HTML Quality check that runs directly against the page's markup and styles.
Where content lives, and whether it's visible, affects whether engines credit it to your page. Two patterns cause problems. CSS-hidden content: text hidden with display:none, visibility:hidden, zero dimensions or off-screen positioning may be discounted, because engines aim to evaluate what users actually see — so important content tucked away in collapsed sections can carry less weight. (Reasonable UI patterns like tabs and accordions are usually fine, since the content is accessible on interaction; the issue is content hidden with no way to reveal it.) Iframe content: content loaded inside an <iframe> is a separate document, and engines may attribute it to its own source rather than to your page — so key content embedded via iframe might not count for you at all. The serious case is cloaking — deliberately showing users one thing and engines another, or hiding keyword-stuffed text from users — which is a clear guidelines violation that can trigger penalties. The principle is simple: content you want to rank or be cited for should be genuinely present and visible in the page's own server-rendered HTML. For GEO, an AI engine can only cite content it can see in your page, so concealed or iframed content is effectively invisible.
It can, depending on why and how it's hidden. Content hidden with CSS (display:none and similar) may be given less weight because engines aim to assess what users actually see, so important text concealed with no way to reveal it can underperform. Deliberately hiding text from users while showing it to engines — for example stuffing hidden keywords — is cloaking, a serious guidelines violation that can trigger penalties. Reasonable interface patterns like tabs and accordions, where users can reveal the content, are generally fine. The rule of thumb: don't hide content you want to count, and never show users and engines different things.
Content loaded inside an iframe is a separate document with its own URL, and search engines may attribute it to that source rather than to the page embedding it — so key content you place in an iframe might not be credited to your page at all. Engines can index iframe content in some cases, but you can't rely on it counting toward the embedding page. If content matters for your page's ranking or citation, include it directly in the page's own HTML rather than embedding it via iframe, reserving iframes for genuinely external embeds like maps or videos.
Cloaking is showing search engines different content than you show human visitors — for example serving keyword-stuffed text to crawlers while users see something else, or hiding text from users that's meant only for engines. It's penalised because it's deliberately deceptive: it manipulates rankings by misrepresenting what the page actually offers. Search engines treat cloaking as a clear violation of their guidelines, and it can lead to ranking penalties or removal. The safe principle is parity — the content engines see should be the same content users see, with no hidden layer aimed solely at manipulating search.
Generally no. Content placed behind tabs, accordions and "show more" toggles is a legitimate user-interface pattern, and because the content is present in the page and revealable by interaction, engines typically index it and treat it reasonably. This is different from content hidden with no way to access it, or content shown only to engines. The key is that the content genuinely exists in the page's HTML and users can reach it. So you can use tabs and accordions to organise a page without worrying that the hidden-by-default content will be ignored, as long as it's truly accessible.
Largely no, and that's the GEO risk. An AI engine cites content it can see in your page's HTML, so content concealed with CSS or loaded in an iframe (a separate document) is effectively invisible to it — just as it may not count for traditional ranking. If you want content to be understood and cited by AI engines, it needs to be genuinely present and visible in your page's own server-rendered markup, not hidden or embedded from elsewhere. Keeping important content in the page itself is the reliable way to ensure both search and AI engines can use it.