Webflow SEO Checklist for Agencies: What to Check Before Launch

Why a pre-launch SEO checklist matters

A Webflow site gives you clean HTML, fast hosting and good control over SEO settings. It does not stop you from launching with the wrong ones. Settings are spread across site settings, page settings, CMS templates and custom code, so something always slips.

I build sites in an agency's workspace and hand them over, so I run the same list every time. This article is that list. It is written for agencies, so each section says who usually owns the task: you, the developer or the client.

One note on menu names. Webflow moves settings around between UI versions, so I describe what to set and roughly where, not exact click paths. Where a setting is documented, I link the official page.

On-page basics: titles, descriptions, Open Graph and headings

Do this per page and per CMS template.

• SEO title and meta description on every key page. Keep titles to around 60 characters, descriptions to roughly 140 to 160, and put the main keyword near the start. These are guidelines for how results get truncated, not hard limits.
• Collection pages: in the template page settings, bind the title and description to CMS fields (for example a dedicated "SEO title" and "meta description" field with a fallback to the name). Otherwise every blog post or product gets the same generic text.
• Open Graph: set title, description and image for pages that get shared. Use a 1200 x 630 px image. Test a few links in a social preview tool before the client does.
• One H1 per page, then a logical H2 and H3 structure. Choose heading levels by meaning, not by font size. Style with classes.
• Readable URLs: short, lowercase, hyphenated slugs. Decide the CMS slug rules with the client before content is entered.
• Canonical URL: every indexable page should point to itself, and the canonical should use the final domain with the correct protocol and the www or non-www version the client chose. Google explains the concept in its guide to consolidating duplicate URLs. Use a custom canonical only where you have a real duplicate, for example filtered or syndicated content.
• Internal links: link key pages from navigation and from related content. Use descriptive anchor text, not "click here".

Indexing control: staging, noindex, robots.txt and sitemap

This is where launches go wrong most often, in both directions.

Staging must stay out of Google

The free webflow.io staging domain can be indexed unless you turn it off. Webflow documents how in its help article on disabling search engine indexing: in site settings, SEO tab, indexing section, switch off indexing for the Webflow subdomain, then save and publish. Webflow's page notes that disabling it requires a Site plan or paid Workspace. Do it at the start of the project, not at the end.

The opposite mistake

A site that was noindexed during the build and is still noindexed after go-live. Check the page-level setting and any custom code in the head for a robots meta tag. View source on the live domain and search for "noindex".

Sitemap

• Turn on the auto-generated sitemap and automatic updates on publish.
• Exclude pages that should not appear in search (thank-you pages, utility pages) with the sitemap indexing toggle in page settings. Webflow notes that blocking a page in robots.txt does not remove it from the auto-generated sitemap, so use the page toggle for that.
• Open /sitemap.xml on the live domain and confirm it lists the right URLs on the right domain.

robots.txt

Keep it short. Allow everything you want crawled, point to the sitemap, and disallow only what you must. A stray Disallow: / copied from a staging setup is the classic disaster. Open /robots.txt on the live domain and read it.

301 redirects and domain setup

For a redesign, redirects decide whether the old rankings carry over.

1. Get the old URL list early. Crawl the old site, export top landing pages from analytics and Search Console, and combine them. Ask the client for the list at kickoff, not in the last week.
2. Map each old URL to its closest new page. Not everything to the homepage. Redirecting irrelevant pages to the homepage tends to be treated like a soft 404.
3. Import in bulk. Webflow lets you manage 301 redirects in site settings and import them in bulk from a CSV file. Keep the CSV in the project folder as the source of truth.
4. Avoid chains. Old URL to final URL in one hop. Re-check after you have changed any slug.
5. Pick one canonical host. Decide www or non-www, force HTTPS, and make the other version redirect. Test all four combinations of http, https, www and non-www.
6. Test on the live domain right after publish. Click through the top 20 old URLs.

If the site is a rebuild with unchanged URLs, you still need to check that CMS slugs and folder structures match the old ones exactly.

Images, structured data and Core Web Vitals

Images and alt text

• Add descriptive alt text to every meaningful image. Describe what is shown and why it matters on the page, without keyword stuffing.
• Leave alt empty for purely decorative images, so screen readers skip them.
• Upload images at the size they are used, in modern formats such as WebP, and give them sensible file names.
• Lazy-load images below the fold, but not the hero image. The hero is usually the Largest Contentful Paint element and should load eagerly.

