Blog

Blocked due to access forbidden (403): Fix checklist for Googlebot

0.765 min read/
/

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.

Subscribe
Get new essays via Substack or RSS. Start with the guided path if you are new.
Start with the main guide
GSC Indexing Statuses Explained: What They Mean and How to Fix Them (2026)

A practical map of Google Search Console indexing statuses (Coverage): what each status means, the most common root causes (canonicals, duplicates, robots, redirects, soft 404s), and the fastest way to validate fixes.

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

Contents

Start with the map:

Related (cluster):

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

  1. Confirm the exact response Googlebot gets (URL Inspection + server logs).
  2. If the page should be indexable: return 200 to Googlebot.
  3. 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.

Tags

More reading

Next in SEO & Search
View topic hub
Previous
robots.txt unreachable: Why it happens and how to fix it

A practical guide to "robots.txt unreachable": what Googlebot is seeing, common causes (timeouts, 403/5xx, WAF), and how to validate the fix in Search Console.

Up next
Crawl anomaly in Google Search Console: What it means and how to debug

What "Crawl anomaly" means in Google Search Console, common underlying causes (timeouts, intermittent 5xx, redirects), and a step-by-step debug flow.