(Search Console)

Blocked due to access forbidden (403)

What does this status mean?

‘Blocked due to access forbidden (403)’ is a status shown in Search Console’s Page indexing report as a reason “why pages aren’t indexed.” The official Help Center defines it this way: “HTTP 403 means that the user agent provided credentials, but was not granted access. However, Googlebot never provides credentials, so your server is returning this error incorrectly.” Pages with this status are not indexed. GSC Help Center

403 is a response code where the server understands the request but refuses it. Google’s Help Center explains it as meaning that login details (credentials) were provided but access wasn’t granted. Googlebot visits without any login details in the first place, so Google treats this response itself as the server’s mistake.

Think of it this way: a delivery driver (Googlebot) arrives at the front gate of the right apartment building, but the security guard (a firewall or security setting) sends them away because they’re not on the visitor list. The address (URL) and the building (server) are fine, but the gatekeeper blocked the way, so the package (content) couldn’t be delivered.

Is it a problem? Google sees it as the server’s mistake

The test is “should this page appear in search results?” If the URL was blocked from outside access on purpose, like an admin screen or an internal-only page, this is the intended result, so just confirm it and move on.

On the other hand, if a page that should appear in search is on this list, it’s a problem you need to fix. In particular, if the page opens fine in a browser but shows 403 only in the report, that’s a sign there’s a blocking mechanism that tells people and bots apart and gives bots a different response.

Leave it, and pages drop out of the index

Google Search Central’s documentation states the consequences of 400-level responses clearly: “Google doesn’t index URLs that return a 4xx status code, and URLs that are already indexed and return a 4xx status code are removed from the index.” Google (official) This means even pages that were already showing up well in search will disappear if the 403 continues.

Google Search Advocate John Mueller also responded about errors where a server or CDN (a network of relay servers that delivers site content on your behalf) blocks Google from receiving content (the ‘Indexed without content’ status). He said this is sometimes a low-level block based on Googlebot’s IP, which is hard to reproduce outside Search Console’s tools, and that it should be treated as urgent because pages start dropping out of the index if it’s left alone. John Mueller’s statement

Why it happens: security tools blocking by mistake

A 403 doesn’t happen because there’s no content; it happens because something refuses access. Semrush lists file permission errors, IP access restrictions and security settings as causes of 403, and lists firewall rules and bot-blocking plugins as causes of a separate access-denied error that rejects bot requests right at the entrance. Semrush blog

  • Bot blocking by firewalls and security plugins – the most common case, where a security tool mistakes Googlebot for a malicious bot and blocks it.
  • CDN and web application firewall (WAF) rules – country blocks or challenge rules (checkpoints that verify you’re human) end up filtering out Googlebot too.
  • IP access restrictions – the server only accepts allowed IP ranges, and Googlebot’s IP isn’t on the list.
  • File and folder permission errors – wrong server-side permissions cause even normal requests to be refused.

If you use a CDN like Cloudflare, it’s worth checking your firewall rules first. The official docs say that when you create country-block or challenge rules, you should exclude Googlebot and Bingbot using the verified bot condition (cf.client.bot). Cloudflare docs (official) A single rule created without this exception can send every Googlebot request back with a 403.

How to check whether only Googlebot gets a 403

First, use the live test in the URL Inspection tool. As the official Help Center explains, “This is a live test. The tool fetches and inspects the URL in real time,” so it shows the response at this very moment. GSC Help Center

Second, open the page in a private browser window. If it opens for people but returns 403 only in the live test, there’s a mechanism that blocks only bots.

Third, check your server logs (visit records) to see whether the IPs of requests that got a 403 are really Googlebot. The official guidance says: “Run a reverse DNS lookup on the accessing IP address from your logs, using the host command. Verify that the domain name is either googlebot.com, google.com, or googleusercontent.com.” Google (official) If you have many IPs to check, match them automatically against the IP range list file Google publishes (common-crawlers.json). As the same doc notes, this same procedure is also used to filter out fake bots pretending to be Google.

The fix: add Googlebot to the exception list

The official solution is a single sentence in the Help Center: “If you want Googlebot to index this page, you should either admit non-signed-in users or explicitly allow Googlebot requests without authentication (though you should verify its identity).” GSC Help Center There are two paths: make the page publicly viewable without logging in, or exempt only Googlebot, with its identity verified by the steps above, from your blocking mechanism.

In practice, the fix depends on the cause. For a firewall or security plugin, allow known search engine bots. For IP restrictions, add verified Googlebot IP ranges to your allowlist (whitelist). For Cloudflare, add a verified bot exception to your rules. For file permission issues, fix them together with your hosting provider.

On the other hand, never return 403 to Googlebot because crawling puts load on your server. Google’s official doc states: “Don’t use 401 and 403 status codes for limiting the crawl rate. The 4xx status codes, except 429, have no effect on crawl rate.” Google (official) It’s a losing choice: your crawl rate doesn’t go down, and you only lose your indexing.

After fixing it, run the live test again to confirm the 403 is gone, and use Request Indexing to bring Googlebot back sooner.

How is it different from other blocked statuses?

The most confusing neighbor is Blocked due to unauthorized request (401). A 401 is when the server blocks access by asking for a login (authentication). The Help Center offers this way to check: “You can verify this error by visiting the page in incognito mode.” GSC Help Center A 401 is a door that asks for ID; a 403 is a door that turns you away without even asking.

  • Blocked due to other 4xx issue – Collects the remaining 400-level responses other than 401, 403 and 404, which have their own entries.
  • URL blocked by robots.txt – The site owner has used rules to ask crawlers not to crawl. A 403 is when the server refuses access itself.
  • Not found (404) – A response saying the page doesn’t exist. A 403 is a response that won’t show a page even though it exists.
  • Server error (5xx) – The server couldn’t produce a response because of a failure or overload. A 403 is a working server refusing on purpose.

References

Jul.2026By Studio JT

More from Search Console

Like this term?
Give it a like!

(41)