Practical guideUpdated 2026-09-15

How to connect Webflow to Google Search Console and use the data

To connect Webflow to Google Search Console, add a Domain property for your root domain in Search Console, verify it with the DNS TXT record at your DNS provider, then submit Webflow's auto-generated sitemap at /sitemap.xml. Use the HTML tag method in Webflow's custom code settings only if you cannot edit DNS. Once verified, the Performance report shows which queries and pages get impressions, which is the input for deciding what to build next.

The query "webflow google search console" is one of the most common Webflow SEO searches, and the answer has a few Webflow-specific details around verification and sitemaps. This guide gives the recommended setup, the alternative when DNS is out of reach, the errors that appear most often, and a short method for turning Search Console data into a list of pages to build.

01

Choose the right property type

Search Console offers two property types. A Domain property, entered as example.com, covers every subdomain and protocol in one view and is verified by DNS. A URL-prefix property, entered as https://www.example.com/, covers only that exact prefix and can be verified by HTML tag, HTML file, Google Analytics, or Tag Manager. For a Webflow site, the Domain property is the better choice because Webflow sites commonly redirect between www and non-www, and a URL-prefix property for the wrong variant shows almost no data.

02

Verify with DNS (recommended)

In Search Console, add a Domain property and copy the TXT record it provides. Add that TXT record at your DNS provider, which is wherever your domain's nameservers point: Cloudflare, your registrar, or Webflow if you use Webflow DNS. Propagation is usually minutes but can take longer; click Verify after a short wait. This method does not require any change in Webflow and survives redesigns and republishes.

Webflow verification methods compared
MethodProperty typeWhere you add itBest for
DNS TXT recordDomainYour DNS providerEveryone who can edit DNS; covers all variants
HTML tagURL-prefixWebflow site settings, custom code, headWhen DNS is not accessible
Google Analytics or Tag ManagerURL-prefixExisting GA or GTM snippet in WebflowSites already running GA/GTM with edit rights
HTML file uploadURL-prefixNot practical on WebflowAvoid
03

Verify with the HTML tag (fallback)

If you cannot edit DNS, add a URL-prefix property for the exact canonical form of your site, for example https://www.example.com/, choose the HTML tag method, copy the meta tag, and paste it into Webflow under Site settings, Custom code, Head code. Publish the site, then click Verify. Remember that this verifies only that prefix; if your site later changes from www to non-www, you will need a new property.

04

Submit the Webflow sitemap

Webflow generates a sitemap when the auto-generate option is enabled under Site settings, SEO. It lives at /sitemap.xml and includes static and collection pages that are not excluded. In Search Console, open Sitemaps, enter sitemap.xml, and submit. The report should show Success and a discovered URL count close to your page count. If you also serve pages beside Webflow on the same domain, for example generated pages routed through a Cloudflare Worker, submit that second sitemap as well; SerionFlow maintains one for its live pages.

05

Common problems and fixes

No data in a URL-prefix property: it was created for the wrong www or protocol variant; add a Domain property instead. Sitemap "Couldn't fetch": the auto-generate option is off or the site has not been republished since enabling it. Pages "Crawled, currently not indexed": usually thin collection variants or pages with identical metadata; fix content and bindings before requesting indexing. Verification lost: a DNS change removed the TXT record, or the custom code was cleared; re-add and re-verify.

  • Wrong variant: switch to a Domain property.
  • Sitemap not found: enable auto-generate and republish.
  • Not indexed: fix thin or duplicate collection pages.
  • Verification lost: restore the TXT record or meta tag.
06

Turning the data into a page plan

Open Performance, set 90 days, and enable average position. Filter to queries at positions 11 to 40 with impressions, then add the page dimension to see which Webflow page Google shows for each. Every query where the ranking page is only loosely related is a page to build; every query where the page fits is a page to improve. Sites that want this loop to run automatically can connect Search Console to a platform that reads it weekly; SerionFlow uses it to recommend new pages, metadata rewrites, internal links, and refreshes per project.

Step by step

  1. 01

    Add a Domain property

    In Search Console, choose Domain, enter your root domain without protocol or www, and copy the TXT record.

  2. 02

    Add the TXT record

    At your DNS provider, add the TXT record on the root domain, wait a few minutes, and click Verify.

  3. 03

    Enable the Webflow sitemap

    In Webflow Site settings under SEO, turn on auto-generated sitemap and publish the site.

  4. 04

    Submit the sitemap

    In Search Console Sitemaps, submit sitemap.xml and confirm the report shows Success with a plausible URL count.

  5. 05

    Check coverage after a week

    Open the Pages report and review any collection pages listed as not indexed for thin content or duplicate metadata.

  6. 06

    Build the page plan

    In Performance, filter queries to positions 11–40 with the page dimension and list the pages to build or improve.

Clear answers

Frequently asked questions

Which Search Console verification method is best for Webflow?

+

A Domain property verified by a DNS TXT record. It covers www, non-www, http, and https together and needs no change in Webflow. Use the HTML tag in Webflow's custom head code only when you cannot edit DNS, and remember it verifies a single URL prefix.

Where is the Webflow sitemap?

+

At /sitemap.xml on your domain, once auto-generation is enabled under Site settings, SEO, and the site is published. It includes static and collection pages that are not excluded. Submit that URL in Search Console's Sitemaps report.

Why does Search Console show no data for my Webflow site?

+

Most often the property is a URL-prefix for the wrong variant, such as non-www when the site redirects to www. Add a Domain property, which aggregates all variants. New properties also take a few days to accumulate data.

Can I connect Webflow to Search Console for pages served beside Webflow?

+

Yes. A Domain property covers every URL on the domain, including paths routed to another origin through a Cloudflare Worker. Submit each sitemap separately: Webflow's at /sitemap.xml and, for SerionFlow-served pages, the sitemap SerionFlow maintains for its live pages.

How do I use Search Console data to decide what to build on Webflow?

+

Filter Performance to 90 days, positions 11 to 40, with the page dimension. Queries where the ranking page is loosely related need a new page; queries where it fits need improvement. Platforms that read Search Console weekly, such as SerionFlow, can generate these recommendations per project.

Continue exploring

Related SerionFlow resources

More in Guides

All guides

Make the next move obvious

Let SerionFlow turn your market evidence into momentum.

Confirm the market, rank the opportunities that matter, create brand matched pages on your domain, and keep moving with controlled weekly intelligence.

Choose how SerionFlow uses cookies.

Essential cookies keep the site secure and working. Product analytics helps us improve reliability. Optional cookies help us remember preferences and improve campaigns. You can change optional cookies anytime in Cookie Settings.