Monitoring FAQs

Does Conductor Monitoring affect my Web Analytics data?

In general, Conductor Monitoring’s monitoring doesn’t have any effect on your analytics data. However, there are certain edge-case scenarios in which Conductor Monitoring can impact the data.

These scenarios also depend on the monitoring configuration you are using in Conductor Monitoring, namely on the JavaScript Rendering feature.

Effect on web analytics when JavaScript rendering is disabled.

If you're using a JavaScript-based web analytics solution such as Google Analytics, Conductor Monitoring won't affect your analytics data.

Conductor Monitoring may inflate your web analytics data in one situation only: when you're using a server-side web analytics solution.

In this case you should prevent our crawlers from being tracked by excluding our crawlers' IP addresses.

Effect on web analytics when JavaScript rendering is enabled.

When monitoring a website with JavaScript Rendering enabled, Conductor Monitoring blocks requests to the most common web analytics and ad services to ensure that your web analytics data don’t get inflated by Conductor Monitoring’s monitoring.

This means that if you’re using a common JavaScript-based web analytics solution such as Google Analytics or Adobe Analytics, Conductor Monitoring’s monitoring does not have any effect on your web analytics data and you can safely enable the feature without any concerns.

If you’re using a non-standard web analytics solution and you want to ensure that Conductor Monitoring’s monitoring doesn’t affect your analytics data, make sure to configure custom on-page request blocking in Conductor Monitoring.

More about how to set up the blocking you can find here: Custom on-page request blocking

 
 

Can I monitor only specific sections of my website?

Although we strongly recommend against doing this it is possible to limit monitoring to specific sections of your website. The reason why we don't recommend doing this is that you create a blind spot for yourself, and tests that rely on multiple data points (such as auditing for broken links or duplicate-content issues) will have limited reliability.

We do understand that not every page may be equally important to the success of your business, but we've learned from experience that serious issues do occur in pages initially deemed to be "uninteresting," and these issues may in turn hurt the entire website's SEO performance.

To support the concept of having your entire monitored, we have made our pricing model as fair and flexible as possible: you only pay for pages (not for errors, redirects, etc.), and the more pages you monitor, the lower the price per page.

Having said all of this, if you still want to continue with monitoring only parts of your website, you can do this through the "URL Exclusion List". See this Support article on how to set this up: How can I exclude certain parts of my website from monitoring?

 
 

Can I pause monitoring on my website?

You can pause (and resume) monitoring through the website's monitoring speed settings. See our article on monitoring speed to learn how to do that.

Keep in mind that when monitoring is paused, your subscription remains active (you are still charged), but no changes will be detected and no alerts will be sent out.

 
 

What IP addresses does Conductor use when monitoring websites?

We monitor websites from the following IP address subnets:

  • 89.149.192.96/27
  • 81.17.55.192/27
  • 23.105.12.64/27
  • 173.234.16.0/28
 
 

How does Conductor Monitoring find URLs?

Just like search engines do, Conductor Monitoring uses several methods to find new URLs on websites:

  • XML Sitemap
  • Links between pages
  • Other relations between pages (canonical links, hreflang, prev/next relations, etc.)
  • Redirects
  • API (if you use this)
  • WordPress plugin (if you use this)

If a URL can be found through any of the methods above, Conductor Monitoring will pick up on it automatically. No further action is needed from you to get URLs added to the Conductor Monitoring database.

 
 

How do I troubleshoot “Unreachable URLs”?

There are times, usually when JavaScript or Lighthouse monitoring are enabled, that Conductor Monitoring is not able to access pages on your website. When this happens, you'll see an “Unreachable” error message, which may have a number of different causes:

Size limit

To ensure smooth performance, Conductor Monitoring has a size limit of 1MB for each URL (2MB when JavaScript rendering is enabled). This means that any page which is larger than 1MB (2MB respectively) can't be monitored in Conductor Monitoring unless we manually increase the size limit.

To resolve a size limit error, Conductor's Support team can increase the page limit for these pages.

Rendering time-out

To ensure smooth performance, Conductor Monitoring has a rendering time-out limit of 10 seconds for each URL. This means that any page that takes longer than approximately 10 seconds to render cannot be monitored in Conductor Monitoring unless we manually increase the time-out limit.

To resolve a time-out error, Conductor's Support team can increase the time limit for these pages.

Max on-page request limit

To ensure smooth performance, Conductor Monitoring can make a certain amount of on-page requests for each URL. If this limit is reached, Conductor Monitoring marks that page as unreachable.

To resolve a time-out error, Conductor's Support team can increase the on-page request limit for these pages.

Connect failure

The website your are monitoring is blocking Conductor Monitoring's crawler. 

To resolve a connection failure, whitelist the crawler so that our crawlers can access your website.

JS redirects

Conductor Monitoring doesn’t follow JavaScript redirects, and marks URLs that have them as unreachable. To resolve this, JavaScript rendering needs to be disabled. 

If you need assistance while troubleshooting the root causes of these errors, please reach out to our Support team.