Understanding of 301 and 302 Redirects

I think these redirects creates more of trouble if done incorrectly. But SEO’s should understand these redirects, that Why we need these?

Many webmasters don’t understand the different between a 301 and 302 redirect. You might think that Google and the other search engines would just follow the redirects, but that’s where things get complicated. A 301 redirect means that the page has moved to a new location, permanently. A 302 redirect means, that the move is temporary. Search engines need to figure out whether to keep the old page, or replace it with the one found at the new location. Use the wrong type of redirects, and the search engines’ view of your web site can get screwed up, badly.

Why does this matter? If you are moving a web page or an entire web site to a new location, for instance if you change your domain name, you want visitors to be able to find your site. A redirect causes the user’s browser to automatically forward from the old location to the new one. You might think that Google and the other search engines would just follow the redirects, but that’s where things get complicated. When a site moves, that can trigger the Google aging delay. Usually the site drops out of the search rankings for several months, sometimes even a year. We’ll come back to this later.

There aren’t too many situations where a 302 is appropriate. How often have you temporarily moved a page? It’s much more common to move pages permanently. Nevertheless, it seems easier to create 302 redirects than 301s. You can use Javascript or a meta tag to create a 302. Creating a 301 redirect requires special commands in your .htaccess file if you use an Apache server. With Windows servers, creating 301 takes even more time and trouble. That’s why there’s a tendency for people to mistakenly use 302 instead of 301.
Google recognizes that many people use 302 when they really mean 301. Fortunately, Google isn’t bound by any law to take people literally. For the sake of producing the best possible search results, Google can and should look at 302s and figure out if the webmaster really means 302, or if it’s run-of-the-mill confusion and they really mean 301.
Whether Google actually handles 302s properly is an open question. If you use a 302 when you should be using a 301, there’s a chance Google or some other search engines might keep your old URL in the index, and then filter out your new URL as a duplicate. You might end up with link popularity divided between the two domains, hurting your search rankings. The search engines might figure out how to handle your 302, or they might not. So why take a chance?
When I permanently move a domain, or a web page, I use a 301 redirect. To me, 302s in this situation seem like double dipping. By saying “temporary move” you tell the search engines to keep the old domain or page indexed, but you also want them to index the new one.
Are you concerned about losing rankings due to a 301? Simple. Don’t change your domain, or don’t rely on rankings for your livelihood. In the real world, businesses avoid changing their names because it can appear shady. Who can blame Google for employing the same heuristic: if you’re changing domain names, you might be up to no good. Let’s wait a while and see if you behave yourself before we recommend you.

Still anymore queries then feel free to call or mail me as mentioned in my contact details.

If You Like Then Add to: BlinkListBlinkList | del.icio.usdel.icio.us | DiggDigg | FurlFurl | redditreddit | GoogleGoogle | LycosLycos | WistsWists


3 thoughts on “Understanding of 301 and 302 Redirects

  1. Thanks a lot for the great post, well, having read a little about SEO recently I actually use 301 when I move a page permanently to another location but currently I’m in a situation where I’m creating a new website and want to use 302 for one of the pages on the site (that page when requested with no parameters, it chooses a post randomly and redirects to it), let me explain:

    for example, let’s assume the page is:

    that page when requested with no parameters (as shown above) should redirect to a random post, for example:


    because the post id is not known in advance there’s no way to do this other than using redirection (it’s just like clicking the “Show me another” link on a question page on Yahoo Answers, it also uses redirection – I actually checked this – because the question is not known in advance), now I wonder what implications could this have when googlebot and other search engine bots crawl my site, will they request the page only once per crawling session? For this website particularly I don’t really care whether it gets indexed properly or not (or even at all!) but I don’t want the search engine crawlers to bring the site down!

    Any ideas would be really appreciated …

  2. Thanks for your answer, actually I already use robots.txt in my website but I don’t have the url to this page in it, I wonder what will happen when a search engine bot visits my site, if the page will be requested once per crawling session then there will be definitely no reason to add its url to robots.txt., I’m not trying to prevent the page from being indexed I just want to make sure it won’t cause trouble.

Its your turn to write me something or inputs on this blog post

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s