How Recall.ai reviews website changes before publishing
Recall.ai’s marketing team publishes website updates. Sitepager gives the team a repeatable QA step across staging and production, helping them keep the bar high without adding more manual work or building and maintaining their own automation.
- 350+
- Scans
- Staging + production
- Environments
- Desktop + mobile
- Devices
Challenge
When one website update unexpectedly affects another page
Recall.ai’s site was growing quickly. As the company ramped up marketing, the team was adding more pages and publishing changes regularly.
But changes did not always stay contained to the page being edited. An update in one place could unexpectedly affect another.
As we ramped up marketing, we were adding a lot of pages to the website, and changes on one page could sometimes affect another. We wanted an easier way to review those changes across the site.
Preventing breakage as the site and team grew was the trigger. But the practical constraint was time.
Recall.ai’s primary focus is on providing the best meeting bot API and desktop recording SDK on the market. Like many customers, they choose to focus on their specialty, but want to put their best foot forward on their website because it is how customers find them. QA across a growing site can be surprisingly time-consuming, especially when you’re trying to review changes across a lot of pages.
Solution
Another layer of review without more manual work
Recall.ai needed a better way to test website changes without turning QA into a bottleneck. Many of the alternatives the team found required some level of coding, with tools such as Puppeteer or Playwright. Even though the marketing team at Recall.ai is deeply technical, they found that their time was better spent building product demos or open-source repositories for meeting bot and desktop recording use cases.
Sitepager gives the team another layer of review across the site without adding code or a lot of setup. It surfaces changes they might otherwise miss and fits into their existing workflow.
A repeatable review step is now part of how the team publishes.
The playbook
Change. Review. Publish.
Recall.ai’s website update process follows three simple stages.
- 01Staging
Change
The team makes website updates to their site and pushes them to staging first.
- 02Before publish
Review
Recall.ai runs Sitepager on staging across desktop and mobile and reviews what changed.
Alongside broader website reviews, the team also has a focused scan covering key pages. That gives them a faster, more targeted option when needed.
The team also manually checks important pages, interactions and anything screenshots cannot capture.
- 03Production
Publish
Once staging is approved, the update goes to production and the team runs Sitepager again on the live site to make sure the intended changes are applied correctly.
After verification, the team sets new baselines on staging and production, so the approved versions become the reference for the next change.
In practice
Helping the team catch unexpected changes
In practice, this means broader coverage during QA. Instead of checking only the places the team expects to have changed, Sitepager surfaces changes across the site.
What Sitepager helps Recall.ai catch:
- Visual changes on pages the team did not intend to touch
- Design-system changes that ripple into connected pages or components
- Changes that show up on desktop or mobile
- Unexpected build issues, such as duplicated elements
One example was a double footer that made it into a build. Sitepager caught it immediately.
Sitepager is useful for things that are easy to gloss over when you’re manually clicking through the site, especially when we make changes to the design system that end up affecting pages or components we didn’t realize were connected. Those are exactly the kinds of issues that can take a long time to find manually.
Result
A consistent review process that gives the team time back
Recall.ai’s website QA process is now consistent.
Sitepager adds broader coverage without replacing manual review. That means less time clicking through pages and more time for work they otherwise would not be able to get to in the day.
I’d definitely recommend it to another marketing or content team. It saves us time, catches issues we might otherwise miss, and gives us an additional check on our own eyes. It doesn’t replace manually reviewing the important parts of the site, but it makes that review much more reliable and lets our team cover a lot more ground.
Review every website change before you publish
Make website QA a part of your publishing process. Catch unexpected changes before they go live.
No credit card required. No code or plugins needed.