Webflow is a genuinely good platform for SEO. It ships clean, semantic HTML without hacks. Its hosting is fast. It handles responsive images automatically. If you've ever maintained a WordPress site with five conflicting SEO plugins fighting over the <title> tag, moving to Webflow feels like relief.
But Webflow has real SEO gaps — and if you don't know where they are, you'll assume everything is fine until you check your rankings and wonder what happened.
This guide maps all of it: the strengths, the gaps, and the six areas you need to nail on any Webflow site.
What Webflow Gets Right Out of the Box
Clean semantic HTML. When you add an H1 in Webflow's Designer, you get an actual <h1> in the DOM — not a <div class="heading-1">. Webflow's heading elements, paragraph elements, and list elements map directly to their HTML counterparts. For crawlers, this matters.
Fast hosting. Webflow sites run on AWS CloudFront CDN. Global edge delivery is included on every plan. You don't need to think about caching headers or CDN configuration. Your TTFB is going to be respectable from day one.
Responsive images with srcset. Upload an image to Webflow and it automatically generates multiple sizes and serves WebP where supported. The srcset attribute is added without any plugin or configuration. This is a real performance win that many platforms charge extra for or leave to the developer.
Auto-generated sitemap. Webflow publishes /sitemap.xml automatically, including all published pages and CMS collection items. New blog posts show up in your sitemap the moment you publish them.
SSL everywhere. HTTPS is on by default. There's no "force HTTPS" toggle to hunt for. This eliminates a whole category of mixed-content and canonical issues.
Per-page meta title and description. Every Webflow page has a dedicated SEO tab in Page Settings where you set the title and description. For CMS collections, you bind these to CMS fields using field tokens. More on that below.
Where Webflow Falls Short
Understanding the gaps is more important than knowing the strengths, because the strengths take care of themselves.
No built-in schema for content types. Webflow doesn't add Article, BlogPosting, Product, or FAQPage structured data automatically. If you want schema on your blog, you're adding it manually via Custom Code embeds or a per-page <script> tag. Webflow makes this possible — it just doesn't do it for you. See how to add schema markup to Webflow CMS collection pages for the full pattern.
OG and Twitter tags require Custom Code. Webflow's built-in SEO tab only covers <title> and <meta name="description">. Open Graph tags (og:title, og:image, og:description), Twitter card tags, and any other <head> meta tags need to be added in the Custom Code section of Page Settings. This is fine once you know about it — but it's a gap that catches a lot of site owners who assume social sharing previews are handled.
Lazy-loading on hero images can hurt LCP. Webflow applies loading="lazy" to images broadly. For images below the fold, this is correct. For hero images — the large image that loads in the viewport immediately — lazy-loading delays the browser from fetching it, which drags Largest Contentful Paint scores. The fix exists in Webflow's Designer, but you have to know to look for it.
Opinionated URL structure for CMS. Webflow's CMS collection slugs follow a pattern you control, but the collection URL prefix (e.g., /blog/) is set at the collection level and cannot be changed per-item. If you ever need to restructure your URLs, you'll need to set up redirects manually.
Redirect management is buried. Webflow supports 301 redirects, including basic wildcards, but the interface lives inside Site Settings → Publishing → Redirects — a location that's not obvious. There's no bulk redirect import from the Designer; you need to go through the Site Settings panel.
Staging sites are noindexed. Webflow's *.webflow.io staging domain blocks indexing by default. This is the correct behavior, but if you're doing pre-launch QA and want to check how pages appear in search preview tools, you need a published production site with a custom domain.
The Six Areas to Nail
Here's the framework. Each area links to a dedicated article with the specific Webflow UI steps.
1. The Full On-Page Checklist
If you want a single starting point, use the SEO checklist for Webflow sites. It covers 23 checkboxes organized by area — meta tags, headings, schema, images, sitemap, redirects, Core Web Vitals, and canonicals. It separates what Webflow handles automatically from what you have to add manually.
2. CMS On-Page SEO
If you're running a Webflow CMS blog or any collection with more than a handful of items, template SEO is where you get leverage. One template covers every collection item. Webflow CMS on-page SEO covers how to bind your meta title and description to CMS fields using the {{wf{...}}} field-token syntax, how to handle reference fields for author bios, and how to prevent duplicate content from filter and pagination URLs.
3. Meta Tags and Open Graph
Webflow's Page Settings SEO tab handles <title> and <meta name="description">. Everything else — OG tags, Twitter cards, and JSON-LD — goes in Custom Code. Webflow meta tags and OG tags has a complete copy-paste snippet for blog post pages with CMS field-token binding, plus the og:image URL gotcha specific to Webflow's CDN.
4. 301 Redirects
Redirects are essential for any site that's been live for a while and has changed URLs. Webflow 301 redirects covers the interface, the wildcard syntax, bulk CSV import format, and how to verify redirects actually work before you pull the trigger on a site migration.
5. Sitemap and Robots.txt
Webflow generates both automatically, but there are decisions you need to make: which CMS items to include or exclude from the sitemap, how to noindex specific pages, and whether you need a custom robots.txt override. Webflow sitemap and robots.txt covers the defaults, the overrides, and the staging-site noindex behavior.
6. Image SEO and Core Web Vitals
This is where most Webflow sites have hidden performance debt. Webflow image SEO and Core Web Vitals covers the lazy-loading LCP issue, how to fix it in the Designer, alt text patterns for CMS images, and what a passing LCP score actually requires.
How to Prioritize
If your site is brand new, work through the SEO checklist first. It'll tell you everything that needs to be in place before you start expecting traffic.
If your site has been live and you're diagnosing a performance problem:
- Poor social sharing previews → Meta tags and OG tags
- Thin or unoptimized CMS pages → CMS on-page SEO
- Bad Core Web Vitals scores → Image SEO and Core Web Vitals
- Post-redesign traffic drop → 301 redirects
- Indexing problems → Sitemap and robots.txt
Running an Audit on a Webflow Site
RankCrab's on-page audit runs 80 checks against any URL. For Webflow sites, it catches things that are easy to miss: missing OG tags on CMS pages where the template wasn't updated, hero images flagged as lazy-loaded, missing canonical tags on paginated collection views, and schema validation errors on manually-added structured data.
The audit also runs a Lighthouse check via Google PageSpeed Insights, so you get real LCP, CLS, and FID scores alongside the on-page data — in one report.
If you're doing a pre-launch checklist or a quarterly SEO review on a Webflow site, run the audit first. It'll surface the items that need attention so you can focus your time on fixing rather than hunting.