Frank for Webflow

QA your Webflow site before it goes live.

Paste your webflow.io staging URL and Frank checks every page and CMS template in the sitemap, before you connect the custom domain.

  • Set up in 30 seconds
  • Unlimited scans
  • No code required

Updated

What slips through on Webflow

The usual Webflow launch gremlins.

  1. 01

    CMS templates

    One template, dozens of items, and the one with an empty field is the one that shows filler.

  2. 02

    Designer vs published

    The Designer preview isn't what visitors see. Check the published staging site.

  3. 03

    Pages outside the nav

    Utility pages, legal pages and campaign pages rarely get clicked through before launch.

What Frank checks

Every page, straight from your staging URL.

Frank works from the published site, so there's nothing to install in Webflow. Paste the staging URL and pick pages from the sitemap.

  1. 01Lorem ipsum

    No filler left behind

    Every block of visible text on every page is checked for Latin filler, including CMS template pages.

  2. 02Links and accessibility

    Every link and the accessibility basics

    Internal and external links are tested, and every page is checked for missing alt text, skipped headings, unlabelled fields and more.

  3. 03Figma and markers

    Review against the design, together

    See each page side by side with its Figma frame, then pin markers for anything your team needs to fix.

Up and running in minutes

Ready before your next launch.

No setup project, no code, no plugins. Add a site and run a scan.

  1. 01

    Create a project

    Name the project and paste your staging URL. Takes 30 seconds.

  2. 02

    Map your Figma pages

    Optional: match each page from your sitemap to its Figma design.

  3. 03

    Run a scan

    Frank checks every page for lorem ipsum, broken links, alt text and accessibility, and scores each one.

  4. 04

    Fix and scan again

    Work through each page's issues, run another scan and keep the record on the project.

Frequently asked questions about QA for Webflow

  • Yes. Paste your webflow.io staging URL and Frank reads the pages from its sitemap. There's nothing to install in Webflow.

  • Yes. Every CMS item page in the sitemap can be scanned, not just the template you designed with.

  • The published staging site. It's what visitors will see, and it's what Frank scans.

Explore Frank

See what else Frank does for you.

  1. 01

    Accessibility checks

    Frank flags missing alt text and common accessibility issues on every page, from skipped heading levels to unlabelled form fields.

    Feature
  2. 02

    Broken link checking

    Frank tests every internal and external link on every page, follows redirects, and flags 404s, server errors and dead development links.

    Feature
  3. 03

    Figma design QA

    Map your Figma pages to your live site once, then review every page side by side with its approved design.

    Feature
  4. 04

    For Framer

    Automated QA for Framer sites: check every page and CMS page on your staging or preview URL before you publish to your domain.

    Solution
  5. 05

    For WordPress

    Automated QA for WordPress sites: check every page on your staging site for lorem ipsum, broken links and accessibility before launch.

    Solution
  6. 06

    For agencies

    Consistent, automated QA across every project and every team member, with a scored record of every scan.

    Solution
  7. 07

    For freelancers

    A second pair of eyes for solo designers and developers: automated checks on every page, so you can hand over with confidence.

    Solution
  8. 08

    Frank vs BugHerd

    BugHerd collects visual feedback from clients and teams. Frank runs automated QA checks on every page. Here's how they compare.

    Comparison
  9. 09

    Frank vs Pixelay

    Pixelay overlays a Figma design on a live page inside Figma. Frank reviews every page against its design and runs automated QA checks too.

    Comparison
  10. 10

    Frank vs Sitepager

    Sitepager tracks what changes on a site between updates. Frank checks a build before launch and lines it up with the Figma design. Here's how they compare.

    Comparison
  11. 11

    Frank vs manual QA

    Manual QA is slow, inconsistent and easy to skip. Frank automates the repetitive half, so your team keeps the judgement calls.

    Comparison
  12. 12

    Lorem ipsum checker

    Frank checks every block of visible text on every page for Latin filler, in any word order, and flags it before your client sees it.

    Feature
  13. 13

    QA reports & scores

    Every page gets a score out of 100 and a red, amber or green status, with issues highlighted on a screenshot, every scan kept, and reports you can share with clients by link.

    Feature
  14. 14

    Team markers

    Pin issues straight onto a scanned page, comment, @mention a teammate and filter by priority, so nothing gets lost between review and fix.

    Feature

More on pre-launch QA

All articles

Launch your next Webflow site clean.

Run your first scan in minutes. Every plan includes unlimited projects and unlimited scans.

  • Set up in 30 seconds
  • Unlimited scans
  • No code required