Key takeaways
- A practical guide to "Blocked due to access forbidden (403)": typical causes (WAF, geo blocks, auth), how to verify what Googlebot sees, and safe fixes
Table of Contents
Start with the map:
Related (cluster):
- Crawled - currently not indexed: what actually fixes it
- Discovered - currently not indexed: why it happens
- GSC redirect error: fastest fix checklist
What this status means
Googlebot received a 403.
This is usually not a content issue. It's access control: WAF, geo blocks, auth, or rate limiting.
Common causes
- Cloudflare / WAF rules blocking bots
- geo/IP restrictions
- auth-required pages leaking into sitemaps
- aggressive rate limiting
Fix checklist
- Confirm the exact response Googlebot gets (URL Inspection + server logs).
- If the page should be indexable: return 200 to Googlebot.
- If the page should not be indexed: remove it from sitemap and return 401/403 consistently (or 404/410 if gone).
Validation
- URL Inspection should show successful fetch.
- Server logs should show Googlebot getting 200 for indexable URLs.
Next in GSC statuses
Browse the cluster: GSC indexing statuses.
- GSC Indexing Statuses Explained: What They Mean and How to Fix Them (2026)
- Page with redirect (Google Search Console): What it means and how to fix it
- Redirect loop: How to find it and fix it (SEO + GSC)
- GSC redirect error: The fastest fix checklist (chains, loops, and canonical URLs)
- Submitted URL marked 'noindex': The fastest fix checklist (GSC)
- Submitted URL blocked by robots.txt: What it means and what to do (GSC)
Next in SEO & Search
Up next:
Crawl anomaly in Google Search Console: What it means and how to debugWhat "Crawl anomaly" means in Google Search Console, common underlying causes (timeouts, intermittent 5xx, redirects), and a step-by-step debug flow.