How to fix “Indexed, though blocked by robots.txt” on PrestaShop
If Search Console shows “Indexed, though blocked by robots.txt” on your PrestaShop 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 PrestaShop. Open-source e-commerce software. SEO and URL settings sit in one menu; multilingual and filter modules can create duplicate URLs.
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 PrestaShop
- 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.
- PrestaShop note: The "Generate robots.txt file" button at the bottom of SEO & URLs rebuilds the file; it can overwrite manual edits, so back up first.
Step-by-step fix on PrestaShop
- In your PrestaShop admin go to: Shop Parameters > Traffic & SEO > SEO & URLs.
- The "Generate robots.txt file" button at the bottom of SEO & URLs rebuilds the file; it can overwrite manual edits, so back up first.
- Remove any setting in a product or category SEO tab that turns indexing off; a product with visibility "Nowhere" is not listed. Make sure maintenance mode is off.
- 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 PrestaShop
- redirects and 404: When a product or category URL changes PrestaShop offers a permanent redirect; set it to 301. Use a redirect module for deleted products.
- sitemap: Core has no sitemap; install the "Google sitemap" module, submit the XML address to Search Console and refresh it with cron.
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 PrestaShop?
Shop Parameters > Traffic & SEO > SEO & URLs.
Related pages
- PrestaShop: Blocked due to unauthorized request (401) / access forbidden (403)Fixes
- PrestaShop: URL is unknown to GoogleFixes
- PrestaShop: Indexed, not submitted in sitemapFixes
- Ticimax: Indexed, though blocked by robots.txtFixes
- IdeaSoft: Indexed, though blocked by robots.txtFixes
- Next.js: Indexed, though blocked by robots.txtFixes