Check Broken Links: HTTP 200 vs 404 Example

Created by

代美小澤

Actor

Affiliate Revenue Leak Monitor

Compare a working URL (HTTP 200) with an intentionally missing page (HTTP 404) using Affiliate Revenue Leak Monitor. This example checks two public HTTP test endpoints, classifies their responses, and exports CSV findings. It demonstrates HTTP status detection, not actual affiliate commission loss.

Try for free

Affiliate Revenue Leak Monitorfaithful_schlumbergera/affiliate-revenue-leak-monitor

Risk level

HTTP status

Link category

Link text

+3 fields

Input

Mode:scan

Manual links (including YouTube description links):https://httpbin.org/status/200 https://httpbin.org/status/404

Output fields

Risk level

HTTP status

Link category

Link text

Checked URL

Finding

Recommended action

How it works

Sign up on Apify or log in

The Affiliate Revenue Leak Monitor Actor is ready to run with the inputs already set for "Check Broken Links: HTTP 200 vs 404 Example". Sign up or log in and you'll land in Apify Console with a copy of this exact task.

Start the "Check Broken Links: HTTP 200 vs 404 Example" task

The Affiliate Revenue Leak Monitor Actor will start running based on the input automatically. You can also change all the input fields, like mode and manual links (including youtube description links), to match your specific use case.

Receive the "Check Broken Links: HTTP 200 vs 404 Example" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as risk level, HTTP status, link category, and more.

Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Check Broken Links: HTTP 200 vs 404 Example" task via API.