Webflow QA Toolkit

Each site gets one small config file. Every check then runs the same way against any site, Webflow or not:

• Page loads, broken links and images
• SEO meta tags and redirect chains
• Accessibility checks with axe-core
• Cookie consent and responsive overflow
• HubSpot and Webflow form submissions
• Webflow mega-menu dropdowns

Checking a form used to mean opening DevTools, submitting it and watching for the request. I wanted that, and the rest of a pre-launch check, to run the same way for anyone on a team, as often as needed, on as many sites as needed.

• A site config lists the staging URL, the pages, the forms to test and any links to ignore.
• One command runs every check or a single one, on desktop Chrome or across four browser profiles.
• The form test fills the fields and submits. It passes only if a request to the form endpoint fires and returns a status under 400.
• A setup step visits every page first to warm the CDN cache.
• Run from Claude Code, a slash command adds a proofreading pass for typos, leftover placeholders and inconsistent calls to action, then explains any failures in plain English.

Webflow templates often lay a decorative link styled as a button over the real submit input, and it intercepts the click. The form test has to force the click through to the input underneath.