Fixes

How to fix “Indexed, though blocked by robots.txt” on Ghost

If Search Console shows “Indexed, though blocked by robots.txt” on your Ghost site, you are in the right place. The URL is blocked by robots.txt yet still in the index. 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: 05.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?

Google did not crawl the URL because robots.txt forbids it, but it knows the address from links on other pages and indexed it without content. The result usually shows "No information is available for this page".

Likely causes on Ghost

  • Only robots.txt was used to hide the page.
  • External and internal links announced the address to Google.
  • The page was indexed first and blocked in robots.txt later.
  • The sitemap still lists the URL.
  • 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. Confirm the site is not marked "Make this site private" in settings; a private site is noindex and password-protected. Remove noindex added through per-post code injection.
  4. If you do not want it indexed, remove the robots block and add noindex; allow crawling so Google can see the noindex.
  5. Protect content that must stay private with a password or login; do not rely on robots.txt alone.
  6. For urgent removal use the Removals tool in Search Console temporarily.
  7. If you want it indexed, remove the robots block and send the URL.
  8. Take blocked URLs out of the sitemap.

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

Why noindex first, then robots?

Google must be able to crawl the page to see noindex. Let noindex take it out of the index first, then close it with robots.txt if you like.

Is this an error?

It is a warning; a content-less listing may be undesirable for your brand.

Where are these settings on Ghost?

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

Related pages