Fixes

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

If Search Console shows “Blocked due to unauthorized request (401) / access forbidden (403)” on your Ghost 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 Ghost. A publishing-focused blog platform. Sitemap and canonicals are automatic; posts have a metadata panel.

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

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

  • 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.
  • Ghost note: Ghost serves a default robots.txt. To customise, add a robots.txt file to your theme; a wrong rule can close post folders.

Step-by-step fix on Ghost

  1. In your Ghost admin go to: Post settings > Meta data, Settings > Code injection and Labs > Redirects.
  2. Ghost serves a default robots.txt. To customise, add a robots.txt file to your theme; a wrong rule can close post folders.
  3. Ghost is fast; slowness usually comes from a heavy theme or external scripts. Remove needless scripts in code injection.
  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 Ghost

  • redirects and 404: Define 301s by uploading a redirects.yaml or .json file under Labs > Redirects. If the file format is wrong Ghost will not apply the redirects.
  • sitemap: The sitemap builds itself at /sitemap.xml with child sitemaps for posts, pages, tags and authors. Submitting the main address is enough.

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

Post settings > Meta data, Settings > Code injection and Labs > Redirects.

Related pages