Fixes

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

If Search Console shows “Indexed, though blocked by robots.txt” on your Drupal 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 Drupal. A flexible, module-based CMS. The Metatag, Simple XML Sitemap and Redirect modules provide indexing control.

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

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

  • 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.
  • Drupal note: Edit robots.txt in the web root or manage it with the RobotsTxt module. On multisite setups each site needs its own file.

Step-by-step fix on Drupal

  1. In your Drupal admin go to: Configuration > Search and metadata (Metatag, Simple XML Sitemap, Redirect).
  2. Edit robots.txt in the web root or manage it with the RobotsTxt module. On multisite setups each site needs its own file.
  3. In the Metatag module check the "robots" value per content type; a noindex left over from a fresh install can spread to every node.
  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 Drupal

  • redirects and 404: The Redirect module can create automatic 301s when paths change. For deleted nodes add a redirect to a related page or return 410.
  • sitemap: Install Simple XML Sitemap, pick content types and submit the resulting /sitemap.xml. Leave out types that should not be indexed.

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

Configuration > Search and metadata (Metatag, Simple XML Sitemap, Redirect).

Related pages