Pro6 min read · Free 1.1.2 / Pro 1.1.2

Read check results correctly

A reachable URL is evidence about a response, not a guarantee about content or SEO.

Passing, failed and unverified

Inspect the recorded response, redirect chain and final destination. Failed checks need review. Network failures, blocked requests and timeouts remain unverified. Checks do not judge whether a destination is relevant to the old page.

Check representative pattern URLs

A wildcard or regex check needs a saved example URL that matches its enabled rule. In the current migration workspace, find Representative URLs for pattern checks under Project tools. A missing sample is a request for more input, not a passing check. If updating from before 0.5.5, re-enter missing samples for affected case-insensitive regex rules and rerun checks. One successful sample does not establish that every possible matching URL works.

Keep background work running

Manual checks run while their page stays open. In the current Migration projects workspace, expand Project tools → Background checks, review the request consent and start the appropriate background job, then view their progress or cancel them under RedirectNest → Monitoring & schedules. Closing the tab does not cancel a queued job.

Unverified background requests retry up to twice. To retry failed results or reset recorded checks yourself, return to Migration projects and expand Retry or reset check results below the mapping table. A quiet site may run WordPress cron late. Check timestamps before trusting a monitoring report.

Know the boundaries

Network checks require PHP cURL and supported direct connections. All resolved target addresses must be public. Proxies, unavailable safe transport and private networks prevent verification. Export reports you need before retention removes them.

Only HTTP(S) ports 80/443 are supported. Every redirect hop is checked, TLS verification stays on, responses are bounded to 1 KB and each HTTP timeout to three seconds; chains have at most eight hops and a 20-second HTTP-loop budget. Hosting DNS resolution can take longer. Results describe reachability at the recorded time, not content relevance or search outcomes.

These guides describe Free 1.1.2 and Pro 1.1.2. Current downloads and availability.