By team & scale · Webflow indexing
Webflow Indexing Tool That Gets CMS Collection Items Indexed When Your Site Is Not Showing on Google
Webflow is unusually easy to misconfigure in ways that are invisible from the Designer. The settings that decide whether a page can be indexed sit in three different places, they only take effect when you publish, and one of them applies to an entire CMS Collection rather than to a single page. So the common failure here is not a slow crawl. It is a site that has been quietly telling Google to stay away since the last publish, while everyone looks at the storefront and sees a working website.
Submit · monitor coverage · official methods only
Indexed pages, week by week
Coverage report78%
Coverage, up from 64%
41 min
Avg time to index
What a check returns
Every URL gets a plain-English reason when a search engine will not index it, and the rest go out through the official channels.
Paste your sitemap and we count every URL it lists, then check a sample of your pages before we submit through the official Google Indexing API and Bing IndexNow.
We could not check that one
Crawlable
checked
Ready to submit
Need a fix first
We fetch the address you paste and read what a crawler sees · nothing is submitted to a search engine from this check
Index status itself comes from Search Console, which you connect on a plan · official Google Indexing API · Bing IndexNow · verified sitemaps · no spam, no PBNs
In short
A Webflow site that is not showing on Google usually has one of five causes, and four of them cost nothing to fix: the change was never published, indexing is disabled on the page or on its CMS Collection template, the .webflow.io staging subdomain is competing with your real domain, the sitemap is off or robots.txt is blocking, or Google crawled the page and declined it. The CMS one is the expensive one, because in Webflow a single Collection template controls indexing for every item built from it, so one toggle can remove hundreds of pages at once with no per-item warning and no visible change for visitors. Start by reading the Last Published timestamp Webflow writes into every page's HTML source: if it predates the SEO change you made, the change is not live and nothing else on the list matters yet. Indexing checks every URL on your Webflow site against Google and Bing, names which of the five applies per URL, and submits the genuinely waiting ones through the official Google Indexing API and IndexNow.
The CMS is where this gets expensive. A Collection template page is one design that renders every item in the Collection, which is the whole point of Webflow's CMS and also the reason a mistake never affects just one URL. Switch indexing off on the template and every blog post, case study or property listing built from it goes with it. Nothing in the Designer warns you, the pages still load perfectly for visitors, and Search Console reports the symptom weeks later without naming the cause.
Search Console is the authoritative place to look and it will not hand you the list. Google caps the example URL list in the Page indexing report at 1,000 items and states plainly that it is not guaranteed to show every URL in a status even when there are fewer than 1,000 of them. On a Webflow site with a few thousand CMS items, the coverage picture you are reading is a sample, and the items missing from the sample are exactly the ones you needed to find.
Indexing works from your published sitemap. Every page and CMS item in it gets checked against both Google and Bing on a schedule, each miss comes back with a plain-English reason attached, and the URLs where submission is genuinely the blocker go out through the official Google Indexing API and Bing IndexNow. No PBNs, no ping spam, and no claim that we can force Google to keep a page, because Google makes that call after it crawls.
Official methods only
White hat · no spam, no PBNs
Why it works
What your team gets with Webflow indexing
Catches the toggle that took out a whole Collection
Disabling indexing on a CMS Collection template removes every item built from it. We check the items themselves, so four hundred missing blog posts show up as one cause rather than four hundred mysteries.
Watches the staging domain too
Webflow serves Disallow: / on .webflow.io, which stops crawling but not indexing. If a staging URL picked up a link and landed in Google, you want to know, because you cannot noindex your way out of a blocked URL.
Submits only what submission can help
Pages Google has never fetched go out through the official Google Indexing API and Bing IndexNow. Pages Google fetched and declined do not, because resubmitting those is how budget gets burned in this category.
What it handles
Submitted, monitored and fixed, automatically
Indexing submits your URLs through the official Google Indexing API, Bing IndexNow and clean XML sitemaps, watches coverage across both engines, and flags any page that drops out with a plain-English reason so you can resubmit and get it back.
- Checks every page and CMS Collection item against Google and Bing on a schedule
- Separates never crawled from crawled and declined, per URL, in plain English
- Flags .webflow.io staging URLs that have surfaced in the index alongside your real domain
- Tells you when a Webflow page that was indexed quietly drops back out
- Submits the genuinely waiting URLs through official channels only
Not indexed yet
/blog/seo-guide-2026 is discovered but not indexed
thin content signal, queued for re-crawl via the Indexing API
Why Indexing
One place to submit, monitor and fix coverage
Not a black-hat indexer that risks your site, not a free checker that only tells you the bad news. Indexing unifies official submission and live coverage monitoring, the white-hat way, across Google and Bing.
Submits the official way
Bulk-submit through the Google Indexing API, Bing IndexNow and clean XML sitemaps. We speed discovery and re-crawl using methods the engines support, never spam, PBNs or black-hat tricks.
Monitors coverage live
You do not refresh a search bar one URL at a time. Indexing watches which pages are in Google and Bing, catches anything that drops out, and tracks time-to-index across your whole site.
Diagnoses and resubmits
Every non-indexed page comes with a plain-English reason, then auto-resubmits through the official API so it gets another shot. Google still decides, but nothing waits in the dark.
At a glance
Why Webflow pages stay out of Google, and what each cause actually needs
Five causes in the order they are worth checking. Four of the five are free to fix yourself, and we would rather you fixed them than bought anything.
| What is happening | How to confirm it in under an hour | What actually fixes it |
|---|---|---|
| The change was never published | View source on the page and read the Last Published comment Webflow writes into every page. If the timestamp predates your SEO change, the change is not live. | Publish to the custom domain, not just to staging. Webflow applies SEO settings on publish, so an unpublished fix is the same as no fix. |
| Indexing is disabled on the page or Collection template | Search the live page source for a robots meta tag containing noindex. On a Collection, check the template page rather than one item. | Turn the setting off in page settings and republish. On a Collection template it affects every item at once, which is why this cause is usually large rather than small. |
| Staging .webflow.io is competing with your domain | Fetch yoursite.webflow.io/robots.txt. We checked a live Webflow staging site on 6 September 2026 and it returns User-agent: * and Disallow: /. | A robots.txt block stops crawling, not indexing. Google says do not use robots.txt to block a page. Remove inbound links to staging and use Search Console removals if a staging URL has already surfaced. |
| Sitemap is off, or robots.txt blocks a folder | Fetch yourdomain.com/sitemap.xml and yourdomain.com/robots.txt. A Webflow site with no robots.txt configured returns a 404 there, which is fine. A Disallow line matching your pages is not. | Enable auto-generate sitemap in site settings, publish to the custom domain, then submit the sitemap URL in Search Console. Remove any Disallow rule covering pages you want indexed. |
| Google crawled the CMS item and declined it | URL Inspection says Crawled, currently not indexed. The URL has a crawl date and is still not in the index. | Editorial, not technical. A Collection template that renders near-identical items is the usual reason. Resubmitting a declined URL changes nothing, because the input did not change. |
Why is my Webflow site not showing up on Google?
If the whole site is missing rather than a few pages, start with publishing rather than with SEO. Webflow applies site and page settings when you publish, which means a correct setting sitting in the Designer does nothing at all until you push it live, and publishing to staging only is not the same as publishing to your custom domain. This trips up more launches than any other cause because the site looks finished to everyone who opens it.
Webflow makes this unusually easy to verify, and the trick is worth knowing. Every page Webflow serves carries an HTML comment near the top of the source recording exactly when that page was last published. Open the live page, view source, and read the timestamp. We fetched three live Webflow sites on 6 September 2026 and found timestamps ranging from 2017 to two days earlier, all of them sitting in plain sight in the markup. If that date is older than the SEO change you made, you have found your problem without needing any tool at all.
The second thing to rule out is that the site is genuinely new. Google says it automatically looks for sites to add to its index and that you usually do not need to do anything except post your site on the web, but it also warns that it can take a few weeks for Google to notice a new site. A few weeks is normal and worth waiting out. Two months with a submitted sitemap and a few inbound links is not, and that is worth diagnosing properly.
Only after both of those should you start looking at individual pages. Buying an indexing tool to solve an unpublished setting is the most avoidable purchase in this category, and we would rather tell you that here than sell you a subscription that cannot help.
- Read the Last Published comment in the live page source before anything else.
- Confirm you published to the custom domain, not only to the .webflow.io staging URL.
- Check the domain verified in Search Console is the one visitors actually reach.
- Allow a few weeks for a genuinely new site before treating slowness as a fault.
- Then, and only then, start diagnosing individual pages and Collection items.
Why are my Webflow CMS collection pages not indexed?
Because in Webflow a Collection is one template rendering many items, a single indexing setting applies to the entire Collection at once. Switch indexing off on the Collection template page and every blog post, case study, job listing or product built from that template stops being indexable together. There is no per item override to catch the mistake, no warning in the Designer, and the pages continue to render perfectly for human visitors. This is the single most expensive Webflow-specific indexing failure, and it almost always presents as a large round number of missing URLs rather than a handful.
The diagnostic is straightforward once you know to run it. Do not inspect one CMS item and conclude the Collection is fine, and do not rely on the Designer showing the toggle in the position you expect. Fetch a published item URL and search the returned HTML for a robots meta tag containing noindex. If it is there, the template is the source, because every item inherits from it. Google is explicit about what that tag does: noindex means do not show this page, media, or resource in search results.
There is a subtler version of this that catches larger sites. Webflow lets you write conditional visibility and custom code into a Collection template, so a noindex can be emitted for some items and not others depending on a field value. When that happens the Collection looks healthy on the two items you spot checked and is quietly broken across a segment you never opened. The only reliable way to see it is to check every item URL rather than a sample, which is exactly the thing Search Console will not do for you once the list passes 1,000.
Worth separating from all of this: a Collection item that is missing because Google crawled it and declined it is not a settings problem and no toggle fixes it. Templated Collections are efficient precisely because every item shares a structure, and when the only thing that varies between items is a name and a number, Google frequently decides one of them is enough. That is an editorial problem, and it is the reason the distinction in the next section matters more than any submission feature.
- One Collection template controls indexing for every item built from it.
- Check the rendered HTML of a published item, not the Designer toggle.
- Custom code in a template can emit noindex for only some items.
- Google: noindex means do not show this page in search results.
- Check every item, not a sample, because Search Console caps its list at 1,000.
Is my webflow.io staging site hurting my SEO?
It can, and the mechanism is more awkward than most advice admits. We fetched a live Webflow staging site on 6 September 2026 and its robots.txt returned exactly two lines: User-agent: * and Disallow: /. Webflow blocks the staging subdomain from being crawled, which is sensible and is what most people assume solves the problem.
It does not, quite, because robots.txt controls crawling rather than indexing. Google can index a URL it has never fetched if it finds enough external signals pointing at it, which is why a staging URL that someone linked in a Slack message, a client email that got published, or a forum post can appear in search results as a bare URL with no snippet. Google is direct about this in its own documentation on removing content: do not use robots.txt as a way to block your page.
The trap is what happens when you try to fix it the obvious way. Adding a noindex tag to the staging site cannot work while the disallow is in place, because Google says these settings can be read and followed only if crawlers are allowed to access the pages that include them. A blocked page is never fetched, so the noindex is never seen, and the URL stays exactly where it is. To clear it properly you either unblock the URL so the noindex can be read and then re-block it afterwards, or you use the Search Console removals tool, which Google says lasts about six months and therefore buys time rather than solving anything.
In practice the fix that sticks is removing the inbound links that made Google aware of the staging URL in the first place, and then confirming the staging URLs are actually out of the index rather than assuming. That confirmation step is worth automating on any site where staging and production run in parallel for months, because the failure is silent: nothing in Search Console for your real domain tells you that a .webflow.io copy of your homepage is sitting in the results next to it.
- Verified 6 September 2026: a live .webflow.io site serves User-agent: * and Disallow: /.
- robots.txt blocks crawling, not indexing. Linked URLs can still be indexed.
- Google: do not use robots.txt as a way to block your page.
- A noindex on a blocked URL is never read, so it has no effect.
- Removals last about six months, so treat them as time bought, not a fix.
Crawled currently not indexed on a Webflow CMS, and why resubmitting does not help
Once a Webflow site passes a few hundred CMS items, some proportion will come back as Crawled, currently not indexed, and it is worth understanding what that status means before treating it as a fault. Google fetched the page, read it, and decided not to include it. That is a judgment about the page, not a queue you are waiting in.
On a templated CMS the usual reason is that the items are too alike. A Collection built to render a location, a plan tier or a product variant produces pages whose structure is identical and whose content differs by a few fields. From Google's side that is a set of near-duplicate documents, and keeping every one of them serves nobody. There is no technical remedy. Adding real, differentiated content to the items that actually earn money is the remedy, and it works, which is why knowing which items are affected beats guessing.
The distinction that saves money is between this and Discovered, currently not indexed. Discovered means Google knows the URL exists but has not fetched it, which is a discovery and crawl capacity problem, and submission genuinely helps there. Crawled means the fetch already happened and the answer was no. Submitting a crawled and declined URL again is the most common way money gets wasted in this category, because the loop can run indefinitely while the page itself never changes.
One more thing worth watching on any site that publishes at volume: Google documents that its crawl limit goes down if a site slows down or responds with server errors, and that 5xx and 429 responses prompt its crawlers to temporarily slow down. Webflow hosting is generally fast, but heavy third party scripts, embedded widgets and large unoptimized assets all push response times up, and a site that gets slow can quietly reduce how much of its own content gets crawled. Keeping an eye on response times with basic uptime monitoring is cheap next to that, and from inside Search Console the two problems look identical.
- Discovered, currently not indexed: never fetched. Submission helps.
- Crawled, currently not indexed: fetched and declined. Submission does not help.
- Near-identical CMS items are the usual cause on a templated Collection.
- Differentiate the items with revenue attached, not all of them.
- Google says 5xx and 429 responses make its crawlers temporarily slow down.
Keep reading
- Crawled Currently Not Indexed Causes and Fixes Crawled currently not indexed means Google read your page but chose not to index it. Here are the real causes around quality and how to get the page indexed.
- How to Check if a URL Is Indexed at Scale How to check if a URL is indexed on Google at scale: the URL Inspection API, why the site: operator fails, and how to verify thousands of URLs without guessing.
- Excluded by Noindex Tag and How to Fix It (2026) Google crawled the page, found a noindex rule and left it out on purpose. The eight real causes, why the header version hides from view-source, and each fix.
- Best Index Monitoring Software for Small Business Search Console samples 1,000 URLs and lags three to four days. Four index monitoring tools compared for sites under a few thousand pages, with what each one misses.
Good questions
Questions about webflow indexing
Explore more
More ways teams get every page indexed
Stop guessing. Get every page indexed and keep it that way.
Bulk-submit your URLs through the official Google and Bing channels, monitor coverage, and resubmit anything that drops out, automatically. White hat only, so we speed discovery without ever guaranteeing what Google chooses to index.
Google Indexing API · Bing IndexNow · sitemaps · coverage monitoring · official methods only