[Google Ads Discussion] False “Cloaking” Suspensions After Verified BOV — Anyone Else Noticing This Pattern?

billy_vonka

Newbie
Joined
Feb 13, 2023
Messages
4
Reaction score
1
Hey guys,


Has anyone else noticed that Google Ads has become insanely sensitive to “Cloaking / Circumventing Systems” lately — even on clean, fully verified accounts?


Here’s what’s happening on my end:


  • I successfully complete Business Operations Verification (BOV)
  • Everything runs smooth for several hours or days
  • Then, boom — permanent suspension for “Circumventing Systems”
  • Appeal = denied with the standard “cloaking” message

No cloaking, no redirects, no dynamic swaps — 100% clean setup.
The lander, domain, and ad copy are fully compliant.
And this already happened twice across different accounts.




Theories I’m considering:​


  • Some new AI-level pattern detection tied to branded keywords?
  • Post-BOV trust score bug or delayed flagging from the previous review?
  • Overlapping DNS/CDN fingerprints between accounts?
  • Or maybe they’re training a new anti-fraud model that correlates account patterns rather than actual cloaking behavior?



What I’d like to discuss:​


  • Have you guys seen similar “false cloaking” bans lately?
  • Any pattern between keyword types, landing page themes, or account age?
  • Any workaround or appeal wording that worked for you recently?



I’m not running anything blackhat here — this is about legit verified setups getting nuked by the system.
Would be great to hear from anyone managing multiple accounts or agency-level setups — maybe we can find a common trigger.


Let’s share some data points and see what’s going on




✅ Goal: to figure out what exactly Google’s latest detection model is flagging as “cloaking” when it’s clearly not.
 
Hey guys,


Has anyone else noticed that Google Ads has become insanely sensitive to “Cloaking / Circumventing Systems” lately — even on clean, fully verified accounts?


Here’s what’s happening on my end:


  • I successfully complete Business Operations Verification (BOV)
  • Everything runs smooth for several hours or days
  • Then, boom — permanent suspension for “Circumventing Systems”
  • Appeal = denied with the standard “cloaking” message

No cloaking, no redirects, no dynamic swaps — 100% clean setup.
The lander, domain, and ad copy are fully compliant.
And this already happened twice across different accounts.




Theories I’m considering:​


  • Some new AI-level pattern detection tied to branded keywords?
  • Post-BOV trust score bug or delayed flagging from the previous review?
  • Overlapping DNS/CDN fingerprints between accounts?
  • Or maybe they’re training a new anti-fraud model that correlates account patterns rather than actual cloaking behavior?



What I’d like to discuss:​


  • Have you guys seen similar “false cloaking” bans lately?
  • Any pattern between keyword types, landing page themes, or account age?
  • Any workaround or appeal wording that worked for you recently?



I’m not running anything blackhat here — this is about legit verified setups getting nuked by the system.
Would be great to hear from anyone managing multiple accounts or agency-level setups — maybe we can find a common trigger.


Let’s share some data points and see what’s going on




✅ Goal: to figure out what exactly Google’s latest detection model is flagging as “cloaking” when it’s clearly not.
Yeah, that may happen but theres nothing much one can do about it... thats why aged accounts are better but sometimes such issues may happen. But usually it"s most probably because of a sort of redflag they can notice, even if your niche is WH
 
Yeah, I’ve seen this too. Google’s AI seems overly sensitive lately, maybe it’s the trust score or new patterns with branded keywords. Feels like legit setups are getting flagged by mistake.
 
If Google's AI triggered the BOV on your account, it means it identified a fairly high probability of global risk associated with your account, prompting it to subject you to this verification. If you are not engaging in cloaking, the AI has therefore banned you preventively, as it cannot take the risk of a potentially fraudulent account impacting the experience of Google users. Consequently, your account has been banned. This specific reason means that you have at least a 70% chance of having your account reactivated after submitting an appeal, since the AI acted on the principle of precaution.
 
If Google's AI triggered the BOV on your account, it means it identified a fairly high probability of global risk associated with your account, prompting it to subject you to this verification. If you are not engaging in cloaking, the AI has therefore banned you preventively, as it cannot take the risk of a potentially fraudulent account impacting the experience of Google users. Consequently, your account has been banned. This specific reason means that you have at least a 70% chance of having your account reactivated after submitting an appeal, since the AI acted on the principle of precaution.
Yes, but I successfully passed the BOV verification. Logically, after that, the account’s trust score should increase, making it more stable against false “cloaking” detections from anti-fraud systems. I expected there to be some correlation between verification levels and the AI’s level of confidence — but it seems like Google’s bots don’t really care. They still flag and ban new accounts indiscriminately if there’s not enough account history or previous activity.
 
Back
Top