According to DEV Community, the Search Console Pages report error "Blocked due to access forbidden (403)" means Googlebot asked for a URL and received an HTTP 403 Forbidden response, so the page cannot be indexed. The page often loads fine in a normal browser, because the block targets Googlebot or requests that look like it.
The guide starts with confirmation. Run URL Inspection and its live test on a few example URLs. A 403 means the problem is current. A 200 means it was temporary, and you can click Validate fix. It also says to check whether the pages should be indexed at all. Admin, account or staging pages that correctly return 403 should be removed from sitemaps and links, not unblocked.
Next, find which layer sent the 403. CDN or WAF (web application firewall) block pages often carry recognisable headers and a branded page. A web server such as nginx or Apache may return its default page, or the app may return its own error template. The article notes that a curl request with a Googlebot user agent from your own IP is not a true test, since many rules check Google's IP ranges.
The listed causes are bot protection or WAF rules, rate limiting, geo-blocking, old server rules, file permissions, and logins or paywalls. For bot rules, it advises allowing a built-in verified bots category, never a user agent string alone. For rate limits, return 429 or 503 rather than 403 and exempt verified crawlers. For geo-blocking, remember Googlebot mostly crawls from US IP addresses. For paywalled content, serve full content to verified Googlebot with paywall structured data.
To verify, re-run live tests, check logs for verified Googlebot requests getting 200, and click Validate fix. The article says validation can take a couple of weeks for many URLs. It also suggests watching the Crawl Stats report for a rise in 403 responses after security changes.
Why it matters
Security tools can lock out search crawlers without anyone noticing, because the site looks normal to people checking in a browser. Pages that Google cannot fetch cannot be indexed, which can quietly hurt search traffic.
The guide's wider point is that a 403 and a 429 send different signals. Treating crawlers differently from abusive traffic, and verifying them by IP rather than by name, protects both security and search visibility.
Source: DEV Community. This brief summarises their reporting; read the original for the full detail.