Skip to main content

How to use alerts for SEO monitoring in Oncrawl

Learn how to create and manage crawl alerts using Pages, Links, and Crawl over Crawl comparison data.

Alerts and monitoring in SEO

Alerts are essential in SEO if you are working on a project associated with website monitoring, quality assurance, non-regression tests, or if you are interested in automating certain aspects of your regular auditing.

Oncrawl allows you to customize alerts that are triggered at the end of an analysis.

The conditions for triggering an alert are associated with a crawl profile and based on crawl metrics.

You can receive these alerts outside of the Oncrawl platform.

To set up a monitoring system with alerts, you will need to schedule regular crawls in order to be able to detect deviations for a given metric or set of metrics.

Alerting tasks in a project

You can find current alerts on the project home page, under the Tasks section at the top of the page.

If you don't have any alerts set up, this is where you can create a new one using the Create an alert button.

Using the Alerts tab in the Tasks table

Hover over the tab name to see how many alerts have been triggered recently.

This tab contains a table with seven (7) columns that can be sorted and filtered. By default, it is sorted by the alerts that were most recently checked.

  • Active / Inactive toggle. If the indicator is green, the alert will be checked and might trigger when a crawl with the associated crawl profile is run.

  • Alert name (can be sorted alphabetically)

  • Last alert status shows the result of the most recent check for this alert:

    • Triggered

    • Not triggered

    • Error: The alert could not be checked. Often this means that the required information to check the alert was not available in the crawl. Show/Edit details for more information.

    • N/A or No data: hover over this text for more information. This usually occurs if crawls that checked this alert are archived, or if no crawl has checked this alert yet.

  • Last checked (can be sorted by ascending or descending date order) shows the last time the alert was checked.

    • Dates are listed with the following format: May 07, 2024 09:14

  • Created at shows the date when the alert was created.

    • Dates are listed with the following format: May 07, 2024 09:14

  • Crawl profile shows the crawl profile associated with the alert.

    • Click on the icon to show the settings for this crawl profile.

  • Show/edit details opens the history of checks for this alert, their details, and the alert editor.

  • The three dots open menu with two options:

    • Duplicate the alert.

    • Delete the alert.

Viewing recently triggered alerts

Use the filters to show specific types of alert status, such as only showing triggered alerts:

Creating an alert

From the Alerts tab in the project’s Tasks section, click Create an alert.

1. Choose a dataset

The dataset determines the type of data and metrics available for the alert.

  • Pages monitors page-level conditions.

  • Links monitors individual links.

  • Comparisons: Pages monitors differences between the latest two crawls.

Using Comparisons: Pages

Comparisons: Pages uses the latest automatically generated Crawl over Crawl comparison for the selected crawl configuration. Manually created comparisons do not trigger alerts.

Comparable metrics can provide:

  • Crawl 1: the metric value in the first crawl.

  • Crawl 2: the metric value in the second crawl.

  • Delta: the numerical difference between Crawl 1 and Crawl 2. Delta is available for integer metrics.

  • Is same: whether the value is identical in both crawls. Is same is available for all comparable metrics.

For example, set Is same title to false to find pages whose title differs between Crawl 1 and Crawl 2. Set Delta follow inlinks to greater than 10 to find pages that gained more than ten followed internal links.

The Links dataset applies the alert definition to individual links rather than pages.

For example, you can create an alert to monitor:

  • internal links whose target returns a 404 status;

  • followed links pointing to external websites.

2. Select a crawl configuration

Select the crawl configuration that the alert should use. The crawl configuration determines which pages are analyzed and which metrics are available.

Choose a crawl configuration that runs regularly so the alert can evaluate new results over time.

Important: The crawl configuration is part of the alert definition and cannot be changed after the alert is created.

3. Choose an alert mode

Value mode

Use Value mode to trigger the alert based on the number of pages or links matching the alert definition.

Ratio mode (%)

Use Ratio mode (%) to compare the results matching the alert definition with a reference group. The alert triggers when the resulting percentage reaches the threshold you define.

4. Define the alert

Add the metric and filters that define what the alert should monitor. The available fields depend on the selected dataset and crawl configuration.

You can combine conditions using Oncrawl Query Language (OQL).

5. Check the preview

Use the Preview chart to check how the alert definition would have behaved against previous crawl results. Change the displayed period when you need more historical context.

6. Define the threshold

Set the value or percentage at which the alert should trigger. Use the preview to choose a threshold that identifies meaningful changes without generating unnecessary notifications.

When available, combine two thresholds with AND or OR to define an expected range.

7. Configure notifications

Choose who should be notified when the alert triggers. Available notification channels include:

  • Email

  • Slack webhook

  • Microsoft Teams webhook

By default, the workspace owner receives the notification by email.

8. Create the alert

Optionally, edit the alert’s name and description. Click Create in the upper-right corner. The alert becomes active immediately.

Editing an alert

Clicking Show/edit details beside an alert in the Tasks table opens details for this alert.

Two tabs are available:

  • Alert history shows past checks for this alert.

  • Settings shows the alert settings and allows them to be edited

Alert history

The alert history records every time the alert was checked during an analysis.

The following information is available:

  • The alert status when it was checked.

    • ⚠️ Triggered: An anomalie has been detected based on alert conditions you’ve set.

    • 🔴: Issues were encountered during alert check.

    • 🕛 : Your alert definition has changed over time.

  • The date the alert was checked.

  • Whether notification(s) were successfully sent. Hover over this column to see which notifications were sent, and which failed.

  • A link to the pages that match the alert's OQL, in the Data Explorer.

This link may be disabled if the OQL is changed after the check has occurred. This is because the new OQL will return a new set of pages in the Data Explorer, not the pages originally identified as potentially problematic.

  • A link to show the full crawl report for the complete analysis.

Settings

The alert settings display the crawl profile, the OQL, the preview, the threshold, and the notification settings for the alert.

All of these elements except for the crawl profile can be modified.

Because the crawl profile defines the available metrics and pages, it is an integral part of an alert and cannot be changed after the alert has been created.

Who receives notifications when alerts are triggered?

By default, the owner of the current workspace will be notified by email if an alert triggers. You can change this behavior by setting different notification information.

You can set notifications by:

  • Email

  • Slack webhook

  • Teams webhook

How to resolve typical errors with alerts?

Alerts that cannot be checked during an analysis are reported as having an error status. When this occurs, a warning will appear at the top of the Alerts tab in the Tasks section of the project page.

Filter the table by Last alert status to view the alerts in error.

To obtain more information about an alert in error, click on Show/Edit details.

A warning at the top of both the Alert history and the Settings tabs explains the error. Often, this error is related to metrics used in the OQL for the alert that are no longer available in the associated crawl profile.

Either correct the crawl profile, or create a duplicate the alert (using the three dots at the right of the alert's listing in the Tasks table on the project page and choosing Duplicate) and assign the duplicated alert to a crawl profile that includes the missing data.

Did this answer your question?