Skip to content

Website Cloaking Checker

Scan any URL for cloaking signals: cross-domain redirects, meta refresh, JavaScript redirects, hidden text and thin visible content.

Website Cloaking CheckerGratisAI PoweredChecks a live URL
Analyzes HTML signals that may indicate cloaking. For definitive detection, compare with a Googlebot crawl tool like Google Search Console's URL Inspection.

Enter a public URL. We fetch the live page and analyse what search engines and AI crawlers see.

Key features of the website cloaking checker

  • Six cloaking and sneaky-redirect checks on any public URL
  • Detects cross-domain redirects, meta refresh and JavaScript redirects
  • Flags CSS-hidden content and white-text patterns for review
  • Checks that the page has enough visible, crawlable text
  • A clear verdict with the detail behind every check

How to use the website cloaking checker

  1. Enter the URL

    Paste the full address of the page you want to test.

  2. Run the check

    Click Check. The tool fetches the page and tests its HTML.

  3. Read the verdict

    See whether the page passed all six checks, raised one concern or raised several.

  4. Review each failed check

    Open the page source and find the redirect, hidden block or white text the check found. Decide whether it is normal design or content meant only for crawlers.

  5. Confirm in Search Console

    For your own site, run URL Inspection in Google Search Console and compare Googlebot's rendered page with the browser version.

What is a website cloaking checker?

A cloaking checker looks for signs that a page shows search engines something different from what visitors see. Cloaking breaks Google's spam policies and can lead to a manual action. This tool fetches the page you enter, tests its HTML against six common cloaking and sneaky-redirect signals, and gives a verdict.

The six checks are: whether the page redirects to a different domain; whether the HTML contains a meta refresh redirect; whether it uses a JavaScript redirect (window.location); whether it contains CSS that hides content (display:none or visibility:hidden); whether it uses white text that could hide keywords; and whether the page has at least 100 words of visible text. Each check shows pass or fail with the detail behind it.

Reading the verdict: no failed checks gives "No cloaking signals detected", one gives "Minor concerns, review manually", and two or more give "Potential cloaking signals found". A failed check is a lead, not proof. Almost every legitimate site uses hidden CSS for menus and tabs and white text on dark sections, so look at what is hidden and why.

Limits: the tool fetches the page once, with its own crawler user agent. It does not request the page as Googlebot, compare two versions side by side or run JavaScript. To see exactly what Googlebot receives, use the URL Inspection tool in Google Search Console (Test live URL, then View tested page) and compare it with what you see in a browser.

Why use a website cloaking checker?

Cloaking is often accidental: a security plugin, a CDN rule, a geo-redirect or a hacked site can serve crawlers a different page. A quick signal check on your own pages, or on a site that looks suspicious, tells you where to look before Google finds a problem.

Website cloaking checker: frequently asked questions

Something else? Ask the team

What is cloaking in SEO?

Cloaking is showing search engines different content or URLs from what people see, in order to manipulate rankings. Google lists it as a spam policy violation, and sites that use it can receive a manual action that demotes them or removes them from search results.

How do I test a website for cloaking?

Run this checker for redirect and hidden-content signals, then compare what a browser shows with what Googlebot gets. For your own site, URL Inspection in Search Console shows Googlebot's version. For other sites, compare a request sent with a Googlebot user-agent string against the browser view, keeping in mind that cloaking sites often recognise real Googlebot by its IP address.

Does this tool fetch the page as Googlebot?

No. It makes one request with the AI Rank Lab user agent and checks the HTML for signals. Use URL Inspection in Google Search Console to see a page as Googlebot sees it.

Is every difference between bot and user content cloaking?

No. Showing different content by language, location or device, personalisation and A/B tests are allowed, as long as Googlebot sees what a typical visitor in the same situation would see. Cloaking means the main content, links or destination differ in order to rank.

Can cloaking happen unintentionally?

Yes. Security and bot-protection plugins, CDN rules that treat crawlers differently, and hacked sites that show spam only to Googlebot all create cloaking without the owner meaning to. That is why it is worth checking your own pages.

Is URL cloaking the same as SEO cloaking?

Not quite. URL or link cloaking usually means hiding a long or affiliate URL behind a short redirect, which is common and not a spam issue on its own. SEO cloaking means serving crawlers different content from users. Redirects become a problem when they send people somewhere other than what search engines were shown (sneaky redirects).

What happens if Google finds cloaking?

Google can issue a manual action, visible in Search Console, that demotes pages or removes the site from results. To recover, remove the cloaking, make sure Googlebot and users get the same content, and file a reconsideration request.

Can I check a competitor's site?

Yes. The tool works on any public URL. A failed check on someone else's page is a reason to look closer, not proof of cloaking.

¿Quieres conseguir más menciones en la IA?

Website Cloaking Checker is one piece of the puzzle. See how ChatGPT, Gemini, Perplexity, and Google AI Overviews actually view your brand, and get a prioritised list of fixes, with a free AEO & GEO audit from AI Rank Lab.

One check is a start. The audit checks the whole site.

Realizar una auditoría AEO y GEO gratuita or Ver precios.

  • Scores SEO, answer-engine (AEO) and generative-engine (GEO) readiness
  • Lists the fixes, page by page
  • Then track whether ChatGPT, Gemini, Perplexity and Google AI Overviews cite you
fieldnote.app4,571 credits

Site audit

fieldnote.app · SEO, AEO and GEO

Illustrative data
SEO
82
+6
AEO
64
+11
GEO
58
+9
Pages
48
Fixesby impact
  • /pricing · Missing H1High
  • /blog/guide · No FAQ schemaMedium
  • /llms.txt · Not foundMedium
  • /about · Meta description too longLow

See where your whole site stands

Paste your site. The free audit scores it for SEO, answer engines and generative engines, with the fixes.