Question concerning a 302 Redirect

[adwordize]

Hi!

I've already done some research on redirects, but I still have a question concerning a 302 redirect implemented at the homepage of a website.

The Website www.domainA.com has a 302 redirect to www.domainA.com/content/.... Also all subsequent pages have the /content/ directory in their URLs: e.g domainA.com/content/products

• First thing I was wondering about, was the use of a redirect to a new site using an additional directory /content/... Why would anyone do this? Would it be enough to replace the 302 with a 301 redirect, or would you recommend to change the entire structure and eliminate this /content/ directory? The most logical structure would be www.domainA.com/products/.., and not www.domainA.com/content/products, right?

• Second thing: Given that 302 means temporary redirect, what are the actual implications when redirecting from domainA.com to domainA.com/content? I've heard that 302 redirects don't pass linkjuice and are detrimental for the site's rankings... What are the actual implications concerning the example above (302 redirect from domainA.com to domainA.com/content ?

Would be great to get some advice about the first problem and maybe some insights about the second one concerning 302s in general.

Thanks in advance!

Cheers,

Chris

[adwordize]

That's fine, I think in that case, they didn't really know why they did it, so it will certainly help them to know, that there's better options around.

Thanks again for your insights and time, you helped me a lot with that one!

Cheers,

Chris

[RyanKent]

I am in agreement with you Christoph.

I do not see any value in adding a "content" directory. From a user stand point, it is not helpful.

The only reason to have a /content directory is if there is a need for it on the server. Sometimes there is shared hosting involved or other considerations that I am not aware of, so I prefer not to criticize others for their choices without knowing all the facts that their decision was based upon.

[adwordize]

Hi Ryan,

thanks for your reply and your view on this. I think I've already read the article by Matt Cutts, but as I've been working in SEA so far, the technical aspects of SEO are still the area where I have to catch up the most. But you've definitely helped me with that one

Coming back once again to the actual website, that I mentioned. Concerning the /content/ directory, you said that it would depend on the perspective. What I meant with "The most logical structure would be www.domainA.com/products/.., and not www.domainA.com/content/products, right?" was that the /content/ directory may be detrimental for the ranking of sub-pages, as subsequent pages, which are lower in the hierarchy like domainA.com/content/products/shoes would be one level deeper than if it was domainA/products/shoes. In the former case, the sub-page "Shoes" would be one click further away than in the latter. So for the sub-page "shoes" it would be "better" to be located one level up, right?

In the specific case, the homepage is permanently redirected from domainA.com to domainA.com/content/, but they did it with a 302 redirect.

So in this case it would be better to use a 301 or change the URL structure, so that no redirect is necesary (e.g: domainA.com/products/shoes). Would that be suitable options according to you?

[RyanKent]

There are many great pages written on this topic. An older but relevant article from Matt Cutts: http://www.mattcutts.com/blog/seo-advice-discussing-302-redirects/

In short, a 302 would only ever be used if the move was temporary. You are correct in that they do not pass a link's value. I would only use a 302 to resolve a temporary problem.

A 301 passes 90%+ of the link's value, but there is some loss. That is why you would prefer not to use it, especially if the move was temporary. Using multiple 301s in a chain can be especially bad for this reason.

First thing I was wondering about, was the use of a redirect to a new site using an additional directory /content/... Why would anyone do this?

There are some very good reasons. It sounds like they originally had the site located in the root directory of their web server, and did a re-organization of their file structure. Their site is now contained in the content directory. Perhaps they set up a new CMS which required this change.

The most logical structure would be www.domainA.com/products/.., and not www.domainA.com/content/products, right?

It depends on your perspective. For example, if you have a WordPress blog site or other CMS paired with forum software, then the wordpress site is often set up at the root domain. The forum software would be in a directory such as /forums or perhaps /content. If it was my site then the products would be located off the root directory as you suggest, but others could certainly offer it within the /content directory.

what are the actual implications when redirecting from domainA.com to domainA.com/content?

It depends. A well established site will often have a lot of link value for their home page. That value would be lost with the 302. There is nothing specifically detrimental per se. It is more of missed opportunities.