Fixes

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

If Search Console shows “Blocked due to unauthorized request (401) / access forbidden (403)” on your PrestaShop 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 PrestaShop. Open-source e-commerce software. SEO and URL settings sit in one menu; multilingual and filter modules can create duplicate URLs.

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

Contents
  1. What does this status mean?
  2. Likely causes on PrestaShop
  3. Step-by-step fix on PrestaShop
  4. Extra checks for PrestaShop
  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 PrestaShop

  • 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.
  • PrestaShop note: The "Generate robots.txt file" button at the bottom of SEO & URLs rebuilds the file; it can overwrite manual edits, so back up first.

Step-by-step fix on PrestaShop

  1. In your PrestaShop admin go to: Shop Parameters > Traffic & SEO > SEO & URLs.
  2. The "Generate robots.txt file" button at the bottom of SEO & URLs rebuilds the file; it can overwrite manual edits, so back up first.
  3. Under Advanced Parameters > Performance enable the Smarty cache and the CCC (combine, compress, cache) options.
  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 PrestaShop

  • canonical and duplicate URLs: Turn on canonical redirection in SEO & URLs. On multilingual or filtered pages, stop parametrised URLs from being indexed as separate pages.
  • redirects and 404: When a product or category URL changes PrestaShop offers a permanent redirect; set it to 301. Use a redirect module for deleted products.

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

Shop Parameters > Traffic & SEO > SEO & URLs.

Related pages