Is 307 the best way to handle temporarily disabled items ?

[Saijo.George]

I was wondering what would be the best way to handle temporarily disabled items. There is 302 and 307 and from what I understand 307 redirect is the HTTP 1.1 successor of the 302 redirect.

Any one has any experience on how Google handles 307?

I am thinking I 307 the temp disabled pages to a generic page like site.com/we-are-adding-some-final-touches-to-this.html where we will explain to users why an item would be disabled and will give them an option to get notification when it goes back up.

Finally when it goes back up I remove the 307 redirect and make the page live.

[Hammad-Haider]

If your product is temporarily unavailable then don't redirect. display a message on the same page that "product is temporarily unavailable". You may also display some relevant product and categories but don't redirect.

[Saijo.George]

Thanks for your reply Zafaryab .

In our case we have to disable user generated content that at times have copyright issues, so we can't show the content as is and let us assume we disable 50 - 60 items a month . There is no way we can have unique content across all these disabled pages .. so I think we might need to look at an option that allows us to redirect to a temp page and bring the pages back to the index once the issue with the content has been resolved.

[Hammad-Haider]

First UGC should be published after verification and approval of moderator. So you may need to change the process of publishing content on the page.

Incase of 302 or 307 your original page will still remain in cache and you may get duplication content penalty.

If you already know which pages have copy right issues then you remove the content. mark the pages as no-index, follow. Make them index follow as soon as you have original piece of content written on them.

[AlanMosley]

302 and 307 are the same except for one small thing, with a 307, the redirect must be the same method as the original request, if the original was a GET then the redirect must be a GET, if it was a POST the redirect must be a POST.
A 302 allows for a change in method, but who ever changes the method? just use a 302