Structured data

Webflow does not add schema markup for you. Add JSON-LD in custom code, either site-wide (Organization, WebSite) or per page (Article, FAQ where it is genuinely a FAQ, Product on product pages). For CMS pages, put the JSON-LD in an embed in the template and bind fields to it. Use Google's structured data introduction for supported types and validate with the Rich Results Test before launch. Only mark up content that is visible on the page.

Core Web Vitals

Google's published "good" thresholds, measured at the 75th percentile of real visits, are LCP of 2.5 s or less, INP of 200 ms or less and CLS of 0.1 or less, as described on web.dev. Before launch, test the staging build in PageSpeed Insights on mobile. The usual Webflow culprits are:

• oversized hero images and background videos
• too many fonts and font weights
• third-party scripts (chat, analytics, tag managers) loaded on every page
• heavy interactions or GSAP timelines that run on load
• images without width and height, which cause layout shift

Real field data only appears after launch, so recheck in Search Console after a few weeks.

Multilingual sites: localisation and hreflang

If the site has more than one language, check three things.

• Hreflang. According to Webflow University, localised sites on subdirectories get hreflang tags generated automatically, in the page head and in the auto-generated sitemap, and you need only one of those signals. Check it in the localisation settings, and view source on a translated page to confirm.
• Language code conflict. Webflow notes that the site-wide language code in site settings overrides the locale-specific ones, so leave it empty on multi-locale sites.
• Custom sitemap. If you replace the auto sitemap with a custom one, you have to add the hreflang entries yourself.

Also translate the SEO title, meta description, Open Graph fields, alt text and slugs, not only the visible copy. Untranslated meta fields are the most common gap I see.

The copy-paste Webflow SEO checklist

Paste this into your project tool. Tick it on the live domain, not in the Designer.

Before launch

• Webflow subdomain indexing disabled for staging
• Title and meta description set on every key page and bound to CMS fields on templates
• Open Graph title, description and image set and previewed
• One H1 per page, logical heading order
• Slugs reviewed, canonical URLs correct
• Alt text added, decorative images left empty
• JSON-LD added and validated where relevant
• 301 redirect CSV imported and tested, no chains
• Preferred domain chosen, HTTPS forced, other host redirects
• Sitemap on, utility pages excluded
• robots.txt reviewed, no stray disallow
• Hreflang and translated meta fields checked (multilingual sites)
• PageSpeed Insights run on mobile, hero image and fonts optimised
• 404 page designed and useful
• Analytics and consent set up and tested

On launch day

• View source on the live site, search for "noindex"
• Open /sitemap.xml and /robots.txt
• Click through the top 20 old URLs
• Add the domain as a property in Google Search Console and submit the sitemap

First weeks

• Review page indexing and 404 reports in Search Console
• Fix new 404s with extra redirects
• Recheck Core Web Vitals once field data appears
• Compare top landing pages with the old site

My take: make SEO part of the handoff, not an add-on

My advice to agencies: make SEO settings part of the QA before the staging link goes to the client, together with the check of all breakpoints, not something to bolt on after launch. It is far cheaper to bind meta fields in a CMS template while building it than to retrofit them across hundreds of items.

On white-label work it also helps to split the list into three parts: what the developer sets, what needs the client's input (redirect list, final copy, schema details) and what only the agency can do (Search Console access, analytics). My handovers end with a Loom walkthrough, which is a good place to show the person who maintains the site where each setting lives. On large catalogues such as Big Moe Watches (1,100+ luxury watches, built white-label for Landrieau Studio), CMS-bound meta fields are the only realistic way to keep page-level SEO consistent.

Read more about the model in white-label Webflow development explained and about how AI search changes content in Webflow AI search optimisation. If you have a launch coming up, send me the project and I will run the list with you.

FAQ

Written byPeter CekanakDesigner & Webflow developer · white-label partner for agencies

I design and build Webflow sites for agencies and startups since 2018 — Client-First, GSAP, CMS and AI automations. Sites I built helped a client to a $10M exit and tripled demo requests for a SaaS.

Webflow Certified ExpertRelume ExpertClient-First