A redirect can be technically correct and still create lost traffic, unnecessary crawl work, slow page loads, or confusing campaign data. A recurring redirect health report helps website owners and SEO teams see those problems early. This guide defines the most useful redirect monitoring metrics, suggests practical thresholds, and provides a monthly workflow for combining server, CDN, crawler, and analytics data.
Overview
Redirect monitoring is the regular review of requests that pass through a URL redirect before reaching a final destination. It applies to permanent redirects used during site migrations, temporary redirects for campaigns, domain forwarding, shortened links, QR code destinations, and routine URL maintenance.
The goal is not to eliminate every redirect. A well-managed 301 redirect can preserve the value of an old URL and guide visitors to a relevant replacement. The goal is to confirm that redirects remain intentional, efficient, measurable, and safe.
A useful redirect health report connects four types of evidence:
- Server or CDN data: Which URLs were requested, which status codes were returned, how long responses took, and where errors occurred.
- Crawler data: Whether internal links, sitemaps, canonical tags, and external references point through chains, loops, or outdated URLs.
- Analytics data: Which redirecting URLs receive visits, campaign clicks, conversions, or other valuable activity.
- Change records: What launches, migrations, tracking updates, or redirect-rule changes took place during the reporting period.
Reviewing these sources together prevents a common mistake: treating a redirect as healthy simply because it eventually reaches a working page. A redirect may return the wrong status code, pass through several intermediate URLs, strip UTM tracking links, expose an unsafe forwarding parameter, or send visitors to an irrelevant destination.
What to track
Redirect volume and request share
Record the number of redirect responses and compare it with total requests or total page views where the data allows. Track both the count of redirecting URLs and the number of requests they receive. A small set of heavily requested retired URLs may matter more than a large set of inactive legacy addresses.
Break the total down by hostname, path group, campaign, status code, device category when available, and source. Pay particular attention to repeated requests for URLs retired during a migration. Those requests can indicate outdated internal links, external backlinks that still need attention, bookmarks, email links, or unresolved campaign placements.
Status-code distribution
Separate permanent redirects from temporary redirects. A 301 generally signals that a move is intended to be permanent, while a 302 or 307 is normally used when the original URL may return or the change is temporary. The correct choice depends on the implementation and business purpose; review the guide to 301, 302, and 307 redirects when a rule's intent is unclear.
Your report should also identify redirects that end in 4xx or 5xx responses. A redirect to a missing page is usually a higher-priority issue than a clean redirect with modest latency. Include direct error requests as a separate category so redirect failures are not hidden inside overall error totals.
Destination errors and relevance
For each important redirect, record the final status code, final URL, and whether the destination is the intended replacement. A successful response alone is not enough. A retired product URL that redirects to a generic category page may technically work while offering a poor experience and weak relevance.
Prioritize destination errors by request volume, conversion value, backlink importance, and business significance. Campaign links and QR code destinations deserve special attention because a small change can affect many placements at once.
Chain and loop frequency
A redirect chain occurs when one redirect points to another before reaching the final page. Count the number of hops for crawled and high-traffic URLs. A loop occurs when rules send a request back to a URL that has already been visited, preventing completion.
Report the number of chains, the longest chain, and the proportion of sampled redirect requests affected. Then identify the first URL in each chain. The cleanest fix is usually to update the original rule so it points directly to the final destination, rather than adding another layer. For a broader investigation, use a redirect audit checklist to review chains, loops, broken links, and related SEO issues.
Response time and availability
Measure redirect response time separately from the destination page's loading time when possible. A redirect that is slow at the server, CDN, DNS, or application layer can add friction before the page begins loading. Track median response time alongside slower requests, because averages can conceal occasional but serious delays.
Also record availability by redirect rule or hostname. Spikes in timeout responses, connection failures, or inconsistent status codes may point to infrastructure or configuration problems rather than an SEO mapping issue.
Traffic, attribution, and value
Connect redirect requests to sessions, landing pages, campaign parameters, conversions, and revenue or lead value where appropriate. Do not assume that the redirecting URL and the final landing page will appear as the same source in every analytics system.
Check whether UTM parameters survive the redirect and whether the destination records the intended source, medium, campaign, content, and term values. Query-string handling can affect both attribution and destination behavior; see how to handle query strings in URL redirects without losing tracking data.
Security signals
Monitor unusual destination parameters, unexpected external hosts, and sudden growth in requests containing arbitrary redirect targets. A forwarding feature that accepts unvalidated destinations can create an open redirect vulnerability. Include a security review in the report for redirect rules that accept user input, especially on login, tracking, and short-link paths. The open redirect prevention guide covers practical ways to constrain destinations.
Cadence and checkpoints
A monthly report is a practical baseline for most established sites. Review weekly, or more frequently, during a migration, domain change, major campaign, or redirect-rule deployment. A quarterly review can supplement the monthly process by examining long-term trends and inactive rules.
Use the same report fields each time:
- Reporting period and comparison period
- Total redirect requests and redirecting URL count
- Status-code distribution
- Requests ending in 4xx or 5xx responses
- Number of chains, loops, and average or median hops
- Response-time measurements and availability issues
- Top retired URLs by requests, traffic value, and referring source
- Campaign or QR code links with attribution changes
- New, changed, and removed redirect rules
- Open issues, owner, priority, due date, and verification status
At the beginning of each period, save a baseline. During the review, compare the current period with the previous period and with the last major launch or migration. After a deployment, run a focused checkpoint immediately: test representative URLs from every mapping group, confirm the expected status code, follow the complete redirect path, preserve approved query parameters, and verify the final page.
For migrations, start with the planned mapping file rather than waiting for live traffic to reveal problems. A URL redirect mapping template can provide a consistent place to document old URLs, final destinations, status codes, owners, and test results.
How to interpret changes
Set thresholds that reflect your site's size and risk, then keep them consistent. As a starting framework, investigate any new redirect loop, any high-value URL ending in an error, any unexpected external destination, and any sudden increase in chains. Treat a growing number of requests to retired URLs as a signal to inspect internal links and important referring pages, even when the redirects still work.
Do not interpret volume in isolation. A rise in redirects may be expected after a launch. A rise in redirect volume combined with slower response times and more destination errors is more concerning. Likewise, a drop in redirect traffic may indicate successful cleanup, but it may also mean that a campaign link broke or a referral source stopped sending requests.
Use a simple priority model:
- Urgent: loops, unsafe external forwarding, widespread errors, or failures affecting active campaigns and critical business pages.
- High: high-traffic chains, destinations returning errors, lost campaign parameters, and migration URLs with strong referral or conversion value.
- Routine: low-volume legacy redirects, isolated extra hops, stale rules, and outdated internal links that do not affect important journeys.
When diagnosing a change, compare the timestamp with deployments, DNS or CDN changes, analytics-tag updates, content releases, and marketing activity. Test from more than one environment when results are inconsistent. A crawler can reveal a rule problem that server logs miss, while logs can reveal real visitor behavior that a crawler never generates.
When to revisit
Revisit the report every month and perform a deeper review each quarter. Return sooner after a site migration, hostname change, HTTP-to-HTTPS change, redesign, CMS update, tracking implementation, major campaign, or QR code placement. These events can alter redirect rules, query-string behavior, canonical URLs, internal links, and attribution.
Keep a short change log beside the metrics. Note what changed, when it changed, which URLs were affected, and whether the follow-up test passed. This turns a recurring report into an operational record rather than a collection of disconnected numbers.
To make the next review actionable, export the top redirecting URLs, destination errors, longest chains, slowest rules, and highest-value campaign links. Assign each issue an owner and due date. After remediation, retest the original URL, every hop, the final destination, approved tracking parameters, and the recorded analytics outcome. Over time, the trend should show fewer unnecessary hops, fewer errors, cleaner attribution, and a smaller backlog of retired URLs still receiving meaningful traffic.
For a complete recurring process, pair this report with redirect log analysis and a documented migration checklist. The specific fields in server, CDN, crawler, and analytics platforms may change, so update the report whenever those tools change their terminology, bot classifications, export formats, or available dimensions.