~/tools/redirect-checker

Redirect Checker

Follow every hop a URL takes before it lands. Long redirect chains and 302s where you meant 301 leak link equity and slow your pages — see the whole path in one shot.

§ what this tool checks

Rules applied to every scan.

Every redirect adds a round trip before your page loads, and every extra hop bleeds a little more ranking signal. A temporary 302 where you meant a permanent 301 tells Google not to pass authority at all. This tool follows your URL hop by hop — recording each status code and Location header — so you can see the exact path, catch loops, and confirm you're using the right redirect type.

Every hop in the redirect chain with its status code

301 (permanent) vs 302/307 (temporary) redirect types

Redirect chains longer than one hop

Redirect loops that never resolve

HTTP → HTTPS upgrade in the chain

Final destination URL and status code

§ faq

Questions, answered.

What is the difference between a 301 and a 302 redirect?

A 301 is a permanent redirect: it tells search engines the page has moved for good and passes ranking signals to the new URL. A 302 (and 307) is temporary: search engines keep the original URL indexed and may not pass authority. Using a 302 for a permanent move is one of the most common SEO mistakes — it silently caps the new page's ability to rank.

Why are long redirect chains bad?

Each redirect is an extra network round trip before the browser gets your content, so chains slow down page loads and hurt Core Web Vitals. Search engines also limit how many redirects they will follow (Google stops following after about 5 hops) and a little ranking signal can be lost at each step. Redirect straight to the final URL whenever possible — A → C, not A → B → C.

What is a redirect loop?

A redirect loop happens when URLs point back at each other (A → B → A) or a page redirects to itself, so the chain never resolves. Browsers give up with a "too many redirects" (ERR_TOO_MANY_REDIRECTS) error and the page never loads. Loops are usually caused by conflicting rules between your CMS, CDN, and server config — for example, both forcing and stripping a trailing slash.

Should www and non-www both redirect to one version?

Yes. Pick one canonical version (either www or non-www, and always HTTPS) and 301-redirect all other variants to it. Serving the same content on multiple host or protocol combinations splits ranking signals and can create duplicate-content confusion. A single permanent redirect to your canonical host consolidates everything onto one URL.

§ run the full audit

Stop guessing. Scan everything in one click.

60 automated checks across meta tags, robots.txt, Open Graph, sitemaps, headings, AI visibility, and more — free, no signup.

run a full scan →

§ other tools

Check another thing.

Single-purpose inspectors for when you need to verify one thing.

01Meta Tag CheckerCheck your page title, meta description, viewport, charset, and robots tags.02Robots.txt ValidatorValidate your robots.txt file for syntax errors and blocking rules.03AI Crawler CheckerTest if ChatGPT, Claude, and Perplexity can actually read your page — not just whether your robots.txt says they can.04Open Graph Tag PreviewCheck your Open Graph and Twitter Card tags for social media sharing.05Sitemap ValidatorValidate your sitemap.xml file format and URL count.06Heading Structure CheckerAnalyze your H1-H6 heading hierarchy for SEO best practices.07SSL Certificate CheckerCheck your SSL certificate: expiry date, issuer, and trust chain.08Structured Data ValidatorValidate your JSON-LD schema markup for missing fields and errors.09Broken Link CheckerScan a page for internal links that return 404s and server errors.10Core Web Vitals CheckerCheck the lab signals behind LCP, CLS, and a fast first byte.11Security Headers CheckerScan your HTTP response headers for CSP, HSTS, and other protections.12Canonical Tag CheckerCheck your canonical tag and confirm it points where it should.