WWW HTTPS & UTM Redirect Checker

Check whether HTTP/HTTPS and www/non-www entry URLs reach your preferred HTTPS domain without losing the path or a synthetic tracking query. Supply an origin and up to ten existing paths; each path generates eight checks automatically.

Useful after a domain, CDN or redirect-rule change. Output is one JSON/CSV-ready row per check, with the observed chain, final status, expected destination and findings. SUMMARY contains the check counts. No site configuration is changed.

{"canonicalOrigin":"https://example.com","paths":["/"]}

Choose your actual preferred host, including www when appropriate. A working non-preferred host that serves content without redirecting is reported as a destination mismatch. Paths must already exist. The query probe contains only synthetic public values; never submit credentials, secret links or personal data.

pass means the observed final URL matched and returned HTTP 200 without flagged redirect behavior. review covers temporary or multiple redirects; fail covers observed mismatches, broken status, loops, missing Location, hop limits or HTTPS downgrades. DNS/TLS/network errors, blocked targets and HTTP 401/403/429 return unknown, not a site-health conclusion. Inspect the observed chain before fixing anything: some sites intentionally canonicalize paths or discard tracking queries.

Limits: HTTP GET only; no JavaScript, page-body inspection, canonical/meta-tag, robots.txt, Google indexing or analytics-attribution check. A pass does not prove SEO health or that analytics records a visit. URL comparison uses standard URL serialization; some equivalent escaping is normalized, but query order, path case and trailing slashes remain significant. No retry/proxy or access-control bypass. Up to seven requests per check, ten seconds per request, sequential with 200 ms spacing. Checking stops after 180 seconds, leaving a partial dataset and a stoppedForTime summary flag. Public HTTP(S) addresses on standard ports only; DNS and redirect targets are checked. Results stay in the caller's Apify run storage under its permissions and retention rules. Network results can differ by region and time.

Pricing: USD0.002 per non-unknown check (check-completed), with platform usage included and no start fee. Eight billable checks cost USD0.016. Observed failures, including loops and hop limits, are billable non-unknown results even when a chain cannot complete. Network/access-error rows marked unknown are free. The run stops when its remaining event budget cannot cover another check.

Support: supply a run ID, non-sensitive expected behavior and finding code. Do not send tokens or private URLs. No response-time guarantee is offered.