Google Docs to WordPress: 7 Easy Steps to Publish Faster
Learn how to prepare a blog in Google Docs and move it to WordPress while keeping headings, formatting, images, tables, links and SEO information organized.
This scanner reads your page and up to 8 internal pages, including their linked CSS files, and flags anything hidden with display:none, visibility:hidden or zero opacity. Some of that is harmless leftover markup, but hidden text stuffed with keywords is a cloaking technique search engines penalize, so it's worth knowing what's actually there.
What counts as "hidden," and why it's worth knowing what's on your page.
Surfaces every element hidden through common CSS techniques, so nothing invisible on the page stays invisible to you.
Hidden text packed with keywords is a known SEO cloaking pattern, this flags it before a manual review or algorithm update catches it instead.
Finds elements hidden with an inline style, with a class in the page's own style blocks, or with a class in up to 6 linked stylesheets like your theme's style.css.
Old hidden sections often mean leftover markup from a previous redesign, removing them shrinks page weight and simplifies future edits.
Checks for display:none, visibility:hidden and zero opacity, not just the one most obvious method.
Each flagged element is shown with enough context to find it in your source, instead of a vague "issues found" count.
A guide to using the hidden element checker, understanding what it flags and deciding what to keep.
The tool loads the page you enter and up to 8 internal pages linked from it. On each page it looks for elements hidden in three ways:
For each element you see the tag, how it is hidden and a short preview of its text, so you can find it in your source quickly.
Most sites hide some content on purpose, and that is fine. Mobile menus, dropdowns, tabs, accordions, popups and cookie banners all start hidden and appear when someone clicks. Search engines understand this kind of interactive content.
Hiding text from visitors while showing it to search engines is a form of cloaking, and Google treats it as spam. If you find this kind of content, delete it from the page instead of hiding it again. If you did not add it yourself, your site may have been hacked, so run the malware scan as well.
Years ago, some sites stuffed pages with keywords in white text or tiny hidden boxes so they would rank for terms visitors never saw. Google's spam policies now treat this as cloaking, and a page caught doing it can lose its rankings or be removed from results. That is why a quick cloaking checker pass is useful even if you never added anything like this yourself. Plugins, old page builders and hacked code can all leave hidden blocks behind without you knowing.
Run this hidden text checker after installing a new theme or page builder, after cleaning up a hacked site, or when you take over a site from someone else. Clearing out hidden leftovers also makes the page a little lighter. Treat it as a cloaking checker for your own pages: if a hidden block holds text you would not want a visitor to see, it should not be there at all.
Keep in mind that the hidden element checker reads the HTML and CSS the server sends. It only matches simple class rules, so hiding done with complex selectors, or by JavaScript after the page loads, will not show up. Check those in your browser's developer tools.
Official reference: Google's spam policies (see "Hidden text and link abuse") describe the kind of hidden content that can lead to a penalty, and the kind that is fine.
When hidden content is normal, when it looks like cloaking, and how the checker tells them apart.
It scans your page for elements hidden with display:none, visibility:hidden or zero opacity, whether that is set inline, in a style block on the page, or through a class in a linked CSS file. Each element is listed with where the hiding rule came from.
It checks the URL you submit plus up to 8 internal pages linked from it. For a bigger site, run it again from other key pages to cover more of it.
Some hidden markup is harmless leftover code, but hidden text stuffed with keywords is a cloaking technique that search engines specifically look for and penalize, so it's worth knowing which one you actually have.
Yes, indirectly, removing unused hidden sections reduces the amount of markup the browser has to parse, which can shave a little weight off page load.
No, the scan analyzes the static HTML and CSS returned by the server. Elements that get hidden dynamically by JavaScript after the page loads aren't covered by this check.
No, accordions, tabs, and mobile menus all legitimately use display:none for content that expands on click. The tool flags what's hidden; deciding what's intentional design versus leftover clutter still needs a quick manual look.
Yes. It downloads up to 6 stylesheets linked from each page and looks for simple class rules that hide content, such as .hide { display: none }. Rules with complex selectors are skipped to avoid false alarms.
Viewing source shows you raw HTML, but spotting which of hundreds of elements is actually hidden by CSS, and how, is tedious by hand. This tool does that scan automatically and lists only what's actually hidden.
Same free, no-signup approach, pick whichever check you need next.
No account needed, and nothing on the page you scan gets stored anywhere.
Explore all tools →