Howdy ryan380,
Thank you for reporting back. We are all waiting here for a reaction from avast's as to what they exactly have flagged,
and what they hold about this all. I PM-ed for a reaction from avast team.
I just reported in this thread on the cloaking info and the difference between code,
as to what Google and Googlebot will be presented with.
Whenever that is what CloudFlare's bot protection is causing, that has to be solved in between the respective development teams.
I cannot be in that crossfire, that is fully out of my scope here. Both parties are helped by cooperation.
I also hope, that jamie128 will also bark up at CloudFlare's tree on this issue.
The waiting now is for an avast team member reaction, as this is their detection, their blocking, and finally also completely theirofficial forums where they have rendered me a platform to comment as an error-hunter in the field of website security intelligence to further their mission. Stay secure both online and offline, is the wish of,
polonus (volunteer 3rd party cold recon website security analyst and website error-hunter)