404 Watch API

By
API Layer
Link checker API with advanced features and reporting capabilities.
404 Watch API
From
10
Vendor
API Layer

Features

Monitor website errors

Track downtime

Alerts for errors and downtime

Provides error analytics

Supports multiple websites

Offers APIs for developers

Customization options for alert notifications

About this Cloud Hub Solution:

Broken links can be detrimental to your website's user experience and search engine visibility. Google discourages broken links and downgrades your SEO reputation accordingly. To avoid this, it's essential to ensure that your website doesn't contain links to broken content or non-functional pages.

The 404 Watch API is a powerful link checker that can help you identify and fix broken links on your website. With its advanced features, you can:

  • Respect nofollow attributes and check external links
  • Discard query parameters and hash parameters
  • Check images, JS, and CSS files for broken links
  • Whitelist and exclude domains from checking
  • Trigger a callback URL when the link checking is done, or poll the results

Whitelisting Domains

If you have multiple domains served from a single site, you can add them to the whitelisted domains list while creating the link checker job. This will treat them as internal resources.

Excluding domains and URLs from checking

You can exclude specific domains from link checking by adding them to the excluded_domains_list or excluded_urls_list variables while creating the link checker job.

Callback when finished

Link checking can be a time-consuming process, especially if you have multiple URLs and assets on your site. To address this, the 404 Watch API uses an asynchronous approach.

You can create a link checking job using the POST /job endpoint and receive an ID in response. You can then poll the GET /job/{id} endpoint to monitor the ongoing link checking process or retrieve the results for finished jobs.

Alternatively, you can provide a callback URL when creating the link checker job via the POST /job endpoint. This will allow the API to call the provided callback URL (via HTTP POST) automatically when the process is completed.

You can also provide a callback_security variable when creating the link checker job, which will be placed in the HTTP header using the X-Callback-Secret header. This can be used for authentication purposes.

Sample Request for creating a new link checker job

Below is a sample request that can be sent to the POST /job endpoint. It includes various configuration parameters for optimizing the link checking process.

When called you'll get a response such as below:

You can use this id for querying the results via GET /job/{id} endpoint.

The response contains comprehensive details about the ongoing process and the results. See below:

Date variables above (created_at) are timestamps. Getting the details for each link that is checked. If you wish to get all the links that is discovered and been checked using the GET /job/{id}/links endpoint. See the following example.

The response contains all the links as well as the details for content types and http status codes. You may filter and use it the way you desire.

Highlights

Monitor website errors

Track downtime

Alerts for errors and downtime

Provides error analytics

Supports multiple websites

Offers APIs for developers

Customization options for alert notifications

Code