Why it happens
Security settings that block unknown bots, whole countries or data centre addresses can block Google crawlers along with the traffic they were meant to stop.
Your server returned 403 Forbidden to Googlebot. Googlebot never sends credentials, so a public page must load for a visitor who is not signed in.
Security settings that block unknown bots, whole countries or data centre addresses can block Google crawlers along with the traffic they were meant to stop.
| Check | How to tell | Fix |
|---|---|---|
| Does the page load for a signed-out visitor? | Open it in an incognito window on a different network, such as mobile data. | Remove sign-in or IP restrictions from pages that should be public.[1] |
| Is a security tool blocking crawlers? | Check security plugin, firewall or CDN logs for 403 responses to Google crawler requests. | Allow verified Google crawlers instead of blocking by user agent or country.[2][1] |
| Does Google see the 403 now? | Run "Test live URL" in URL Inspection. | Once the live test succeeds, validate the fix in the Page indexing report.[3] |
Google publishes how to verify its crawlers, using reverse DNS or its published IP ranges, so you can allow real crawlers and block fakes.[2]
Your website, fully managed — no big upfront cost.
We design, build, host, maintain and keep improving your site for one simple monthly fee.
A one-off custom build you own outright.
A defined scope and a single fixed quote — delivered once, and yours to keep.
Get a free, no-obligation quote for your project. We respond within 24 hours.