Fixes

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

If Search Console shows “Blocked due to unauthorized request (401) / access forbidden (403)” on your WordPress 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 WordPress. The most widely used open-source CMS. Most indexing controls live in an SEO plugin such as Yoast SEO, Rank Math or All in One SEO.

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

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

  • 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.
  • WordPress note: WordPress serves a virtual robots.txt; edit it in your SEO plugin or replace it with a real file in the web root. Review any Disallow lines beyond /wp-admin.

Step-by-step fix on WordPress

  1. In your WordPress admin go to: Settings > Reading and the post or page box of your SEO plugin.
  2. WordPress serves a virtual robots.txt; edit it in your SEO plugin or replace it with a real file in the web root. Review any Disallow lines beyond /wp-admin.
  3. A caching plugin, image compression and decent hosting raise crawl speed. Remove unused plugins; a slow server makes Googlebot crawl less.
  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 WordPress

  • noindex and visibility: Make sure "Discourage search engines from indexing this site" under Settings > Reading is off; for a single post check the Advanced tab of your SEO plugin.
  • canonical and duplicate URLs: Core and SEO plugins add the canonical tag automatically; override it per post in the plugin canonical field. Check whether category, tag and paginated archives are indexed on their own.

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

Settings > Reading and the post or page box of your SEO plugin.

Related pages