"Blocked by robots.txt" means Google found a URL but a Disallow rule in your robots.txt file stopped it crawling the page. If the page should be in search, find the matching rule, remove or narrow it, confirm the change is live and retest. If you want the page kept out of search, allow crawling and add noindex instead.
Why it matters
A blocked page cannot be read, so Google has no content to judge and cannot follow its links. For pages you want visitors to find, that is a real loss. For pages you meant to hide, the block may not even work, since the address can still be listed.
How to fix it
- In Google Search Console, open the Page indexing report and select the Blocked by robots.txt reason to see the affected URLs.
- Decide for each group of pages whether it should be crawlable. Do not unblock admin areas or internal search results out of habit.
- Open
https://www.example.com/robots.txtand find the rule that matches the address. Rules match from the start of the path, and*and$act as wildcards. - Edit the file. Often a rule that is too broad needs narrowing:
# Before: blocks every URL that starts with /blog
Disallow: /blog
# After: blocks only the drafts folder
Disallow: /blog/drafts/
- Save and upload the file, then reload
/robots.txtin a browser to confirm the live version is the new one. - Run the URL Inspection tool on an affected page. It shows whether crawling is now allowed.
- Back in the Page indexing report, select Validate fix. Google caches robots.txt, often for up to a day, so allow time before expecting results.
If a stray Disallow: / was the cause, check that your hosting platform or an SEO plugin is not adding it again.
Common mistakes
- Leaving
Disallow: /from a staging site in the live file. - Blocking stylesheet or script folders, so Google cannot display the page properly.
- Adding noindex to a page while robots.txt still blocks it. Google cannot read the tag, so it has no effect.
- Editing the robots.txt of the wrong host, such as the non-www version when the site uses www.
- Treating the status as an error when the block is deliberate, for example on cart or filter pages.
Frequently asked questions
Is "Blocked by robots.txt" a penalty?
No. It reports that your own file asked crawlers to stay away. If that is what you intended, nothing needs fixing.
Will unblocking the page get it indexed?
It lets Google crawl the page, which is a requirement for indexing. Whether Google then indexes it turns on the content and other signals, and no outcome is promised.
How do I keep a page out of search then?
Allow crawling and use a noindex robots meta tag or an X-Robots-Tag header. For anything private, require a login.
Related guides
- Blocked by robots.txt in Search Console
- Robots.txt blocking search engines
- noindex vs robots.txt
- The Page indexing report explained
To test your own site for accidental blocks, Try the free website sample.