Blocked Due to Access Forbidden (403)
This Page indexing status means your server answered Googlebot with HTTP 403 Forbidden, so the page cannot be indexed. This guide explains why that happens, how to test it, and exactly which server, firewall, CDN and WordPress settings to check.
- What 403 means
- Why Googlebot gets it
- Test and fix
- Validate
Googlebot --GET /page/--> server
server --403 Forbidden--> Googlebot
Status: Blocked due to
access forbidden (403)Your server returned HTTP 403 to Googlebot. Googlebot never sends credentials, so Google treats this as a server misconfiguration and will not index the page. Fix it by letting non-signed-in users, or Googlebot specifically, reach the page. Check your firewall, security plugin, CDN bot rules and server access rules, then validate the fix.
What the status means
HTTP 403 means the server understood the request but refuses to allow it. When Googlebot receives it, the page is blocked from indexing. Google notes that Googlebot never provides credentials, so a 403 is generally a server misconfiguration rather than an intended login wall.
The family of status codes is explained in HTTP status codes for SEO.
403 compared with similar responses
| Code | Meaning | Typical fix |
|---|---|---|
| 403 | Forbidden: server refuses access | Change access rules |
| 401 | Authentication required | Page needs login (my own note) |
| 404 | Not found | See fix 404 errors |
| 5xx | Server error | See server errors |
Common causes
Google names the cause as server, firewall or access rules that reject unauthenticated requests. In practice these are the places to look (my own list):
WAF or security plugin
Rules that block bots or specific user agents.
Bot protection
CDN challenge or bot-fight settings.
Access rules
Directory permissions, .htaccess or nginx deny rules.
Login or membership walls
Pages restricted to signed-in users.
Test what Googlebot sees
Use the URL Inspection tool and run a live test on the URL. If the live test reports the page as blocked, the 403 is still happening. You can also compare with a normal browser request. A page that loads for you but fails for Googlebot points to a rule that targets bots.
HTTP/1.1 403 Forbidden
Fix by cause
| Cause | Fix |
|---|---|
| Firewall or security plugin | Allow verified Googlebot; review blocked-request logs |
| CDN bot rules | Allow verified search bots; see Cloudflare SEO settings |
| Server permissions or deny rules | Remove rules that deny unauthenticated access |
| Page requires login | Make it public if it should be indexed; otherwise leave it |
| Hotlink or geo blocking | Exempt Googlebot (my own advice) |
Google’s instruction is to allow non-signed-in users to access the page, or explicitly allow Googlebot without authentication.
Fix it step by step
Open the affected URLs
Indexing, then Pages, then the 403 status.
Should these be public?
If a page is meant to be private, 403 is fine. Only fix pages you want indexed.
Run a live test
Confirm Googlebot still gets 403.
Find the rule
Check security plugin, CDN and server logs for the blocked request.
Permit Googlebot
Allow unauthenticated access or whitelist verified Googlebot.
Retest and validate
Run the live test again, then click Validate fix.
Allow Googlebot safely
Do not allow anything that merely claims to be Googlebot. Google says Googlebot’s identity can be verified to guard against spoofed crawlers. Follow how to verify Googlebot and use that to build your allow rule.
Notes for WordPress sites
- Security plugins. Rate limiting and bot blocking are common causes (my own note). Check the plugin’s blocked log.
- Hosting firewalls. Some hosts block unfamiliar user agents by default. Ask your host.
- .htaccess rules. Look for deny directives added by tutorials or plugins.
- Maintenance or coming soon plugins can return 403 to bots.
Troubleshooting
| Symptom | Likely cause (my own diagnosis) | Fix |
|---|---|---|
| Loads in browser, 403 for Googlebot | Bot-targeted rule | Allow verified Googlebot |
| Intermittent 403 | Rate limiting | Relax limits for crawlers |
| Only some folders | Permission or deny rule | Check that directory |
| Fixed but status remains | Google has not rechecked | Validate fix and wait |
Checklist
Diagnose
- List affected URLs
- Run live test
- Decide public or private
- Read firewall logs
Fix
- Remove deny rules
- Allow verified Googlebot
- Review CDN bot settings
- Check plugins
Safety
- Verify crawler identity
- Do not disable all protection
- Keep private pages private
- Document the change
Close out
- Retest
- Validate fix
- Monitor email updates
- Recheck in two weeks
What Google’s page does not say
Google does not list every product that can produce a 403 and does not provide a bot allow-list for your specific firewall. It also does not give a re-crawl time beyond the validation estimate.
Key terms
- 403 Forbidden
- The server refuses to fulfil a request it understood.
- WAF
- Web application firewall that filters requests.
- Credentials
- Login details such as a username and password.
- Spoofed crawler
- A fake bot pretending to be Googlebot.
Common mistakes
Testing only in a browser
Bot rules hide the problem.
Allowing any Googlebot claim
Spoofers get in.
Turning off the firewall
Risky.
Fixing private pages
Some 403s are intended.
Validating early
One bad URL fails it.
Ignoring the CDN
Often the real cause.
Related guides
403 forbidden questions
What does 403 mean for Googlebot?
The server refused access, so the page cannot be indexed.
Does Googlebot log in?
No. Googlebot never sends credentials, so Google treats the 403 as a server misconfiguration.
How do I fix it?
Allow non-signed-in users, or explicitly allow Googlebot without authentication.
How do I stop spoofed bots?
Verify Googlebot’s identity before allowing it.
Is 403 ever fine?
Yes, for pages you do not want indexed or that are private.
How long does validation take?
Typically up to about two weeks, sometimes longer.
Can a CDN cause it?
Yes, bot protection rules are a common cause (my own experience-based note).
How do I test it?
Run a live test in the URL Inspection tool.
The definition, no-credentials point, fix instruction and verification advice come from Google’s Page indexing report help. The cause list, comparison table, step-by-step routine, WordPress notes and checklists are my own.