Why does Search Console say Blocked by robots.txt?

The Google Search Console help pages give 4 common reasons. The first to rule out: When several rules could apply to a page, Google follows the most specific one, so a narrow rule can block a page a broader rule allows.

Reach · Are people seeing me?

Is it broken, or just quiet?

A number can fall because fewer people came, or because something stopped counting them. Below are the causes the Google Search Console help pages give, and how to check each one yourself.

What causes it?

  1. When several rules could apply to a page, Google follows the most specific one, so a narrow rule can block a page a broader rule allows.

    In the Google Search Console help: When matching robots.txt rules to URLs, crawlers use the most specific rule based on the length of the rule path. How Google Interprets the robots.txt Specification, read 2026-11-19.

  2. Google's crawler follows only one group of rules in the file, so the group that applies to it decides what is blocked.

    In the Google Search Console help: Only one group is valid for a particular crawler. How Google Interprets the robots.txt Specification, read 2026-11-19.

  3. Your robots.txt file tells search crawlers which pages on your site they may visit, so one rule there can keep Google off a page.

    In the Google Search Console help: A robots.txt file tells search engine crawlers which URLs the crawler can access on your site. Robots.txt Introduction and Guide, read 2026-11-19.

  4. A rule in your own robots.txt file told Google not to crawl the page.

    In the Google Search Console help: This page was blocked by your site's robots.txt file. Page indexing report - Search Console Help, read 2026-11-19.

How do I check it myself?

  1. Check the robots.txt file on the exact address the page uses, such as with or without www, since each file covers only its own address.

    In the Google Search Console help: A robots.txt file applies only to paths within the protocol, host, and port where it is posted. Create and Submit a robots.txt File, read 2026-11-19.

  2. Check that the capital and small letters in your rules match the page's address, since rule matching is case-sensitive.

    In the Google Search Console help: Note that the matching is case-sensitive. How Google Interprets the robots.txt Specification, read 2026-11-19.

  3. If you blocked the page to keep it out of search results, remove the robots.txt block and use a noindex instruction instead.

    In the Google Search Console help: To ensure that a page is not indexed by Google, remove the robots.txt block and use a 'noindex' directive. Page indexing report - Search Console Help, read 2026-11-19.

How would I know the day it starts?

  • Feder reads your clicks and impressions in Google Search from Search Console each day and compares each day with your own history.
  • Feder does not read your robots.txt file, so it does not flag a blocked page itself. It tells you when impressions go quiet or move outside your usual range.

Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.

See what Feder reads from Google Search Console, which feeds Reach. Feder only reads. It never changes anything in Google Search Console.

Where do these answers come from?

Every cause and check on this page comes from the Google Search Console help pages, quoted above with the date we read them. Last reviewed 2026-11-19. We read them again by 2027-11-19. If one changes, this page changes or comes down.

Know the day a number breaks, not the month after.