Skip to main content

Siteimprove Response Overview

Modified on: Tue, 16 Aug, 2022 at 3:03 PM

This article addresses some typical questions regarding the Siteimprove Response module. 

What is Response?

Response is a module within the Siteimprove platform used to check the availability of a given URL (checkpoint). 

It will test the URL availability using an HTTP request, in much the same way as a browser or command line request would.

The HTTP status code response for each check is registered within the Response module. The URL/checkpoint is registered as either Up (Successful) or Down (Failed). 

An alert is sent to selected users via SMS or email if a request fails.

Response can be configured to check from a preferred location, at a particular check frequency and if required, to check for a specific content match. (Note: Your checkpoint URL can be checked from a different location if the preferred location server is under load or unavailable.)

Successful HTTP Response (Up): If an acknowledged HTTP status code response indicates “everything is fine” such as HTTP 200 status code, Response will register this and continue to check the URL at the configured check frequency.

Failed response (Down): If an acknowledged HTTP status response code indicates “something is wrong”, such as HTTP 3xx, 4xx or 5xx status code then we re-test the URL/checkpoint from another location. If Response receives the same error from a second location or several locations, an alert will be sent.


What are some typical reasons for a failed (Down) HTTP response?

A failed (Down) HTTP response may be received for the following reasons:

  • Location: Geo-blocking (geo-restriction) is a method used to restrict the access of specified content based on a user’s geographic location. The most common method of achieving this is by using IP addresses to determine the location and restrict access. If this happens it is possible to configure a different location see - How do I choose server locations in Response?
  • No access: The URL/checkpoint that Response is checking may require specific user access. (Note: Authentication can be configured at Settings > Response > [Select Site] > Specifications.)
  • Temporary issues: See - Why did Siteimprove report my site as down when the server was running?

How does Response differ from Siteimprove Performance?

Siteimprove Response monitors the server’s HTTP-requests, and if the response time from the server exceeds a time limit, it will send a notification via SMS/E-mail. Response is intended to be used as a means of monitoring your different site URLs for server outages, availability problems or other factors that can limit the availability of your site. Response can also provide historical data based on these measurements over time.

Siteimprove Performance, on the other hand, is intended to be used as a means of monitoring, auditing, and improving your sites load times and web performance by means of what is called synthetic testing. Through this synthetic testing, Performance will emulate visitors using a range of parameters (e.g. network speed, location). These checks are scheduled in order to provide overviews that give users a better understanding of the front-end load experience for visitors of the pages in question. Performance also provides data on how the front-end load experience can be improved.

Other useful resources

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.