A redirect checker helps you confirm that an old, campaign, or insecure URL reaches the intended destination without unnecessary hops, loops, broken responses, or device-specific surprises. This guide explains how to test 301, 302, and HTTPS redirects, record the results, and build a recurring review process for migrations, technical SEO audits, and link maintenance.
Overview
A URL redirect test should answer more than “does this link open?” A browser may follow several redirects automatically and display a working page even when the underlying path is inefficient or incorrectly configured. A proper check records the response from the original URL, each intermediate hop, and the final destination.
For every important URL, verify five points:
- The source responds as expected. The old URL should return an intentional redirect rather than a server error, soft 404, or unrelated page.
- The redirect type matches the change. A permanent move and a temporary routing rule have different purposes.
- The chain is controlled. The source should reach its final destination in as few hops as practical.
- The destination is correct. Check the path, protocol, hostname, query string, language, and device experience.
- The result is repeatable. Test with the relevant protocol, user agent, location, or authentication state when those variables affect delivery.
This process is useful after a domain change, HTTPS migration, site redesign, URL restructuring, campaign launch, affiliate update, or server configuration change. It also complements a broken link and redirect audit and a broader outbound link monitoring workflow.
What to track
301 versus 302 redirects
A 301 redirect generally communicates that a resource has moved permanently. Use it when an old URL has been replaced and the old address should consistently lead to the new one. A 302 redirect generally communicates a temporary move or temporary routing decision. Use it when the original URL is expected to remain relevant and the alternate destination is not intended to replace it permanently.
The correct status depends on the publishing and technical context, not simply on which code appears to work in a browser. Before changing a rule, document whether the move is permanent, temporary, conditional, or part of an experiment. Also check whether your server or framework is returning a different 3xx code than the one configured.
Redirect chains and loops
A redirect chain occurs when URL A sends the visitor to URL B, which sends the visitor to URL C. Chains can result from several historical migrations, such as HTTP to HTTPS, an old domain to a new domain, and an outdated slug to a current slug. Wherever practical, update the source rule so it points directly to the final canonical destination.
A redirect loop occurs when the request is sent back to a URL it has already visited, or when two systems repeatedly redirect to each other. Common causes include conflicting HTTP and HTTPS rules, proxy settings, host normalization, and application logic that does not recognize the forwarded protocol.
HTTPS and hostname behavior
Test each relevant protocol and hostname separately. For example, check the HTTP and HTTPS versions, with and without the preferred hostname, and any legacy subdomain that was publicly used. Confirm that the final URL uses the intended protocol and hostname rather than stopping at an intermediate version.
Do not assume that a successful HTTPS page proves every variant is configured correctly. A redirect checker can reveal whether http://example.com, http://www.example.com, and other accepted variants follow the same policy. If URL normalization matters to your site, compare the results with the conventions documented in your URL parsing and normalization workflow.
Other variables worth recording
- Source URL and the exact time of the test
- Every response status and intermediate URL
- Hop count and final URL
- Whether the destination returns a successful page response
- Query parameters, fragments, and tracking parameters
- Mobile, desktop, regional, or language-specific behavior
- Whether the result changes when cookies or authentication are present
- Owner, priority, required action, and review date
Redirect checker capability comparison
| Capability | Basic checker | Advanced checker or workflow | Why it matters |
|---|---|---|---|
| Final URL | Usually | Yes, with full path details | Confirms the visitor reaches the intended destination. |
| Status code per hop | Sometimes | Yes | Distinguishes intentional redirects from errors and unexpected responses. |
| Chain and loop detection | Limited | Yes | Finds inefficient paths and repeating rules. |
| HTTPS and hostname variants | Manual | Batch or scripted | Tests migration and canonicalization coverage. |
| User-agent or regional testing | Rarely | Often configurable | Reveals conditional behavior that a single browser test can miss. |
| Export and history | Rarely | Common in monitored workflows | Supports audits, ownership, and recurring comparisons. |
For a small number of URLs, a web-based redirect checker may be sufficient. For a migration or large link inventory, use a bulk URL validation process, a crawler, or a developer link API that can export each hop and response. Keep the test method consistent so results from one review can be compared with the next.
Spreadsheet-ready redirect test log
Copy the following header row into a spreadsheet or issue tracker. Add one row per source URL and preserve the original test result before making changes.
source_url,hop_count,final_url,status_code,redirect_chain,protocol_result,device_or_region,owner,priority,action,review_date,notes https://old.example/page,1,https://www.example/page,301,https://old.example/page > https://www.example/page,pass,desktop,web-team,high,none,2026-11-05,Direct permanent move
The status_code field should identify the source response; if there are multiple hops, record the full sequence in redirect_chain or add one row per hop. Avoid storing only a final “pass” label, because a later reviewer needs enough detail to diagnose a change.
Cadence and checkpoints
Redirects are most useful when checked at predictable points rather than only after a visible failure. Use the following cadence as a starting framework and adjust it to the risk and volume of your URL inventory.
Before a migration or launch
Build a source list from old URLs, XML sitemaps, analytics landing pages, internal links, campaign documents, and external link inventories. Test the proposed mappings in a staging or controlled environment when possible. Pay special attention to high-value pages, URLs with backlinks, and pages referenced in printed materials or QR codes.
Immediately after a change
Run the same test set after a domain move, HTTPS rollout, CMS change, permalink update, server migration, or redirect-rule deployment. Compare the new hop count, status sequence, and final URL with the baseline. Recheck representative mobile, regional, and authenticated paths if those experiences use separate routing logic.
Monthly or quarterly maintenance
Review priority redirects on a monthly or quarterly schedule. A smaller site may test every important redirect; a larger site can sample stable URLs and fully test recently changed, high-traffic, or externally referenced paths. Also inspect newly reported broken links and destination changes. Link monitoring and redirect checks work better together: monitoring identifies what changed, while the redirect test explains how it changed.
After infrastructure changes
Repeat tests when a CDN, reverse proxy, hosting platform, security layer, DNS configuration, application router, or caching policy changes. These systems can alter protocol detection, host handling, cookies, or geographic responses even when the page content itself has not changed.
How to interpret changes
A change is not automatically a defect, but it should be explained. Use the following questions to separate intentional updates from problems:
- Did the status code change? A 301 becoming a 302 may indicate a deployment or configuration change that needs confirmation. A 3xx response becoming a 4xx or 5xx response requires investigation.
- Did the hop count increase? Trace each hop and identify which rule added it. Replace avoidable historical chains with a direct mapping where practical.
- Did the final URL change? Compare the path, hostname, protocol, query string, and language or regional version. A page that loads is not necessarily the intended page.
- Does behavior vary by client? Test the affected device, user agent, location, cookie state, or login state before changing a general rule. Conditional behavior may be intentional, but it should be documented.
- Are tracking parameters preserved or altered deliberately? Campaign URLs should follow the agreed naming and retention rules. Review the UTM parameter governance guide when a redirect changes campaign attribution data.
Prioritize issues that affect many source URLs, important entry points, or URLs used in active campaigns. A single extra hop on a low-priority legacy URL may be less urgent than a redirect loop on a primary landing page, but both should have an owner and a recorded decision.
When to revisit
Revisit this redirect checker workflow on a monthly or quarterly cadence, after any migration or routing change, and whenever monitoring shows a destination or status change. Review the article and your internal checklist when browser behavior, server configurations, or relevant search guidance changes materially; the testing principles remain stable, but tools and implementation details can evolve.
To put the process into practice, start with a focused inventory of important URLs. Run a redirect checker against HTTP and HTTPS variants, legacy hostnames, campaign links, and recently changed paths. Record the source URL, every hop, final URL, status code, test conditions, owner, and review date. Fix loops, broken destinations, incorrect permanent-versus-temporary signals, and avoidable chains. Then save the results as a baseline and schedule the next review.
For larger inventories, connect the log to a crawler, bulk URL validator, or link management API workflow. Keep redirect rules, campaign links, and migration mappings under version control where practical. This turns a one-time URL redirect test into a repeatable part of website maintenance.