Top 10 Things to Check Before Launching a Large Webflow Website

Before launching a large Webflow website, check redirects, indexing, CMS template metadata, canonicals, CMS content, forms, analytics, performance, mobile and accessibility, and who owns the site after launch. On a big site, one mistake in a Collection template repeats across hundreds of pages, so test templates and patterns, not just the homepage.

Why large launches go wrong

Small sites fail loudly. Large sites fail quietly. A missing redirect on one URL is easy to spot. A broken canonical on a template that generates 800 pages can go unnoticed for weeks. The checks below are ordered by how much damage a miss usually causes.

1. Redirects from every old URL

If the site replaces an older one, collect every old URL from the old sitemap, Search Console and a crawl. Map each to the closest new page and add 301 redirects in Site settings > Publishing > 301 redirects.

• Redirect to the most relevant page, not the homepage
• Avoid chains; point old URLs straight to the final page
• Use folder patterns where the structure maps cleanly
• Test a sample of old URLs after publishing

/blog/(.*)  ->  /articles/%1

2. Indexing settings

Staging is often blocked from search on purpose. Make sure that block does not reach production.

• Review robots.txt in the SEO settings
• Remember the subdomain indexing option only affects webflow.io
• Search custom code for a stray noindex tag
• Confirm the auto-generated sitemap is on

3. Metadata on CMS templates

Open each Collection template's page settings and check that the title and meta description pull from CMS fields, not a fixed string. Check Open Graph fields too.

Example: a 300-page resource library where every item uses the title "Resource | Brand". Search results would show 300 identical titles, fixed by one template change.

4. Canonicals and the default domain

Set one default domain, with or without www, and make the other redirect to it. Set the global canonical URL in the SEO settings. If you use Localization, check hreflang output on each locale.

5. CMS content gaps

• Filter collections for empty summaries, images and alt text
• Search for "Lorem ipsum" or "TBD"
• Check reference fields point to published items
• Look for slugs ending in "-2", a sign of duplicates

6. Forms

Submit every form on the production domain. Confirm the submission arrives, the notification reaches the right inbox, the success and error states show, spam protection is on, and the conversion event reaches GA4.

7. Analytics

Install GA4 once, through Webflow's integration or GTM, not both. Verify page views and key events in GTM Preview and GA4 DebugView. Check that consent loads before tracking where required. Submit the sitemap in Google Search Console.

8. Performance per template

Run PageSpeed Insights on one URL per template type and check LCP, INP and CLS.

• Hero images sized correctly and not lazy loaded
• Below-the-fold images set to Lazy load
• Only the font weights you use
• Third-party scripts deferred or page-specific

9. Mobile and accessibility

Check each template at every breakpoint and on a real phone. Then cover the basics: one H1 per page, logical headings, alt text, visible focus states, readable contrast and real form labels.

10. Ownership after launch

Decide who has site access and in what role, who can publish, where the redirect map and tracking plan live, and who watches Search Console for new 404s in the first weeks.

Launch day order

1. Final staging publish and checklist run
2. Connect the domain and set the default domain
3. Publish to production
4. Test redirects, forms and tracking live
5. Submit the sitemap and crawl for 404s

FAQ

When should these checks start?

Start the redirect map and CMS review once the structure is final. Leave performance, forms and tracking for the last week.

Do I need to check every CMS item?

No. Check every template, then use collection filters to find items with empty or broken fields.

What should I watch after launch?

Search Console's Pages report for new 404s, GA4 for drops in key events, and your form inbox.

Dealing with this on a live Webflow site? It is the kind of work I do in a Webflow audit. Send me your site and I will tell you what I would fix first.