How Arlanet embedded Conductor Website Monitoring to drive their quality assurance processes

Arlanet (opens in a new tab) is a software solution provider with a strong focus on eCommerce based in The Netherlands. They deliver complex eCommerce solutions for major brands, creating extensive integrations with CRM and ERP systems through enterprise-grade platforms such as Episerver and Umbraco.

The challenge

When it comes to software development, there’s a vast array of sophisticated QA tooling available to continuously audit software for bugs and performance bottleneck. But Arlanet’s clients not only expect their eCommerce platform to be rock-solid and agile, it also needs to outperform their competitors in search engines. That’s why Arlanet went looking for tooling to continuously audit their projects from an SEO perspective.

The solution

Arlanet found the solution in Conductor Website Monitoring. Its continuous monitoring and auditing made it the perfect answer to their search for digital marketing QA tooling and they moved fast to embed Conductor Website Monitoring in their workflows and processes.

Conductor Website Monitoring has become fully integrated in our release cycles, and in the near future we’ll extend the embedding of Contentking to other processes and services to clients. For example, client reporting, and proactive advice and application management.”

LinkedIn (opens in a new tab)Onno van Gils, Senior Project Manager, Arlanet

A big benefit in choosing Conductor Website Monitoring was how easy it was to get started. Van Gils: “We could start right away. The user training was very welcome, but we probably could have even done without it.”

The results

Since Arlanet embedded Conductor Website Monitoring in their QA processes they are now alerted about significant problems during their development cycles that would’ve been disastrous if they had been shipped.

In one example, a “noindex” directive was inadvertently placed in a template, which, if shipped, could’ve lead to the website’s full removal from the search engine result pages. Fortunately, with Conductor Website Monitoring, Arlanet caught the mistake very early in the process and addressed it before the incorrect directive was released.

Thanks to Conductor Website Monitoring’s collaboration features, Arlanet now even invites their clients to join them on the platform, working together to ensure everything is set up correctly for the next upcoming release.

Today Conductor Website Monitoring is a key part of Arlanet’s QA toolbox, giving them the control they need to ensure their clients not only get a rock-solid and feature-rich platform, but are also able to compete in search engine results.