URL Status and Expected Redirect Checker

Check a list of public URLs and find out whether they respond and reach the destination you intended. Useful for testing a supplied migration map, checking redirects after a site change, or verifying a batch of links.

What you provide

A JSON list of URLs. Add an expected destination when checking a migration or redirect rule:

{
  "checks": [
    {"sourceUrl": "https://old.example.com/product", "expectedUrl": "https://new.example.com/product"},
    {"sourceUrl": "https://new.example.com/contact"}
  ],
  "requirePermanent": true,
  "ignoreQuery": false
}

These example domains illustrate the format; they are not claims of live working customer sites. Use URLs you are authorized to request. Do not submit login credentials, secret query strings, or private-network addresses.

What you receive

One structured result per completed unique check, plus a readable HTML report. Results include the observed HTTP status, each redirect hop, final URL, expected URL, a verdict, and a suggested next action.

A final 200 response does not automatically pass: when an expected destination was supplied, it must also match. An access restriction or rate limit is reported as inconclusive rather than mislabeled a missing page.

Exact duplicate input rows are skipped. Invalid or prohibited URLs appear in the complete report but are not charged as checked results. Network/DNS/time-out outcomes are reportable checked results, not guarantees that a page is missing.

Limits

Only supplied URLs are checked; the tool does not crawl a website, discover a sitemap, render JavaScript, inspect page content, or bypass access controls. It does not predict search rankings or traffic. A URL fragment is not part of an HTTP request and is not verified. Query strings are compared unless you explicitly turn that comparison off.

At most 1,000 input rows are accepted per run. Run limits and customer spending limits can stop processing early; the report identifies unprocessed rows. Use smaller batches for slow targets. Only public HTTP(S) destinations and standard ports are supported. No proxy or login is used.

Pricing

The price is $0.003 per completed unique URL check ($3 per 1,000), plus $0.01 each time the Actor starts. There is no dataset-insertion fee and no separately configured customer platform-usage surcharge.

One run completing 10 chargeable results costs $0.04; 100 costs $0.31; 1,000 costs $3.01. Rejected unsafe or malformed rows have no result charge, but a started run still has its start charge. Completed negative HTTP, DNS, TLS, and timeout findings are charged because they are delivered check results.

Customer maximum-charge limits can stop a batch before every row is processed. Set a limit of at least $0.013 to cover one start and one result. The final report identifies unprocessed rows.

Each resurrection incurs another $0.01 start charge. In testing, resurrecting an already completed run added this charge even beyond the original maximum-charge setting. Do not resurrect completed runs; start a new run with a new spending limit to perform fresh checks.

Support boundary

For a suspected defect, supply the run ID and a nonsensitive example URL. This utility reports observations; it does not modify your website or sell custom migration consulting.

Verified platform examples

A private Apify run checked two purpose-built public testing-service URLs:

Supplied URL	Observed HTTP status	Report verdict
https://httpbingo.org/status/200	200	PASS
https://httpbingo.org/status/404	404	NOT_FOUND

The run completed both checks and produced two dataset rows, an HTML report, and a complete JSON report. With live private pricing, Apify recorded two $0.003 URL events and one $0.01 start event, totaling $0.016.

A $0.013 maximum-charge test delivered one result, left one row unprocessed, and recorded exactly one URL event plus one start event. An interrupted run was aborted after two stored rows, resurrected, and finished with six unique rows and no duplicate URL charges. Apify recorded six URL events and two start events, totaling its $0.038 limit.

These are owner-run public-test integration and billing-control checks, not customer work. They do not establish demand, revenue, profitability, or payout.

These observations are a historical sample. A later request can produce different results when a test service or network is unavailable.