Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Should I run 302 first before implementing 301?
-
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?
-
This is a friend's tool that has some more options.
http://incredibill.me/htaccess-rewrite-wizard -
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.
-
Thanks esiow2013 & others for discussing on 301 redirect, I also had same issue.
-
That's also a useful tool Ash, although it won't deal with URLs that that have parameters in such as question marks.
-
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
-
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 .
-
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?
-
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'!
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
301 redirect hops from non-https and www
It's best practice to minimize the amount of 301 redirect hops. Ideally only one redirect hop. It's also best practice to 301 redirect (or at least canonical) your non-https and/or your non-www (or www) to the canonical protocol/subdomain. The simplest (and possibly the most common) way to implement canonical protocol/subdomain redirects is through a load balancer or before your app processes the request. Both of which will just blanket 301 to the canonical domain/protocol regardless if the path exists or not In which case, you could have: Two hops. i.e. hop #1 http://example.com/foo to https://example.com/foo, hop #2 https://example.com/foo to https://example.com/bar 301 to a 404. Let's say https://example.com/dog never existed, but somebody for whatever reason linked to it (maybe a typo). If I request https://www.example.com/dog, the load balancer would 301 to a 404 page. Either scenario above should be fairly rare. However, you can't control how people link to you. Should I care about either above scenario? I could have my app attempt to check if the page exists before forwarding, but that code could be complicated.
Intermediate & Advanced SEO | | dsbud0 -
301 redirects Ruby on Rails
Can anyone point me to the best way to implement 301 redirects on a Ruby on Rails website?
Intermediate & Advanced SEO | | brianvest0 -
Will I lose Link Juice when implementing a Reverse Proxy?
My company is looking at consolidating 5 websites that it has running on magento, wordpress, drupal and a few other platforms on to the same domain. Currently they're all on subdomains but we'd like to consolidate the subdomains to folders for UX and SEO potential. Currently they look like this: shop.example.com blog.example.com uk.example.com us.example.com After the reverse proxy they'll look like this: example.com/uk/ example.com/us/ example.com/us/shop example.com/us/blog I'm curious to know how much link juice will be lost in this switch. I've read a lot about site migration (especially the Moz example). A lot of these guides/case studies just mention using a bunch of 301's but it seems they'd probably be using reveres proxies as well. My questions are: Is a reverse proxy equal to or worse/better than a 301? Should I combine reverse proxy with a 301 or rel canonical tag? When implementing a reverse proxy will I lose link juice = ranking? Thanks so much! Jacob
Intermediate & Advanced SEO | | jacob.young.cricut0 -
Better to 301 or de-index 403 pages
Google WMT recently found and called out a large number of old unpublished pages as access denied errors. The pages are tagged "noindex, follow." These old pages are in Google's index. At this point, would it better to 301 all these pages or submit an index removal request or what? Thanks... Darcy
Intermediate & Advanced SEO | | 945010 -
For URLs that require login, should our redirect be 301 or 302?
We have a login required section of our website that is being crawled and reporting as potential issues in Webmaster Tools. I'm not sure what the best solution to this is - is it to make URLs requiring a login noindex/nocrawl? Right now, we have them 302 redirecting to the login page, since it's a temporary redirect, it seems like it isn't the right solution. Is a 301 better?
Intermediate & Advanced SEO | | alecfwilson0 -
For how long does Google honor a 302 redirect?
Greetings! I would love some recent experiences to support our experience which is +/- 1 year old on this question. Based on our experiences around a year ago, I believe that Google will only honor a 302 temporary redirect for a relatively short period - perhaps up to a month - and then it will begin treating the redirect as a 301 redirect and will remove the old page from the index. Have others seen this? Is there an update on what the max "safe" period to have a 302 in place could be? We have a domain that is soon to experience about 3 months of "downtime" with no content on it, but the content will be back after that time. Ideally we would 302 redirect the pages elsewhere just for that downtime period. However, I don't want to do a 302 redirect if there is a risk that the pages will lose all of their accumulated authority and indexing. Basically, is there any safe way to just put the domain on ice for a few months? Please share recent experience only. Thanks for your insights!
Intermediate & Advanced SEO | | g-s-m0 -
302 redirects in the sitemap?
My website uses a prefix at the end to instruct the back-end about visitor details. The setup is similar to this site - http://sanfrancisco.giants.mlb.com/index.jsp?c_id=sf with a 302 redirect from the normal link to the one with additional info and a canonical tag on the actual URL without the extra info ((the normal one here being http://sanfrancisco.giants.mlb.com,) However, when I used www.xml-sitemaps.com to create a sitemap they did so using the URLs with the extra info on the links... what should I do to create a sitemap using the normal URLs (which are the ones I want to be promoting)
Intermediate & Advanced SEO | | theLotter0 -
301 Redirect - What happens to backlinks
Hello... One of my sites is losing rankings in G. I received the webmaster notification of unnatural links... My question is, should i do a 301 redirect of every page on my site to a new domain? If so, do the backlinks (which i believe are causing my rankings to drop) carry over? How about the good backlinks? Also, what would happen to the rankings i currently have on page 1? Thanks
Intermediate & Advanced SEO | | Prime850