What does “Blocked due to unauthorized request (401) / access forbidden (403)” mean and how do you fix it?
Googlebot could not read the page because it asked for login or access was denied. The server answered Googlebot with 401 (login required) or 403 (forbidden). Googlebot does not log in, so the page cannot be indexed.
Contents
What does this status mean?
The server answered Googlebot with 401 (login required) or 403 (forbidden). Googlebot does not log in, so the page cannot be indexed.
Possible causes
- The page is members-only or password-protected.
- A firewall, WAF or bot protection blocks Googlebot IPs.
- A country or IP restriction covers Google IPs.
- A hotlink or user-agent rule rejects Googlebot.
How to fix it
- If the page should be public, remove the protection; if it should stay private this line is expected.
- Allow-list Googlebot as a verified crawler in the WAF and firewall.
- Allow Googlebot by verifying with reverse DNS rather than trusting the user agent.
- Confirm the response code with a live test in URL inspection.
- After fixing, start validation and send the URL.
Steps for your platform
Open the matching fix page for menu names and setting locations on your platform:
- WordPress
- WooCommerce
- Shopify
- Wix
- Blogger
- Webflow
- Squarespace
- Joomla
- Drupal
- Magento
- OpenCart
- PrestaShop
- Ticimax
- IdeaSoft
- Next.js
- React SPA
- Laravel
- Ghost
After fixing
In Search Console start "Validate fix" for the status, resubmit the page with URL inspection and confirm the blocker is gone with the free Free indexability checker tool. For many URLs see Bulk URL indexing: how to send thousands of pages to Google. Validation can take days to weeks.
Related terms
Frequently asked questions
Can Google see members-only content?
No. Previews need structured data and paywalled-content markup.
How do I tell if I am blocking Googlebot?
Look for 403 entries for Googlebot requests in your firewall logs.