Indexed, though blocked by robots.txt: search kept a URL it did not fetch

Read the warning as an indexed URL with no fresh HTML

‘Indexed, though blocked by robots.txt’ means the URL is in Google’s index and a robots.txt rule still prevents Googlebot from requesting it. This is a warning, not a reason in the ‘not indexed’ table. The page can appear in search. The snippet is usually short, because Google assembled it from the page that linked here, not from HTML it was refused.

That is a different SEO issue from a disallow that simply keeps a new URL out of the crawl. A block does not reliably remove a URL that is already known, and it is not a noindex. Noindex is read only when the crawler is allowed to fetch the page. The GEO issue is the same missing fetch. An answer engine that honours robots.txt cannot quote a passage it was not allowed to read, so the source it keeps is a title, a link, or a competitor whose HTML is open.

• Treat this as a warning on an indexed URL.
• Keep it separate from a block that never entered the index.
• Expect a thin snippet until the HTML can be fetched.

Sort pages you meant to hide from pages you meant to rank

Open the sample URLs and test each one against the live robots.txt. A filter, an internal-search URL, or an admin path that is indexed only because another site linked it should not stay in search. The block did the crawl job and failed the removal job. A service page, a guide, or a Traditional Chinese URL in the same report is the opposite problem: the page you want found is indexed from a link and never refreshed.

On a Hong Kong site, the usual miss is a path rule wider than the junk it was meant to cover. Disallow: /zh, a CMS folder that also holds guides, or a prelaunch Disallow: / left on the production host will leave the English page fetchable and the Chinese page indexed only as a shell. Write the rule beside one real content URL. If the content URL matches, the warning is describing a page you still publish.

Allow the fetch, or remove the URL on purpose

When the URL should rank and be cited, delete the disallow that matches it. Keep robots.txt for URL spaces that should not be crawled: internal search, useless filters, and admin paths. Confirm with URL inspection that the live URL is allowed, then request indexing so Google fetches the HTML you want quoted. Put the bounded answer in that HTML, with the organisation and the place next to the claim. A sitemap entry for a URL that robots.txt still blocks will not clear the warning.

When the URL should leave search, a disallow is the wrong tool. Remove the robots.txt block, add a noindex robots meta or header, and let Google fetch that directive. A 404 is the other honest exit for a page that no longer exists. Watch the same template until the warning clears on the pages you reopened, and the pages you meant to hide report a noindex exclusion instead. The fix is a fetch that matches the decision, not another line that only stops the crawler.

• Unblock every URL you still want found or cited.
• Use noindex, after the URL is fetchable, for pages that should leave the index.
• Re-check URL inspection until the warning and the live robots.txt agree.

What does Indexed, though blocked by robots.txt mean?

Google has the URL in its index and your robots.txt file still blocks a crawl. Search can show the URL from other links. It cannot refresh the page or build a full snippet until the block is removed.

Will removing the robots.txt rule make the page rank?

It lets Google fetch the HTML. Rankings still depend on whether that HTML is the canonical page for the query. If the URL should not be in search, remove the block and add noindex instead.