Fixes

How to fix “Blocked due to unauthorized request (401) / access forbidden (403)” on Webflow

If Search Console shows “Blocked due to unauthorized request (401) / access forbidden (403)” on your Webflow 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 Webflow. A designer-focused visual builder. SEO settings exist per page and per collection; an indexed staging domain is a frequent mistake.

Updated: 05.11.2026 · 2 min read · Türkçe

Contents
  1. What does this status mean?
  2. Likely causes on Webflow
  3. Step-by-step fix on Webflow
  4. Extra checks for Webflow
  5. After fixing
  6. More information

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 Webflow

  • 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.
  • Webflow note: You can edit robots.txt under Site settings > SEO > Indexing. Before publishing, check that no rule blocks Googlebot by mistake.

Step-by-step fix on Webflow

  1. In your Webflow admin go to: Page settings > SEO settings and Site settings > SEO / Hosting.
  2. You can edit robots.txt under Site settings > SEO > Indexing. Before publishing, check that no rule blocks Googlebot by mistake.
  3. Large images, many interactions and external scripts lower speed. Upload images as WebP and delete unused interactions.
  4. If the page should be public, remove the protection; if it should stay private this line is expected.
  5. Allow-list Googlebot as a verified crawler in the WAF and firewall.
  6. Allow Googlebot by verifying with reverse DNS rather than trusting the user agent.
  7. Confirm the response code with a live test in URL inspection.
  8. After fixing, start validation and send the URL.

Extra checks for Webflow

  • redirects and 404: Under Site settings > Hosting > 301 redirects map old paths to new ones; you can also enter a bulk list.
  • sitemap: Turn on the automatic sitemap under Site settings > SEO and submit /sitemap.xml to Search Console. Exclude pages you do not want from the sitemap in their page settings.

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 Webflow?

Page settings > SEO settings and Site settings > SEO / Hosting.

Related pages