I have tried just about everything I can think on the static deployment of the page. I am concerned that something about Cloudflare’s security system is triggering Google’s “malicious page” detection?
What are the steps to reproduce the issue?
Google has been reluctant to share any specifics. Has anyone ever encountered this on Cloudflare Pages? I am pretty amazed that a simple, static Next site could get flagged like this. I have taken steps to ensure that all static resources are pulled from our own CDN… we have no idea what Google is flagging, and their own site scanners say that we are good to go.
But every appeal keeps getting denied. Any ideas on why this is happening or how I might be able to mitigate would be amazing!
I appreciate that! Good to have other tools to reference.
We ended up deploying the exact same site on another domain, and Google was fine with it. My suspicion is that something triggered google to flag the domain? And maybe there is some timeline that they require it to sit before it is free again? We will keep poking at it.
The only data point I had:
At one point, we referenced / loaded images from randomuser.me
At one point, that Google ad account referenced a shared domain (subdomain) for this pages deployment that got flagged because of another Wordpress site…
Trying to learn a bit about Google’s “blast radius,” but it seems that a whole domain can get delisted pretty darn quick (we had like 5 landing pages on that parent domain get axed within a few days that the one Wordpress site did).