Webflow does a lot of SEO groundwork for you: clean HTML, fast hosting, SSL and an automatic sitemap. But the settings that decide whether your pages actually get indexed and rank are scattered across site settings, page settings, CMS collections and the Assets panel, and several of them default to something you would not choose. This Webflow SEO checklist walks through every setting that matters, in the order I check them on a new or inherited site.
Webflow renames tabs and moves panels from time to time, so I describe what each setting does as well as where it usually lives. If a label looks slightly different on your screen, the principle still applies.
Is Webflow good for SEO?
Yes, with a caveat. Webflow handles the technical basics well: semantic HTML elements, responsive images, hosting on a CDN, HTTPS by default and full control over titles, descriptions, slugs and redirects without plugins. That removes a whole class of problems that slow, plugin-heavy sites suffer from.
What Webflow cannot do is decide your site structure, write pages that answer real questions or earn links and reviews. Those still determine most rankings. Good Webflow SEO is about using the settings properly and then getting out of the way of the content.
Webflow SEO vs WordPress
| Webflow | WordPress | |
|---|---|---|
| Hosting and speed | Included, CDN-backed, little to tune | Depends on host, theme and plugins |
| SEO fields | Built into page and CMS settings | Usually via an SEO plugin |
| Redirects | Built into site settings | Plugin or server rules |
| Schema markup | Custom code, with CMS fields inserted on templates | Plugins generate much of it automatically |
| Maintenance risk | Low: no plugin updates | Higher: updates, conflicts, security |
| Very large content sites | Workable, within CMS plan limits | More flexible at scale |
For a fuller comparison of the two for business sites, see Elementor vs Webflow, and for the wider picture including Shopify and Wix, which website platform suits a small business.
Site-wide settings
Start the Webflow SEO checklist here. These settings live in Site settings, mostly under the SEO tab and the publishing (domains and hosting) section. Get them right once and every page benefits.
-
Set the default domain.
Connect your custom domain and choose one version, usually
wwwor the bare domain, as the default. Webflow then redirects the other version to it, so search engines see one site rather than two. -
Stop the staging subdomain being indexed.
Every Webflow site also lives on a
webflow.iosubdomain. Use the setting that disables indexing of the Webflow subdomain, so the staging copy does not compete with your real domain. Check it on any site you inherit. -
Turn on the auto-generated sitemap.
With it on, Webflow rebuilds
sitemap.xmlon every publish, CMS items included. Submit/sitemap.xmlin Google Search Console once the domain is live. -
Review robots.txt.
The SEO tab has a robots.txt field. Leave it short. A common leftover from development is
Disallow: /, which blocks crawling of the whole site. Never use robots.txt to remove pages from Google; usenoindexinstead. -
Set the global canonical URL.
Enter your preferred domain, including
https://, in the global canonical tag field. Webflow then adds a self-referencing canonical to each page, which helps consolidate duplicate URL variations. -
Verify Search Console.
Use the Google site verification field, or verify through DNS at your domain registrar. DNS verification covers every version of the domain and survives redesigns.
-
Switch on minification.
The advanced publishing options include minifying HTML, CSS and JavaScript. Turn them on and test the site after publishing.
Page settings for static pages
Open the settings for each page (the cog next to the page name in the Pages panel) and work through these Webflow SEO settings:
- Slug: short, lowercase, hyphenated, descriptive.
/emergency-plumber-leeds, not/page-7. Decide slugs before launch; changing them later means redirects. - Title tag: unique per page, roughly 50–60 characters, main topic near the start. Do not leave the page name as the title.
- Meta description: a specific summary that earns the click. Google may rewrite it, but a good one is often used.
- Open Graph: title, description and image for social sharing. Use the option to copy the SEO values if you do not want to write them twice, and set an image for every important page.
- Noindex where needed: thank-you pages, internal campaign duplicates and thin utility pages can take a
<meta name="robots" content="noindex">tag in the page’s custom head code, and should be excluded from the sitemap. - Headings: one H1 per page, set as the Heading element’s tag, then H2 and H3 in order. Webflow makes it easy to style an H2 to look like an H1; choose tags for structure and classes for looks.
Check this first on any inherited site: pages duplicated during design often keep the original page’s title and description, so you end up with five pages called “Home”. Go through the Pages panel one page at a time before you look at anything else.
CMS collections and template pages
Blog posts, services, locations and case studies usually live in the CMS, and each item gets its page from one collection template. That makes CMS templates the most efficient place for Webflow SEO optimisation: fix the template once and every item is fixed.
- Bind SEO fields to CMS fields. In the template page’s settings, set the title and meta description from fields such as Name or a dedicated “SEO title” and “Meta description” field. Add those fields to the collection so editors can write proper ones instead of relying on the post name.
- Bind the Open Graph image to the main image field.
- Choose the collection URL carefully. Items live under the collection’s path, for example
/blog/post-slugor/services/service-slug. Changing the collection path later changes every item URL at once. - Make sure the H1 is the item name (or an SEO heading field), not a static “Blog” heading repeated on every post.
- Use rich text headings properly. Editors should use H2 and H3 inside rich text fields rather than bold paragraphs.
- Handle draft and archived items. Archived and draft items are not published, so if an item that once ranked is archived, redirect its URL to the most relevant live page.
Webflow 301 redirects
Redirects live in the site settings publishing section, as a list of old path and new path pairs. They are the setting most likely to save or lose rankings during a redesign or URL change.
- Add a redirect every time you change a page slug, a collection path or delete a page that had traffic or links.
- Redirect to the most relevant equivalent page, not the homepage.
- Use pattern-based redirects for whole folders when a structure changes. Webflow supports wildcard-style rules with capture groups; test them carefully, because a broad pattern can catch more than you intended.
- Avoid chains. If A redirects to B and B now redirects to C, update A to point straight to C.
- Republish after adding redirects, then test the old URLs in a browser or a header checker to confirm a 301 to the right page.
Moving to Webflow from another platform is where redirects matter most. The full process, including crawling the old site and mapping every URL, is in the website migration SEO checklist.
Images and performance
- Alt text: set it on the asset in the Assets panel, and override it on individual image elements where the context differs. Mark purely decorative images as decorative so they get an empty alt.
- Format and size: Webflow can convert uploaded images to modern formats such as WebP or AVIF from the Assets panel, and generates responsive versions automatically. Upload images at a sensible maximum size anyway rather than straight from the camera.
- Lazy loading: leave images below the fold on lazy load, but set the main above-the-fold image to load eagerly so it does not hold back the largest contentful paint.
- Interactions and embeds: heavy animations, Lottie files, video backgrounds and third-party scripts are the usual cause of a slow Webflow page. Remove what does not earn its place, and check Core Web Vitals in PageSpeed Insights and Search Console after changes.
Schema and local SEO
Webflow does not generate structured data for you in the way some WordPress plugins do, so schema goes in as JSON-LD custom code:
- Site-wide:
OrganizationorLocalBusinessmarkup in the homepage’s custom head code, with name, address, phone, URL and opening hours matching your Google Business Profile exactly. - CMS templates: on collection template pages you can insert CMS fields into the custom code, so each blog post can output
Articlemarkup and each FAQ item or service can output its own data. - Validate: test with Google’s Rich Results Test and the Schema Markup Validator before and after publishing.
Only mark up what is visible on the page, and keep it accurate. For service businesses, structured data works best alongside good location pages; local SEO for service area businesses covers how to build those without thin, duplicated content. Clear structure and schema also help AI search tools understand and cite your pages, which is covered in AI SEO for ChatGPT and AI Overviews.
After every publish
The last part of the Webflow SEO checklist is a short routine that keeps the site healthy:
- Spot-check new pages for unique titles, descriptions and a single H1.
- Confirm new pages appear in
/sitemap.xmland noindexed pages do not. - Test any URL you changed for a working 301.
- Use URL Inspection in Search Console on important new pages and request indexing.
- Review the Page indexing report monthly for pages Google has found but not indexed.
Mistakes to avoid
These are the problems I find most often when I run this Webflow SEO checklist on an inherited site:
- The
webflow.iostaging site left indexable alongside the real domain. - Duplicated pages sharing one title and description.
- CMS template titles left as the plain item name with no context.
- Changing slugs or collection paths without adding redirects.
- Every redirect pointed at the homepage.
- A
Disallow: /line left in robots.txt after launch. - Headings chosen for size, so the page has three H1s or none.
- Alt text missing on CMS images because the collection has no field for it.
- Animation and third-party scripts piled on until the “fast” Webflow site is slow.
Further reading: Google: redirects and Google Search · Google: canonical URLs · Google: sitemaps overview.
FAQ
Is Webflow good for SEO?
Yes, provided the settings are used properly. Webflow produces clean markup, includes hosting with SSL and a global CDN, generates a sitemap and lets you control titles, descriptions, slugs, redirects and canonical tags without plugins. What it cannot do is write useful content or fix a weak site structure for you, and those still decide most rankings.
Is Webflow SEO better than WordPress?
Neither platform ranks better by itself. Webflow gives you fewer moving parts, fast hosting and clean code out of the box. WordPress needs more care with plugins and hosting, but offers dedicated SEO plugins, deeper schema automation and more flexibility for very large content sites. A well-built site on either will rank; a neglected one on either will not.
How do I set up 301 redirects in Webflow?
Open Site settings, go to the publishing section where redirects live, enter the old path and the new path, save, and republish the site. Webflow supports pattern-based redirects for whole folders. Always test the old URL afterwards, check it returns a 301 to the right page, and avoid chains where one redirect points to another.
Does Webflow create a sitemap automatically?
Yes. With the auto-generate option switched on in the SEO settings, Webflow builds and updates sitemap.xml every time you publish, including CMS item pages. You can exclude individual pages and collections, or switch auto-generation off and paste a custom sitemap. Submit the sitemap URL in Google Search Console once the custom domain is live.
Want a second pair of eyes on your Webflow settings, templates and redirects before or after launch? See the Webflow and SEO services for what a Webflow SEO pass covers.