G6 · Security & HTML Quality

    Hidden Content Checker — is important content hidden from engines?

    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.
    Updated June 2026 · Technical SEO & GEO · Part of Security & HTML Quality

    Check for hidden content

    Paste a URL — GEObubbly checks whether important content is hidden with CSS or buried in iframes.

    ✓ Free check1 signal✓ No signup required
    In short: Important content shouldn't be hidden behind CSS, tabs or accordions in a way crawlers may discount, and your main content shouldn't live inside an iframe — iframed content is hard to associate with the page.

    What does the hidden content check look for?

    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.

    How is it evaluated, and how is it scored?

    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.

    Why hidden content and iframes matter for SEO and GEO

    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.

    How this check scores
    Pass: Key content is visible and not trapped inside an iframe.
    Warning: Some important content is tab- or accordion-hidden by default.
    Fail: Main content is hidden via CSS or lives inside an iframe.

    FAQ

    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.

    Related checks in Security & HTML Quality

    G5
    Valid & semantic HTML
    G3
    Accessibility basics

    Audit your page across all 8 checks in Security & HTML Quality

    See which checks pass, warn or fail — in seconds.

    Run a free audit →
    ← Back to the full Security & HTML Quality guide
    Free TrialContact