check_redirects NEW
Verify source and clone redirects match before go-live
Overview
Before going live, your clone site must honour every redirect rule that exists on the source site. This tool checks redirect parity between source and clone: you supply URL pairs derived from the source site's redirect rules, and it confirms the clone site handles each one correctly — catching missing redirects, wrong destinations, and redirect chains that hurt SEO.
How It Works
- Takes an array of source-to-clone URL mappings derived from the source site's redirect rules.
- Follows each redirect chain on the clone to its final destination.
- Compares the final destination against the expected clone URL.
- Reports missing redirects (4xx/5xx), wrong destinations, and unnecessary chains.
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
url_map |
array |
required | Array of { old_url, new_url } mappings to verify |
follow_chains |
boolean |
optional | Follow redirect chains to final destination (default: true) |
max_concurrent |
number |
optional | Max concurrent checks, 1-10 (default: 5) |
What You Get Back
- Status for each redirect (working, broken, wrong_destination, chain)
- HTTP status codes at each hop
- Final destination URL vs. expected URL
- Redirect chain details
Example Use Case
Export all 301 redirect rules from your WordPress source site, then run this tool against the clone to verify every rule is correctly configured. The tool finds 5 redirects the clone is missing entirely and 3 that land on the wrong destination page.
Tips
Export redirect rules from your source site (e.g. via a WordPress redirect plugin) and use them as the url_map input.
Run this after redirects are configured on the clone but before go-live.
Redirect chains (A → B → C) hurt SEO — fix them so the clone redirects A directly to C.