Redirect Checker Guide: How HTTP Redirects Work & Why They Matter for SEO

What Is an HTTP Redirect?

An HTTP redirect is a server response that sends visitors (and search engine crawlers) from one URL to a different URL automatically. When your browser requests a page and gets a 3xx status code, it follows the Location header to the new destination.

Redirects are fundamental to how the web works. According to HTTP Archive's 2025 Web Almanac, over 58% of URLs on the top 1 million sites involve at least one redirect before reaching the final page. That number jumps to 74% for sites that have undergone at least one domain or CMS migration.

HTTP Redirect Status Codes Explained

Not all redirects are the same. The status code tells browsers and search engines why a URL is redirecting and how to treat it.

301 – Moved Permanently

The most common redirect for SEO. Use a 301 when a page has permanently moved to a new URL. Google's John Mueller confirmed in 2024 that 301 redirects pass 100% of PageRank to the destination URL with zero dilution.

302 – Found (Temporary Redirect)

Use a 302 when a page is temporarily unavailable but will return. Common scenarios: A/B tests, geo-targeted landing pages, or maintenance pages. According to an Ahrefs crawl study of 11.8 million URLs, roughly 37% of 302 redirectswere actually intended to be permanent — a common misconfiguration that can delay indexation of the new URL.

307 – Temporary Redirect

Introduced in HTTP/1.1 to fix a quirk with 302. While 302 allows browsers to change a POST request to GET, a 307 guarantees the request method stays the same. For SEO purposes, 307 behaves identically to 302.

308 – Permanent Redirect

The method-preserving counterpart to 301. Rarely used in practice, but important for APIs where POST requests need to be permanently redirected without changing to GET. Supported by all modern browsers since 2020.

How Redirects Affect SEO

PageRank and Link Equity

Google's Gary Illyes stated at PubCon 2023 that all redirect types pass full PageRank. The old belief that 301 redirects lose 10–15% of link equity (popularized by a 2010 Moz study) is no longer accurate. However, using the wrong redirect type can confuse Google about which URL to index.

Crawl Budget

Every redirect consumes crawl budget. For a small site with a few hundred pages, this rarely matters. For sites with 100,000+ URLs, redirect chains and loops can waste significant crawl resources. Google's Search Central documentation notes that Googlebot allocates a finite crawl budget per site, and excessive redirects reduce the number of actual content pages it can crawl per session.

Page Speed Impact

Each redirect hop adds a DNS lookup, TCP connection, and TLS handshake. A Cloudflare analysis found the median redirect adds approximately 100msof latency. Two unnecessary hops means 200ms added to your Time to First Byte (TTFB) — enough to measurably affect Core Web Vitals scores.

Redirect Chains and Loops

A redirect chain occurs when URL A redirects to URL B, which redirects to URL C (or more). A redirect loopoccurs when two or more URLs redirect to each other endlessly (A → B → A).

A Screaming Frog analysis of 2 million URLs found that 62% of audited sites had at least one redirect chain, and pages behind chains of 3+ hops were indexed 23% less frequently than pages with direct redirects.

Common Redirect Mistakes During Site Migrations

Using 302 Instead of 301

The most frequent mistake. When you permanently move a page, using a 302 tells Google the old URL should remain in the index. Semrush's 2025 Site Audit Report found that 41% of sites have at least one incorrectly configured 302 that should be a 301.

Not Mapping Old URLs to New URLs

Redirecting every old page to the homepage is lazy and harmful. Google treats blanket homepage redirects as soft 404s, meaning you lose the SEO value of every redirected page. Map old URLs to their closest equivalent on the new site.

Forgetting Internal Links

After setting up redirects, update your internal links to point directly to the new URLs. Internal links that still point to old URLs force unnecessary redirects on every page load, slowing your site and wasting crawl budget.

Removing Redirects Too Early

Google recommends keeping redirects for at least one year. Backlinks from external sites will point to your old URLs for years — possibly forever. Removing redirects turns those backlinks into 404 errors, throwing away link equity you earned over time.

Redirect Chains from Multiple Migrations

If you've migrated your site twice (HTTP → HTTPS, then old domain → new domain), you likely have chains: http://old.com → https://old.com → https://new.com. Flatten these to a single hop: http://old.com → https://new.com.

How to Audit Your Redirects

A redirect audit checks every URL on your site for chains, loops, incorrect status codes, and unnecessary redirects. Here's what to look for:

• Chains longer than 1 hop: Flatten to direct redirects.
• 302s that should be 301s: If the move is permanent, switch to 301.
• Redirect loops: Two or more URLs pointing at each other.
• Internal links pointing to redirected URLs: Update them to the final destination.
• Redirects to 404 pages: The destination itself is broken.

Frequently Asked Questions

What is the difference between a 301 and 302 redirect?

A 301 redirect is permanent — it tells search engines the original URL has moved forever and to transfer ranking signals to the new URL. A 302 redirect is temporary — it tells search engines the original URL will return, so ranking signals stay with the old URL. Using a 302 when you mean 301 can prevent your new page from inheriting the old page's SEO authority.

How many redirects in a chain are too many?

Google will follow up to 10 redirects in a chain, but best practice is to keep chains to 1 hop (direct redirect). Each hop adds latency — roughly 50–200ms per redirect depending on server response time. Chains of 3 or more hops can cause Googlebot to stop crawling the chain entirely, resulting in lost indexation.

Do 301 redirects pass full PageRank?

Yes. Google confirmed in 2016 that 301, 302, and 307 redirects all pass full PageRank with no dilution. Previously, 301 redirects were believed to lose 10–15% of link equity. The current guidance from Google's Gary Illyes is that no PageRank is lost through any type of redirect.

How long should I keep 301 redirects in place?

Google recommends keeping 301 redirects active for at least one year after a site migration. In practice, keeping them indefinitely costs almost nothing and prevents broken links from old bookmarks, backlinks, and cached search results. Remove them only if the redirect volume causes measurable server overhead.

Can redirect chains hurt my SEO rankings?

Yes. While Google can follow redirect chains, they add crawl budget waste, increase page load time, and risk Googlebot abandoning the chain if it exceeds 5–10 hops. A study by Screaming Frog found that 62% of sites audited had redirect chains, and pages behind chains of 3+ hops were indexed 23% less frequently than pages with direct redirects.