Webflow hands you every control and explains none of them

This is a platform that can do everything correctly. It can also, through a toggle somebody flipped during a redesign, quietly remove your best pages from search, and nothing about the site will look wrong.

Run the free check

Webflow automatically generates a sitemap.xml and updates it on every publish, adding and removing pages as you create and delete them, and it automatically generates a robots.txt with a link to your sitemap by default. The risk is the per-page indexing toggle, which adds a noindex tag, and the site-level setting that publishes a blocking robots.txt on the webflow.io subdomain.

What Webflow does automatically

The foundation is solid and largely handled, which is why Webflow sites that fail usually fail for a specific configuration reason rather than a structural one.

Webflow automatically generates a sitemap.xml and updates it every time you publish, dynamically adding and removing pages as you create or delete them. By default that auto-generated sitemap includes every live page on the site.

It also automatically generates the robots.txt, and adds a link to your sitemap in that file by default, which is how crawlers discover it without you doing anything.

Pages are served as real HTML rather than assembled by script in the browser, so the rendering problem that dominates this whole category does not apply here.

The toggle that removes pages

This is the most common real cause of a Webflow page not appearing, and it is worth checking before anything else.

Page settings include a sitemap indexing toggle. Turning it off adds a noindex robots meta tag to that page, which tells search engines not to index it.

Note the interaction that catches people, because it is genuinely confusing. Disabling indexing of a page through robots.txt does not remove it from the auto-generated sitemap, so you can end up with a page listed in your sitemap while also being told not to index it. Those are two different mechanisms and they do not coordinate.

Check the toggle on every page you want found. Like most per-page settings, it can be correct on the page you inspected and wrong on the other eleven.

The subdomain setting people forget

Webflow lets you prevent search engines from indexing your site's webflow.io subdomain, which publishes a unique robots.txt on that subdomain telling search engines to ignore it.

This is a genuinely good feature and the right default behaviour to want, because it stops the staging address competing with your real one.

The trouble arrives when a site is only ever published to the subdomain. If you have not connected a custom domain yet, that setting is doing exactly what it says and your entire site is being told to stay out of search.

So if your Webflow site is on a webflow.io address and appears nowhere, this is very likely the reason, and the fix is to connect the real domain rather than to change the setting.

Publishing is not the same as being live

A Webflow-specific point that catches people moving from other tools.

Changes made in the designer are not on the live site until you publish, and publishing to the staging subdomain is a different action from publishing to your custom domain. It is entirely possible to have made every correct SEO change and published none of them to the address the public uses.

The same applies to settings changes. Adjusting the robots.txt rules or the sitemap configuration in site settings requires a publish before it takes effect on the live domain.

When something you changed does not appear to have taken effect, check the published state of the domain you are actually testing before investigating anything more complicated.

Where Webflow sites usually go wrong

Given a solid technical foundation, the failures cluster into a short list.

  • The per-page indexing toggle switched off during development and never switched back.
  • The site living on the webflow.io subdomain with subdomain indexing disabled, which is the intended behaviour of a setting nobody remembers turning on.
  • Changes made and never published to the custom domain.
  • Duplicate titles across pages, since Webflow gives you the fields and does not require you to make them different.
  • A site of five pages that all describe the business, which is the constraint no platform addresses.

What the control gets you

It is worth ending on the positive side, because the risk described above is the cost of something genuinely valuable.

Webflow gives you real control over the robots.txt directives, over which pages appear in the sitemap, and over the metadata on every page, including pulling values from CMS fields so that generated pages get genuinely different titles rather than one repeated.

That combination means a Webflow site can be set up properly and stay properly set up, which is more than can be said for a stack where the mechanism has to be built by hand.

The discipline it asks for is a checklist before launch. Go through the indexing toggles, confirm the custom domain is connected and published, and read the live robots.txt with your own eyes rather than trusting what the settings screen implies.

Part of a larger guide

This page is one part of Vibe coding SEO. The other parts:

Questions people ask

Does Webflow generate a sitemap automatically?
Yes, and it updates on every publish, dynamically adding and removing pages as you create or delete them. By default the auto-generated sitemap includes every live page, and Webflow also adds a link to that sitemap in the robots.txt it generates.
Why is my Webflow page not being indexed?
Check the sitemap indexing toggle in that page's settings first, since turning it off adds a noindex robots meta tag. It is commonly switched off during development and never switched back, and being per-page it can be correct on the page you checked and wrong on the others.
Why is my whole Webflow site invisible to search engines?
If you are still on a webflow.io address, the setting that prevents indexing of the subdomain is likely doing exactly what it says. It publishes a unique robots.txt on the subdomain telling search engines to ignore it, which is correct behaviour for staging and wrong if that is your only address.
Does a noindex page still appear in my Webflow sitemap?
It can, and this confuses people. Disabling indexing through robots.txt does not remove a page from the auto-generated sitemap, so a page can be listed in the sitemap while also carrying instructions not to index it. They are separate mechanisms that do not coordinate.
I changed a setting and nothing happened. Why?
Changes in the designer are not live until you publish, and publishing to the staging subdomain is a different action from publishing to your custom domain. Settings changes including robots.txt rules also require a publish before they take effect on the live site.
Is Webflow good for SEO?
The foundation is strong: real HTML, an auto-updating sitemap, a generated robots.txt, and genuine control over metadata including values pulled from CMS fields. The cost of that control is that several toggles can silently exclude pages, so it rewards a pre-launch checklist.

Read your live site rather than your settings screen

The free Get Found Check fetches your published Webflow site and reports what the live robots.txt, sitemap and page tags actually say.

Run the free check Have Licheo do it for you