Redirect Checker
Check if your website redirects correctly between HTTP/HTTPS and WWW/non-WWW variants. All four versions of your domain should point to a single canonical URL.
What Is a Redirect?
A redirect automatically sends visitors and search engines from one URL to another. The most common types are 301 (permanent) and 302 (temporary) redirects. Every website should ensure that all four variants of its domain — HTTP, HTTPS, WWW, and non-WWW — redirect to a single preferred version.
Why Redirects Matter for SEO
If your domain is accessible at multiple URLs without redirecting, search engines may index the same content under different URLs, diluting your link equity and causing duplicate content issues. A proper redirect setup ensures all authority flows to your canonical domain.
The Four URL Variants
| Variant | Example |
|---|---|
| HTTP non-WWW | http://example.com |
| HTTP WWW | http://www.example.com |
| HTTPS non-WWW | https://example.com |
| HTTPS WWW | https://www.example.com |
All four should 301 redirect to your preferred URL (usually https://www.example.com or https://example.com). The redirect should be a single hop — no chains through intermediate URLs.
Common Redirect Issues
| Issue | Impact |
|---|---|
| No redirect from HTTP to HTTPS | Insecure version is accessible, duplicate content. |
| WWW and non-WWW both resolve | Duplicate content, split link equity. |
| Redirect chains (A → B → C) | Slower page load, potential loss of link equity. |
| Using 302 instead of 301 | 302 is temporary — search engines may keep indexing the old URL. |
| Redirect loops | Page never loads, completely blocks indexing. |
301 vs 302 vs 307: What Actually Matters
| Status | Meaning | SEO Behaviour | When to Use |
|---|---|---|---|
| 301 Moved Permanently | The URL has moved and will not come back | Transfers link equity to destination; old URL drops from index | All permanent URL changes — the default choice |
| 302 Found / Moved Temporarily | The URL has moved temporarily | Does not transfer link equity; old URL stays in index | A/B testing, maintenance pages, genuinely temporary |
| 307 Temporary Redirect | Like 302 but preserves HTTP method | Same SEO treatment as 302 | POST redirects that must stay POST |
| 308 Permanent Redirect | Like 301 but preserves HTTP method | Same SEO treatment as 301 | API endpoints that must preserve method |
For almost every website use case, 301 is the correct choice. Using 302 by mistake keeps the old URL in Google's index for months, preventing your new URL from accumulating authority.
How to Fix Common Redirect Problems
Missing HTTP-to-HTTPS Redirect
The most critical redirect every site needs. Browsers flag HTTP pages as "Not Secure" and Google treats HTTPS as a ranking signal. Configure at the server level using the htaccess generator for Apache, or equivalent for your stack.
Both WWW and Non-WWW Resolve
Pick one as canonical and 301-redirect the other. The choice is arbitrary — what matters is consistency. Enforce through server redirects, not just canonical tags.
Redirect Chains
If you have A → B → C, every visitor pays the latency of two hops. Worse, Google's crawlers give up after 5-10 hops, which can block indexing entirely. Fix by updating A to point directly to C.
Redirect Loops
A redirects to B which redirects back to A. Browsers show "too many redirects" and the page never loads. This is a site-killing bug — fix immediately by removing one of the redirects.
302 Where 301 Belongs
Check your redirect status codes. Many CMSs default to 302 for category redirects; that blocks link equity transfer. Change to 301 for any permanent move.
Redirecting to Wrong Page
Sometimes old URLs redirect to the homepage instead of an equivalent new page. This is "soft 404" behaviour — Google treats it as effectively broken. Map each old URL to its best-matching new URL, not a generic fallback.
Checking Redirects for SEO Migrations
During HTTPS migrations, domain changes, or large site restructures, redirects are what protect your rankings. The safe process:
- Export all current URLs from your sitemap or Search Console.
- Map each to its new URL. Use a spreadsheet. Every old URL should have an intended destination.
- Configure 301 redirects at the server level or CDN. Avoid WordPress plugins for large redirect sets — server rules are faster and more reliable.
- Test every redirect. Use this tool plus the Bulk Checker to validate status codes across the whole migration.
- Submit the new sitemap. Help Google discover the new URLs quickly.
- Monitor Search Console. Watch Coverage and Enhancements reports for errors post-migration.
- Keep redirects in place indefinitely. Never remove old redirects — backlinks and bookmarks can reference them for years.
Need a full SEO audit? Go to the RankNibbler homepage and enter any URL for a free 30+ point check.