A global trading platform on Webflow. 20M+ monthly visits. A website QA team that went from hours of manual checking to under 20 minutes of review before every publish.
The Situation
After completing a large-scale migration to Webflow (6,000+ pages, 18 language versions, content spanning multiple subdomains), the team had a new problem: maintaining it.
At this scale, a single change to a shared component could ripple across hundreds of pages. A locale that looked fine in English might render incorrectly in French. A cookie banner might disappear in one region and go unnoticed until a visitor did.
The QA and Webflow teams worked together, but their process was manual. A team of four — two QA engineers and two Webflow designers — checked thousands of pages before every publish. It took hours each time.
They needed a way to validate that what went live matched what they intended, visually, across every language, before every publish.
With visitors across 18 countries, they also needed to check how the site looks in different locations, not just in their own environment.
How They Use Sitepager
They built Sitepager into their release workflow, mirroring the way their site is structured.
Each language version is tracked independently. When a change is made to a specific locale, the team re-runs that scan and sees exactly what changed — without having to re-check the entire site.
They follow the same approach across environments and devices. Staging and production are validated separately, and mobile is treated as its own surface, not an afterthought.
They also check how the site appears from different locations, making sure region-specific versions show up correctly before publishing.
Beyond static pages, they check interaction states. Navigation menus and dropdowns are checked as part of each run, with overlays and click-driven states captured when needed. Login-protected areas are checked when relevant, as they are just as likely to break as public pages.
They run scans twice a week, aligned with their publish cadence. The QA team and Webflow team review results together before anything goes live.
What It Catches
The issues that surface consistently are the ones manual checking misses:
- Style changes on one page that unexpectedly affect other pages
- Elements that stop showing up
- Translations that break layouts or push content out of place
- Navigation that stops working or links to the wrong place
One example: before publishing, a scan caught that the main navigation menu was not visible on mobile for certain languages and locations. This would have gone live unnoticed without checking each language version separately. On a site with 20M+ monthly visits, that’s a meaningful amount of traffic hitting a broken navigation.
This isn’t a rare edge case. It’s what happens when changes are made across shared parts of the site at scale, and exactly what this process is designed to catch before users see it.
Shaping the Product
Working at this scale surfaced problems smaller teams don’t run into. The team fed those back directly, and two features in Sitepager came out of that.
The first was page review tracking. Reviews were spread across multiple sessions and people, so it was easy to lose track of what had already been checked. This led to the Mark as Done feature.
The second was multi-scan runs. Scans had to be started one by one across every locale, device, and environment, which was slow. They needed a way to start multiple scans in one action. This is available as bulk scan runs.
Both features are now part of Sitepager.
The Result
What used to take hours of manual checking now takes under 20 minutes of review. Over time, more than 1,300 scan runs have been completed, making it part of how updates are published.
The team now has a structured, repeatable release process across 6,000+ pages and 18 language versions. Changes to one language no longer require re-checking the entire site. Each scan is scoped to the pages that matter, avoiding noise from sections like the blog or newsroom that change on their own schedule.
Scans run twice a week, aligned with the publish cadence. Before any update goes live, there is a clear record of what changed, and nothing ships unreviewed.
5,800+
pages across 18 languages
1,300+
scan runs completed
Hours → 20 min
review time before publishing
“Sitepager gives us complete coverage of our website and makes it easy to catch UI bugs across every page. The team is incredibly responsive, quick to action feature requests, and always proactively suggests ways to reduce our manual effort.”
— QA Team, Enterprise Marketing Website
This case study describes an anonymized enterprise customer. Company name and identifying details have been withheld at their request.
