Fixes

How to fix “Blocked by robots.txt” on Drupal

If Search Console shows “Blocked by robots.txt” on your Drupal site, you are in the right place. robots.txt stops Googlebot from fetching the URL. 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: 06.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?

A Disallow rule in your robots.txt forbids crawling this URL. Google cannot read the content; if other sites link to it, it can still appear in the index without content.

Likely causes on Drupal

  • A "Disallow: /" rule added during development was forgotten live.
  • A broad pattern (for example /*?) also catches pages you want.
  • The CMS or a plugin rewrote robots.txt on its own.
  • Sitemap URLs sit in folders closed by robots.txt.
  • 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. Use the Search Console robots.txt report or a robots tester to find which rule closes the URL.
  4. Narrow or delete the rule; close only folders that really should not be crawled.
  5. Verify that sitemap URLs do not conflict with robots.txt.
  6. After fixing, give Google a day to refresh its robots.txt cache or request a recrawl in the report.
  7. Send the URL for indexing and follow progress with URL inspection.

Extra checks for Drupal

  • speed and crawling: On the Performance screen enable page and block caching and CSS/JS aggregation; the dynamic page cache lowers server load.
  • noindex and visibility: In the Metatag module check the "robots" value per content type; a noindex left over from a fresh install can spread to every node.

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

Does robots.txt remove a page from the index?

No. It blocks crawling, it does not remove from the index. To remove, allow crawling and use noindex.

How do I test robots.txt?

Enter the file and a URL in our free robots.txt tester to see the Googlebot allow status.

Where are these settings on Drupal?

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

Related pages