65 replies to this topic

[incrediblehelp]

I just don't understand why people use 302 for anything more than temporary redirect? If your redirect is clearly PERMANENT then use a 301 redirect. I am not confused.

[DanThies]

It's a messy scene, with Google's ambiguity on how they handle redirects. They can and should do better. Yahoo didn't have a problem publishing what they do. This is one of those areas (like cross-site dupe checking) where Google is getting a little too cute, to the point where they are doing harm.

[projectphp]

So, when do you use a 307 or 303? BTW: 307 is actually a temporary redirect, and 302 is listed as "Found". Not that there is a heck of a lot of difference that I can see.

There aren't too many situations where a 302 is appropriate

A 302 is always better, unless a 301 worked to change bookmarks (it doesn't, I have checked in IE, Firefox AND Opera) or servers had rewriting functions, or if there was an extraneous reason, like SEO. Otherwise, a 302 has heaps of benefits and uses:
1. For tracking (Adwords, banners etc).
2. Error checking. 301 is likely to be cached by a browser (terribly hard to test that), and that means you have one chance to check anything (especailly if you want to keep stats of redirects, say to see how long to have an old domain registered).
3. It can be undone. How many changes are permanent? Today the boss decides to drop a few products from a line, tomorrow they are back. Better not overdo it and use a 301, as that would be harder to recover from.

In life, taking the path of least severity is usually better. If you aren't positive you want to remove a tree, killing it can't be recovered from, but pruning it might have the same effect.

A 301 is permanent, as in forever. Got to be VERY careful about using that unless you are certain. Even with litigation, you might win on appeal!

As for which redirect to use when moving a site, the "best" is whatever achieves the goals under which "best" is qualifies. The only reason to choose one over tother is if one helps more, or if one doesn't help at all. That being te case, you choose that one.

Edited by projectphp, 23 January 2007 - 12:46 AM.

[DanThies]

I've been using 301 redirects to change domains for a long time, and we've never had a problem with it.

[dchan34]

I wonder if 302 on-domain redirect will affect my google ranking or will it work for me if I have not switching to a new domain.
But the major structure of my site will be changed including URL name since I am going from Static html to CMS based.

Thank you in advance

[Randy]

Welcome dchan34 !

If the base domain name is staying the same your best bet is to use a 301. The agingdelay should have no bearing when you're keeping the same domain.

Do realize however that when you change all of the page names and locatoins you're going to need to give the engines some time to catch up with the changes.