Redirect Types (301 vs 302)

← Back to glossary · Category: Technical

What Redirect Types Are, in Plain Language

Redirect types are the different status codes a server can send when it tells a browser or a crawler that a requested page lives somewhere else. The code is a short number, and it carries a meaning beyond the new address itself: it says whether the move is permanent or temporary, and whether the browser should repeat its original request in exactly the same way or may change it. Choosing the right code matters because browsers and search engines treat the codes differently, and a code chosen carelessly can send the opposite message from the one the site owner intended.

The two codes most site owners meet first are 301 and 302. A 301 redirect means the move is permanent: the old address has been retired, and the new address is the page's lasting home. A 302 redirect means the move is temporary: the old address still exists in principle, and the visitor is only being sent elsewhere for now. Those two words, permanent and temporary, are the heart of the distinction. Everything else about redirect types, including the less common codes, is a variation on that question, plus a second question about whether the request method should be preserved.

Redirect types matter most in ordinary, unglamorous situations: a page renamed, a section reorganised, a product replaced, a post moved into a guide, a site switched to secure addresses, or a page taken down for a short period while it is rebuilt. In each case the site owner must decide what the old address means from now on. Is it gone for good, or is it coming back? The answer to that question, expressed as a status code, tells search engines whether to update their records and tells browsers whether to remember the new address for future visits.

What Redirect Types Are Not

Redirect types are not a ranking trick, and picking a particular code does not, by itself, make a page perform better in search. A 301 redirect is appropriate when a move is permanent, and it helps search engines update their records, but it does not transfer value that the old page never had, and it does not rescue a page whose content is thin or irrelevant. Treating a status code as a lever to pull for visibility, rather than as an honest statement about where a page lives, leads to exactly the kind of misuse that confuses both readers and crawlers.

Redirect types are also not interchangeable, even though they all send the visitor to a new address and the visitor often cannot tell them apart. A reader clicking a link will usually arrive at the same final page whether the redirect was a 301 or a 302, and may never know which code was used. The difference is visible to the systems behind the visit: the browser's memory of the redirect, the search engine's index, and the handling of the request itself. Two redirects that look identical to a reader can therefore have quite different long-term effects on how the site is understood.

Finally, a redirect type is not a substitute for a decision about content. If a page has been removed and nothing replaces it, no redirect code can honestly say where its readers should go. Sending them to a homepage or to an unrelated page may look tidy, but it answers a question nobody asked. In such a case the honest options are to show a clear not-found page, or to redirect only where a genuinely equivalent page exists. The code describes the move; it cannot invent a destination that does not exist.

How Redirect Types Work

When a browser requests a page, the server can answer with a status code in the 300 range and a Location header naming the new address. A 301 response, Moved Permanently, tells the browser and the crawler that the old address should be replaced by the new one in future. A 302 response, Found, tells them that the move is temporary and that the old address remains the canonical one, even though the current visit is being sent elsewhere. Browsers may cache a permanent redirect, so a later visit to the old address goes straight to the new one without asking the server again, while a temporary redirect is normally checked again each time.

Two further codes complete the common set. A 307 redirect is the method-preserving equivalent of a 302: it means temporary, but it also insists that the browser repeat the original request method, so a form submission stays a form submission rather than silently becoming a simple page request. A 308 redirect is the method-preserving equivalent of a 301: permanent, with the same insistence on preserving the method. These codes exist because the older codes, 301 and 302, were historically handled inconsistently for requests that were not simple page loads, and the newer codes remove that ambiguity. For an ordinary page move, where the visitor is simply requesting a page, 301 and 302 remain the usual choices, and 307 and 308 are the precise alternatives when method preservation matters.

Why the Right Redirect Type Matters

The first reason is how search engines update their records. A permanent redirect tells a search engine to treat the new address as the current version of the page, so over time the new address is the one that appears in results and the old address fades. A temporary redirect tells the search engine to keep the old address as the current one, because the page is expected to return. Using a temporary code for a permanent move therefore leaves the search engine waiting for a return that will never happen, and the new address takes longer to be recognised. Using a permanent code for a temporary move is worse in the opposite direction: the search engine may retire an address that the site owner intends to bring back.

The second reason is what browsers remember. A permanent redirect may be cached, which makes repeat visits faster, because the browser does not need to ask the old address again. A temporary redirect is normally rechecked, which is correct when the destination may change soon, but wasteful when the move is actually permanent. The difference is invisible on a first visit and only shows up over time, in the accumulated behaviour of returning visitors and of the search engine's index, which is why the wrong code can go unnoticed for months while quietly sending the wrong signal.

Common Mistakes With Redirect Types

The most common mistake is using a 302 redirect for a permanent move, often because it is the default in a plugin or a platform, or because the person setting it up did not think the distinction mattered. The page still loads, the reader still arrives, and nothing looks wrong, which is why the mistake survives. The cost is paid slowly, in a search index that keeps treating the old address as current and a new address that takes longer to settle. The fix is simple once the mistake is spotted: change the code to 301 where the move is permanent, and check the result.

The opposite mistake, using a 301 redirect for a temporary move, is less common but more damaging. A seasonal page, a page under maintenance, or a page moved during a short test may be redirected permanently, and by the time the original page returns, browsers and search engines have already learned to treat the new address as its home. Undoing a permanent redirect is possible, but it takes time for the cached behaviour and the index to catch up, and during that interval visitors may keep being sent to the wrong place. Temporary situations deserve temporary codes, even when a permanent code feels more decisive.

