Introduction to DeepCrawl Automator:  SEO QA

Alec Bertram
Alec Bertram

On 27th April 2020 • 4 min read

 

What is Automator?

Engineering teams often release code without understanding the full impact it can have on the overall SEO performance of the website.

This creates risk for sudden losses of traffic, rankings and in turn overall revenue.

DeepCrawl’s Automator gives development teams the ability to test their code for SEO impact before pushing to production with a smart, automated and frictionless tool that allows for better collaboration between development & SEO/Marketing teams.
 

Who should use Automator?

Automator has been designed to help solidify the communication between marketing and engineering teams and reduce the chance of human error.

In becoming part of the development process Automator can be used by engineers, QAs, Release Managers and SEOs.

How can Automator help Developers?

Automator works by integrating into a business’s CI / CD tool e.g Jenkins, Github Actions or TeamCity using a wide range of authentication options in order to cater to any need. Automator enables SEO to become part of the core workflow, which means teams can fix and identify problems proactively on an ongoing basis rather than having to go back after releases.

How can Automator help QAs?

Automator can be set up to run alongside the normal QA process, reducing time needed to check for SEO issues. It can deploy across multiple pre-production test /QA environments and you can select from more than 160 tests and receive instant notifications of issues over email or slack.

How can Automator help Release Managers?

As Automator is part of the development and QA process, releases can go ahead with greater confidence that errors will be significantly reduced. Automator has an extensive and flexible set of configuration options that let you define the outcome of tests either by blocking a release or raising a warning. This saves time and money in correcting any problems.

How can Automator help SEOs?

Automator helps SEO teams to maintain existing optimisation to prevent unnecessary traffic and revenue loss. Using Automator as part of the QA process means many problems will be identified and fixed without the need for SEOs to be continuously involved with releases – saving you valuable time which can be spent on revenue generating opportunities.
 

How Automator works

Automator works by integrating into a business’s CI / CD tools e.g Jenkins, Github Actions or TeamCity using a wide range of authentication options in order to cater to any need.

You can select from more than 160 tests and group them in different test suites that can be deployed across multiple pre-production test / QA environments. With an extensive and flexible set of configuration options you can fine tune the crawling experience and define the outcome of tests either by blocking a release or by raising a warning.

Notifications are sent instantly over both email and slack and you can close the feedback loop with an integration into Jira** to automatically create tickets.

With the introduction of Automator, we want to solidify the communication between marketing and engineering teams and reduce the chance of human error.


**Coming soon

Author

Alec Bertram
Alec Bertram

Alec is the Head of Product at DeepCrawl. He has 10 years' of experience in SEO, and works to make sure we're building the most valuable things we can for our users.

Get the knowledge and inspiration you need to build a profitable business - straight to your inbox.