Skip to content
Google Ads suspension experts based in ScotlandMon–Fri, 9:00–18:00 UK time 07777 148453
Guides
Guide · Google Ads Policy

Flagged for Cloaking When You’re Not Cloaking: Seven Setups to Check

Gianluca Catinella, Director, Ad Restore Ltd11 min read
Cover: a navy eye with a line through it on a light grey tile, with the label Google Ads, the title Flagged for cloaking, and a red Suspended chip.
Google’s wording, word for word

It’s okay to show slightly different content to different people, like showing a landing page or ad destination in different languages, having different special offers, or adjusting for geographical location or slower internet speeds, but the promoted product or service needs to be the same for everyone.

Google’s own wording, from the cloaking section of its Circumventing systems policy, checked on 7 November 2026.

You run a real business. You weren’t hiding anything, and Google Ads has suspended the account for cloaking anyway. Google defines cloaking as showing different content on your website to different people or to Google to try to hide things that might break its rules. So what matters is any gap between what Google’s systems were shown and what a customer was shown. Ordinary setups can open that gap without anyone meaning to.

This guide goes through seven of them and what Google says about each. For the policy itself (what Google counts as cloaking, why there’s no warning, and what an appeal needs), read our Google Ads cloaking guide first.

Checked against Google’s help pages on 7 November 2026. Some guidance below comes from Google Search’s or Merchant Center’s documentation rather than Google Ads; we say so where it does. Google changes its pages without notice, so check the linked page before relying on a detail.

At a glance

  • The gap is what counts

    Google’s definition turns on what its systems are shown versus what people are shown.

  • Some variation is allowed

    Languages, offers and location are fine, as long as the product is the same for everyone.

  • AdsBot often crawls from the United States

    Google’s own words.

  • Redirecting isn’t cloaking in itself

    Google says appropriate click trackers and redirects are okay if they aren’t used to hide a policy breach.

  • A fine-tooth comb, in our experience

    If Google thinks it was deliberate, the account stays suspended.

On this page8 sections

What Google is comparing

Google checks ad destinations with its own crawler, AdsBot, in two versions: one where AdsBot checks desktop web page ad quality, and one where AdsBot Mobile Web checks mobile web page ad quality. One of its best practices for this policy is to make sure Google can easily find all the pages on your website.

The stakes are high. Google says violations of this policy are taken very seriously and are considered egregious, and this suspension occurs upon detection and without prior warning. Destination problems are different: for those, Google will issue a warning at least 7 days before suspending your account. If your ads are disapproved but the account isn’t suspended, read destination not working or destination mismatch instead.

In our experience, it really takes a fine-tooth comb to look through a cloaking case. If Google thinks you’re cloaking on purpose, it’s treated as an egregious violation, and the account stays suspended.

Seven legitimate setups that can look like cloaking

These seven come from Google’s own policy and help pages. They’re in no particular order.

1. Geo or language redirects

Google allows it in principle: you can show slightly different content to different people, including different languages or adjusting for location. But the promoted product or service needs to be the same for everyone.

Two things can go wrong:

Google Search’s guidance, written for search rather than for ads, says to avoid automatically redirecting users from one language version of a site to another, and that its crawler sends HTTP requests without setting Accept-Language. Those pages are about Googlebot, not AdsBot, so treat them as a pointer, not a rule.

2. Bot protection and firewall challenges

Google says that if your site works for you but not for Google Ads, your server’s security settings, firewalls, or Content Management System (CMS) plugins might be blocking the automated crawl system. Its fix is to allowlist the AdsBot-Google and AdsBot-Google-Mobile user agents.

Two details matter. AdsBot and Google’s other special-case crawlers operate from a different IP range from its common crawlers, so a rule written only for Googlebot may not cover it. And AdsBot ignores the global robots.txt user agent, so only a robots.txt rule that names AdsBot applies to it. More in our guide to destination not working.

Google’s cloaking examples include a pop-up, also known as an “intrusive interstitial”, that blocks access to most of your content, so Google can’t see the page it’s meant to review. An age check or a cookie wall that covers the whole page can do the same.

Google’s Merchant Center landing-page requirements, written for Shopping rather than Google Ads, say to use legally required redirects, such as an age check where the law needs one, and to make sure the page behind it meets the same guidelines. For other pop-ups, make sure that the boxes can be closed and aren’t blocking product details.

What we won’t suggest is giving Google’s crawler a way round the gate that customers don’t get. That would show Google a different page, which is what the policy describes.

4. Different mobile and desktop pages

Google crawls with a mobile AdsBot and a desktop one, and it disapproves destinations that return an HTTP error code to its AdsBot crawlers on common devices globally. So the mobile page has to load for the mobile crawler and promote the same thing as the desktop page.

If the mobile page lives on another address, the domain in your ad’s display URL still has to match the final and mobile URLs where users are taken to. Google Search’s guidance, for search rather than ads, is to make sure that your mobile site contains the same content as your desktop site.

5. A/B testing and personalisation tools

Testing a new headline or button isn’t cloaking in itself: Google allows slightly different content, as long as the product is the same for everyone.

Google Search’s testing guidance, written for Googlebot rather than for ads, says not to show one set of URLs to Googlebot, and a different set to humans, whether you’re running a test or not. It adds that if you’re using cookies to control the test, keep in mind that Googlebot generally doesn’t support them. So check which version a crawler gets, and that every version promotes the same product.

