{
  "id": 20659101,
  "title": "How to fix 'Blocked due to access forbidden (403)' in Google Search Console (it's usually your WAF or bot rules)",
  "url": "https://urgent.news/2026/11/18/how-to-fix-blocked-due-to-access-forbidden-403-in-google-search",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-18T21:26:54.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/seotto/how-to-fix-blocked-due-to-access-forbidden-403-in-google-search-console-its-usually-your-waf-4eed"
  },
  "original_language": "en",
  "account": "To resolve Googlebot-specific access blocked (403) errors in Google Search Console, follow these steps. First, confirm the issue persists by selecting a few URLs from the report and performing URL Inspection followed by a live URL test. If the live test displays a 403, the problem is current. Next, identify which layer returned the 403 response. This can be done by analyzing the headers and body of the response, which often reveal identifiable patterns such as CDN or WAF blocks, server-level 403 pages, or custom app error templates. Keep in mind that Googlebot requests are protected and return different headers compared to typical requests.\n\nCommon causes of the 403 error include bot protection or WAF rules, rate limiting, geo-blocking, server-level rules, and file permissions. WAF or CDN rules are the most frequent culprits; they often become active after tightening security settings or adding new rules. To address this, verify that verified Googlebot requests are passing through by examining your WAF or CDN logs for requests from Google's IP ranges. Additionally, if your site implements rate limits or geo-blocking, ensure that Googlebot's IP addresses are exempt from these restrictions. For server-level rules, inspect your server configuration (like .htaccess or Nginx files) for any user agent patterns that might be blocking Googlebot. If only specific files or directories return 403, check file permissions or missing index files.\n\nAfter making the necessary adjustments, verify the fix by running URL Inspection's live test on the affected URLs to ensure they now return a 200 status. Monitor your access or CDN logs over the following day to ensure verified Googlebot requests are being granted access, and validate the fix through the Search Console. Remember to check for a possible increase in 403 responses in the Crawl Stats report as an indicator of any ongoing issues.",
  "summary": "Automated technical SEO checks that catch indexing blocks and deploy regressions — seotto.com Search Console's Pages report has a reason that looks simple: Blocked due to access forbidden (403) . Googlebot requested the URL and got HTTP 403 Forbidden, so the page can't be indexed. The confusing part is that the page usually loads perfectly in your browser. The 403 is aimed at Googlebot…",
  "key_points": [
    "Confirm issue by selecting URLs and performing URL Inspection and live URL test",
    "Identify WAF or bot rules layer causing 403 response through headers and body analysis",
    "Verify fix by ensuring Googlebot requests return 200 status in live test"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}