Google Ads Disapproved – “Destination Not Working” 403 error
-
Hi there,
For quite a while now, we’ve gotten daily alerts from Google that large chunks of our ads are getting disapproved because our site destination isn’t working. However, in all of these cases, our destination is working perfectly fine. Sometimes the alert will provide us with the HTTP error code (403), so I’m assuming that’s probably the same error code they’re all returning.
I’m trying to narrow down where this issue is stemming from. My first assumption is that a firewall somewhere is blocking Googlebot. We have hundreds of thousands of ads, so if Googlebot is checking them all at once, I can see how that would raise flags.
We have a few different connections where a firewall could be getting triggered, so I’m just touching base with all of them to see if that is in fact the issue and, if so, we can add Googlebot to a whitelist so that it will never be throttled and hopefully resolve the issue.
I’ve read the stickied threads, but I’m not sure if that’s related to the issue I’m having, as I don’t seem to be getting notices from WP Cerber, but rather from Google. I’m just not sure if WP Cerber is perhaps doing some kind of blocking that I’m not aware of due to the sheer mass of potential Googlebot requests at a time.
Thank you!
- The topic ‘Google Ads Disapproved – “Destination Not Working” 403 error’ is closed to new replies.