How to test a Webflow site before launch

Webflow makes a site look finished long before it is. The Designer preview hides the CMS bindings, the interactions that fire on real scroll, the forms that need to actually reach an inbox, and the breakpoints that break only on a real phone. Here's how to test a Webflow site properly before it goes live or back to a client.

CMS collections and dynamic content

• Every collection page renders with real content, not just the one you designed against
• Empty states (a collection with 0 items, a missing image) don't break the layout
• Filters, sorting and pagination on collection lists actually work
• Reference and multi-reference fields resolve to the right linked items

Interactions and animations

• Scroll, hover and click interactions fire once and clean up - no stuck or half-played states
• Animations don't cause layout shift or hide content on slower devices
• Nothing depends on hover on touch devices (menus, tooltips, reveals)
• Reduced-motion users get a sane experience

Forms

Webflow forms fail quietly more than anything else. For each form:

• Submission actually arrives where it should (Webflow, an email, or the integration/webhook)
• Success and error states both show correctly
• Required fields and email validation work
• Spam protection is on but doesn't block real people

Responsive and breakpoints

Check every breakpoint on a real device, not just the Designer's canvas. Watch for overflow, overlapping elements, tap targets that are too small, and typography that collapses on the smallest screens.

Links, SEO and details

• No broken internal links or leftover placeholder / Lorem content
• Each page has a unique title and meta description set in page settings
• 301s are in place for any changed slugs; the sitemap is published
• Open Graph image and text render when the URL is shared
• Favicon, 404 page and canonical are configured

Performance

Compress and lazy-load images, check the page weight isn't dominated by huge assets, and confirm the site loads fast on a mid-range phone. Webflow is fast by default - it's usually oversized media that slows a build down.

The pre-handoff pass

Before handing a Webflow site to a client, run the forms, the CMS pages and the mobile layout one more time. The bug you catch now is a five-minute fix; the one the client catches is an awkward email.