Hi,
Shield has special handling in there for all major search engines so that if they ever try to access your site in any way, Shield will never stop them – they’re basically whitelisted.
Shield doesn’t issue 403 errors. It’s possible it might interfere, somehow, so we never rule it out, but it doesn’t sound like.
Have you checked for changes to your .htaccess and robots.txt?
If you disable Shield, does the google fetch work?
Thanks.
Yes its abe to crawl after disableing the plugin — but it happened the same with wordfence that why i disabled it and installed Shield Security
But it does the same — after deactivating the issue is gone
I’m not sure how that’s possible. We verify all Google Crawlers and no-one else is reporting this.
Interestingly from your image it cites a 403 error – Shield doesn’t issue 403 errors. So there’s something else going on. I suspect, perhaps, it’s a configuration issue with the hosting and perhaps Shield is triggering that issue in some way – you could check your hosting apache/nginx logs for 403 errors. But Shield will not block or interefere with any verified Google bots.
To illustrate, you can go to your Activity Log and Shield will tell you everything it’s doing – particularly if you’re triggering page blocks. If there’s a block happening by Shield, it’ll be in Shield’s Activity Log.
yes after verification it was in my Htaccess!! thx for your help
Great, glad you found the underlying issue!