Customer Impact

Website & Development

Webflow SEO: the complete checklist for a findable B2B website

Copy for AI

You handle Webflow SEO largely inside the Webflow interface itself.

Meta titles, slugs, redirects, sitemap and even a schema field sit in the page and site settings. You don’t need a plugin.

The verdict: Webflow gives you clean SEO fields, but it doesn’t fill them in for you. The gain isn’t in “turning Webflow on”, it’s in the choices you make per page.

The platform takes sitemap generation, responsive images and CDN hosting off your plate by default.

This checklist shows where to find each setting, what Webflow does automatically, and where the manual work begins.

Want the bigger picture of a findable B2B site? Read the B2B website development guide first. This page zooms in on the technical SEO settings within Webflow.

What exactly is Webflow SEO?

Webflow SEO is the whole of settings and choices that make a Webflow site crawlable, understandable and fast for search engines.

Built in, not bolted on

The big difference with WordPress? No separate SEO plugin.

The core settings are built into the Designer and the site settings.

That’s where you’ll be working:

Webflow homepage presenting its visual website platform, where Webflow SEO settings are built into the Designer and site settings Webflow’s homepage, October 2026.

A strength and a pitfall

Strength: you depend less on plugins that contradict each other or slow your site down.

Pitfall: “built in” doesn’t mean “filled in well automatically”. Webflow gives you clean fields, but you still decide what goes in them.

Here’s the split at a glance:

WEBFLOW SEO CHECKLIST What Webflow does vs what you do Webflow does it You set it per page Sitemap rebuilt on publish Meta title and description Responsive images via CDN Slugs and URL structure Lazy loading below the fold 301 redirects (paid plan) Schema markup (paid plan) Content and focus stay yours.

Our angle: forget the green score in a tool.

Steer toward being found by the right B2B buyer, and turning them into a lead.

Does the platform itself hold you back? Read is Webflow good for SEO.

How do you set meta titles and descriptions in Webflow?

Open the page settings and scroll to the SEO section.

That’s where the meta title and description live.

Static pages

Each static page gets its own. Make every one unique.

Tip: write the title keyword-first and keep it short enough not to get cut off in the search results. Our guide on how to write a good meta title covers the length, and the SERP snippet preview shows how it’ll look.

CMS collections

CMS collections work differently. Think blog articles or service pages.

In the collection template settings you can bind the meta fields to CMS fields.

Webflow then pulls the item name or a summary field into the meta title and description, for each item separately.

For example, say your blog has 200 articles. One template setting then gives you 200 unique meta titles. That saves an enormous amount of manual work.

Our guide to the Webflow CMS explains how collections and templates fit together.

AI-generated metadata

Webflow also added AI to fill in missing metadata. Useful, but limited.

Watch out: treat that as a starting point, not a finished product. An AI-generated meta description often lacks the sharp hook that gets a B2B buyer to click.

Open Graph

Don’t forget Open Graph. It’s in the same panel.

It decides how your pages look when they’re shared on LinkedIn or in a newsletter.

In B2B that’s often the first point of contact.

How do you get clean slugs and URL structure?

You set the slug per page in the page settings.

For CMS items you use the slug field of the collection item.

What a good slug looks like

Keep slugs short. Make them descriptive. Include your main term.

For example, /services/webdesign instead of a vague or automatically generated string.

Two things that hurt later

Watch out for two things that hurt later if you ignore them now:

  1. Changing slugs: don’t change them lightly once a page is indexed. You’d break existing links and rankings.
  2. Folder structure: think about it in advance, because it shapes how logically your site is built.

A well-considered structure helps both visitors and search engines, as we explain in website architecture and SEO.

In Webflow you set the hierarchy partly through folders and partly through the structure of your CMS collections.

How do you set up 301 redirects in Webflow?

You manage 301 redirects under Site settings > Publishing > 301 redirects.

There you fill in the old path and the new destination.

You need a paid plan

Check your plan first. Webflow’s help center says redirects need a paid Site plan or a paid Workspace plan.

So a free Starter site can’t use them.

Our overview of Webflow pricing shows which plan you need.

Keep it under 1,000 rules

There’s no hard limit on the number of redirects.

But Webflow recommends 1,000 at most, because every rule is added to a file that visitors’ browsers download.

Use wildcard redirects where you can.

Watch out: redirects don’t apply to localized subdirectories automatically. /old-url and /es/old-url each need their own rule.

Bulk import via CSV

Webflow supports bulk import and export of redirects via a CSV file (up to 16MB).

That makes a larger restructure workable.

Why redirects matter

Redirects aren’t a detail. They’re your insurance against ranking loss.

If you change your URLs or migrate to Webflow, a correct set of 301s keeps built-up authority from evaporating.

Read how to handle that in our guide on website migration without losing rankings, or plan it with a 301 redirect plan.

Tip: after publishing, test a few old URLs with our redirect checker.

What does Webflow handle automatically (sitemap and speed)?

Some fundamentals run on autopilot. Here’s which.

The sitemap

