A 301 redirect can continue working for years without anyone checking whether it still leads to the right page. Over time, URL changes, site migrations, content updates, and added redirect rules can create unnecessary chains, loops, broken destinations, or outdated redirects. These issues can make it harder for users and search engines to reach the intended page. A 301 redirect audit helps uncover these problems by tracing each redirect from its source URL to its final destination and checking whether the path still works as intended.
What to Check in a 301 Redirect Audit
Evaluate a 301 redirect as a complete path, not a single HTTP response. Start with the original URL and follow the request through every redirect to the final destination. At each point, the goal is to determine whether the path is intentional, efficient, and technically sound.
A complete audit should establish:
- The source URL: Is this an old or changed URL that should still redirect?
- The redirect status: Does the source return a permanent redirect when the move is actually permanent?
- The redirect path: Does it go directly to the intended destination, or pass through additional redirects?
- The final response: Does the request end at a working page rather than another redirect or an error?
- The destination: Does the final page appropriately replace the original URL?
- The supporting signals: Do internal links, canonical URLs, and XML sitemaps consistently reference the preferred destination?
Step 1: Build a List of 301 Redirects to Audit
You cannot audit redirects you haven’t identified. Start by building a URL inventory that includes both redirects currently visible on the site and older URLs that may still receive traffic, links, or search activity.
A current site crawl is a useful starting point, but it should not be the only source. Review existing redirect rules, CMS or redirect-plugin records, previous migration files, XML sitemaps, and other available URL data. Google Search Console, analytics data, and server logs can also help uncover URLs that are no longer linked internally but may still be requested.
For each URL, record the source URL, current HTTP status, redirect destination, and final URL. Keeping these details together gives you a consistent dataset to test in the next stage and makes it easier to identify missing, outdated, or unexpected redirects.
Step 2: Trace Each Redirect to Its Final Destination
Once the URL list is ready, test each source URL and record the complete redirect path. The first response shows how the server handles the old URL, but it doesn’t tell you whether the request ultimately reaches the right page.
A simple result might look like this:
/old-page/ → 301 → /new-page/ → 200
That is a direct redirect to a working destination. A more complicated path might look like:
/old-page/ → 301 → /updated-page/ → 301 → /current-page/ → 200
The second example contains an additional hop that may no longer be necessary. Recording the full path makes these issues visible, rather than treating the first 301 response as proof that everything is working correctly.
For each URL, capture the source URL, the status code at each hop, the destination after each redirect, and the final response. You can use a crawler such as Screaming Frog, an SEO auditing platform, or an HTTP status checker to collect this information. The tool matters less than being able to see the complete path from the original URL to the page where the request finally stops.
Check for Redirect Chains
A redirect chain occurs when one redirect leads to another before reaching the final page:
/old-page/ → 301 → /page-2/ → 301 → /new-page/
If /new-page/ is already the intended destination, the old URL should generally point directly to it:
/old-page/ → 301 → /new-page/
Google recommends avoiding unnecessary redirect chains and redirecting directly to the final destination where possible. Googlebot can follow multiple redirects, but longer chains add requests and can increase the time it takes to reach the final page.
Check for Redirect Loops
A redirect loop occurs when URLs redirect back to one another instead of reaching a final page:
/page-a/ → 301 → /page-b/ → 301 → /page-a/
Because the request never reaches a final destination, the affected URL cannot resolve normally. Trace the redirect rules to find where the cycle begins, then change the conflicting destination so the request reaches the intended page.
Step 3: Verify That the Final Destination Is Correct
A redirect is not successful simply because it reaches a final URL. Check that the destination returns a successful response and does not end in another unexpected redirect, a 404 or 410 response, or a server error. If the destination fails, decide whether to restore the page, redirect it to a suitable replacement, or retire it intentionally.
The destination should also make sense in relation to the original URL. Compare the old page’s purpose with the new page’s content and intent. Redirecting a discontinued product page to its relevant replacement can be appropriate, but sending an unrelated page to the homepage simply because it is available does not provide a meaningful replacement. Google advises against redirecting unrelated old URLs to a single destination when no relevant replacement exists.
Step 4: Check Whether the 301 Is Still Necessary
Not every redirect needs to be removed just because it is old, and not every redirect should remain indefinitely without review. Check why the redirect was created and whether the original URL still has value, such as traffic, external links, or a role in an earlier site structure. If the old URL still needs to lead visitors and search engines to a relevant replacement, keeping the redirect may be appropriate.
Also check whether the website still relies on the redirect unnecessarily. Internal links should point directly to the current URL rather than continue sending visitors through an old address. For site moves, Google recommends keeping redirects in place for as long as possible, generally for at least one year, while updating internal links and other references to the new URLs.
Step 5: Check Internal Links and Other URL Signals
Once you’ve verified the redirect paths and destinations, check whether the rest of the website still references the old URLs. Internal links should point directly to the preferred destination rather than sending users through a 301 first. The same principle applies to XML sitemaps: they should contain the URLs the site wants search engines to crawl and index, not outdated URLs that simply redirect elsewhere.
Also review canonical URLs on important destinations to make sure they support the same preferred URL. Redirects and canonical tags are separate signals, but conflicting signals can make a site’s URL structure harder to interpret. The goal is consistency: internal links, sitemaps, canonical signals, and redirects should all support the same destination where appropriate.
Step 6: Fix the Redirect Issues
Once the audit identifies problems, fix each redirect according to what the URL is supposed to do. A correct 301 that leads directly to a relevant, working replacement can remain in place. Generally, shorten redirect chains by pointing the original URL directly to the final destination, and fix redirect loops by correcting the conflicting rules that prevent the request from resolving. If a redirect ends at an error or an unrelated page, identify an appropriate replacement or allow the old URL to return the correct response when no relevant replacement exists.
Also update the site’s own references after changing the redirect. Replace internal links that still point to redirected URLs, update sitemap entries to use preferred URLs, and correct conflicting canonical references where necessary. Make changes carefully, especially on large sites, because changing one redirect rule can affect other URLs that depend on the same rule.
Step 7: Re-Crawl and Validate the Fixes
An audit isn’t complete when you change redirect rules. Re-crawl the affected URLs and follow each redirect again to confirm that the changes produced the intended result. Check that permanent redirects reach the correct destination, unnecessary chains have been removed, loops no longer occur, and previously broken destinations now resolve correctly.
Also verify the supporting changes made during the audit. Internal links should point directly to the preferred URLs, sitemap entries should use the appropriate URLs, and canonical signals should remain consistent. If the site has undergone a larger URL change or migration, continue monitoring the affected URLs after the fixes to catch problems that may not appear during the initial re-crawl.
301 Redirect Audit Checklist
Use this checklist after completing the audit to confirm that the important issues have been covered:
- URL inventory: Have you included all known current and legacy URLs that may redirect?
- Redirect status: Does each permanent URL change use an appropriate permanent redirect?
- Redirect path: Does each URL reach its destination without unnecessary hops or loops?
- Final response: Does the final URL resolve successfully?
- Destination relevance: Does the destination provide an appropriate replacement for the original URL?
- Redirect necessity: Is the redirect still needed, or has the URL structure changed since it was created?
- Internal links: Do internal links point directly to the preferred URLs?
- XML sitemap: Does the sitemap contain the preferred URLs rather than outdated redirecting URLs?
- Canonical signals: Do canonical URLs support the intended destination?
- Validation: Have the affected URLs been re-crawled after the fixes?
Consider a redirect fully checked only after you’ve verified its path, destination, and related URL signals.
Conclusion
A 301 redirect audit is more than checking whether an old URL returns a 301. The real test is whether the request reaches the right replacement through a clean, working path and whether the site’s internal links, sitemap, and canonical signals support that destination. By systematically identifying redirects, tracing their paths, verifying destinations, fixing issues, and re-crawling affected URLs, you can keep an ageing or frequently changing URL structure accurate and easier to manage.