301 Permanent Redirect
Indicates that a URL has permanently moved to a new location. It is commonly used for deleted pages with relevant replacements, URL restructuring, and domain migrations.
Analyze URL redirects, identify redirect chains, and inspect HTTP status codes. Find unnecessary redirect steps and help keep your website's URL structure clean and SEO-friendly.
Enter a URL to inspect its redirect destination, or paste a redirect trace to analyze every step in the chain.
Enter a complete URL, including https:// or http://.
curl -IL https://example.com/old-page in your terminal.
A URL redirect automatically sends visitors and search engines from one web address to another. It helps preserve access to important content when pages move, URLs change, or websites are reorganized.
When someone visits a redirected URL, the web server returns an HTTP status code and, in most redirect responses, a destination URL. The browser or search engine can then request the new address.
For example, if you change a page from /old-services/ to /services/, a redirect can guide visitors and search engines to the updated page instead of leaving them with an outdated link.
Send visitors to the correct page instead of showing outdated URLs or broken links.
Permanent redirects can help search engines understand when a page has moved and consolidate signals toward its replacement.
Clean redirect paths help search engines reach the intended destination without unnecessary intermediate requests.
Manage URL changes during redesigns, migrations, content updates, and domain changes more effectively.
SEO tip: Use redirects only when there is a relevant destination. Update internal links and XML sitemaps to point directly to the final URL rather than relying on redirects.
Not all redirects work the same way. Choosing the correct HTTP status code helps browsers and search engines understand whether a URL has moved permanently or temporarily.
Indicates that a URL has permanently moved to a new location. It is commonly used for deleted pages with relevant replacements, URL restructuring, and domain migrations.
Indicates that a resource is temporarily available at another URL. The original URL is generally expected to remain in use.
Temporarily redirects a request while preserving its HTTP method and request body. Unlike a traditional 302, it explicitly requires the method to remain unchanged.
Indicates a permanent move while preserving the original HTTP request method and body. It is the permanent counterpart to a 307 redirect.
Directs the client to retrieve another resource using a GET request. It is commonly used after a form submission to prevent accidental resubmission.
Indicates that multiple representations or destinations are available. The client may need to choose which option to follow.
Use when the original URL has moved permanently and the new destination should replace it.
Use when the original URL is expected to remain relevant or a specific request-handling behavior is needed.
SEO reminder: For a permanent page move, 301 or 308 is generally appropriate. For temporary changes, choose the status code that matches the intended behavior. Search engines may interpret redirect signals alongside other canonicalization signals.
Incorrect redirects can create confusing navigation paths, waste crawl resources, and send visitors to irrelevant pages. Identify these issues early to keep your website technically healthy.
A redirect chain occurs when one URL redirects to another URL that redirects again before reaching the final destination. Long chains add unnecessary requests and can slow down navigation.
A redirect loop happens when URLs keep sending requests back to each other. The browser cannot reach a final page and may display an error instead.
A redirect may point to a destination that no longer exists or returns an error. This leaves visitors unable to access the content they expected.
Sending unrelated deleted URLs to the homepage can confuse users and search engines. A homepage is not always a suitable replacement for removed content.
Choosing a permanent redirect for a temporary change, or a temporary redirect for a permanent move, can send confusing signals about the intended URL.
Use our free Redirect Checker to inspect redirect behavior and analyze redirect traces.
A well-managed redirect structure makes it easier for visitors and search engines to reach the right pages. Follow these practical steps to reduce redirect issues and maintain a healthy website.
Whenever possible, send visitors directly from the original URL to the final destination. Avoid unnecessary intermediate URLs that create long redirect chains.
Choose a permanent redirect for a permanent URL move and a temporary redirect when the original URL is expected to return. Use specialized status codes when their request-handling behavior is required.
Map old pages to the closest relevant replacement. Avoid redirecting unrelated deleted pages to your homepage just to prevent 404 errors.
Update navigation, internal links, canonical references, and XML sitemaps to use the final destination URL directly. Do not rely on redirects to fix outdated website references.
Test important redirects after website updates or migrations. Confirm that every redirect reaches an appropriate working destination without looping or ending at an error page.
Keep a record of changed URLs and test your redirect mappings after a domain change, redesign, or URL structure update. Review crawl reports to catch issues that automated checks may miss.
Find out where a URL redirects, identify its final destination, and investigate redirect issues with a simple checking process.
Copy the complete URL, including HTTPS if applicable, and paste it into the Redirect Checker input field.
Start the check to inspect the URL's final response and available redirect behavior. Browser security restrictions may prevent direct checks of some external websites.
Review the final HTTP status, destination URL, and any redirect hops available in the results. Look for unexpected destinations or errors.
If you need a complete hop-by-hop trace, run curl -IL in your terminal and paste the output into the Analyze Redirect Trace tab.
Use the command below to request redirect headers from your terminal. Paste the resulting output into the tool's trace analyzer to inspect individual redirect responses.
curl -IL https://example.com/old-page/
Run a redirect check and review the available results with our free tool.
Whether you're updating old pages, restructuring your website, or fixing broken URLs, managing redirects correctly helps visitors reach the right content and keeps your website structure organized.
Redirect plugins let you create and manage URL redirects through your WordPress dashboard without manually editing server configuration files.
Apache server users can create redirects directly in their website's
.htaccess file. This method is useful when you want server-level
redirect rules.
Redirect 301 /old-page/ https://example.com/new-page/
Back up your configuration before editing. This example applies to Apache servers, not Nginx.
Some hosting providers and CDN platforms offer redirect settings outside WordPress. These can be useful for site-wide changes, domain migrations, and larger redirect projects.
A redirect should lead users to the most relevant replacement page. Follow this process to reduce mistakes and avoid unnecessary redirect chains.
Find the page that has moved, changed, or been removed.
Choose a relevant replacement page rather than redirecting everything to the homepage.
Use 301 for permanent moves and temporary redirects when the change is genuinely temporary.
Check the redirect destination, status code, and chain. Update internal links where necessary.
Avoid managing the same redirect through multiple plugins, server rules, and CDN settings unless you understand how they interact. Conflicting rules can create redirect loops, unexpected destinations, and difficult troubleshooting.
Use our free Redirect Checker to inspect destinations, response codes, and redirect behavior.
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More