How to Get Google to Index Your Webflow Website

Webflow produces clean, crawlable HTML, so when a Webflow site is missing from Google the cause is almost never the code. It is a setting, and usually one of a small group that interact in a way that catches experienced people out. You can build a perfect site that Google indexes at completely the wrong address.

This guide shows you how to get Google to index your Webflow website in five steps. You will see why every project has two live addresses, where the settings that control them live, the one CMS switch that can hide an entire collection, and how to diagnose a site that is still missing.

Key Takeaways

• Every Webflow project has two live addresses: the webflow.io staging subdomain and your custom domain.
• Publish to your custom domain first, because a project published only to staging has no indexable production site.
• Disable Webflow subdomain indexing under Site settings, then SEO, so staging never competes with your real site.
• Webflow applies SEO settings at publish time, so nothing you change is live until you publish again.
• One CMS template setting can hide a whole collection, removing every item from Google and from your sitemap at once.

How to get Google to index your Webflow website

These five steps depend on each other, so work through them in order. Skipping the first one makes every later step pointless.

1. Publish to your custom domain.
2. Disable indexing on the webflow.io subdomain, then publish.
3. Turn on the auto-generated sitemap, then publish.
4. Check that no page or CMS template has indexing disabled.
5. Submit the sitemap for your custom domain in Search Console.

Why every Webflow site has two addresses

Webflow gives each project a staging subdomain at yoursite.webflow.io from the moment you create it. Your custom domain only serves content once you connect it and publish to it.

That split causes most Webflow indexing problems. If Google indexes the staging subdomain, your real domain competes with a duplicate of itself, and the staging copy often wins because it has been live and crawlable for longer. Webflow noindexes staging by default, which protects most people, but that protection disappears the moment someone switches it off, and on an inherited project you cannot know without checking.

The animation shows the sequence that moves Google from the staging address to your real one.

Step 1: Publish to your custom domain

Connect your domain in Site settings, then publish and make sure your custom domain is included. Webflow lets you publish to staging alone, and a project in that state has no indexable production site at all.

Check the result by loading your domain directly. If you see your site, carry on. If you see a Webflow 404 or a parked page, the publish did not include your domain.

Step 2: Stop Google indexing webflow.io

Open Site settings, go to the SEO tab, and in the Indexing section switch on Disable Webflow subdomain indexing. This setting is narrow: it stops crawlers indexing yoursite.webflow.io while leaving your custom domain fully indexable.

Then publish again. Webflow applies settings at publish time, so a changed setting with no publish afterwards does nothing. This trips up many people who change the setting, check the live site, see no difference and assume it is broken.

Step 3: Turn on the auto-generated sitemap

In the same SEO tab, find the Sitemap section and switch on Auto-generate sitemap. Webflow then serves yourdomain.com/sitemap.xml and keeps it current as you add pages and CMS items.

Publish to the custom domain, then load the sitemap URL in your browser to confirm your pages are listed. Avoid a hand-written sitemap unless you have a specific reason, because a manually maintained sitemap goes stale the moment someone adds a page.

Step 4: Check per-page and CMS template settings

Every page and every CMS collection template carries its own Disable indexing for this page setting. When it is on, Webflow adds a noindex robots tag to the page and removes the page from the auto-generated sitemap.

That combination is quietly severe. The page vanishes from your sitemap, so you never notice it is missing, and it carries an explicit instruction not to index, so Google obeys even when it finds the page through a link. On a CMS site, one template with indexing disabled removes every item in that collection at once, which might be your entire blog or product catalogue. Open each collection template and confirm the setting is off.

Step 5: Submit the sitemap in Search Console

Add your custom domain to Google Search Console, verify it, and submit sitemap.xml. A Domain property is the safest choice, because it covers both the www and bare forms of your domain whichever one Webflow redirects to.

If you use a URL-prefix property instead, add the version your site redirects to, since that is the version Google will index.

How long does it take to index a Webflow site?

Expect a few days to a few weeks. New domains take longest, because Google has no crawl history for them and few links pointing in. Established sites that link to new pages from existing ones see those pages picked up much faster.

If a Webflow site stays unindexed for six weeks with every setting correct, stop adjusting settings. At that point the cause has almost always moved to thin pages, near-duplicate collection items or a domain with no inbound links. Our guide on why Google ignores half your backlinks covers that side of the problem.

How to speed up Webflow indexing

Link new pages and CMS items from pages Google already crawls, such as your homepage or a collection index. Collection items with no internal links have only one discovery route, the sitemap, which works but slowly, so add pagination or an index page that links to every item.

For individual priority pages, inspect the URL in Search Console and click Request indexing. Webflow has no built-in IndexNow integration, and IndexNow would not reach Google anyway, since Google does not take part.

For a launch, a migration or a large CMS import, SEO Indexing lets you submit up to 10,000 URLs per project without a Search Console connection, then check which ones landed with its index checker.

Why is my Webflow site not indexed?

Match the symptom you see to its likely cause, and apply the fix beside it.

• Google shows your webflow.io address: staging was indexed first, so disable subdomain indexing, publish, and link only to your custom domain.
• A whole CMS collection is missing: its template has indexing disabled.
• A settings change did nothing: you have not published since making it.
• Collection items appear slowly: too few items are linked from any page.
• Password protection is on: a protected page or site cannot be crawled at all, which is easy to forget on a staging-turned-production project.

How to check if your Webflow site is indexed

Use URL Inspection in Search Console for a definitive answer, and pay close attention to the canonical Google selected. On Webflow, that canonical tells you whether Google settled on your custom domain or on staging.

For a quick look without an account, search for site:yourdomain.com. To check a full CMS collection at once, the SEO Indexing index checker verifies up to 2,000 URLs per run, and our guide on how to check if a page is indexed on Google compares every method.

Common questions

How long does it take Google to index a Webflow site?

Usually a few days to a few weeks. A page on an established domain with internal links can appear within days, while a brand new domain with no links often takes several weeks because Google has no reason yet to crawl it often.

Do I need to disable webflow.io indexing if I have no custom domain?

Understand the trade-off first. Without a custom domain, staging is your only live address, so disabling its indexing means nothing gets indexed. If you intend to rank, connect a custom domain first, because building on webflow.io puts your search presence on a hostname you do not own.

Why does Google show my webflow.io URL instead of my domain?

Google indexed the staging subdomain before your custom domain went live. Disable subdomain indexing, publish, and make sure your sitemap and internal links all point at the custom domain. The staging URLs then drop out over the following crawls.

Does Webflow support IndexNow?

Not natively, so submission has to go through an external tool. IndexNow also reaches Bing, Yandex and other participating engines but not Google, which does not take part.

Will publishing again make Google recrawl my site?

Publishing updates your content and sitemap, which can prompt a recrawl, but it does not force one. Republishing an unchanged page repeatedly gives Google no new reason to visit.

The short version

To get Google to index your Webflow website, publish to your custom domain first, disable webflow.io subdomain indexing, switch on the auto-generated sitemap, and confirm that no page or CMS template has indexing disabled. Then submit the sitemap in Search Console. Publish again after every settings change, because in Webflow nothing is live until you do.