Redirect Checker
Check your redirect setup against our Website Standards: one canonical host, single-hop redirects, clean error pages, with evidence for every finding
Enter the page address, with or without https://
What This Tool Checks
MetadataBase set (OG/canonical absolute, resolve)
Fat footer on every page incl. 404/500
Custom 404: branded, full nav, way home, real 404 status
Custom error boundary; no stack traces/codes exposed
ONE canonical host + slash convention; 301 every variant
XML sitemap from content source, only 200 canonical URLs, submitted GSC+Bing
Real 404/410; no redirect chains >1 hop; no orphans; at most 3 clicks from home
Hreflang: reciprocal clusters, self-canonical, targets 200, x-default
Subfolder strategy; never auto-redirect by IP
HTTPS every page/asset; http to https at edge; auto-renew certs
Page inventory: Home/About/Contact/Services/Privacy/404/thank-you
Zero lorem ipsum, placeholder imgs, coming-soon stubs, broken links/images
Domain auto-renew ON, payment current, expiry alerts, registrar 2FA
One canonical host, other 301s; DNS hygiene
Zero console errors on key pages; no broken links/images
Redirects from all old URLs after relaunch
Every result quotes the evidence we found. Anything we cannot measure from outside is listed plainly instead of guessed.
Frequently Asked Questions
Common questions about this tool and how to use it effectively
A 301 redirect is permanent: it tells search engines the page has moved for good, and they transfer the old page's ranking signals to the new URL. A 302 redirect is temporary: search engines keep the original URL indexed. Using a 302 where you mean a 301 can stall your SEO because ranking signals never consolidate.
A redirect chain is when URL A redirects to B, which redirects to C. Every extra hop slows the visitor down, leaks link equity, and risks crawlers giving up. Our standards allow at most one hop: every old URL should point straight at its final destination.
A loop is when a URL eventually redirects back to itself, leaving browsers showing a too-many-redirects error. Common causes are conflicting rules between your server, CMS plugins, and CDN (for example one layer forcing www while another strips it). Fix it by picking one canonical host and protocol and declaring it in one place only.
Done right, redirects preserve your rankings through URL changes and consolidate duplicate hosts (http vs https, www vs bare domain) into one canonical version. Done wrong, chains and loops waste crawl budget, dilute ranking signals, and can drop pages from the index entirely.
Yes, always, with a permanent redirect at the edge, and every asset on the page should load over HTTPS too. Google treats HTTPS as a ranking signal and browsers mark plain HTTP pages as not secure. This is one of the checks this tool runs.
Every URL that ever ranked or was linked should permanently redirect to its closest equivalent on the new site, in a single hop. Pages that genuinely no longer exist should return a real 404 or 410, never a blanket redirect to the homepage. This is part of our launch checklist and one of the checks here.
More than one hop between the requested URL and the final page is too many by our standards. Each hop adds latency (often hundreds of milliseconds on mobile) and another chance for misconfiguration. Audit your redirect rules whenever you change domains, protocols, or URL structures.
Still have questions?
Contact our team for helpRelated Tools You Might Like
Continue optimizing your website with these complementary tools