Just to be sure, I tried to add a CNAME to the R2 subdomain directly, but CF doesn't allow that and forces the use of their custom domain integration.

The way R2 works is if you use their endpoint (XXX.r2.cloudflarestorage.com), all egress is free and unlimited. If you set it up using a CNAME (like XXX.oursite.com), all R2 traffic counts toward the bandwidth. So we have to be able to verify the R2 subdomain (XXX.r2.cloudflarestorage.com) directly.

The solution you offered, unfortunately, doesn't work for us because we don't use the R2 custom domain integration. If we did, all traffic would pass through our Cloudflare account and would cost us a lot of money because it would count toward the bandwidth allocation.

Hi @johnmu.com, your post has perfect timing because we've been having a lot of trouble verifying a Cloudflare R2 subdomain in Google Search Console.

Unsurprisingly, given that I don't think it's currently possible, the post has received no responses: support.google.com/webmasters/t....