Check HTTP/HTTPS, WWW & Query Redirects with Apify (n8n)

Check your HTTP/HTTPS, WWW, and query redirects with Apify—right from n8n

This n8n workflow uses Apify to manually verify how your site redirects across HTTP vs HTTPS, WWW vs non-WWW, and query URLs for up to 10 existing paths. You’ll get completeness-checked redirect observations and clear verdict counts (pass/review/fail/unknown).

What this workflow does

• Runs on manual trigger and reads your target canonicalOrigin, a list of paths (1–10), and an optional existing Apify run ID.
• Validates inputs (origin and paths), enforces limits, and requires you to acknowledge a capped paid Apify run before execution continues.
• Resumes or starts an Apify run:
  • If you provide a run ID, it reads and waits for that existing run’s results without restarting it.
  • Otherwise, it starts a new run of the Apify actor ecomopskits/www-https-query-redirect-checker with a USD0.16 maximum total charge cap.
• Polls the Apify Run API until the run succeeds, or fails if it doesn’t complete within allowed attempts.
• Verifies consistency: when resuming, it confirms the original Apify run input matches the current origin and paths. It then checks the Apify SUMMARY and dataset items to ensure the result set is complete.
• Returns detailed verdict counts plus observations about the observed redirects.

Use cases

• Validate redirect behavior after a migration to HTTPS or WWW canonicalization.
• Spot redirect inconsistencies on key landing pages and dynamic query patterns.
• Use n8n to routinely audit redirect correctness using Apify run history (resume runs when needed).

Technical details

• Apify integration: Add an Apify API token to an n8n HTTP Header Auth credential with header name Authorization and value Bearer YOUR_APIFY_TOKEN.
• n8n nodes/logic: Manual Trigger, if, set, code, sticky note, and HTTP Request steps.
• Inputs: canonicalOrigin, paths (1–10), and optional Apify run ID.