302 errors with screaming frog

[edward-may]

Hi all,

Iv recently just run a crawl through screaming frog and it seems im coming up with 302 errors, looks like it has something to do on the client side of my website as I can tell from the url.

Can anyone explain perhaps what this might be about?

Thanks appreciate the feedback

[Keszi]

Hi Justin,

302 status codes are temporary redirects on your website. To get to know more about status codes and best practices, you should check the following articles:

• http://moz.com/learn/seo/redirection
• http://moz.com/learn/seo/http-status-codes
• http://moz.com/academy/redirects

I hope these will clear your question.

Gr., Keszi

[Travis_Bailey]

The 302 response code isn't an error, per se. It's a redirect code that generally means 'found'. It doesn't pass 'link juice'.

Some of the common uses I've seen include using 302 codes for external links, when they can simply be set to nofollow. The nofollow link attribute is handy when you feel it's necessary to link to an external source, but don't want any of the baggage that comes with passing PR.

In the worst case, someone moved pages 'temporarily' when the pages were actually moved permanently. Which may mean pages with incoming links at the old URL aren't passing 'juice' or 'PR' like they should to the new URL.

Here's the Moz Guide to Redirect Codes for further reading.

I don't know anything about your site, so there may be a good reason for the 302 responses. But the good reasons are quite limited.