How to QA a Webflow Site Before Going Live (The Complete Agency Checklist)

You've built a great site. The client's approved the design. The staging link is live on yourproject.webflow.io. All that's left is to connect the domain and ship it.
‍

And then your client emails you on day three to say the contact form doesn't work, the "Our Team" page still has placeholder text, and the nav link to Pricing goes to a 404.
‍

It happens to almost every agency. Not because anyone is bad at their job — but because manual QA on a deadline is unreliable by nature. You're tired, you're context-switching, and you've looked at this site so many times that your brain autocorrects the lorem ipsum.
‍

This guide gives you the full pre-launch checklist we recommend for every Webflow build, covering the nine categories you need to sign off before a domain connects.

‍

Category 1: Links & Navigation

Broken links are the most embarrassing and most common launch issue. Click every single one — internal pages, external links, anchor links, CTAs, footer links, nav items, and buttons. Don't trust Webflow's Designer; test the published staging URL.

‍

Category 2: Copy & Placeholder Content

Lorem ipsum is the agency's public enemy number one. It sneaks in during the build phase and hides in secondary pages, CMS collection templates, and components that aren't checked during client reviews. Every single text node on every single page needs to be a real word.

‍

Category 3: Design Parity (Figma vs. Live Build)

Design drift is silent and cumulative. By the time a site ships, the developer's made a hundred small decisions — rounding a font size, adjusting a spacing value, picking a slightly different shade of the brand colour — and individually they're invisible. Together, they create a site that doesn't quite look like what was approved.

The fix is comparing the live staging build against the approved Figma frames, systematically. Look for:

• Font sizes, weights, and line heights that don't match the design spec
• Colour values that have drifted (check hex codes, not just visual similarity)
• Spacing and padding inconsistencies — especially on mobile
• Button corner radius, border width, or shadow values that don't match
• Image crops or aspect ratios that have changed

‍

Category 4: Forms & Interactions

Forms are the most critical functional element on most agency websites. They are also statistically the thing most likely to be broken on launch day because they require back-end configuration that isn't visible in the Webflow Designer. Test every form submission in the published staging environment.

‍

Category 5: Responsive & Cross-Device

Webflow's breakpoints are a starting point, not the finish line. Real devices don't line up neatly with the Designer's 991px, 767px, and 478px presets. Test on actual devices, or at a minimum test at 320px (iPhone SE), 375px (standard iPhone), 768px (iPad portrait), and 1440px (standard desktop).

‍

Category 6: SEO & Meta

This is the category that haunts agencies months after launch when a client asks why they're not ranking. Every page needs a unique title tag and meta description — not the Webflow defaults, and not the same text on every page.

• Unique page title and meta description on every page (including CMS templates)
• OG image set for social sharing (check with a Facebook/Twitter card debugger)
• Favicon uploaded and showing in the browser tab
• Google Analytics or other tracking is installed and firing
• Search engine indexing is enabled (not blocked on staging, but check the setting is correct for production)
• Canonical tags are set correctly if you have duplicate or similar pages

‍

Category 7: Images & Media

• All images load correctly — no broken image icons or missing files
• All images have descriptive alt text (not just "image" or left empty)
• Images are appropriately compressed — oversized images are a Core Web Vitals killer
• Videos autoplay correctly (or don't, per the brief) and load without delay
• No placeholder images or stock photo watermarks remain

‍

Category 8: Performance

Run a Lighthouse audit on the published staging URL. Aim for a performance score above 80. Common Webflow culprits are unoptimised images, unminified custom code, and third-party scripts loaded synchronously.

‍

Category 9: Cross-Browser

Webflow's output is generally good, but Safari in particular handles CSS differently. At minimum test in Chrome, Safari, and Firefox. If your client's audience has significant Safari/iOS traffic (which almost all do), Safari testing is non-negotiable.

‍

Making This Process Repeatable

The problem with a checklist in a document is that it doesn't scale. The third time you run it, someone skips the forms section because they're in a rush. The fifth time, the checklist itself is outdated.

The agencies that ship consistently clean sites don't have better checklists — they have better systems. That means a QA step that's non-negotiable in the project timeline, happens on the staging URL before any domain connection, and produces a record that something was checked.

That record matters. When a client comes back four weeks after launch saying "the site was already broken when you handed it over," you need to be able to show that it wasn't.

‍

Why Beta Users Get More Than Free Access

Beta closes Friday 19th June — and if you join before then, you're not just getting early access to a tool, you're helping build it. We need real agency workflows, real edge cases, and real feedback to make Frank genuinely useful. In return:
‍

• You get Frank completely free until 19th June
• You'll be invited into our private community to share feedback, report bugs, and vote on what ships next
• We'll run case studies with beta users who want them — real stories of real agencies saving real time
• When Frank moves to paid plans, beta users lock in a founding rate that no future customer will ever access

After Friday, beta signup closes and founding member pricing kicks in from £39/month. This is your one chance to get in at the ground floor. Once the 19th passes, that rate is gone.