v1.7.0 2026-10-26 Check live redirects against your redirect map, on your live site or its staging copy, 100 URLs per check, basic auth, and a more accurate redirect checker.
New
- Check live redirects against your redirect map. In the redirect checker, choose “Against expected destinations” and paste or upload your source and expected destination pairs. Every source is checked live and gets one verdict: pass, wrong destination, no redirect, chain, temporary redirect, destination not 2xx, loop or error. Each result shows the expected and the actual URL side by side, and the CSV export includes the verdict. URLs are compared the way RFC 3986 defines them: differences in letter case of the domain, a default port or encoded letters are ignored, but a trailing slash or a change of letter case in the path makes it a different URL, and the result says when that is the only difference. A destination path such as
/new-pageis read on the source’s site. - Check paths and staging copies. Enter a site to test, and sources written as paths, such as
/old-page, are checked on it. Tick “Check full URLs on this site too” to run a map written for your live site against its staging copy before the switch: each URL keeps its path and query but is requested from the site you entered, expected destinations included. - Password-protected staging sites. Enter a user name and password under “Password-protected site (basic auth)”. They are sent only to the site you entered, never to another site a redirect leads to, and they are not stored.
- Choose the Accept-Language. Sites that redirect visitors by language now get the language you pick, from 16 common ones or your own value. By default the checker still sends English (US) as a browser and no language as a crawler.
- Filter the results by status class (2xx to 5xx, or no response) and by issue (errors, chains, loops, bot protection), or by verdict when checking against expected destinations. The CSV export contains the rows you see.
- Meta refresh redirects. The redirect checker now follows meta refresh and Refresh header redirects and marks them in the chain. Instant ones are shown as permanent and delayed ones as temporary, which is how Google treats them.
- Redirect loop detection. A loop is reported as soon as a URL comes back with the same cookies, instead of running into the redirect limit.
- Bot protection labels. When a site answers with a block or challenge page from AWS WAF, Cloudflare, DataDome, Akamai, Imperva, Sucuri or HUMAN, the result says so. Real visitors and search engines may get a different status. Akamai’s check page is recognized even when it answers 200, and the timed refresh on a check page is no longer followed as if it were the site’s own redirect.
- More user agents. Chrome Mobile and Googlebot Smartphone join Chrome Desktop, Googlebot Desktop, Bingbot and RedirectaBot.
- Live progress. Bulk checks show how many URLs are done, and results appear as they come in.
- Google’s 10-redirect limit. Chains longer than 10 redirects are flagged, because Google stops following them there.
Improved
- Check up to 100 URLs at once, up from 50. The limit of 150 URLs per minute stays, so a second full check within the same minute pauses with a message saying when to try again.
- Upload a file in the live checker. When checking against expected destinations, choose a CSV file or drop it on the text box.
- Accurate status codes. Every hop is requested with GET, like a browser or Googlebot does. Some servers answer HEAD requests differently, which showed codes real visitors never get.
- Chrome is the default user agent. Many sites block requests that claim to be Googlebot but do not come from Google, which showed 403 errors that Google itself never sees. A note under the user agent menu explains this when you pick a crawler.
- Clear error messages. DNS failures, refused connections, timeouts, expired certificates and missing intermediate certificates each get their own message instead of a generic connection error.
- More detail per hop. Every hop shows the status text (for example 301 Moved Permanently) and whether the redirect is permanent or temporary.
- CSV export. Opens correctly in Excel with non-English URLs, and includes the redirect type and any error for each hop.
- Rate limit. The limit now counts URLs (150 per minute) rather than requests.
Fixed
- Checking several URLs on a slow site could stop with “the chain took longer than 30 s” although no single response was slow. Time spent waiting for our own earlier requests to the same site no longer counts.
- The checker’s requests carried two tracing headers from our error monitoring, which no browser sends.
- Bulk checks could fail with an internal error after a mapping job had crawled destination pages.
- A slow site could make every later check of the same site wait indefinitely.
- Relative redirect targets such as //host/path, ?page=2 and ../page were resolved incorrectly.
- A 304 response was reported as a broken redirect.
- Domains that do not exist were reported as pointing to a private IP address.
- When a chain broke halfway, the final URL showed the last working hop instead of the URL that failed.
- https://example.com and https://example.com/ were treated as different final URLs in the canonical domain check.