A redirect is a mechanism by which a request addressed to a specific resource is automatically forwarded to another resource. In the web context, it is a response that the server sends to the client indicating a new address to reach, so that the browser or search engine can continue navigating to the correct destination. The term comes from the English “to redirect”, meaning to reroute, and indicates the shift of the communication flow from one URL to another.
In SEO, a redirect is a fundamental tool for preserving a page’s authority and user experience when content changes location. If an address is modified, deleted, or merged with another, a well-configured redirect prevents visitors from hitting an error and allows search engines to update their indexes without dispersing the value accumulated over time. Proper management of redirects is therefore an integral part of any professional SEO strategy.
When an HTTP response becomes a redirect
Technically, a redirect occurs when the server responds to an HTTP request with a status code in the 3xx family. This code tells the client that the requested resource is no longer at the original address and that it must look elsewhere. The client, typically a browser or a crawler, receives the indication in the form of a location header and repeats the request to the new address.
Redirects can be configured at different levels: on the web server, through rules in the configuration file; at the application level, through the programming language used; or through the control panel of a content management system. The choice of level depends on the technical skills available and how often the rules need to be updated.
Permanent or temporary: what changes
Not all redirects are the same: the most relevant difference concerns the permanence of the redirect. A permanent redirect signals that the resource has moved permanently, while a temporary one indicates a momentary shift. This distinction has important consequences for both browsers and search engines, which treat the two cases differently in managing indexing.
Permanent redirect
The permanent redirect, identified by the 301 (or 308) status code, communicates that the page has been moved permanently. For Google it is a strong signal to choose the new URL as canonical, and the index updates progressively. Redirects do not cause PageRank loss. It is the recommended choice when content is merged with another or when the site structure changes stably.
Temporary redirect
The temporary redirect, associated with the 302 (or 307) code, indicates that the move is momentary and that the original address will become valid again. For Google it is a weaker signal: it tends to keep the original URL in the results. Temporary redirects also pass PageRank, and if they stay in place for a long time Google may treat them as permanent. They are used, for example, during maintenance or time-limited promotions.
Redirect from protocol or domain change
When a site migrates from one version of the protocol to another or changes domain, permanent redirects configured globally are used. This operation requires particular attention, because an error in the redirect chain can slow down navigation and confuse crawlers.
Besides HTTP redirects, there are meta refresh, written in the HTML code, and JavaScript redirects: Google follows them, but server-side redirects remain the most reliable choice.
Status codes compared
| Code | Name | Permanence | Typical use |
|---|---|---|---|
| 301 | Moved Permanently | Permanent | Stable URL change, content consolidation |
| 302 | Found (Temporary Redirect) | Temporary | Maintenance, testing, time-limited promotions |
| 307 | Temporary Redirect | Temporary | Preserves the original request method |
| 308 | Permanent Redirect | Permanent | Like 301, but keeps the request method |
| 303 | See Other | Temporary | Redirects to a different resource after a submission |
What happens to rankings
A correctly implemented redirect allows you to preserve the rankings a page has earned: Google has stated that redirects do not cause PageRank loss. A long redirect chain or a loop, on the other hand, slows down navigation and can prevent access to content; Googlebot follows up to 10 hops. For this reason, it is good practice to point directly to the final destination (see redirect chain).
Response time also affects user experience: a redirect adds a step to navigation and, if poorly configured, can slow down perceived load time. Keeping rules tidy and periodically checking their effectiveness helps prevent the site from accumulating obsolete or unnecessary redirects.
Common mistakes to avoid
Common mistakes include using a temporary redirect instead of a permanent one, creating chains that pass through multiple intermediate URLs, and failing to remove old rules after a migration. Another recurring problem is redirecting all pages to the homepage, which Google may treat as a soft 404 and which denies visitors the page they were looking for.
From choosing the URL to the server rule
- Identify precisely the source URL and the destination URL, checking that the latter returns a valid page.
- Decide whether the redirect should be permanent or temporary based on the nature of the move.
- Access the server panel, the configuration file, or the content management system.
- Enter the redirect rule following the syntax required by the environment in use.
- Save the changes and clear the site and browser cache to avoid misleading results.
- Check that it works with an HTTP header analysis tool.
- Check that no chains or loops have been created and fix any anomalies.
- Monitor indexing and traffic in the following days to confirm the outcome of the operation.
Frequently asked questions about redirects
What is the difference between a 301 and a 302 redirect?
The 301 indicates a permanent move and is a strong signal for Google to choose the new page as canonical; the 302 signals a temporary move and is a weaker signal. Both pass PageRank.
Does a redirect cause ranking loss?
If configured well, a redirect preserves rankings: Google has stated that redirects do not cause PageRank loss. The time it takes for the new URL to replace the old one in results may change.
Can I redirect multiple pages to a single address?
Yes, it is possible and sometimes advisable when multiple similar pieces of content are consolidated, as long as the destination is relevant and offers quality content.
What are redirect chains?
They are sequences where one URL points to a second, which in turn points to a third, and so on. They slow down navigation and waste crawl resources, so they should be avoided by pointing directly to the final destination.
Does a redirect affect site speed?
Each redirect adds a step in the communication between client and server, so a high number of redirects in sequence can affect the load times perceived by the user.
How do I check if a redirect works correctly?
You can use online tools or browser analysis features to check the returned status code and the destination address, making sure there are no errors or loops.
From glossary to projectDo you need to change domain or platform without losing visibility?SEO migration prepares the transition (redirects, structure, checks before and after) to reduce the risk of losing rankings on Google.Discover SEO migration
Related entries:
Redirect chain Redirecting 302 error 301 error