Importing a CSV of redirects into Webflow "removes any existing redirects on your site", according to Webflow's help centre. Run a checklist in the wrong order and the redirect step can wipe out the slug redirects Webflow created a week earlier. That is why this list is sequenced, not just complete.
It holds 38 settings and habits, grouped by when we apply them: before the first Collection exists, during the build, on CMS templates, on staging, on launch day and afterwards. The rules come from Webflow's help centre and Google Search Central, read on 20 October 2026. Whether Webflow suits SEO at all is covered in our post Is Webflow Good for SEO?
Why the order matters more than the list
Webflow's SEO settings depend on each other. The noindex toggle only works if the auto-generated sitemap is on. A template's SEO pattern can only use fields that exist. Schema cannot read Reference fields, so the field list has to plan for it. Out of order, you rebuild a Collection after launch.
We build marketing sites in Webflow and applications in Next.js, so we have a stake in Webflow working well. In the last twelve months we built more than 20 Webflow sites as a white-label partner to Web Tonic, two to three weeks each, the largest with a CMS of over 1,200 items. Our marketing-site process runs four weeks, and the phases below map onto it.
| Phase | Items | When | Owner |
|---|---|---|---|
| Before the build | 1 to 6 | Week 1, with the page map | Strategist and developer |
| During the build | 7 to 16 | Weeks 2 and 3 | Developer |
| CMS templates | 17 to 23 | As each Collection page is built | Developer |
| Staging | 24 to 30 | Late in week 4 | Developer and content lead |
| Launch day | 31 to 34 | The publish to the custom domain | Developer |
| After launch | 35 to 38 | First 30 days, then monthly | Content lead |
Source: Octo Agency build process; settings from Webflow Help Center, read 2026-10-20
Before the build: decisions that are expensive to change
- 1. Write the URL map before any Collection exists. Only static pages can sit in folders, and a folder cannot share a URL with a Collection. Collection items live under the Collection's URL, so name them now.
- 2. Agree the slug rules. Webflow supports only lowercase a to z and 0 to 9 in page URLs. Other characters are removed or transliterated, so č and ü will not survive.
- 3. Inventory every old URL. On a redesign, Google's site move guidance says to map each old URL to its new one, gathered from sitemaps, logs, analytics and the old CMS.
- 4. Plan redirects as patterns. Webflow recommends 1,000 rules at most, because each rule is loaded into the site's manifest file. A capture group such as /oldfolder/(.*) covers a whole folder in one line.
- 5. Put the SEO fields in the Collection schema. A plain text field for alt text, an Image field for the Open Graph image, and plain text copies of anything schema needs from a Reference field, because Reference, Multi-reference and Multi-image fields cannot feed schema.
- 6. Decide on locales. Webflow's 301 redirects ignore localised subdirectories, so /old-url and /es/old-url need two rules. With Localize on, the auto-generated sitemap adds hreflang entries.
During the build: pages the way crawlers read them
- 7. One visible H1 that states the subject. Google lists the main visual title and headings among the sources it uses to write a result's title, and recommends making the main title the most prominent text.
- 8. Headings in order. A skipped level is usually a heading picked for its size; fix the class, not the tag.
- 9. Meaningful images as image elements. Google finds images through the src of an img element and does not index CSS images.
- 10. Alt text on the asset. Set it once in the Assets panel and every instance inherits it. Mark decorative images as decorative.
- 11. Alt text inside rich text. Images in a rich text element take their own alt text, set in the CMS item when the rich text comes from a field.
- 12. Descriptive file names before upload. Google says short, descriptive file names give it light clues and suggests avoiding names like image1.jpg.
- 13. Upload images inside Webflow. Webflow creates responsive variants, up to seven for an image wider than 3,200px, only for images uploaded through the Assets panel or a CMS image field. The upload limit is 4MB.
- 14. Link every important page from another page. Use descriptive link text, and check that no Collection item is reachable only through search or a filter.
- 15. Minify HTML, CSS and JavaScript. Three separate toggles under advanced publishing options.
- 16. Test asynchronous JavaScript and per-page CSS on staging. Both are off by default. Async loading can break custom scripts that expect Webflow's JavaScript first, and per-page CSS can break shared Library styles.
CMS templates: one pattern, hundreds of pages
- 17. Title pattern bound to a field. Webflow suggests titles under 60 characters. Check the longest item in the Collection, not the first.
- 18. Description pattern from a summary field. There is no character limit, but search engines truncate long descriptions. A summary field beats binding the body's first paragraph.
- 19. Open Graph from the SEO fields. Tick the boxes that copy the SEO title and description, and bind the image to an Image field. All Open Graph images in a Collection must share the same dimensions.
- 20. Alt text bound to its field. Bind each CMS image's alt text to the field from item 5.
- 21. Schema with bound fields, then validated. Webflow AI can draft template schema with supported fields included; manual schema has to bind them. Valid schema makes a page eligible for rich results, not guaranteed one.
- 22. Noindex for thin items. On paid Site plans each CMS item has a Sitemap indexing toggle that adds noindex and drops it from the sitemap.
- 23. Canonicals from the global setting. Page-level canonical overrides are documented for static pages only, so CMS pages rely on item 31.
Staging: the pass before anyone sees the site
- 24. A unique title and description on every static page. Webflow has no site-wide fallback; a page without its own has none.
- 25. Open Graph on every static page. Webflow warns that without it, random content, or none, appears when the page is shared.
- 26. Noindex the utility pages. Thank-you, legal and confirmation pages get Sitemap indexing turned off, which only works when the auto-generated sitemap is on.
- 27. Never hide a page with robots.txt alone. Webflow notes a page disallowed in robots.txt stays in the sitemap and can still be indexed through links.
- 28. Review the bot toggles. Search and AI bots are allowed by default. Webflow notes that blocking them can cut bandwidth but may reduce visibility in AI-powered search, so it is the client's decision.
- 29. Organization schema on the home page. In the Schema markup field only, because Webflow advises against duplicating structured data in custom code.
- 30. Merge the redirect file before importing it. Export the existing redirects, add the new map, import the combined file. Specific rules go above wildcards, because older redirects are tried first.
| Item | What goes wrong | How it shows up | Check |
|---|---|---|---|
| Global canonical with a trailing slash | Subpage canonicals get a double slash | Google picks its own canonical | View source on two subpages |
| Canonical also injected by a tag manager | Two canonical tags, which may both be ignored | Same as above | Search the source for rel="canonical" |
| CSV redirect import | Earlier redirects deleted | Old URLs return 404 weeks later | Export before every import |
| robots.txt used to hide a page | Page stays in the sitemap | It still turns up in search | Use the noindex toggle |
| Images imported by API or CSV | No responsive variants | Slow mobile pages after a migration | Spot-check srcset on imported items |
| Hero image set as a background | Not indexed by Google Images | Image search traffic never arrives | Inspect the hero element |
Source: Webflow Help Center and Google Search Central, read 2026-10-20
Launch day: four settings on the live domain
- 31. Set the global canonical URL. The base URL with https, with www if the default domain uses it, and no trailing slash. Leave it blank if a tag manager already injects canonicals.
- 32. Turn off staging indexing. One toggle stops search engines indexing the webflow.io subdomain. It needs a paid Site plan or Workspace.
- 33. Turn on the auto-generated sitemap. Webflow rebuilds it on every publish and adds it to robots.txt; adding it by hand as well leaves two sitemap lines.
- 34. Verify the domain in Search Console and submit the sitemap. Webflow notes this can speed up indexing.
After launch: the habits that keep it clean
- 35. Test the old URLs. Open a sample from the item 3 inventory and confirm each lands on the right page. Google recommends keeping migration redirects for at least a year.
- 36. Watch Search Console for a month. Google says a medium-sized site can take a few weeks or more to show new URLs in place of old ones. Webflow adds that title and description changes can take days, weeks or months to appear.
- 37. Every slug change gets a redirect. Tick "Permanently redirect the old URL to this new one" when renaming. To redirect a CMS item, archive, unpublish or rename it first.
- 38. A monthly alt text and metadata pass. Webflow AI can draft missing alt text in bulk from the Audit panel; someone still reads each one.
What this means for your next Webflow launch
Items 1 to 6 get skipped because nothing looks wrong without them, yet no toggle fixes them later: a Collection URL, a field list and a redirect plan have to be rebuilt to change. Items 31 to 34 take ten minutes on launch day, and they are what we would check first on any Webflow site we inherit.
Give each phase an owner and a date, and keep items 35 to 38 on a calendar rather than in a document. Our marketing website service page explains how we scope a build with this checklist inside it.
