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
-
302 > 302 > 301 Redirect Chain Issue & Advice
Hi everyone, I recently relaunched our website and everything went well. However, while checking site health, I found a new redirect chain issue (302 > 302 > 301 > 200) when the user requests the HTTP and non-www version of our URL. Here's what's happening: • 302 #1 -- http://domain.com/example/ 302 redirects to http://domain.com/PnVKV/example/ (the 5 characters in the appended "subfolder" are dynamic and change each time)
Intermediate & Advanced SEO | | Andrew_In_Search_of_Answers
• 302 #2 -- http://domain.com/PnVKV/example/ 302 redirects BACK to http://domain.com/example/
• 301 #1 -- http://domain.com/example/ 301 redirects to https://www.domain.com/example/ (as it should have done originally)
• 200 -- https://www.domain.com/example/ resolves properly We're hosted on AWS, and one of my cloud architects investigated and reported GoDaddy was causing the two 302s. That's backed up online by posts like https://stackoverflow.com/questions/46307518/random-5-alpha-character-path-appended-to-requests and https://www.godaddy.com/community/Managing-Domains/My-domain-name-not-resolving-correctly-6-random-characters-are/td-p/60782. I reached out to GoDaddy today, expecting them to say it wasn't a problem on their end, but they actually confirmed this was a known bug (as of September 2017) but there is no timeline for a fix. I asked the first rep I spoke with on the phone to send a summary, and here's what he provided in his own words: From the information gathered on my end and I was able to get from our advanced tech support team, the redirect issue is in a bug report and many examples have been logged with the help of customers, but no log will be made in this case due to the destination URL being met. Most issues being logged are site not resolving properly or resolving errors. I realize the redirect can cause SEO issues with the additional redirects occurring. Also no ETA has been logged for the issue being reported. I do feel for you since I now understand more the SEO issues it can cause. I myself will keep an eye out for the bug report and see if any progress is being made any info outside of this I will email you directly. Thanks. Issue being Experienced: Domains that are set to Go Daddy forwarding IPs may sometimes resolve to a url that has extra characters appended to the end of them. Example: domain1.com forwards to http://www.domain2.com/TLYEZ. However it should just forward to http://www.domain2.com. I think this answers what some Moz users may have been experiencing sporadically, especially this previous thread: https://moz.com/community/q/forwarded-vanity-domains-suddenly-resolving-to-404-with-appended-url-s-ending-in-random-5-characters. My question: Given everything stated above and what we know about the impact of redirect chains on SEO, how severe should I rate this? I told my Director that I would recommend we move away from GoDaddy (something I don't want to do, but feel we _**have **_to do), but she viewed it as just another technical SEO issue and one that didn't necessarily need to be prioritized over others related to the relaunch. How would you respond in my shoes? On a scale of 1 to 10 (10 being the biggest), how big of a technical SEO is this? Would you make it a priority? At the very least, I thought the Moz community would benefit from the GoDaddy confirmation of this issue and knowing about the lack of an ETA on a fix. Thanks!0 -
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 -
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 -
301 redirect subdirectory to new domain
I'm planning on using 301 redirects to spin out a subdirectory of my current website to be its own separate domain. For instance, I currently have a website www.website.com and my writers write tech news at www.website.com/news. Now I want to 301 redirect www.website.com/news to www.technews.com. Will this have any negative impact on SEO? What are some steps that I can take to minimize these impacts?
Intermediate & Advanced SEO | | Chris_Bishop1 -
Multiple 301 redirects for a HTTPS URL. Good or bad?
I'm working on an ecommerce website that has a few snags and issues with it's coding. They're using https, and when you access the website through domain.com, theres a 301 redirect to http://www.domain.com and then this, in turn, redirected to https://www.domain.com. Would this have a deterimental effect or is that considered the best way to do it. Have the website redirect to http and then all http access is redirected to the https URL? Thanks
Intermediate & Advanced SEO | | jasondexter0 -
Disavow first (and link removal outreach second) as tactic?
I need to remove/disavow hundreds of domains due to an algorithmic penalty. Has anyone disavowed first and done the outreach thing second as a tactic? The reason why I was considering this was as follows: Most of the websites are from spammy websites and unlikely to have monitored accounts/available contact details. My business is incredibly seasonal, only being easily profitable for half of the year. The season starts from next month so the window of opportunity to get it done is small. If there's a Penguin update before I get it done, then it could be very bad news. Any thoughts would be much appreciated. (Incidentally, if you are interested in, I also posted here about it: http://moz.com/community/q/honest-thoughts-needed-about-link-building-removal)
Intermediate & Advanced SEO | | Coraltoes770 -
301 or 302 Redirects to Mobile Site
When it's detected that a mobile device is accessing the site it has the ability to redirect from www.example.com to m.example.com. Does it make more sense to employ a 301 or 302 redirect here? Google says a 301 but does not explain why (although usually I stick to "when in doubt, 301") . It seems like a 302 would prevent passing link juice to the mobile site and having mobile-optimized results also showing up in Google's index. What is the preference here?
Intermediate & Advanced SEO | | SEOTGT0 -
How To 301 Redirect .html pages
I need to redirect a page/URL that is purely .html to a new location. I don't know how to do this. All the redirects I can find are for server side code pages .php/.aspx etc. From my understanding I can't put a server side redirect in a .html file. I am hosting on a microsoft server, however the new page I am redirecting to is .php. I am running some WordPress (.php) files on the server. I need to make it redirect before the old page loads so visitors don't start reading something that is about to get redirected Can someone please help me?
Intermediate & Advanced SEO | | MyNet0