Welcome to the Q&A Forum

Thank you for the responses, I think we've made our decision based on all of your suggestions.

Hi sorry to Dig this old post up but a client has a similar problem and I'd like to know how this panned out in the end, did that page ever get its DA back?

Hi Dave, I assume you are talking about webnames.ca, in which case if you drop the url for the press_releases into screaming frog then you see a whole bunch of 302's to an error page. I had a quick look and could not see an obvious link that was spawning these but something must be in there if both tools are seeing it. Most obvious thing would probably be a relative link (so like href="/default.aspx") maybe in one of the press releases themselves since your main menu items at first glance look ok. If you export the errors list from moz and filter for the 302s, then the referring page shown in the far right column in combination with the error page shown in the first column might help track down the place where the whole thing starts off. Tracking down the link(s) causing these kind of issues can be a real pain sometimes! Hope that helps!