URL Re-Writes & HTTPS: Link juice loss from 301s?
-
Our URLs are not following a lot of the best practices found here: http://moz.com/blog/11-best-practices-for-urls
We have also been waiting to implement HTTPS.
I think it might be time to take the plunge on re-writing the URLs and converting to a fully secure site, but I am concerned about ranking dips from the lost link juice from the 301s. Many of our URLs are very old, with a decent amount of quality links.
Are we better off leaving as is or taking the plunge?
-
Thanks all...Much appreciated!
Looking at the examples below, does anyone think this move could result in a negative effect?
**From: **http://www.xyzwidgets.com/widgets/commercial-widgets/small_blue_widget.htm
**To: **https://www.xyzwidgets.com/small-blue-widget
**From: **http://www.xyzwidgets.com/info/videos/general/what-are-widgets.htm
-
If youre going to be updating your URLs for best-practices, I would incorporate the conversion to https as well - do it all in one shot, as you've said.
Just ensure you're implementing 301 redirects properly. Not doing so can have disastrous results.
-
In addition to what Robert just said. If you add a 301 now to format url properly, and later add a second 301 to move to HTTPS, you will add redirect to redirect losing that little bit of page juice twice.
-
The only downside to that approach is if there is no benefit to moving to HTTPS, you have wasted time (if that was the only reason for you doing so). However, if you are using 301's either way, you may as well move to HTTPS - it won't hurt you and it might help you.
-
My thinking is that the potential for increase in CTR in the SERPS can have a greater affect than the potential 301 harm.
I notice many of you are still waiting for the jury to be a bit more conclusive on whether to move to HTTPS. However, if I'm redirecting all pages using Moz's bes practice, shouldn't I just take the HTTPS plunge at the same time? Is there any reason not to?
-
301's of any kind can result in a slight decrease in "link-juice" moving forward, although it can be hard to determine exactly how much (not a large amount relatively speaking). That being said, as Massimiliano stated, I haven't personally come across this scenario in my work.
The HTTP/HTTPS debate is still going and as Ray said, it might be best to adopt a "wait and see" strategy.
Of these things, you have pointed out that your urls do not follow best practices stated in the link - it is likely that new urls combined with 301 redirects to HTTPS will not hurt your rankings and may in fact help you. As Ray stated, it is about cost and whether you think the potential rankings are worth the time, effort and money you will spend making it happen.
-
In my experience the power of proper url, with the right keywords in the right place, is so great I wouldn't wait a second before to fix them.
Again based on my experience I never noticed a decrease in ranking due to 301.
I recently moved three websites from http to https and I didn't notice any decrease in ranking I could associate with the redirect.
Of course since we daily work on improving ranking is hard to distinguish a small decrease due to 301 from the general improvement.
-
The benefit in the ranking influence for http / https sites is still unclear. Many SEOs are still holding off on this conversion to see what its impact, hopefully measurable, may end up being.
Moz has a great post on Https necessities and practices here: http://moz.com/blog/seo-tips-https-ssl
If it is going to be an intense project (costs an mount of money that makes you question its worth), I would hold off until more information is exposed about https as a ranking factor. If the conversion is easy, then I would get it implemented now and reap any benefits that come from https.
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
-
Will disallowing URL's in the robots.txt file stop those URL's being indexed by Google
I found a lot of duplicate title tags showing in Google Webmaster Tools. When I visited the URL's that these duplicates belonged to, I found that they were just images from a gallery that we didn't particularly want Google to index. There is no benefit to the end user in these image pages being indexed in Google. Our developer has told us that these urls are created by a module and are not "real" pages in the CMS. They would like to add the following to our robots.txt file Disallow: /catalog/product/gallery/ QUESTION: If the these pages are already indexed by Google, will this adjustment to the robots.txt file help to remove the pages from the index? We don't want these pages to be found.
Intermediate & Advanced SEO | | andyheath0 -
Switching from HTTP to HTTPS: 301 redirect or keep both & rel canonical?
Hey Mozzers, I'll be moving several sites from HTTP to HTTPS in the coming weeks (same brand, multiple ccTLDs). We'll start on a low traffic site and test it for 2-4 weeks to see the impact before rolling out across all 8 sites. Ideally, I'd like to simply 301 redirect the HTTP version page to the HTTPS version of the page (to get that potential SEO rankings boost). However, I'm concerned about the potential drop in rankings, links and traffic. I'm thinking of alternative ways and so instead of the 301 redirect approach, I would keep both sites live and accessible, and then add rel canonical on the HTTPS pages to point towards HTTP so that Google keeps the current pages/ links/ indexed as they are today (in this case, HTTPS is more UX than for SEO). Has anyone tried the rel canonical approach, and if so, what were the results? Do you recommend it? Also, for those who have implemented HTTPS, how long did it take for Google to index those pages over the older HTTP pages?
Intermediate & Advanced SEO | | Steven_Macdonald0 -
URL Construction
Working on an old site that currently has category urls (that productively rank) like this example: LakeNameBoating.com/category/705687/rentals I want to enhance the existing mid page one rank for terms related to "Lake Name Boat Rentals," 301ing the old urls to the new, would you construct the new urls as: LakeNameBoating.com/lake-name-boat-rentals or... LakeNameBoating.com/boat-rentals And why? It's all for one particular lake with "name" being just an anonymous placeholder example. Thanks!
Intermediate & Advanced SEO | | 945010 -
Site wide links - should they be nofollow or followed links
Hi We have a retail site and a blog that goes along with the site. The blog is very popular and the MD wanted a link from the blog back to the main retail site. However as this is a site wide link on the blog, am I right in thinking this really should be no follow link. The link is at the top of every page. Thanks in advance for any help
Intermediate & Advanced SEO | | Andy-Halliday0 -
Does Google Read URL's if they include a # tag? Re: SEO Value of Clean Url's
An ECWID rep stated in regards to an inquiry about how the ECWID url's are not customizable, that "an important thing is that it doesn't matter what these URLs look like, because search engines don't read anything after that # in URLs. " Example http://www.runningboards4less.com/general-motors#!/Classic-Pro-Series-Extruded-2/p/28043025/category=6593891 Basically all of this: #!/Classic-Pro-Series-Extruded-2/p/28043025/category=6593891 That is a snippet out of a conversation where ECWID said that dirty urls don't matter beyond a hashtag... Is that true? I haven't found any rule that Google or other search engines (Google is really the most important) don't index, read, or place value on the part of the url after a # tag.
Intermediate & Advanced SEO | | Atlanta-SMO0 -
If I own a .com url and also have the same url with .net, .info, .org, will I want to point them to the .com IP address?
I have a domain, for example, mydomain.com and I purchased mydomain.net, mydomain.info, and mydomain.org. Should I point the host @ to the IP where the .com is hosted in wpengine? I am not doing anything with the .org, .info, .net domains. I simply purchased them to prevent competitors from buying the domains.
Intermediate & Advanced SEO | | djlittman0 -
Capitals in URLs
Hello Mozzers. I've just been looking at a site with capitals in the URL - capitals are used in the product descriptions, so you'll have a URL structure like this: www.company.com/directory1/Double-Beds-Luxury (such URLs do not work if I lower the case of the capitals). There are 50,000 such products on the site. Clearly one drawback is potential customers might type in, or link to, the lower case of the URL and get a "not found" result (though the urls are relatively long so not that likely I'm thinking). Are there any additional drawbacks with the use of capitals outlined here?
Intermediate & Advanced SEO | | McTaggart0 -
Does the number of links on a page metric include repeated links?
Just wondering if the number of links on the page metric includes links that are repeated? So, if I had 100 links to one page would this count as 100 or 1 link?
Intermediate & Advanced SEO | | Cornwall
If it's the former does this mean more links to one page adds weight? Thanks0