How to fix “Indexed, though blocked by robots.txt” on WordPress
If Search Console shows “Indexed, though blocked by robots.txt” on your WordPress 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 WordPress. The most widely used open-source CMS. Most indexing controls live in an SEO plugin such as Yoast SEO, Rank Math or All in One SEO.
Contents
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 WordPress
- 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.
- WordPress note: WordPress serves a virtual robots.txt; edit it in your SEO plugin or replace it with a real file in the web root. Review any Disallow lines beyond /wp-admin.
Step-by-step fix on WordPress
- In your WordPress admin go to: Settings > Reading and the post or page box of your SEO plugin.
- WordPress serves a virtual robots.txt; edit it in your SEO plugin or replace it with a real file in the web root. Review any Disallow lines beyond /wp-admin.
- Make sure "Discourage search engines from indexing this site" under Settings > Reading is off; for a single post check the Advanced tab of your SEO plugin.
- If you do not want it indexed, remove the robots block and add noindex; allow crawling so Google can see the noindex.
- Protect content that must stay private with a password or login; do not rely on robots.txt alone.
- For urgent removal use the Removals tool in Search Console temporarily.
- If you want it indexed, remove the robots block and send the URL.
- Take blocked URLs out of the sitemap.
Extra checks for WordPress
- canonical and duplicate URLs: Core and SEO plugins add the canonical tag automatically; override it per post in the plugin canonical field. Check whether category, tag and paginated archives are indexed on their own.
- redirects and 404: Use the Redirection plugin, Rank Math, Yoast Premium or .htaccess for redirects. If you changed permalinks, map the old URLs to the new ones with 301.
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 WordPress?
Settings > Reading and the post or page box of your SEO plugin.
Related pages
- WordPress: Blocked due to unauthorized request (401) / access forbidden (403)Fixes
- WordPress: URL is unknown to GoogleFixes
- WordPress: Indexed, not submitted in sitemapFixes
- WooCommerce: Indexed, though blocked by robots.txtFixes
- Shopify: Indexed, though blocked by robots.txtFixes
- Wix: Indexed, though blocked by robots.txtFixes