# WWW HTTPS & UTM Redirect Checker (`ecomopskits/www-https-query-redirect-checker`) Actor Check HTTP/HTTPS and www redirects with automatic path and query-preservation tests. One preferred origin generates eight checks per path, with observed chains and structured results. - **URL**: https://apify.com/ecomopskits/www-https-query-redirect-checker.md - **Developed by:** [Vladimir Oprea](https://apify.com/ecomopskits) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing $2.00 / 1,000 completed redirect checks This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## 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. ```json {"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. # Actor input Schema ## `canonicalOrigin` (type: `string`): For example https://example.com or https://www.example.com. No path, query, credentials or private host. ## `paths` (type: `array`): Use existing paths such as / or /products/item. Synthetic public UTM parameters are added automatically. No private query data. ## Actor input object example ```json { "canonicalOrigin": "https://example.com", "paths": [ "/" ] } ``` # Actor output Schema ## `checks` (type: `string`): No description ## `summary` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "canonicalOrigin": "https://example.com" }; // Run the Actor and wait for it to finish const run = await client.actor("ecomopskits/www-https-query-redirect-checker").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "canonicalOrigin": "https://example.com" } # Run the Actor and wait for it to finish run = client.actor("ecomopskits/www-https-query-redirect-checker").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "canonicalOrigin": "https://example.com" }' | apify call ecomopskits/www-https-query-redirect-checker --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,ecomopskits/www-https-query-redirect-checker" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/bk0IjVADsctt3rrXA/builds/GIjMBnEK16gYb7s3Y/openapi.json