Google is clear that using appropriate click trackers and redirecting users is okay, as long as you aren’t doing it to hide something that breaks its policies. What it bans is using click trackers to redirect people to websites with content prohibited by its policies. Its best practice is to use certified click trackers, and it publishes a list of certified click trackers.

Google’s destination rules add more:

With parallel tracking, people are taken to the final URL while the tracking template URL is loaded in the background, and Google says any tracking redirects need to be server-side.

7. Parked, expired or changed domains

Google lists parked domains and “Under construction” or “Coming soon” pages as destinations that don’t offer a service, and names a web domain that isn’t officially registered or has expired as a cause of DNS errors.

Changing domain needs care too. Among its Circumventing systems examples, Google lists bypassing enforcement by creating variations of ads, domains or content that have been disapproved, and creating new websites or accounts to show ads that are similar to ones already disapproved.

How to see what Google sees

Google publishes its own tools for this. Its help pages show how to use Chrome’s developer tools to mimic the Google AdsBot web crawler used to review destination URLs, and suggest Google Search Console (URL Inspection tool) to test a landing page. For tracking, Google says you can use the Test button to check that your tracking is set up correctly. And because websites can get hacked and cloaking content can be added without you knowing, Google points to its Safe Browsing tool as a first check.

Fixing it without making it worse

  • Don’t build a page just for Google. Giving AdsBot a different page from the one your customers get is what Google’s cloaking examples describe.
  • Don’t rush a big change. In our experience, moving to a new domain or switching security off can affect the whole site and its trust, even how it does in Google Search. Google’s fix for a blocked crawler is narrower: let AdsBot through, so it sees the same page as everyone else.
  • Fix first, then appeal. In our florist case, the original problem had been corrected years earlier, but the account stayed suspended until a proper appeal went in.

Can it be fixed?

Often, when the cause is a setting rather than an intention. Google says accounts are only reinstated in compelling circumstances, such as in the case of a mistake. Its appeal tip for cloaking asks you to provide details about why you were showing different content to Google than to other people, and where there’s been a mistake, to share the steps you took to make sure cloaking isn’t happening, like removing redirections.

We’re upfront about the cases we can’t win: if an account really was arranged to get round Google’s review, no appeal can change that. We tell you at our first review, and we never help open another account.

None of this is a promise. Only Google decides.

Don’t open a new Google Ads account to get round this.

Google’s Circumventing systems policy names creating new accounts to re-enter the system after a suspension as a violation of the same policy, and its suspensions overview says any new accounts that the advertiser tries to create may also be suspended. Read why a new account makes things worse.

The appeal route

Before you write it, read what the appeal form asks and why appeals get rejected.

Frequently asked questions

Can a geo-redirect get my Google Ads account suspended for cloaking?

Google’s cloaking policy doesn’t name geo-redirects, and it allows slightly different content for different locations as long as the promoted product is the same for everyone. But Google says AdsBot often crawls from the United States, and it names geo-redirection to different domains as a cause of destination mismatch.

Is a cookie banner or an age check cloaking?

Google’s policy doesn’t name either. Its cloaking example is a pop-up that blocks access to the majority of your content, so Google can’t review the page. Don’t give Google’s crawler a way round it that customers don’t get.

Can A/B testing count as cloaking?

Testing small changes isn’t cloaking in itself, as long as the product is the same for everyone. Google Search’s guidance warns against showing its crawler one set of URLs and people another, even during a test.

Do tracking templates and click trackers count as cloaking?

Not if they’re used properly. Google says appropriate click trackers and redirects are okay, and recommends a certified click tracker. It bans using click trackers to send people to prohibited content, and disapproves tracking templates that don’t lead to the same content as the final URL.

Should I let AdsBot through my firewall?

Yes. That’s Google’s own instruction: allowlist the AdsBot-Google and AdsBot-Google-Mobile user agents, so the crawler sees the same page as everyone else.

Should I move to a new domain to start clean?

In our experience, a move like that can affect the whole site’s trust, even in Google Search. Google’s Circumventing systems examples also include creating new websites to show ads similar to ones already disapproved.

Gianluca Catinella, director of AdRestore
Written by

Gianluca Catinella

Director, Ad Restore Ltd

Gianluca Catinella is the Director of Ad Restore Ltd. He has worked with businesses across a wide range of industries, managing high-spend Google Ads accounts and handling complex account suspensions — including some of the most challenging policy and reinstatement cases. His work covers Circumventing Systems Policy, Suspicious Payment Activity and Unacceptable Business Practices, along with advertiser verification, Merchant Center and Google Business Profile suspensions. He came to this work from the receiving end. Running Google Ads for his own first business, he had an account suspended and found almost no support available to explain what had actually been flagged or how to put it right. He spent the months that followed reading the policies properly — every suspension type, what reviewers look for, and what a successful appeal has to contain — and he now tracks Google’s policy changes as they ship. Automated enforcement has to cast a wide net to keep scammers and bad actors out, and legitimate businesses get caught in it. Gianluca’s job is the bridge from confusion to clarity: working out exactly which policy was triggered, fixing the underlying issue, and putting a clear, evidenced appeal in front of Google so the business can get back to trading.

More from the blog