Webflow sitemap and indexing: settings that decide what Google sees

Google can only show pages it has indexed (added to its index, the library it answers from), and the AI answers built on its results draw from the same pool. This guide, part of our platform indexing guides, covers the sitemap, Search Console, Bing, IndexNow, robots.txt and noindex, staging and canonical gotchas, and a checklist, with menu paths from Webflow's help center as of October 2026.

Where does Webflow put your sitemap?

Webflow puts your sitemap at /sitemap.xml on each domain you publish to, once Auto-generate sitemap is on. Its help center says the feature "automatically generates a sitemap.xml for your site and updates it each time you publish your site" (Webflow: Create a sitemap). To turn it on, as of October 2026: Site settings → SEO tab → Sitemap section, set Auto-generate sitemap to Yes, click Save changes, then publish.

What the same page says:

• <lastmod> is the publish time. Each URL's lastmod shows "the date and time that page was last published," but you have to republish the site before a new timestamp appears.
• Localized sites get hreflang tags for every static and dynamic page in the auto-generated sitemap.
• You can paste your own. Set Auto-generate sitemap to No and paste XML into the Custom sitemap.xml field. With Localize on, you then add hreflang tags yourself.
• It can't be deleted. "It isn't possible to delete the /sitemap.xml page once you've created your sitemap and published your site."
• robots.txt gets the Sitemap line automatically. Add it again by hand and the file "will contain 2 sitemaps." Removing the default line with the Remove sitemap.xml from robots.txt toggle needs a paid Site plan.

We fetched Webflow University's live files (university.webflow.com, a Webflow-hosted site) on October 17, 2026. Its robots.txt held a single line, the automatic one:

Sitemap: https://university.webflow.com/sitemap.xml

The sitemap listed 1,316 URLs, each with only <loc> and a timestamped <lastmod> such as 2026-10-16T20:07:21.958Z, and no <priority> or <changefreq>. That suits Google, which says it "ignores <priority> and <changefreq> values" and uses lastmod when it's "consistently and verifiably" accurate (Google Search Central: build a sitemap).

One setting matters if you serve Webflow through a reverse proxy: Webflow's proxy guide has you turn on Use your global canonical URL as the base URL for each sitemap.xml entry, so the sitemap lists your public domain rather than the origin subdomain (Webflow: self-managed reverse proxy).

How do you connect Webflow to Google Search Console?

You connect Webflow to Google Search Console by adding a URL-prefix property in Search Console, choosing the HTML tag method, and pasting the ID into Webflow's Google site verification field (Webflow: Google site verification). The steps as of October 2026:

1. In Search Console, enter your domain with https:// (for example https://www.yourdomain.com) as a URL prefix property and click Continue.
2. Under Other verification methods, choose HTML tag and copy the value after content=. Keep the window open.
3. In the Webflow dashboard, click the three dots on your site's thumbnail, then Settings → SEO tab → Google site verification.
4. Paste the ID in the Google site Verification ID field, click Save changes and publish.
5. Back in Search Console, click Verify.

If you verified the domain before moving to Webflow, paste your existing ID in, or "Google may stop detecting the verification ID."

Alternatively, Webflow's Google site tools for Webflow app connects Search Console, Analytics and Tag Manager (click Add to site, sign in, confirm your Search Console domains); only Designer or Marketer roles can install it (Webflow: Connect Google site tools).

Then submit sitemap.xml in Search Console's Sitemaps report, and use the URL Inspection tool for individual new pages.

How do you connect Webflow to Bing Webmaster Tools?

The quickest way to connect a Webflow site to Bing Webmaster Tools is to import it from Search Console once Google has verified it. Bing says imported sites "will be added and get automatically verified," and it keeps importing new sitemaps it finds in your Search Console account (Bing Webmaster Tools help).

To verify by meta tag instead, add Bing's <meta> tag through Webflow's site-wide head code: Site settings → Custom code tab → Head code, then Save changes and publish (Webflow: Custom code in head and body tags). Custom code needs a Core, Growth, Agency or Freelancer Workspace or an active Site plan. Then submit your sitemap in Bing's Sitemaps tool. Our Bing Webmaster Tools guide covers the rest of the console.

