Next, click the “+Create a crawl schedule” button.
Once you have set up the scheduled crawl, return to the “Crawl Alerts” section and begin setting up alerts specifically for your website. You can create as many alerts as you need since JetOctopus does not impose a limit on the number of alerts.
For JS alert settings, you can choose any of the data tables: “Pages”, “Difference in Pages”, “Links”, “Sitemap URLs”. However, most specific alerts for JS can be created based on the “Pages” data table.
To facilitate working with alerts, let’s briefly review their structure. Setting up each alert involves three steps.
Step 1: Configure conditions – in this step, you can specify what needs to be checked. For instance, you can choose the types of pages to monitor, specific elements on those pages, technical specifications, and more.
Step 2: Alert configuration – here, you define the conditions that trigger the alert. If the conditions set in step two are met for the pages or issues configured in step one, you will receive an alert.
Step 3. Send alerts to – configure the email addresses of team members or developers responsible for monitoring JS performance. This ensures that they receive the alerts. You can also send alerts to a Slack channel or receive SMS notifications on your mobile device.
The standard alert triggers when there is an increase in JS loading time by more than 50%. However, you can customize it to suit your specific requirements. For example, in the configuration settings, you can choose the type of pages for which you want to monitor the load time.
Apart from monitoring load time, you can also set up alerts to stay informed about the availability and changes in JS resources. These alerts are particularly useful for keeping track of resource availability and managing any fluctuations in their numbers.
Step 1: Configure conditions – select “Status code” – “=Equals” – “399”.
Step 2: Alert configuration – here, you need to set up the condition specific to your website. For example, if you have 100 verified JS redirects, you can choose an absolute value of 100 as the threshold. Any value higher than that would be considered an error.
Additionally, you can configure an alert to trigger when the number of JS alerts increases by more than 10%.
To set up these alerts, use the “Pages” datatable and configure alerts for changes in indexing rules, titles, meta descriptions, and other aspects resulting from JS rendering.
What does this mean? It often happens that the web server initially provides default indexing rules, titles, and meta descriptions to bots. However, after executing the JS, the page receives correct indexing rules, a unique title, and meta description. Search bots, however, always enforce more restrictive rules. Therefore, monitoring such cases is essential.
To configure this alert, select the “JS Content Changes” block in the conditions and choose the desired item to track. For example, select “Meta Indexation changed” – “Yes”.
Next, in the alert configuration, choose “Rows count” – “Current count” – “More than” – “0”.