Turn on the auto-generated sitemap under Site settings > SEO. From then on, Webflow rebuilds sitemap.xml every time you publish.

It includes:

  • a lastmod date per URL
  • hreflang tags if you use Localize

You can then disable indexing per static page with a toggle.

For example, a thank-you page you don’t want in the index. More on the format in how to create an XML sitemap.

Two indexing settings to check

The same SEO tab holds two settings people forget:

  • Staging (subdomain) indexing: keep your webflow.io staging copy out of Google, so it doesn’t compete with your real domain. This needs a paid plan.
  • robots.txt: a custom field where you write your own crawl rules.

Keep robots.txt simple. One rule for all crawlers plus the sitemap line is often enough:

The robots.txt file of customerimpact.be with one rule that allows every crawler plus the sitemap line, an example of a simple robots.txt to set in Webflow SEO settings Our own robots.txt, October 2026: one rule for all crawlers, plus the sitemap line.

Speed out of the box

Speed gets a head start too:

  • uploaded images are served via a global CDN
  • responsive variants are delivered via the srcset attribute
  • you can convert images to WebP or AVIF in the Assets panel
  • images below the fold are lazy loaded

A baseline, not a free pass

That’s a good baseline. It’s not a free pass.

These can still drag down your Core Web Vitals:

  • an overly heavy hero image
  • too much custom code
  • heavy external scripts

Compress images before you upload them. Watch your page weight.

Our guide to optimizing images for your website shows how.

If you want to measure where it pinches, a PageSpeed report like this one points to the exact element:

PageSpeed Insights LCP breakdown showing the LCP element is the H1 heading with an element render delay of 2,370 ms, the kind of speed check to run on a Webflow site PageSpeed Insights for our own largest contentful paint article, October 2026. The H1 in the first screen is the LCP element.

Our explainer on Google Lighthouse helps you read that report.

Connect Search Console

Finally, connect your site to Google Search Console to monitor indexing and sitemap status.

That’s not a Webflow setting. But it’s where you see whether all your work is actually being picked up:

Google Search Console performance report for customerimpact.be with 1.53K clicks and 1.21M impressions over 28 days, the report to check after Webflow SEO changes Our own Search Console for customerimpact.be, last 28 days, October 2026. Clicks and impressions show whether your settings are paying off.

How do you add schema markup in Webflow?

You add schema markup (structured data that helps search engines understand your content) in two ways:

The schema field

The field needs a paid Site plan, and Webflow AI can generate a first draft for you.

Watch out: check that draft with the Schema Markup Validator before you trust it. This is what a clean result looks like:

Schema Markup Validator result for the customerimpact.be English homepage listing the detected structured data types, the check to run on Webflow schema markup The Schema Markup Validator on our own English homepage, October 2026. Check that each detected type matches what the page visibly says.

Our guide to schema markup testing covers the other validators.

Schema on CMS templates

On CMS templates, schema scales.

You bind CMS fields into your JSON-LD, in the schema field or a code embed.

Every collection item then gets its own correct structured data, without filling it in manually per item.

Limit: reference, multi-reference and multi-image fields can’t be bound in the schema field.

That’s how you build scalable markup for a blog or a service overview.

We explain the principles behind it, independent of the platform, in schema markup and structured data.

When is Webflow the right choice for your B2B site?

Webflow is a strong choice when you want a marketing-driven site with a lot of design control and a clean SEO baseline without plugin bloat.

Where Webflow excels

It excels for teams that publish landing pages and content often.

They steer visually. No developer needed each time.

Where it isn’t an automatic winner

Some things that are built in elsewhere require custom code or a paid plan in Webflow.

And not every team feels at home in the Designer.

Our guide to Webflow CMS limits lists where teams hit the ceiling.

Platform-agnostic by choice

We’re platform-agnostic: we build in Webflow, WordPress and custom or headless.

Our experience: WordPress, Drupal, Webflow and Joomla all used to be really good choices. Today it depends on the company, and digital-native teams increasingly move to custom, agentic websites without plugin updates.

Which one fits depends on your team, your content volume, your budget and your growth plans, not on the platform itself.

Your situationLikely fit
Marketing team publishes landing pages oftenWebflow
Team already runs WordPress and its pluginsCompare before you move
Digital-native team, fast updates, languages built programmaticallyCustom or agentic

You’ll find a comparable checklist for another stack in WordPress SEO, and a head-to-head in Webflow vs WordPress.

Leads decide, not the platform

Any platform can get the settings right.

The difference is whether the site is aimed at leads.

That’s why we build conversion-focused websites that turn visitors into inquiries.

The short summary

Webflow gives you the SEO fundamentals built in:

  • meta and slugs per page
  • redirects on a paid plan
  • an automatic sitemap
  • optimized images via CDN
  • a schema field for structured data

Webflow handles the tedious work.

The input, the structure and the focus on the right buyer stay your job.

Decision rule: a technically clean site that isn’t aimed at leads is still a missed opportunity.

Want to know whether Webflow fits your growth plans? Contact us and we’ll check your current setup against this checklist.

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.