Web tool · FREE · NO ACCOUNT
Free Redirect Checker for WordPress Migrations
Check where old links actually land after moving a WordPress site. This redirect checker records each HTTP status and URL in the chain, follows up to six redirects, and highlights whether the final destination uses the origin you expect. Use small batches to audit important pages before and after a migration.
Checks follow up to six redirects using GET requests. Servers may respond differently to browsers, cookies, or geography. A matching origin does not confirm that the final page has the right content.
How to use migration redirect checker
- Paste up to five public HTTP or HTTPS URLs, one per line.
- Optionally enter the destination website origin that the migrated URLs should use.
- Run the check and review permanent redirects, temporary redirects, errors and loops.
- Download the CSV report and verify that the final pages contain the content you expect.
Questions and limits
What is the difference between 301 and 302?
301 indicates a permanent redirect; 302 indicates a temporary redirect. The checker reports the server’s actual status rather than deciding which status your migration should use.
Does this follow JavaScript or meta refresh redirects?
No. It follows HTTP Location headers for 301, 302, 303, 307 and 308 responses. Browser-only redirects need a separate browser check.
Why might a browser see different results?
Cookies, user agents, geography, bot protection and cached responses can affect redirects. This tool uses a public GET request with an identified tool user agent.
Can I check a staging site?
Public staging domains can be inspected. Private networks, IP addresses, password-protected sites and nonstandard ports are not supported.