check_redirects NEW
Validate old-to-new URL redirects
Overview
After cloning, your old WordPress URLs need to redirect properly to the new site. This tool validates that every redirect works correctly — catching broken redirects, wrong destinations, and redirect chains that hurt SEO.
How It Works
- Takes an array of old-to-new URL mappings.
- Follows each redirect chain to its final destination.
- Compares the final destination against the expected new URL.
- Reports broken 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
After setting up 301 redirects on your new site, validate that all 200 old WordPress URLs correctly redirect to their new equivalents. The tool catches 5 broken redirects and 3 that land on the wrong page.
Tips
Run this after your redirects are configured but before going live.
Redirect chains (A → B → C) hurt SEO — fix them to go directly A → C.
Use the URL mappings from discover_all_pages (source_url → clone_url) as input.