Does Webflow support IndexNow?

No. As of October 2026 Webflow has no IndexNow setting or help article. IndexNow (an open "this page changed" notice that Bing and other participating engines accept; Google doesn't use it) needs a key file "at the root directory of your website" or "in other locations within the same host" (IndexNow documentation). Webflow documents root-level settings for robots.txt, sitemap.xml and llms.txt (Site settings → SEO → LLMs.txt), but none for other files, so there's no supported place for a key file.

Your options for Bing:

Bing calls IndexNow "Strongly Recommended" and says URL Submission "may be deprecated in the future as IndexNow adoption expands" (Bing: URL submission). See how to submit URLs to Bing by hand.

If you do run a proxy, Webflow's lastmod tells you what changed. Webflow's site_publish webhook reports the published domains and whether a whole site or one page went out, not a list of URLs (Webflow developer docs), so reading the sitemap is the simplest way to find changed pages. We wrote and ran this script on October 17, 2026:

# changed_since.py: URLs whose Webflow <lastmod> is after a cutoff,
# plus the IndexNow JSON body you'd POST for them (not sent).
import json, sys, urllib.request, xml.etree.ElementTree as ET
from datetime import datetime, timezone

sitemap, since = sys.argv[1], datetime.fromisoformat(sys.argv[2]).replace(tzinfo=timezone.utc)
ns = {"sm": "http://www.sitemaps.org/schemas/sitemap/0.9"}
req = urllib.request.Request(sitemap, headers={"User-Agent": "Mozilla/5.0"})
root = ET.fromstring(urllib.request.urlopen(req, timeout=30).read())
changed = []
for url in root.findall("sm:url", ns):
    loc, lastmod = url.findtext("sm:loc", namespaces=ns), url.findtext("sm:lastmod", namespaces=ns)
    if lastmod and datetime.fromisoformat(lastmod.replace("Z", "+00:00")) > since:
        changed.append(loc)
print(f"{len(root.findall('sm:url', ns))} URLs in sitemap, {len(changed)} published after {sys.argv[2]}")
host = sitemap.split("/")[2]
print(json.dumps({"host": host, "key": "<your-key>", "keyLocation": f"https://{host}/<your-key>.txt",
                  "urlList": changed[:3] + (["..."] if len(changed) > 3 else [])}, indent=2))

Run as python3 changed_since.py https://university.webflow.com/sitemap.xml 2026-10-10, it reported 1,316 URLs, 31 published after October 10, 2026. We didn't send the body, since only the site owner can host the key.

FreshlyCited has the same requirement: its IndexNow sending needs the key on your host, so for a standard Webflow site it covers Google only. Our IndexNow explainer covers the protocol in full.

What can you control in Webflow's robots.txt and noindex settings?

Webflow gives you a robots.txt editor, bot traffic toggles and a per-page noindex toggle. Robots.txt controls crawling (a bot's visit to read a page); the Sitemap indexing toggle controls indexing.

The robots.txt editor

You edit robots.txt under Site settings → SEO → Indexing: add rules, click Save and publish (Webflow: Set robots.txt rules). Two things to know, as of October 2026:

• It can't be fully removed. Webflow says "Once the robots.txt has been created, it can't be completely removed," so to undo blocks you replace them with User-agent: * and an empty Disallow: (Webflow: Disable search engine indexing).
• Your CDN assets aren't covered. Webflow serves assets from its CDN, not your domain, so a robots.txt on your domain can't keep them out of search.

The same Indexing section holds Traffic control toggles that write robots.txt rules for groups of known bots: one for search engine crawlers (Googlebot, Bingbot, OAI-SearchBot and others) and one for AI bots (GPTBot, ClaudeBot, PerplexityBot, ChatGPT-User and others). Both are on by default, and Webflow warns that blocking them "may also reduce your site's visibility in traditional and AI-powered search experiences." Check what each one does in our AI crawlers directory first.

Webflow can also send a Content-Signal line (for example ai-train=no, search=yes, ai-input=no), which it notes is "not yet an accepted standard." Webflow's own robots.txt, fetched on October 17, 2026, used it:

User-agent: *
Content-Signal: ai-train=yes, search=yes, ai-input=yes

For how robots.txt groups and stacked rules work in general, see our WordPress robots.txt guide.

The Sitemap indexing toggle (noindex)

The Sitemap indexing toggle noindexes one static page and removes it from your sitemap: open the page's Page settings → SEO settings, switch Sitemap indexing off and publish. Webflow says it "adds <meta content="noindex" name="robots"> to your site page" (Webflow: Disable search engine indexing). It only works when the auto-generated sitemap is on.

Noindexed pages show in Search Console as Excluded by 'noindex' tag, which is correct for pages you hid on purpose. Google's condition applies: "For the noindex rule to be effective, the page or resource must not be blocked by a robots.txt file" (Google Search Central: block indexing).

What Webflow gotchas affect indexing?

The Webflow gotchas that cost indexing are the public staging subdomain, a canonical URL that doesn't match your default domain, and robots.txt used where noindex was needed.

The webflow.io staging subdomain

Every Webflow site can be published to a staging subdomain such as yoursite.webflow.io, and search engines can index it unless you switch Staging indexing off. Go to Site settings → SEO → Indexing, set Staging indexing to off, click Save and publish. Webflow says this publishes "a unique robots.txt only on the subdomain," and it needs a Site plan or paid Workspace (as of October 2026).

We fetched the webflow.io staging subdomains of three live Webflow sites, including Webflow University's, on October 17, 2026. All three served this robots.txt with an X-Robots-Tag: noindex header:

User-agent: *
Disallow: /

Their staging homepages also carried a canonical tag pointing to the live domain, and one added <meta name="robots" content="noindex, nofollow">. The catch: once robots.txt blocks the subdomain, Google can't fetch those pages to see the canonical or noindex. If staging URLs were indexed before you switched the setting, they can linger as Indexed, though blocked by robots.txt. Webflow's advice for already-indexed pages: "don't add it in the robots.txt," and use Google's removals tool instead.

Default domain and global canonical

Webflow redirects every connected domain to your default domain, set in Site settings → Publishing → Production → Make default; Quick connect sets the www subdomain as default (Webflow: Set a default domain). Then set Site settings → SEO → Global canonical tag URL to that same base URL, with the protocol and without a trailing slash, which "will include double slashes" in every subpage's canonical (Webflow: Set canonical tags). Don't also inject canonicals through Google Tag Manager: two canonical tags "search engines may ignore entirely."

Without a clear canonical, parameter URLs and www or non-www copies can show up as Duplicate without user-selected canonical, Google's status for a duplicate where you declared no preferred version.

If those fixes have just freed up pages that matter, check which of your Webflow pages Google has indexed rather than waiting to find out.

How do you check your Webflow pages are indexed?

You check your Webflow pages are indexed by confirming your settings, submitting the sitemap to Google and Bing, then inspecting the pages that matter:

1. Sitemap on: yourdomain.com/sitemap.xml lists your key pages after your latest publish.
2. Staging closed: yoursite.webflow.io/robots.txt shows Disallow: /.
3. One domain, one canonical: default domain and Global canonical tag URL match exactly.
4. No accidental noindex: Sitemap indexing on for pages you want found, and nothing blocks Googlebot or Bingbot.
5. Google verified, with sitemap.xml submitted in Search Console.
6. Bing connected by import or meta tag, with the sitemap submitted.
7. Key pages requested: after publishing a new or updated page, inspect it and request indexing. Google says "Crawling can take anywhere from a few days to a few weeks" (Google Search Central: ask Google to recrawl).
8. Results read in the Page indexing report; our guide to Search Console's indexing statuses explains each one.

For more than a few URLs, FreshlyCited checks each one against Google ("Seen by Google" or "Invisible"), pushes only the invisible ones and re-checks on days 1, 3 and 7. If a link still isn't indexed after day 7, its credit comes back (exclusions apply, such as pages that return an error or carry noindex). Google still decides what it indexes.

Just published on Webflow? Check your Webflow pages free: 10 free links to try, then 100 free checks a month, no card needed.