How to fix “Blocked due to unauthorized request (401) / access forbidden (403)” on Squarespace
If Search Console shows “Blocked due to unauthorized request (401) / access forbidden (403)” on your Squarespace site, you are in the right place. Googlebot could not read the page because it asked for login or access was denied. This page covers the causes and a step-by-step fix for Squarespace. A template-based site builder. Sitemap and canonicals are automatic; robots.txt cannot be edited, so control sits mostly in page settings.
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.
Likely causes on Squarespace
- 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.
- Squarespace note: Squarespace manages robots.txt itself and it cannot be edited. For pages you want to keep out, use the per-page option to hide from search results.
Step-by-step fix on Squarespace
- In your Squarespace admin go to: Pages > page settings > SEO and Settings > Advanced > URL mappings.
- Squarespace manages robots.txt itself and it cannot be edited. For pages you want to keep out, use the per-page option to hide from search results.
- For load speed, shrink images and use fewer heavy gallery and video blocks. Hosting belongs to Squarespace; there are no server-side settings.
- 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.
Extra checks for Squarespace
- sitemap: The sitemap builds itself at /sitemap.xml and cannot be changed. To leave a page out, hide it from search results.
- noindex and visibility: "Hide page from search results" must be off in the page settings; a disabled page or a password-protected site is not indexed.
After fixing
In Search Console start "Validate fix" for this status and resubmit the page with URL inspection. First confirm the blocker is gone with the free Free indexability checker tool; for many URLs follow Bulk URL indexing: how to send thousands of pages to Google. Google makes the indexing decision itself and timing ranges from days to weeks.
More information
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.
Where are these settings on Squarespace?
Pages > page settings > SEO and Settings > Advanced > URL mappings.
Related pages
- Squarespace: URL is unknown to GoogleFixes
- Squarespace: Indexed, not submitted in sitemapFixes
- Squarespace: Crawled - currently not indexedFixes
- Joomla: Blocked due to unauthorized request (401) / access forbidden (403)Fixes
- Drupal: Blocked due to unauthorized request (401) / access forbidden (403)Fixes
- Magento: Blocked due to unauthorized request (401) / access forbidden (403)Fixes