How to fix “Indexed, though blocked by robots.txt” on Webflow
If Search Console shows “Indexed, though blocked by robots.txt” on your Webflow 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 Webflow. A designer-focused visual builder. SEO settings exist per page and per collection; an indexed staging domain is a frequent mistake.
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 Webflow
- 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.
- Webflow note: You can edit robots.txt under Site settings > SEO > Indexing. Before publishing, check that no rule blocks Googlebot by mistake.
Step-by-step fix on Webflow
- In your Webflow admin go to: Page settings > SEO settings and Site settings > SEO / Hosting.
- You can edit robots.txt under Site settings > SEO > Indexing. Before publishing, check that no rule blocks Googlebot by mistake.
- Use the option that disables indexing of the webflow.io subdomain for staging; on the live site make sure that option is not hiding pages and that no page is excluded from search results in its SEO settings.
- 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 Webflow
- sitemap: Turn on the automatic sitemap under Site settings > SEO and submit /sitemap.xml to Search Console. Exclude pages you do not want from the sitemap in their page settings.
- speed and crawling: Large images, many interactions and external scripts lower speed. Upload images as WebP and delete unused interactions.
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 Webflow?
Page settings > SEO settings and Site settings > SEO / Hosting.
Related pages
- Webflow: Blocked due to unauthorized request (401) / access forbidden (403)Fixes
- Webflow: URL is unknown to GoogleFixes
- Webflow: Indexed, not submitted in sitemapFixes
- Squarespace: Indexed, though blocked by robots.txtFixes
- Joomla: Indexed, though blocked by robots.txtFixes
- Drupal: Indexed, though blocked by robots.txtFixes