403 Forbidden
4xx client error
The server understood the request and identified the client but still refuses access, unlike 401, because re-authenticating with the same credentials will not help.
Common causes
- IP or geo allow-listing rejects the caller.
- A WAF rule or bot challenge blocks the user agent.
- File permissions deny the authenticated user.
How to fix it
- Check the WAF and firewall logs for the blocked request.
- Allow known search engine bots where the block is bot-specific.
- Return the blocked identity or rule in a header or body for diagnosis.
What it means for redirects and SEO
A hard block for crawlers, so the URL drops from the index over time. Cloudflare and WAF rules that 403 known bots are a frequent cause. Confirm the block with a fetch as Google before blaming the content.