A third mistake is mixing redirect types inside a redirect chain, so that one hop says permanent and the next says temporary, or one hop preserves the method and the next does not. A mixed chain sends contradictory instructions about which address is lasting, and it makes the route harder to reason about. Chains should be shortened to a single direct redirect wherever possible, and when a chain cannot be avoided, its hops should at least agree with each other about whether the move is permanent or temporary.

Step by Step: Choosing and Checking a Redirect With the Redirect Checker

Begin by stating, in one sentence, what has happened to the page. Has it moved for good, with a new address that will stay? Is it away for a short period and expected to return? Has it been replaced by a genuinely equivalent page, or is it simply gone? That sentence determines the code. A move for good calls for a 301 redirect. A short absence calls for a 302 redirect, or a 307 redirect where the request method must be preserved. A move for good where the method must be preserved calls for a 308 redirect. If no equivalent page exists, do not force a redirect at all; show a helpful not-found page instead.

Next, set the redirect at the server level or through the site's redirect tool, pointing the old address directly at the final address, not at a middle address that itself redirects. This is where many redirect chains begin: the new redirect points at an address that was current last year, rather than at the address that is current now. Pointing straight at the final page avoids that trap and keeps the route to a single hop, which is easier to test and easier to trust.

Then open the Redirect Checker and test the old address. The tool follows the redirect and reports the final address and whether the address changed. Compare the final address with the one you intended, and check that the route is direct. If the tool shows middle addresses, shorten the route before moving on. If the final address is the homepage when you intended a specific article, the destination is wrong even though the redirect works, and it should be corrected rather than left in place.

After that, check the related pieces of the site. Update the site's sitemap so that it lists the new address rather than the old one, and update internal links in articles that still point at the old address, so that readers and crawlers reach the new page directly rather than through the redirect. A redirect is a safety net for links you do not control, such as links from other sites and old bookmarks. Links you do control should be updated to the new address, because a direct link is always better than a link that relies on a redirect to work.

Finally, revisit the redirect after any later change to the page. If the page moves again, update the original redirect to point at the newest address, rather than adding a second redirect on top of it. If a temporary redirect's reason has ended, remove it and restore the original page, or convert it to a permanent redirect if the move has become lasting. Recording the reason and the date for each redirect, even briefly, makes these later decisions easy, because the next person to touch the page can see what was intended rather than guessing from the code alone.

How Rankenza Handles Redirect Types

Rankenza's article process is built around current pages, which keeps redirect questions from arising in new content in the first place. Research starts from the top 10 pages for a keyword, filtered by what the searcher actually wants, so outlines are built around pages that currently rank rather than around retired addresses. Drafts are written in original words, reviewed by a human editor, and given internal links drawn from the customer's own sitemap, which lists current addresses. New articles therefore link directly to current pages, rather than relying on redirects to bridge from old addresses to new ones.

For existing sites, the Redirect Checker is the practical companion to that process. It lets a site owner test an old address, see where it actually lands, and confirm that the route is direct. Combined with the refresh process described in how to refresh old blog content for SEO, it supports a simple routine: refresh the content, update the internal links to current addresses, and check that any redirects left in place for outside links still point directly at the right page. Related glossary terms include canonical URL, internal linking, and crawl budget, and the wider writing process is covered in how to write blog posts that rank on Google and internal linking strategy for blogs.

How This Looks on Rankenza

Typical approach: a redirect is added with whatever code the tool defaults to, usually a temporary code, and nobody checks whether the move was permanent, whether the destination is the final page, or whether internal links still point at the old address. The page loads, so the mistake is invisible until the search index fails to settle on the new address.

Rankenza's approach: top-10 search research first; outline filtered by what the searcher wants; original draft reviewed by a human editor; internal links drawn from the customer's own sitemap; first article free, then $3.60 per article or $89 for 50 credits. See it in practice in how to write blog posts that rank on Google, and test any old address with the Redirect Checker.

Sources: What the Research Says

According to Google Search Central guidance on redirects, a permanent redirect should be used when a page has moved for good, and the guidance distinguishes permanent moves from temporary ones for exactly the indexing reasons described here. MDN Web Docs on HTTP redirects explains each status code, including the method-preserving distinction between 301 and 308 and between 302 and 307, and the status pages for 301 and 302 give the precise definitions used in this guide. Where this guide gives no figure, that is deliberate: the sources above define behaviour and give guidance, not a single number that would apply to every site.

• Google Search Central: Redirects and Google Search
• MDN Web Docs: HTTP Redirects
• MDN Web Docs: 301 Moved Permanently
• MDN Web Docs: 302 Found

Frequently Asked Questions

When should I use a 301 redirect? When a page has moved for good and the new address is its lasting home: a renamed article, a reorganised section, a merged guide, or a site-wide change of address format. The 301 code tells browsers and search engines to update their records, so the new address becomes the one that is remembered and shown.

When should I use a 302 redirect? When the move is temporary and the old address is expected to return: a page under short maintenance, a seasonal offer, or a test destination. The 302 code tells browsers and search engines to keep treating the old address as current, and to check again on the next visit rather than remembering the detour.

What is the difference between 301 and 308, or between 302 and 307? The first pair are the permanent codes and the second pair are the temporary codes. Within each pair, the newer code, 308 or 307, guarantees that the browser repeats the original request method, while the older code, 301 or 302, historically allowed the method to change for requests that were not simple page loads. For ordinary page moves the older codes are fine; for form submissions and other interactions, the method-preserving codes are the precise choice.

Can I change a redirect type later? Yes, and you should when the situation changes. A temporary redirect that has become permanent should be changed to a permanent code, and a permanent redirect for a page that returns should be removed. The change takes time to propagate through browser caches and search indexes, so it is better to choose correctly at the start than to rely on a later correction, but a later correction is always better than leaving the wrong code in place.