Home · Guides · Guide

The ultimate Webflow QA checklist before launch

Last updated: Mar 24, 2026

Author: Nopi Editorial Team

This Webflow QA guide gives teams a practical pre-launch checklist for responsive behavior, forms, SEO basics, accessibility, and launch-day validation. Use it to catch issues before DNS cutover and collect client feedback with clearer context during staging review rounds.

Use this list on staging before you point DNS. It is optimized for marketing sites and light CMS builds — the goal is no surprises on go-live day.

Try it on this page

Drop a demo pin anywhere below — nothing is uploaded; refresh to reset.

Responsive & layout

  • Spot-check mobile (375px), tablet, and desktop on real devices — not only Webflow preview.
  • Scroll every long page: sticky nav, section spacing, and footer legal links.
  • Test landscape on phones for hero headings and nav overflow.
  • Confirm images use appropriate sizes; watch for blurry retina assets or multi-MB hero files.

Interactions & CMS

  • Every dropdown, tabs component, and slider: tap targets, focus states, and animation performance.
  • CMS collection pages: empty states, long titles, and featured images with odd aspect ratios.
  • Custom code embeds (maps, calendars, chat): still load after cookie consent if required.

Forms & integrations

  • Submit each form with valid and invalid data; confirm success and error messages.
  • Verify notifications hit the right inbox (and spam folder once).
  • If using Zapier/Make: run an end-to-end test submission.

SEO & sharing

  • Title tags and meta descriptions on key templates.
  • Open Graph image and title for the homepage and at least one CMS template.
  • robots.txt and sitemap in Webflow hosting settings.
  • 301s for renamed slugs if migrating from an old site.

Accessibility basics

  • Keyboard-navigate the main header, mobile menu, and primary CTAs.
  • Check color contrast on buttons and links over photography.
  • Alt text on meaningful images; decorative images marked appropriately.

Performance & analytics

  • Run one Lighthouse pass on homepage and a heavy inner page.
  • Confirm analytics tags only fire after consent if you use a banner.
  • Third-party scripts: load order and failures (ad blockers).

Client review round (where Nopi fits)

After internal QA, send a single review link for the staging domain. Clients pin feedback on the live rendered site — you avoid the “which breakpoint was this?” email game. Your team can use the Nopi Chrome extension to triage and supplement pins before you cut the launch build.

Launch day smoke test

  1. DNS propagated — check from mobile data, not just office Wi-Fi.
  2. HTTPS certificate valid on apex and www (if used).
  3. Critical forms one more time on production.
  4. Remove or noindex true staging subdomains if they should not be indexed.

Need a tool comparison before finalizing your review stack? Compare Nopi vs Marker.io, Nopi vs BugHerd, and Pastel alternatives.

Collect client QA on the staging URL

Nopi works on pages your review session allows — share one link, gather pinned feedback in one place.

Get started free Available in the Chrome Web Store