Temporary Redirect Warnings

[UnderMe]

This post is deleted!

[TomRayner]

Hi James

You'll probably be aware that 302 redirects tell the Google crawler that the page has been "found", but doesn't pass on any of the "strength" or "juice" that the page has to the new destination.  You can read more in the Moz guide to redirects.

The recommendation would be to change it to a 301, as then any strength the page does have would pass.

Now, should you do it? Personally, I don't think it's that necessary.  I can't imagine that those temporary pages would have much strength to pass to begin with and there is also a school of thought that says a 302 redirect does in fact pass strength.

However, I would take action.  7794 is an awful lot of redirects and I imagine that this will only increase over time.  Having too many redirects in your .htaccess file (if your site is running apache, which yours is) could potentially slow down the file and therefore the site.

My recommendation would be to get in touch with whoever provides your CMS and ask if there is a better solution to the login situation that doesn't involve creating mass redirects.

[Marcus_Miller]

Hey, I have seen this in a bunch of older ecommerce platforms and often the this is just a case of the shopping cart or some such doing some processing and then issuing a redirect to throw the user back where they need to be.

You may not be able to easily fix this but these redirects are part of the platform rather than a 'page moved' kind of response so ultimately you are best clearing this out of your reports so you have a nice clean report and can forget about this.

I would imagine this is not something you need to worry about but you could consider noindexing these pages and nofollowing the links. You could also potentially block them from the SEOMoz and Google crawler in robots.txt if you don't want to mess with the platform itself.

Hope that helps!
Marcus

[UnderMe]

Hi Guys,

Thanks for taking the time to reply, the information is helpful.

Regards

James