Webflow Indexing Issues? 7 Fixes (2026 Triage Guide)

If your Webflow pages aren't showing up in Google, the cause is almost never mysterious. It's usually one toggle, the wrong domain, or a leftover noindex tag. This guide skips the generic "what is indexing" lecture and goes straight to Webflow-specific diagnosis: the exact settings to check, how to confirm each one, and the fix. By the end you'll know which of the seven common causes is yours, and you can run a free index audit on your live URLs to confirm Google can actually see them.

Why is my Webflow site not getting indexed?

A Webflow site usually fails to index for one of these reasons, in order of likelihood:

1. "Disable Webflow Indexing" is ON in Project Settings → SEO. Webflow then serves a robots.txt that blocks every crawler.
2. You only published to the webflow.io staging subdomain, which Webflow auto-noindexes so it never competes with your live domain.
3. A page-level "No-index" setting in Page Settings is excluding individual pages.
4. A manual Disallow rule in the robots.txt field under Project Settings → SEO.
5. A redirect error (loop or chain) stopping Google from reaching the page.
6. The auto-generate sitemap toggle is off, or the sitemap was never submitted to Google Search Console.
7. You changed an SEO setting but never re-published. Webflow settings only apply after a publish.

Check them in this order. The first two account for the large majority of "my Webflow site won't index" cases.

Cause 1: The "Disable Webflow Indexing" toggle

This is the single most common cause. In your Webflow indexing settings (Site settings → SEO → Indexing), the toggle Webflow now labels "Disable search engine indexing" (older projects called it "Disable Webflow Indexing"). Turning this on makes Webflow publish a robots.txt that disallows every crawler from your entire domain. When it is on, search engines are asked not to crawl any page on the site.

To confirm, visit yourdomain.com/robots.txt. If you see Disallow: / applied to all user-agents, the toggle is on. Turn it off, save, and re-publish: the robots.txt does not change until you publish. This setting is easy to leave on after a staging phase, which is why it surprises people the moment they connect a custom domain and expect Google to start crawling.

Cause 2: Publishing only to the webflow.io subdomain

Every Webflow project gets a free yoursite.webflow.io staging address, and Webflow keeps that subdomain out of search engines so your unfinished staging version never ranks against your real site. When the subdomain-indexing setting is on (it publishes a robots.txt that disallows crawlers on the webflow.io domain, and earlier projects also served a noindex tag there), a site published only to webflow.io will not show up where you want it. Note one caveat: a search engine can still index a staging URL if other sites link to it, so blocking crawling is not a guarantee of removal.

Confirm it by checking which domains have a green "Published" status in the Publishing panel. If only webflow.io is live, you need to connect a custom domain (Project Settings → Publishing → Custom domains), set it as default, and publish your live content there so Google has a real URL to index.

Cause 3: A page-level "No-index" setting

Sometimes the site indexes fine but specific pages vanish. Open Page Settings for the missing page and find the "Sitemap indexing" toggle (some guides call it the page-level "No-index"). When it is off, Webflow adds <meta content="noindex" name="robots"> to that page and drops it from the sitemap, so the page is invisible to Google by design. The same toggle exists per CMS item, but on-item control there requires a paid Site plan.

The fastest way to confirm a page-level block is the URL Inspection Tool in Google Search Console: paste the page URL and read the "Indexing allowed?" line. If it says "No: 'noindex' detected," re-enable Sitemap indexing in Page Settings and re-publish, then click Request Indexing.

Cause 4: Manual robots.txt Disallow rules

Webflow's SEO settings have a robots.txt field where you can add custom rules (this field needs a paid Site plan; the global toggle in Cause 1 does not). A stray Disallow: line, often pasted from a template or left over from a staging phase, can silently block whole sections. This is distinct from the global toggle in Cause 1; it blocks only the paths you list.

View yourdomain.com/robots.txt and read every Disallow line. Remove any that target live, important paths, save, and re-publish. For a deeper primer on how blocking differs from a page simply not being chosen, see our guide on why pages get crawled but not indexed.

Cause 5: Redirect errors

Redirect loops and broken chains are a recurring complaint in the Webflow forums (the "redirect error" threads). If you set up 301 redirects under Project Settings → Publishing → 301 redirects, a misconfigured rule can point a URL at itself or bounce Google between two pages until it gives up.

Run the affected URL through URL Inspection in Search Console: a redirect problem shows up as "Page with redirect" or "Redirect error" in the coverage status. Audit your redirect table for circular rules, then test the live URL again after fixing.

Diagnostic table: Webflow cause → confirm → fix

Webflow cause	How to confirm	Fix
"Disable search engine indexing" toggle ON	View /robots.txt: global Disallow: /	Toggle off in Site settings → SEO → Indexing, re-publish
Published only to webflow.io	Check Publishing panel for custom domain	Connect custom domain, set default, publish
Page-level "Sitemap indexing" off	GSC URL Inspection: "noindex detected"	Re-enable Sitemap indexing in Page Settings, re-publish
Manual robots.txt Disallow	Read /robots.txt Disallow lines	Remove the rule, save, re-publish
Redirect error	GSC: "Page with redirect" status	Fix circular/broken 301 rule
Sitemap missing or not submitted	Visit /sitemap.xml; check GSC Sitemaps	Enable auto-generate sitemap, submit to GSC
SEO change not published	Settings differ from live site	Re-publish: Webflow applies on publish only

Run a free index audit before you guess

Instead of toggling settings blind, confirm what Google actually sees. Drop your live Webflow URLs into our free Webflow index audit: it checks each page's real index status in bulk, so you immediately know whether the problem is site-wide (Cause 1 or 2) or a handful of pages (Cause 3 or 5). That single check tells you which row of the table above applies before you change anything.

Cause 6 & 7: Sitemap and re-publishing

Two quieter causes round out the list. First, the auto-generate sitemap toggle in Site settings → SEO must be on for Webflow to build yourdomain.com/sitemap.xml; then submit that URL in Google Search Console → Sitemaps so Google discovers pages faster. Second, and this catches almost everyone, Webflow only applies SEO changes when you publish. If you flipped a toggle but didn't hit Publish, the live site still carries the old setting.

For background on the indexing statuses you'll see in Search Console while you wait, read discovered – currently not indexed and how to check if a page is indexed.

Key takeaways

• The "Disable Webflow Indexing" toggle and the webflow.io subdomain noindex cause most Webflow indexing issues.
• Webflow applies SEO settings only on publish: always re-publish after a change.
• Use GSC URL Inspection for page-level blocks and /robots.txt for site-wide ones.
• Confirm reality, don't guess: a bulk index check shows you which cause is yours.

What to do once it's indexing

Fixing the toggle is step one; staying indexed is the real game. After your pages start appearing, monitor them so a re-published change or a stray noindex never silently drops you again. SearchOptimo can monitor index status at scale and send de-indexing alerts the moment a Webflow page falls out of Google. Start by running a free index audit on your Webflow URLs: it takes about a minute and tells you exactly where you stand.