How to view the real page of a clocked page

pd4089200

Newbie
Joined
Feb 17, 2025
Messages
27
Reaction score
13
Is there a way to see the real page of the page you clocked?
Change the user agent to Google, and I can't see it even if I use rich-results
 
Changing user-agent alone won’t reveal much anymore. Modern cloaking is IP + behavior based, not just UA string. If you’re not coming from Google ASN ranges, you’ll still see the money page. Compare raw HTML vs rendered DOM, sometimes that’s where the difference shows.
 
Is there a way to see the real page of the page you clocked?
Change the user agent to Google, and I can't see it even if I use rich-results
It depends on the skill level of the cloaker. Most will be able to keep their original html from end users eyes, but there are a couple of vectors that you can try:
Bing/Yandex Cache - these two search engines may have a copy of what html they were served up by the site
Google Sheets IMPORTXML function - you can try an =IMPORTXML formula in a Google Sheets cell - this can sometimes return uncloaked html, as it's a request from certain Google IPs
 
yeah, sometimes you still won’t see it even with a googlebot UA, because real cloakers don’t just key off user-agent, they also key off IP ranges, geo, headers, JS challenges, etc.

ways people usually confirm what google is actually seeing:

  1. google cache
    search: cache:theirdomain.com/page
    if it exists, it often shows the “bot” version.
  2. search console “view crawled page”
    best method, it shows what google rendered. but you need access to that property.
  3. textuploader / fetch tools with google IPs
    some third party “fetch as google” tools use google cloud IPs that might trigger the bot version, sometimes.
  4. compare multiple signals
    try: normal browser + VPN, then googlebot UA + VPN, then curl with minimal headers. cloaking sometimes breaks depending on accept-language, referer, etc.
realistically: if they’re doing IP-based cloaking, you won’t reliably see the real page from your own machine. cache + search console are the closest “truth.”
 
Yeah, changing your user agent to Googlebot often doesn't work because sophisticated cloaking checks for more than just that, like specific IP ranges or behavior patterns . Your best bet is using a dedicated cloaking checker tool that simulates different bots and compares the content for you . Or, check the page in Google's own URL Inspection tool to see exactly what Googlebot sees . :suspicious:
 
the best approach is to work with websites you own or have permission to test.
 
If it's your own site, use your cloaker's preview/debug mode or whitelist your IP to verify the destination page. If it's someone else's cloaked page, there's no reliable or appropriate way to bypass it.
 
Back
Top