When the address of a page changes, the previous URL should not simply lead to a dead end. With a 301 redirect, you can automatically forward visitors and search engines from the old address to the new URL.
A 301 redirect is especially useful when a page has been permanently moved, renamed, or replaced by a new page.
In this guide, we will explain to you what a 301 redirect is, when you should use it, and how you can set up redirects with your web hosting and then test them properly.
Briefly explained: A 301 redirect indicates that a resource is permanently available under a different URL. Visitors who access the old address are automatically redirected to the new destination.
What is a 301 redirect? #
When a webpage is accessed, browsers or other clients communicate with the web server via HTTP. The server responds to a request with a so-called HTTP status code.
For a normal successful request, the status code is typically 200 returned.
A permanent redirect, on the other hand, uses the status code:
301 Moved Permanently
The server indicates that the requested resource is permanently located at a different address.
Simply put, the process looks like this:
Old URL
https://example.com/alte-seite/
↓ 301
New URL
https://example.com/neue-seite/The visitor does not need to know or enter the new address themselves. The browser follows the redirect automatically.
When does a 301 redirect make sense? #
You should use a 301 redirect when a URL is permanently replaced by another URL.
Typical use cases include a changed page address, a new page structure, or the merging of two similar pieces of content.
Even during a website relaunch, 301 redirects can become important if existing URLs change.
Example of a changed page address #
Assuming your previous page can be reached at the following address:
Following a revision, the new address is:
Without a redirection, visitors, saved bookmarks, or external links can still access the old URL.
If this no longer exists, a 404 error can result from it.
With a 301 redirect, visits to the old URL are automatically forwarded to the new page instead.
Why are redirects important for visitors? #
URLs are not accessed exclusively via a website's navigation.
An old address can still exist, for example, in:
- search engine results,
- Bookmark,
- Links from other websites,
- social media posts,
- Emails,
- documents or PDF files.
A properly configured redirect ensures that such requests still reach a meaningful destination.
Why are 301 redirects important for SEO? #
Even search engines may still know the previous URL.
A permanent redirect provides a technical signal to them that the content in question is permanently available at a different address.
This allows search engines to better process the change and update their stored information or search results over time.
Important: A 301 redirect is not an SEO trick to improve rankings. Its purpose is to technically map a permanent URL change properly.
301 or temporary redirection? #
The status code 301 stands for a permanent redirect.
If, on the other hand, a redirection is expressly intended to be only temporary, a different HTTP status code may be more appropriate.
Next to 301 exist, among other things 302, 307 and 308.
We explain the differences in detail at 301, 302, 307 and 308: HTTP redirects simply explained.
The redirect destination must match the old content #
An old URL should not simply be redirected across the board to just any accessible page.
The new destination should correspond as closely as possible to the previous content or the original search intent.
For example, if a specific guidebook is replaced by a new version, this new version is the obvious target.
On the other hand, a blanket redirection of all deleted pages to the homepage is not a good solution in many cases.
Practical Tip: Ask yourself with every redirect: „Which existing page helps a visitor who actually wanted to access the old URL?“ Exactly this page is usually the most sensible destination.
When should a page not be redirected? #
Not every deleted URL automatically requires a 301 redirect.
If content has been permanently removed and there is no factually suitable replacement, it may be more correct not to set up an artificial redirect to a thelematically unrelated page.
A redirect should reflect an actual new destination and not merely serve to prevent every possible 404 status at all costs.
Set up a 301 redirect in cPanel #
With CURIAWEB web hosting, you can manage redirects via cPanel.
First, log in to cPanel and open the Redirects feature.
Select a permanent redirection there if the previous address is permanently replaced by the new URL.
Then you specify which old address should be redirected and which new destination will be used.
Carefully check the old and new URL #
Before saving, you should check both addresses again.
Example:
Source:
/alte-seite/
Target:
https://example.com/neue-seite/Especially when it comes to the destination, you should pay attention to typos, the correct domain, and the full path.
A redirect to a misspelled destination address does not solve the original problem, but merely shifts it.
Redirect for individual pages #
For a single changed URL, the redirection should affect this specific address as precisely as possible.
Example:
https://example.com/preise-alt/
↓ 301
https://example.com/preise/This is more precise than an unnecessarily broad rule that might affect other URLs.
Redirect to another domain #
A 301 redirect can also point to a URL on a different domain.
Example:
https://alte-domain.example/angebot/
↓ 301
https://neue-domain.example/angebot/This may be necessary, for example, during a domain change or website consolidation.
However, in the event of a complete domain change, you should not only consider a single URL, but rather take the entire existing URL structure and matching target pages into account.
Redirects during a website relaunch #
A relaunch is one of the most important use cases for 301 redirects.
If the URL structure changes in the process, you should record which old URLs exist and which new pages they correspond to before making the switch.
A simple mapping can look like this, for example:
OLD
/about-us.html
NEW
/about-us/
----------------------------
OLD
/products/webhosting.html
NEW
/web-hosting/
----------------------------
OLD
/contact.php
NEW
/contact/From this mapping, the required redirects can then be created.
Important during a relaunch: Create the URL mapping as early as possible before the actual migration. Finding out afterwards which old URLs existed and where they belong is much more time-consuming.
Avoid redirect chains #
A so-called redirect chain occurs when a URL does not redirect directly to the final destination.
Example:
URL A
↓ 301
URL B
↓ 301
URL CIf URL C meanwhile the final goal is, the redirection of URL A directly to, if possible URL C show.
URL A
↓ 301
URL CThis avoids an unnecessary additional redirection.
Avoid redirect loops #
Even more problematic is a redirect loop.
It can arise, for example, when two rules reference each other:
URL A
↓
URL B
↓
URL A
↓
URL B
↓
...As a result, the browser does not reach a final destination and eventually aborts the request with an error message.
If a message about too many redirects suddenly appears after setting up a redirect, you should check the redirect rules involved.
Test redirects after setup #
You should always test a saved forwarding rule practically.
Open the old URL directly in the browser and check if you arrive at the expected new destination.
Also check the browser's address bar. The new URL should then actually appear there.
Test in private browsing window #
Browsers can cache permanent redirects.
If you have just changed a redirection rule, a test in a private browser window or with a second browser can therefore be helpful.
This is especially useful if your browser continues to exhibit previous behavior.
Check the HTTP status code of the redirection #
That the browser arrives at the correct destination does not necessarily indicate which HTTP status code was used.
For a technical inspection, you can use, for example, a browser's developer tools or a suitable HTTP inspection tool.
With a permanent 301 redirect, the original request should be answered accordingly with the status code 301 be answered.
We will cover the most important status codes under HTTP status codes explained: 200, 301, 404, 403, and 500.
What is a 404 error? #
When a requested URL is not found, a web server typically responds with the status code 404 Not Found.
This can happen, for example, if a page has been deleted or its address has been changed and there is no appropriate redirection.
We explain how to systematically find and evaluate such errors under Find and fix 404 errors.
Do not automatically redirect every 404 error #
It can be tempting to simply redirect all non-existent URLs to the homepage.
You should refrain from doing that.
A redirection should have a meaningful destination. A request for a non-existent or completely unknown URL does not automatically have a topical connection to the homepage.
Update internal links after a URL change #
A 301 redirect ensures that an old URL continues to work. Nevertheless, you should update internal links on your own website to the new address whenever possible.
Instead:
internal link
↓
old URL
↓ 301
new URLis a direct link better:
internal link
↓
new URLThe redirection remains useful for old external links, bookmarks, or search engine entries.
Do not delete 301 redirect immediately #
After a URL change, old addresses can still be accessed for a longer period via external links, bookmarks, or search engines.
Therefore, do not remove a working permanent redirect just because the new URL is now visible on Google.
As long as the old URL can still be accessed and the new destination exists, the redirect can still be useful for visitors.
Do not make unnecessary URL changes #
A redirect can technically handle URL changes cleanly. Nevertheless, you should not change existing URLs without a reason.
When an established address is understandable and works technically without issues, a change solely for the sake of a slightly „nicer“ spelling often does not provide sufficient benefit.
Basic rule: Keep good URLs as stable as possible. If a change is really necessary, cleanly redirect the old address to the new destination.
Document redirects #
In the case of multiple redirects, simple documentation is helpful.
For example, you can note:
Old URL:
https://example.com/alte-seite/
New URL:
https://example.com/neue-seite/
Type:
301
Reason:
Page replaced during relaunchFor extensive websites or relaunches, a spreadsheet can also be used for this purpose.
This makes it easier to understand later why a particular rule exists.
What to do if the redirection doesn't work? #
First, check the entered source and destination addresses for typos.
Then check whether you are actually testing the correct domain or URL.
Test the old address additionally in a private browser window.
If other forwarding rules already exist, you should also check whether they conflict with each other or cause a forwarding chain or loop.
What to do about „too many redirects“? #
A browser message about too many redirects often indicates that multiple rules are conflicting or a loop has been created.
In this case, check in particular whether the target of one rule is redirected back to the original address by another rule.
Do not randomly change multiple rules at the same time. Specifically disable or correct the most recently modified redirect and then test again.
Redirects and HTTPS #
Redirects can also occur in the context of HTTPS.
For example, a request via an unencrypted address can be redirected to the corresponding HTTPS version.
However, if issues arise with HTTPS requests or SSL certificates, the actual SSL or HTTPS configuration should be checked first.
The article on this will follow in this category Check SSL Certificate and HTTPS: Identify Common Errors.
301 Redirect Checklist #
Does the URL change permanently?
↓
Determine suitable new destination
↓
Set up 301 redirect
↓
Open old URL in browser
↓
Check new destination URL
↓
Check status code
↓
Avoid redirect chains
↓
Update internal links
↓
Document redirectSummary #
A 301 redirect is used when a URL has been permanently replaced by another address.
It ensures that visitors, external links, bookmarks, and search engines do not simply run into a dead end at the old address, but are redirected to the appropriate new content.
The content of a redirect destination should match the previous page. Avoid blanket redirects of all non-existent URLs to the homepage, as well as unnecessary redirect chains and redirect loops.
Then test every newly set up redirect on the public website and update internal links directly to the new address if possible.
The best 301 redirect is not the one that simply reaches just any page, but the one that leads a visitor from the old URL directly to the correct new content.
