Webflow gives you more control than most visual builders, which means more ways to help your rankings and more ways to break them. This checklist walks through the settings that decide whether Google indexes your site cleanly, in the order you should touch them: indexation first, then metadata and schema, then CMS collections, then speed. Work top to bottom before launch and after every major design change.
If you want it handled for you, our Webflow SEO agency can take it on; this is the tactical checklist for doing it yourself.
Control what Google indexes
The fastest way to sink a Webflow site is to leave the wrong pages open to crawlers, or to ship the whole site with indexing turned off.
- Turn off "Disable Webflow subdomain indexing" only when you are live on your real domain. Webflow blocks indexing on the .webflow.io staging subdomain by default. Good. But confirm your production domain is set to allow indexing before launch. This one setting has killed more Webflow launches than any other.
- Set a robots.txt in Site Settings then SEO. Block /search and any utility paths. Do not block CSS or JS.
- Noindex thin utility pages using the per-page SEO settings: style guides, password pages, and 404 templates.
- Publish the sitemap. Webflow auto-generates one at /sitemap.xml when you enable it in SEO settings. Turn it on and submit it to Search Console.
Check the live robots.txt and sitemap in a browser after every publish. Webflow republishes them on deploy, and a staging setting can carry over if you are not watching.
Set metadata on every page and CMS template
Webflow separates static page metadata from CMS collection metadata. You have to set both.
Static pages. Each page has a Settings panel with title and meta description fields. Write them by hand:
| Field | Rule | Character target |
|---|---|---|
| Title tag | Primary keyword first | Under 60 |
| Meta description | One benefit plus one action | 140 to 155 |
| Open Graph title and image | Match the title, 1200 by 630px image | Image under 200KB |
CMS collection templates. This is where Webflow sites usually break. On a collection template page, the title and description fields accept dynamic bindings. Bind the title to the collection's Name field and the description to a dedicated SEO summary field, not the full body. If you bind the description to the rich text body, Google gets 155 characters of raw HTML-stripped intro that rarely reads well.
Add a plain-text "SEO description" field to every CMS collection and bind the meta description to it. It takes ten minutes per collection and fixes every item at once.
Add structured data
Webflow has no native schema generator, so you add JSON-LD by hand in the page or site custom code.
- Organization schema in the site-wide head code: name, logo, URL, social profiles.
- Article or BlogPosting schema on the blog CMS template, with dynamic bindings for headline, author, and publish date.
- BreadcrumbList schema if your site uses a clear folder hierarchy.
- Product or LocalBusiness schema where it applies to your business.
Bind the dynamic values from CMS fields inside the embed. Validate every template in Google's Rich Results Test using a live published URL, because Webflow only renders the bindings after publish.
Optimize CMS collections
Most of a growing Webflow site's pages come from CMS collections. Get the collection structure right and every future item inherits it.
- Set the collection URL slug field. Webflow generates slugs from the item name. Shorten long ones by hand: /guides/webflow-seo, not /guides/the-complete-guide-to-webflow-seo-in-2026.
- Add an SEO title and SEO description field to each collection, separate from the display name, so you can tune metadata without changing what shows on the page.
- Add a featured image field sized for social sharing and bind it to the Open Graph image.
- Paginate long collection lists and confirm the paginated URLs are crawlable. Webflow's default pagination uses query parameters that Google can read, but check that page 2 and beyond are not accidentally noindexed.
For a platform-agnostic pass, run our technical SEO checklist. If you are weighing Webflow against a hosted builder, our Squarespace SEO tips cover the trade-offs.
Build URL structure and internal links
URL structure on Webflow is set by folders and collection slugs, and it is hard to change after launch without a wave of redirects. Decide it once, before you publish.
- Use folders to group related pages. A structure like /services/web-design reads better than a flat list and signals topic grouping to Google.
- Keep slugs short and descriptive. Three to five words, lowercase, hyphenated, no dates or stop words.
- Match CMS collection paths to how people search. A blog at /blog and guides at /guides beats burying both under a generic /posts folder.
Internal links carry as much weight as structure. Webflow builds none for you inside body copy, so add them deliberately.
- Link every new blog post to its pillar service or topic page with descriptive anchor text.
- Link the pillar page out to its supporting posts so the cluster connects both ways.
- Add 3 to 5 in-content links per page as you publish.
- Keep every important page within three clicks of the home page.
Use Webflow's built-in collection lists to auto-generate related-post links at the bottom of each CMS template. That covers breadth. Hand-placed in-content links cover relevance. You want both.
Keep Core Web Vitals green
Webflow's hosting is fast, but design choices decide your Core Web Vitals. Three metrics matter.
- Largest Contentful Paint under 2.5 seconds. Usually your hero image or heading. Compress hero images to under 300KB, set them to load eagerly, and lazy-load everything below the fold.
- Cumulative Layout Shift under 0.1. Set explicit width and height on every image and embed so the layout does not jump as assets load. Webflow lets you set these in the element settings.
- Interaction to Next Paint under 200ms. Trim heavy Webflow interactions and third-party scripts. Each animation and each embedded widget adds main-thread work.
Use Webflow's responsive image feature: it serves sized variants automatically when you upload through the asset manager. Then run PageSpeed Insights on mobile, which is stricter than desktop and matches how Google evaluates you.
Redirects and launch checks
Webflow makes redirects easy and easy to forget. Before you point your domain at a new Webflow site:
- Map old URLs to new ones. Add 301 redirects in Site Settings then Publishing for every URL that changes.
- Redirect non-www to www or the reverse. Pick one canonical host.
- Confirm HTTPS. Webflow provisions SSL automatically. Verify it resolves and that HTTP redirects to HTTPS.
- Recheck indexing settings on the production domain, not staging.
Run a crawl of the live site after launch to catch redirect chains and orphaned pages before Google does.
Run a post-launch crawl and monitor
Launch is where problems surface, not where they end. A crawl and a monitoring routine catch the issues a manual click-through misses.
- Crawl the live site with any SEO crawler within a day of launch. Look for redirect chains, broken internal links, pages missing titles, and any URL still set to noindex.
- Confirm indexing in Search Console. Submit the sitemap, then use the URL Inspection tool on five key pages to confirm Google can fetch and index them.
- Watch the Coverage report for the first two weeks. A spike in excluded pages usually means a noindex tag or canonical error slipped through.
- Recheck after every redesign. Webflow republishes the whole site on deploy, so a single design change can reset a setting you fixed months ago.
Set a recurring reminder to re-crawl monthly. Most Webflow ranking losses trace to a setting that changed on a publish nobody audited.
Frequently asked questions
Is Webflow good for SEO? Yes. Webflow gives you control over title tags, meta descriptions, URL slugs, custom code for schema, and clean semantic HTML. It hosts on a fast CDN. The main risk is the staging-to-production indexing setting, which can leave a site invisible to Google if you miss it. Handle that and Webflow competes well.
Why is my Webflow site not showing on Google? The most common cause is the indexing toggle. Webflow disables indexing on the .webflow.io staging subdomain, and site owners sometimes leave production set to noindex, or the robots.txt blocks crawling. Check Site Settings then SEO, confirm the production domain allows indexing, then request indexing in Search Console.
How do I add schema markup in Webflow? Add JSON-LD in custom code. Put Organization schema in the site-wide head code, and Article or Product schema in the relevant page or CMS template head code, binding dynamic values from CMS fields. Publish, then validate the live URL in Google's Rich Results Test, since bindings only render after publish.
How do I set meta descriptions for Webflow CMS items? Add a dedicated plain-text SEO description field to the CMS collection, then bind the meta description field on the collection template to that field. This gives you clean, hand-written descriptions for every item instead of a raw slice of the body text.
Can I change a Webflow URL after launch? Yes, but add a 301 redirect from the old path to the new one in Site Settings then Publishing at the same time. Changing a slug without a redirect breaks every existing link and any ranking the old URL held. Plan structure before launch to avoid a wave of redirects later.
Where to go next
A Webflow site ranks when indexation is correct, metadata is set on both static and CMS pages, schema validates, and Core Web Vitals stay green. Work this checklist before launch and after every redesign. If you want a second set of eyes on your Webflow setup or help fixing what a crawl turns up, our Webflow SEO agency team will prioritize the changes that move your rankings.