makorihi Currently, I am seeing the page up, however, it was receiving an error about an hour ago. My first recommendation is to have your host whitelist the following IP's
52.20.63.25
3.225.202.138
3.217.200.190
54.212.71.227
52.12.170.68
34.218.21.81
3.7.90.144
13.127.240.219
18.139.6.69
18.140.184.0
3.106.6.164
3.106.176.6
13.237.131.67
15.222.77.144
15.222.108.52
18.157.131.187
18.157.105.182
3.126.25.160
34.248.174.237
52.16.85.139
34.255.61.232
15.236.165.82
15.236.137.228
15.236.166.30
18.228.20.129
18.228.107.195
2600:1f10:4c55:e200::/56
2600:1f13:393:600::/56
2406:da1a:e10::/56
2406:da18:9d0:1400::/56
2406:da1c:58a:e100::/56
2600:1f11:f39:6f00::/56
2a05:d014:776:a600::/56
2a05:d018:dd:7800::/56
2a05:d012:4d8:6800::/56
2600:1f1e:342:2f00::/56

When it comes to integration methods, there is no need for added benefit to Cloudflare. CF integration allows for a more quicker and streamlined integration process, but since you are already integrated with us there would be no benefit to switching methods.

MichaelH Ok, I'll explicitly whitelist those, but just to confirm you're saying you don't get 403 on this URL?

https://dereproject.com/vtuber/shylily-lily-vtuber-face-reveal-interesting-facts-more/

makorihi Hi there,
I am seeing a 403 error on the page you have shared.

Let us know when you have whitelisted these IPs at your host and in any security plugins you are using.

Chelsea_W Checking the server rules, those IPs should be whitelisted. They actually were before as well, but explicitly confirmed now.

makorihi Hi again! Thanks for confirming this. Checking the page on my end, I am not currently seeing any error and the page is up and showing Ezoic ads now. Are you still seeing the error on your end? If so, does the error persist if you try viewing the page on a different device or browser?

Coley Are you sure? Based on this, the page is unavailable around the world. Maybe you're checking the copied article rather than the original blocked one?

Hi there,
I have checked the page on my end and I am indeed seeing the error, additionally I have checked global uptimes and it seems it is only available in one location currently (on both cached and uncached).

When I bypass Ezoic, and access your site directly from your host, I am able to see the redirect you have placed on that page (screenshot). Although I am unable to confirm if the original page is available.
When did you first notice this issue occur? And had you been making any changes to your site at this time?
Had you made any changes to any security settings within Cloudflare, or have there been any changes since?

AnyaR Thank you for the reply- sorry, I didn't see it until just now...

To answer your questions:

When did you first notice this issue occur? Around 2 weeks ago
And had you been making any changes to your site at this time? No, other than posting more content
Had you made any changes to any security settings within Cloudflare, or have there been any changes since? No, but the same day I noticed the issue (6 days ago) I tried creating a Cloudflare account and re-connecting Ezoic. It didn't help so I switched back to the previous setup

Would it be possible to bypass Ezoic for just this article? It seems like it has to do with something mis-configured on Ezoic's side, and I want google to see the redirect so it re-indexes the page. Currently it has no visibility on the page which caused a de-index.

makorihi You can add this article to the excluded pages tab to remove all Ezoic processes from showing on that page. More information on how to do that here.

makorihi Hi there! I checked the disable ads by page rules and didn't see the page in the rule, so I think either it was not saved or wasn't added correctly. I added both the original and updated pages as URL rules to prevent Ezoic from running on either version of the page (screenshot attached). These rules can sometimes take up to 30 minutes to be correctly reflected on the page, so please give it some time then check the pages again preferrably in an incognito tab or after clearing the browser cache to make sure you're seeing the most up to date version of the page. If the issue persists after this please let us know and we can take another look. Thanks!

Coley Thanks! Though I checked and the same issue still exists. I don't think Ezoic is actually being bypassed for the page giving a 403

makorihi I've edited the rule you had set so that It actually applies to the page. Please check now.

JeanPierre That didn't fix the issue either.

makorihi Thanks for letting us know you're still getting the error. I've reached out to our wider team to look into if this is being blocked on our end, and if so why. As soon as we hear back I'll update you. Thanks for your patience!