To track redirects, first define which URLs to check, then verify the response statuses, number of redirects, and final destinations. Checking only the first hop is not enough. Run regular technical audits and review whether temporary redirects are still needed; after a site redesign, migration, or domain change, conduct a comprehensive audit. A tool’s option to keep following redirects means following the redirect path to its endpoint, not continuously monitoring the website.
Define the scope first: the entire site, old URLs, and key user flows
The scope should match the purpose of the check. Results from a partial list of URLs cannot be treated as conclusions about the entire site.
- Routine audits: Review the site’s redirects to check whether their types are appropriate and whether any redirect chains or loops exist.
- Migration validation: Start with a list of old URLs and verify that each reaches the correct new destination, rather than checking only the new site.
- Key user flows: Pay particular attention to pages that handle user information, such as login and shopping cart pages, and check whether redirects affect data handling.
A 2023 Semrush article advises checking whether data is preserved during redirects on pages that handle user information. This does not mean that all login or shopping cart pages must use the same status code.
Maintain a tracking list so temporary redirects are not forgotten
A spreadsheet can record redirects, but maintaining it can be cumbersome. If you miss an entry, you may later forget to remove a redirect that is no longer needed. Semrush’s 2023 article recommends tracking 302 redirects and removing them when they are no longer needed. For example, temporary redirects used for short-term promotions or page maintenance should be reviewed once the promotion or maintenance ends, rather than kept indefinitely.
The article describes how to use Site Audit’s redirect list to review redirect types and its issue reports to identify redirect chains and loops. These instructions reflect the tool at the time; interface labels or locations may differ today.
Follow redirects to the endpoint and keep the full list for migration audits
Screaming Frog’s 2013 release notes for version 2.20 state that enabling “Always follow redirects” allows list mode to ignore crawl depth and follow redirects to the final destination. For example, an old URL might return a 301, pass through another 301, and ultimately reach a 404. Checking only the first hop would miss the problem.
Screaming Frog’s 2015 article further explains that the redirect mapping report includes all uploaded URLs and their responses, along with the number of redirects or any loops. Migration validation should check the complete list of old URLs, not just entries with redirect chains. Even if a redirect reaches an endpoint, verify that the destination and response match expectations.
Recheck after major changes and audit regularly
A 2021 Semrush article recommends a full-site audit after a redesign, migration, or domain change, since these changes can unintentionally create redirect loops. When troubleshooting, also check for conflicting redirect rules in plugins or custom code. Regular technical audits are recommended as part of routine maintenance, but the article does not specify a fixed weekly or monthly schedule. It therefore does not establish an audit interval that applies to every website.
Redirect tracking and auditing: perspectives from across the web
If an old URL returns a 301, does that mean the migration passes validation?
No. A 301 on the first hop alone is not enough to pass validation. An old URL may pass through two 301 redirects and ultimately reach a 404, so you also need to check the final response and destination. Screaming Frog’s 2015 migration audit guide starts with a list of old URLs, and the resulting mapping report also includes uploaded URLs without redirect chains. You can use this report to check the list item by item, but the conclusions apply only to the uploaded URLs.
How should you handle an existing 302 redirect after a short-term campaign ends?
Reassess whether the campaign’s 302 redirect still serves a purpose, and remove it when it is no longer needed. A spreadsheet can track these configurations, but if a redirect is not recorded when it is created, it may also be forgotten later. A spreadsheet alone therefore cannot establish that the list is complete. Redirects listed by a site audit tool can help with the review; each should then be assessed against its original purpose.
When you find a redirect loop, what should you check besides the URLs themselves?
Check whether plugins or custom code have conflicting redirect rules. Semrush suggested this troubleshooting approach in a 2021 article, particularly for loops discovered after a site redesign, migration, or domain change. However, plugins are not necessarily the cause of a loop; the actual configuration still needs to be checked.
References
- 308 Permanent Redirect: What It Means & When to Use Itwww.semrush.com · 2023-11-20T09:24:00Z — Source used in the article above.
- Screaming Frog SEO Spider Update – Version 2.20www.screamingfrog.co.uk · 2013-07-15T11:06:00+00:00 — Discusses: If an old URL returns a 301, does that mean the migration passes validation?
- 10 Features In The SEO Spider You Should Really Knowwww.screamingfrog.co.uk · 2015-01-22T11:48:45+00:00 — Discusses: If an old URL returns a 301, does that mean the migration passes validation?
- How to Set Up an HTML Redirect (+ Alternatives)www.semrush.com · 2023-07-24T08:57:00Z — Discusses: How should you handle an existing 302 redirect after a short-term campaign ends?
- What Is the ‘Too Many Redirects’ Error? & How to Fix Itwww.semrush.com · 2021-08-13T15:59:00Z — Discusses: When you find a redirect loop, what should you check besides the URLs themselves?




