Webflow

Webflow disable indexing: the SEO checkbox

The Disable search engine indexing switch sits in Site settings > SEO > Indexing and noindexes the published site. The checkbox people miss, and the fix.

Webflow writes a sitewide noindex when "Disable search engine indexing" is enabled under "Site settings > SEO > Indexing," and the change is not live until the site is published. Turn the setting off, click Save, publish the site, then run the indexability check on a live page to confirm the noindex meta tag is gone.

Why Webflow does this

Webflow's Help Center documents the switch in "Disable search engine indexing": the setting lives under "Site settings" > "SEO" > "Indexing," and Webflow's publishing flow shows a "Disable search engine indexing" checkbox on the publish dialog, which is the one people click past. Two documented traps sit around it. First, per-page indexing is a separate control: the "Sitemap indexing" toggle in "Page settings" > "SEO settings" "adds <meta content="noindex" name="robots"> to your site page." Second, Webflow's own warning covers the false fix: "Content from your site may still be indexed, even if it hasn't been crawled," so a robots.txt Disallow added at the same time looks like a fix while the page stays in the index.

Check it right now

Before changing anything, confirm what a crawler actually sees. The check is free, takes one URL and needs no account.

Run the check

How to fix it

  1. Open Site settings > SEO > Indexing.
  2. Check the "Disable search engine indexing" setting and turn it off if it is enabled.
  3. Click Save, then publish the site. Webflow's indexing settings take effect only on publish.
  4. Open any page that had the problem in the Designer, go to Page settings > SEO settings, and confirm the Sitemap indexing toggle is on.
  5. Run the indexability checker on a live page and confirm the robots noindex meta tag is gone.
  6. If Google still shows the site after the fix, use Search Console > Removals > Temporary Removals > New Request while the crawl catches up.

Why it happens again

The switch exists for the build phase and the publish dialog carries its own checkbox, so a redesign on the live domain keeps the site noindexed at launch. Anyone with Site settings access can flip it back, per page or site-wide, and nothing in Webflow warns the rest of the team before the next publish ships the change.

stillindexed re-checks the URLs you give it every 30 minutes on Starter and alerts when a directive changes, at most 30 minutes after it does. It is a monitor rather than a crawler: it watches a list you choose and tells you when one of seven things changes. Start with a 30-day free trial, 3 sites, no card required, and a 30 day refund after that.

Start the 30-day free trial, 3 sites, no card required

Catching it next time

Fixing it once is the easy half. The setting that caused this can be changed again by anyone with access, and the page will keep returning 200 while it happens.

Other ways Webflow loses pages

A noindex tag hiding the site from search, on other platforms

How Search Console reports it

Sources

Every claim about Webflow above is from their own documentation, read on 2026-10-25. Platforms change their settings; if one of these is out of date, their page wins and we would like to know.