Should I run 302 first before implementing 301?

[esiow2013]

I just want to ask if it is necessary to run 302 redirections first before redirecting old to new URLs permanently. I heard that we should run temporary redirects first so we can check after and to avoid passing the link juice but I want to hear thoughts from experts. Do i need to test 302s for old pages that are still live or should we redirect old URLs once these pages already removed from the site?

[trainSEM]

This is a friend's tool that has some more options.
http://incredibill.me/htaccess-rewrite-wizard

[esiow2013]

We will remove a vertical/division from our current site and migrate the URLs (category and product-specific pages) to new URLs under a new domain. Let me know your thoughts Max!

By the way, thanks for sharing the redirect generator tool.

[Futura]

Thanks esiow2013 & others for discussing on 301 redirect, I also had same issue.

[Milian]

That's also a useful tool Ash, although it won't deal with URLs that that have parameters in such as question marks.

[trainSEM]

I have found that a 301 takes some time to take effect in the index, so I don't bother with a 302 first, There are many redirect tools on the web and I like this one: http://www.rapidtables.com/web/tools/redirect-generator.htm

[Milian]

What are you actually doing, redesigning a site and URLs have changed?

Although regardless, the process is normally the same. As soon as you have launched your new site, made live your new page or whatever is you are redirecting, set the redirects at the same time. There is no reason to delay them and again I really wouldn't bother with doing the redirects as 302's to start with. Just set the 301's, then check them all after, then double check. Even if some are incorrect after implementing, its no biggie. Simply edit it again so its correct .

The best thing to do is prepare all your redirects before I hand. I like to get organised and use a spread sheet with two columns, old URLs in one column, new URLs in the 2nd column. This way you can easily map them out.

Also to speed up the process of actually coding the redirects, I use this tool, it saves a huge amount of time: HtAccess 301 Redirect Generator Tool .

[esiow2013]

Thanks Max! Your answers are a big help. Last question, do I need to 301 redirect the old to new URLs within the day we will launch the new site after removing the old site? or should we prepare 302 redirects and check each URL that are still live(will be removed in site launch) if they land on the appropriate and new URLs and run 301 redirections after?

[Milian]

Like you mentioned, the reasoning behind doing 302 redirects initially is in case the redirect has been set incorrectly, giving you time to check them before Google re-crawls and updates the index. As 302 redirects are temporary, after setting the redirect the old page will usually stay in Google's index indefinitely.

However I do many 301 redirects every week and I have never taken this approach; I simply set the 301 redirect, then check everything is correct straight after. If you have hundreds of redirects to do you can check them more efficiently using the Screaming Frog web crawler. You can import your list of pages that should have been redirected in a txt file, then Screaming frog will crawl them telling you what response code they are sending and where they are redirecting too.

Even if you set an incorrect 301 redirect, it can takes weeks to months before Google updates the index, so you shouldn't really need to worry about sending the 'juice' to the incorrect page; although I suppose it depends on how long until you check if you have done those redirects correctly!

There could also be adverse issues. Say you were doing a site migration and you 302 redirected every URL on your site to other URLs, I don't know how Google would react to that, but it could be rather bad!

As the saying goes 'Measure Twice, Cut Once'!