[Estimated read time: 6 minutes]
It's been almost two years (August 2014) since Google announced that HTTPS was a ranking signal. Speculation ran rampant, as usual, with some suggesting there was little or no benefit to switching (and possibly significant risk) while others rushed to sell customers on making the HTTPS switch. Two years later, I believe the data speaks for itself — Google is fighting, and winning, a long war.
What's happened since?
If you only consider the impact of Google's original HTTPS update, I understand your skepticism. Prior to the update, our 10,000-keyword tracking system (think of it as a laboratory for studying Google searches) showed that roughly 7% of page-1 Google results used the "https:" protocol. A week after the update announcement, that number had increased only slightly, to just over 8%:
The blue/purple show the before/after based on the announcement date. As you can see, the update probably rolled out over the course of a few days. Even over a 2-week period, though, the impact appears to be fairly small. This led many of us to downplay Google's statements and ignore HTTPS for a while. The next graph is our wake-up call:
As of late June, our tracking data shows that 32.5% (almost one-third) of page-1 Google results now use the "https:" protocol. The tiny bump on the far left (above "A-14" = August 2014) is the original HTTPS algorithm update. The much larger bump in the middle is when Wikipedia switched to HTTPS. This goes to show the impact that one powerhouse can have on SERPs, but that's a story for another time.
What does it mean?
Has Google rolled out multiple updates, rewarding HTTPS (or punishing the lack of it)? Probably not. If this two-year trend was purely a result of algorithm updates, we would expect to see a series of jumps and new plateaus. Other than the Wikipedia change and two smaller bumps, the graph clearly shows a gradual progression.
It's possible that people are simply switching to HTTPS for their own reasons, but I strongly believe that this data suggests Google's PR campaign is working. They've successfully led search marketers and site owners to believe that HTTPS will be rewarded, and this has drastically sped up the shift. An algorithm update is risky and can cause collateral damage. Convincing us that change is for our own good is risk-free for Google. Again, Google is fighting the long war.
Is our data accurate?
Of course, our tracking set is just one sample of search data. The trendline is interesting, but it's possible that our keywords are overstating the prevalence of HTTPS results. I presented a number of roughly 30% at SMX Advanced in mid-June. Later that same day, Google's Gary Illyes called me out and confirmed that number:
Gary did not give an exact figure, but essentially gave a nod to the number, suggesting that we're in the general ballpark. A follow-up tweet confirms this interpretation:
This is as close to confirmation as we can reasonably expect, so let's assume we showed up to the right ballgame and our tickets aren't counterfeit.
Why does 30% matter?
Ok, so about one-third of results use HTTPS. Simple arithmetic says that two-thirds don't. Projecting the trend forward, we've got about a year and a half (16–17 months) before HTTPS hits 50%. So, is it time to panic? No, probably not, but here's the piece of the puzzle you may be missing.
Google has to strike a balance. If they reward sites with HTTPS (or dock sites without it) when very few sites are using it, then they risk a lot of collateral damage to good sites that just haven't made the switch. If, on the other hand, they wait until most sites have switched, a reward is moot. If 100% of sites are on HTTPS and they reward those sites (or dock the 0% without it), nothing happens. They also have to be careful not to set the reward too high, or sites might switch simply to game the system, but not too low, or no one will care. However I feel about Google on any given day, I acknowledge that their job isn't easy.
If rewarding HTTPS too heavily when adoption is low is risky and rewarding it when adoption is too high is pointless, then, naturally, the perfect time to strike is somewhere in the middle. At 30% adoption, we're starting to edge into that middle territory. When adoption hits something like 50–60%, I suspect it will make sense for Google to turn up the algorithmic volume on HTTPS.
At the same time, Google has to make sure that most of the major, trusted sites have switched. As of this writing, 4 of the top 5 sites in our tracking data are running on HTTPS (Wikipedia, Amazon, Facebook, and YouTube) with the only straggler being #5, Yelp. The top 5 sites in our tracking account for just over 12% of page-1 results, which is a big bit of real estate for only 5 sites.
Of the top 20 sites in our tracking data, only 7 have gone full HTTPS. That's 35%, which is pretty close to our overall numbers across all sites. If Google can convince most of those sites to switch, they'll have covered quite a bit of ground. Focusing on big players and convincing them to switch puts pressure on smaller sites.
In many ways, Google has already been successful. Even without a major, algorithmic HTTPS boost, sites continue to make the switch. As the number climbs, though, the odds of a larger boost increase. I suspect the war is going to be over sooner than the trendline suggests.
What are the risks?
Am I telling you to make the switch? No. While I think there are good reasons to move to HTTPS for some sites and I think most of Google's motives are sincere on this subject, I also believe Google has been irresponsible about downplaying the risks.
Any major change to sitewide URLs is risky, especially for large sites. If you weigh the time, money, and risk of the switch against what is still a small algorithmic boost, I think it's a tough sell in many cases. These risks are not theoretical — back in May, Wired.com wrote up the many problems they've encountered during their HTTPS switch, a switch that they've since paused to reconsider.
Like any major, sitewide change, you have to consider the broader business case, costs, and benefits. I suspect that pressure from Google will increase, especially as adoption increases, and that we're within a year of a tipping point where half of page-1 results will be running on HTTPS. Be aware of how the adoption rate is moving in your own industry and be alert, because I suspect we could see another HTTPS algorithm update in the next 6–12 months.
Not sure you can just conclude "not an algorithm update" because of "lack of jump and plateau" and linear progression of https website count in top10.
I think you could have pushed your analysis deeper. Instead of just counting websites which have HTTPS every month, it would be better to check if this new HTTPS website in page #1 was already on page #1 without HTTP or if it's coming from deeper SERP. Also, if you have SERP history of 10k kw, you can detect when a website switched to HTTPS and check if there is a minor improvement on all its rankings. The count of HTTPS website alone can't demonstrate an algorithm update.
But anyway it is a useful piece of information to know we have more websites using HTTPs every day. I also tend to think HTTPS is a minor boost (if any) like page speed. I think switching sooner is better than later, but it shouldn't be done in a hury. Regarding big website, they are not forced to switch everything to HTTPS in one shot, they can do it part by part, and watch for consequences before going further.
I couldn't agree more. This is, at best, a hint at correlation. It doesn't even sniff at the heels of causation. If the point of the article was to show that Google has managed to con some big sites into switching to HTTPS, then it hit the mark. If it was to prove that HTTPS made a difference in how the sites rank, it missed its target by a long shot!
Of course, those who sell SEO services would rather believe there is causation so that they can sell even more unnecessary services to gullible clients. "Switch to HTTPS or get left behind in the rankings. We'll do it for you ..."
Seeing the rankings differences pre and post HTTPS would have been the way to go here. It also might be interesting to see if it has made any impact at all on Bing/Yahoo SERPs.
In the end, Google knows that the key to market dominance is the reliability of its organic search engine rankings. If the results suck, people will stop using Google. They are hoping articles like this one sway even more people into employing HTTPS (in most cases, for no reason at all, since no truly private data is being exchanged). Otherwise, they run the risk of serving up some pretty crappy results if only a third of the sites are using it.
My guess is, you will not see much of an increase going forward. The ones who can make the move or even know they are "supposed to", have already done it. There will be a few major stragglers left, but don't count on this percentage topping 50% and even if it does, what does that mean? I'd maintain that it means that half the sites on page one switched, NOT that half the sites got to page one because of the switch. As it stands, 2/3 of the results on page one don't have HTTPS. Can't be much of a rankings boost. THAT is the real story!
@Scott -- Respectfully, that's exactly what I said in the post. The data suggests that Google's PR campaign for HTTPS has been effective and people are gradually switching, not that any HTTPS-friendly update is improving rankings. The trick, and this is where I think it's dangerous to ignore the trend, is that as adoption increases, Google's freedom to increase the ranking boost will increase.
It was eluded to in the article but the main theme, at least to me, was that you better switch or else. My gut feeling is that, like so many other things that Google has tried and later pulled off the table, making this a ranking signal that is anything other than of scant importance will severely harm the quality of their search results. Far too many good websites are going to ignore this advice for the simple reason that they have no reason to be secure.
The fact is, practically zero websites need to be 100% HTTPS. Requiring it on pages where sensitive data is entered is one thing; expecting websites to implement it across the entire domain is ludicrously unnecessary.
If only far more people would shrug when Google says "jump", they would lose the power to control webmasters. Then, maybe, Google would spend more time on trying to improve their obviously inadequate algorithm and less time trying to get webmasters to "fix" their websites to compensate for Google's own incompetence.
Perhaps it would be more precise to say that this pattern of increase isn't consistent with a handful of HTTPS-friendly algorithm updates. If Google had made a few HTTPS updates, we'd expect more of a step pattern, not a gradual upward trend. We know that the one confirmed HTTPS update caused a small step up, which backs up this general theory. It's possible that Google also rolled out an algorithm update during the same period that Wikipedia made the switch, but that's nearly impossible to separate.
The problem with analyzing the ranking boost directly is that rankings are very volatile (the biggest lesson I've learned from running the MozCast project). If a page/site that previously wasn't ranking appeared in the top 10 with an "https:" URL, there are many reasons that could happen. If we know a site switched to HTTPS, we could theoretically look at just that site, but any major sitewide switch tends to cause short-term ranking fluctuations. By the time those fluctuations even out, too much has changed to get an accurate read on the situation.
When Wikipedia rolled out HTTPS, I did analyze the rankings of all "https:" URLs before and after and saw a slight improvement, but it's unclear whether that was due to an overall rankings boost or just the power of Wikipedia URLs in general (and they fact that they rank, on average, higher than most sites). That's why I've stuck to total HTTPS adoption for the long-term trend.
If someday HTTPS gets more relevant than typical http, Google would lost some of their democratic way of SEO, the people who can cost ther HTTPS would have more benefits from the people who couldn´t afford.
i'm still a bit bitter about Google trying to force people into https with the promise of benefits which really didn't exists.
Finally, Google is 'the boss' (especially in Europe), and we only can do one thing: obey :(
I have no argument with that sentiment.
Dear Peter,
I'm really glad I've read this post, really had no idea that https was a ranking signal for Google. I've just read the article from Wired too and I just can imagine that if it's hard for a big company, how would it be for a small one who can't assume the cost of all of this?
I know that, in a long term way, it's going to be better to go from http to https but, what if you're a small company that has had a web for, let's say 10 years, well positioned and with a lot of PA and DA, but you've made it through the years? Now you could loose almost everything you had achieved? Cause growing on the ranking again must not be an easy task...
I think Google should rethink about some changes they're making cause, even though they're also a company, they we've a lot of people that indirectly count on them too =/.
Anyway, thank you very much for such an informative post, much appreciated!
I have been skeptical about switching my sites to https because people I trust reported significant drops in their Adsense revenue after making the switch. I don't think it is wise to risk possible migration problems, your Adsense revenue and the time/cost involved for a rankings boost that people argue about.
Just checked your link, it was 2 years ago. Adsense probably evolved since, they did it while adsense was saying : "We don’t recommend that publishers with HTTP sites convert their sites to HTTPS unless they have a strong reason to do so.". It is no more the case. Would be great to have up to date feedback.
Yes, it is two years old. Still, don't want to convert my site with the "hope" that they are now doing a better job. I am waiting to see people say... "I converted my site and my Adsense revenue didn't change." I have not seen that yet. Too much money is involved to take chances.
Up to date feedback: flipped my primary eight AdSense sites to https this spring, experienced no traffic drops (in fact traffic went up across the board but I am not attributing that to SSL) and no AdSense drop except for an expected change as I swapped out about 30% of my AdSense impressions this year to Facebook Audience Network. This is over aggregate four million or so pageviews. The first 60 days before I added the FAN, revenue was pretty much the same - didn't go up, didn't go down.
Biggest issues I experienced were convincing other ad networks to stop serving insecure images and/or pixels.
It just shows you how powerful Google are. They throw a hint about something boosting SERP position by a minuscule (MAYBE) and everyone falls over themselves to obey them. https is likely much more beneficial for the website user than the website owner and rightfully so.
Dear Peter,
Help full information about HTTPS.
But still there are 30% - 60% ratio so confuse that we have to suggest all our client to move HTTPS or not because some of them are only information sharing website.
Thanks for this interesting data, now I need to see how many of our competitors have HTTPS for the most important keywords.
I think HTTPS will be the standard way to go in the future for ecommerce, especially for new websites. Eventually I think that the ranking boost will be similar to having a mobile or responsive site. However, I completely agree that making a major URL change to pages that rank good is a pretty big scary.
Currently we have HTTPS only for the checkout (where a secure connection really matters). Does anyone have any insights on this compared to a full HTTPS site?
I really had no idea about this. Now I will have to investigate how change my blog into https :(
Thanks!
It is better to turn to your hosting provider and they will provide a tutorial. For example, in mine is made as follows. This in Spanish, sorry, but it is how do.
Yesterday I was searching for it at my providers's blog and there is a lot of information about how to do it!
Thanks a lot!
you're welcome. luck
Great article, Pete.
It's nice to see an update on this matter.
If you were to start a new website today - would you always choose https over http?
We are having this discussion at our team right now on a new project. I'm a big fan of going https from the start, while our IT guys are not, since it'll be heavier on the server. I just have a feeling that it will play a role at some point (if not already), so it makes perfect sense to implement it from day 1. But without anything other than a gut-feeling, is it really worth the fight?
Years passed, but we have same ugly HTTPS snippets in Google SERP.
Watching your own industry is an important suggestion.
In our industry 9 of 10 sites on page 1 for a lot of important keywords have gone full HTTPS. If you are the only one not making the switch, you could look like an amateur.
And if your customers are techies you should have a close eye on your CTR, too. Perhaps being the only "unsafe" site makes your customers consider other options?
So, it is not so much about rankings for me, it is more about the trust of your customers.
Tracking within your own industry and competition is definitely a smart move.
I am wondering why https and microdata URL mark-up display seem to be mutually exclusive. The site I look after switched to https in February. I have noticed that since the switch, our URLs in search results either show as microdata-prettified like www.greenpeople.co.uk > shop › by product › skin care › moisturiser or https, like https://www.greenpeople.co.uk/shop/by-product/natu.... I have been looking for a while now but still have not seen any https URLs in search results that contain the microdata formatting. I am happy to be proven wrong! I just can't work out why Google would not want https URLs to be pretty too.
I look at it from an adoptive perspective. If the user adopts the intent of doing business with secure sites, then I shall adopt the same understanding. Similarly, if a user becomes aware and mute to the idea of search advertisements displayed to the right of Google SERPs, then Google shall "switch it up" and remove it. Users are creatures of habit, and ranking factors go as deep as you subconscious. Directly or indirectly, we can conclude that https sites are ranking higher than non-https sites. Data doesn't lie.
Wow, this really got Google what they wanted. There are still hundreds of factors though.. I'm not seeing any controversy here.
Does Google want to sacrifice relevance signals and just reward everybody with SSL?
Of course not.
Did Google need to give even +0.001% value to SSL to motivate everybody to switch?
Probably not.
Are they still motivated to reward SSL?
Sure looks that way.
This question was referenced in an earlier comment, is it better to move a large site at once to HTTPS or move in sections? Can anyone offer the pros and cons of doing this?
Anyone changing to https be very careful. One of my site - https://Mediatimes.com.au/ was moved to https few months back and i ntoiced my PA and DA reduced from original. Overall SEO of the site was badly affected with this change. Finally I had to get rid of it, leading to other set of troubles like https version was indxed by this time. Stay away from migrating to https in most cases.
HTTPS is ideal for ecommerce or any website that deals sensitive input data like (bank account, email add etc..) having SSL certificate gives proof that your site is safe and not for scamming purposes. It also adds trust to the visitors knowing that your business and site is legit.
Sure, on pages where sensitive information is entered - like checkout pages. Requiring informational pages to be secure is just plain stupid!
That's why I moved to https
Ohh 30% Great!! In few years it'll cross 50%. Wow!!! Don't mean to offend you Dr. Peter, but let us discuss one thing. HTTPS uses very strong public-key cryptography to encrypt the connection between a client (often a web browser) and a server. Providing the private part of the certificate remains private and there are no other hiccups in implementation, HTTPS is highly secure. But, lots of sites don’t need that level of privacy and security. The average blog, for example, doesn’t need its public-facing pages encrypted with high-grade cryptography, but Google is a fan of the “security by default” and “HTTPS Everywhere” concept, so I think it’s using SEO to incentivize webmasters to implement HTTPS. We all know that HTTPS uses a lot of Server resources, hence a slow website might get outranked from Top 10 positions. Than what?? Should we opt for another service to boost our website's speed?? Sometimes I really feel, a day will come when such things will sidetrack Google.
Hi Peter
As I have said just the opposite ... In my top search words appear normal is that HTTP and not HTTPS. But the truth is that this issue'm pretty green and still do not understand what is really the difference
I know a few people in the marketing industry that were annoyed SSL was kind of forced onto us, but I think it's a good thing personally. Better security on the site, less likely that your information is hijacked or stolen, safer transactions. The only thing that is annoying is the cost of getting that damn green bar, those certificates are so expensive, and as far as I can see, there is no need for them to be.
As I see it...if google doesn't have the green bar, they can't expect me to have it either.
Google can penalize you for stuffing too many ads above the fold but then stuff too many ads above the fold on their own results, so I'm pretty sure that's not a safe assumption.
Sadly, you have a point there. It is too bad that when it comes to search engines, google has absolutely no competition. Bing and Yahoo search results are so horrible, even my parents in their 70's know not to use them.
I totally agree with you. We have to deal within its own manners and measures.
According to me I don't SSL actually make a difference, I have two sites and one of them is doing well in search engines whereas the site which is having SSL is not going good.
[Link removed by editor.]
Those are some well thought points you brought up, Dr. Peter. Though I just switched to HTTPS, I'm watching the results ;)
Excellent Explanation
I'm not quite sure what it means when a website runs on HTTPS, can someone explain it? It does seem like whatever it is, everything is trending that way and you should switch within a year so there is not a possibility of being penalized
Hello Claytonjay,
I 'll try to explain what that is. It is a protocol level indicating security of your website. It is to install an SSL certificate that identifies the company and its tax data (email, address, contact details, etc.). As a result, it gives more security to the website, not hacker -level security, but the user. To get a cash SSL certificate must generalize an accurate stating that your business is real and not scamming anyone. It is essential in e- commerce. I hope I have clarified the issue.
I find it very difficult to explain in English.
HTTPS top 30% is great.This article to know me and that i feeling good.
Thank you for this detailed presentation introducing the importance of https. Though the change is truely important one has to make sure that proper redirects are made and that external urls are gradually changed to https.
Doesn't this just mean that more websites have started using HTTPS? So the same websites are ranking but have installed an SSL, rather than Google increasing the rank of HTTPS websites?
I apologize for my English, we work with the team we have handled different tests migrating to HTTPS and only 30% have seen good results, we continue working a few months more to see if the change goes well we did.
Difficult decision, although it appears that the future will score better https : //. I do not think that it is only by Google , we all know that the issue of security is becoming an essential issue at government level , and that will eventually affect all . For now, for those sites that do not perform e-commerce or security information they need , and they do not want to have to start from scratch in their position , I recommend waiting .
Another possibility is that those sites that changed to https are websites that undergo an extensive SEO strategy, thus it is not by accident that these sites are on the top of the SERPs. If I am doing some serious SEO campaign for a client, i would recommend to go to https! Nice info that we can use to convince others to change to https!
Hi all , first thank you because I ayudais much to understand this world, you need to devote as much time to keep abreast of the changes that occur every day . In the end, if you want to devote to this, we 're like medical graduates , you always have to be studying if you want to do something in this sector. Many times we learn from these post , but rarely thank you, today I learned something more . Thank you.
For a big site, making the switch over to https can be such a headache! It's better to start the process sooner rather than later, though.
Dear
Very good tip for us. I am Quangle from Vietnam.
After reading your post, i want to change my domain " https://quanglepro.com " to " https ".
But if we change like this, Does it happen 404 page not found? Or affect to my ranking?
Nice day
Quangle
Seeing how HTTPS has its promised benefits, it wouldn't be long before most of the website would officially switch with the security vertical. After all, https provides authenticity and integrity which are the values that internet surfers look for in a website. The challenge however is how you should be able to maintain your SEO when you do the switch.
To be honest, I'd be surprised if 1% of the internet surfers even noticed whether or not they were on a secure site as opposed to a insecure site.
We are just waiting for it to be imperative. It's a potential traffic loss to a small B2B site. Also, we waited until our developer partner had more implementations under their belt. Pantheon has now made it easier to manage as well as CloudFlare. It will happen. Many of us will hold out until it's really necessary. Good read, thanks.
I conducted several hours of my own research and hand-counted first and second page results, with well over a hundred different queries. The actual result is 12% of results are https:// I used local, but high competition queries in industries that would actually have revenue budget to redo their site like [new york attorney] and others; several high level e-commerce product queries with Brand, Brand + Catalog pages and product name queries.
My synopsis is that Google is counting wordpress.com blog sites and Amazon in their calculation, which means millions of blogs and product pages from Amazon are skewing the data. I disagree that suddenly in the last 2 years people have been converting their site to https:// Completely bogus assertion, in my opinion.
A fair assessment would be to see how many domains (actual websites) have converted.
This is my data, not Google's, across a controlled set of 10,000 queries. I'm not sure how you can pick a site, like Amazon, and say that it's skewing the data. If a big site switches, that supports Google's ability to turn up the algorithm, and it matters quite a bit. Amazon's switch is actually very late on this graph and a pretty small bump. Wikipedia's switch had a big impact. The pattern in our data, though, is consistent and steady. We're looking at a consistent 2-year trend across a large and carefully tracked data set.
I think it's right people are sceptical about the update as a switch to HTTPS is not simple. I think the most important data is from the original update increase, this gives us an idea of the sort of impact it has, anything after is just showing us the number of sites converting to HTTPS and not that Google is adding weight to the use of it.
It could be a pain to change to HTTPS. I supposed it depend of the scope of your site and its positioning. Big sites could suffer from the change, although small sites could pass to HTTPS easily. Google would have to be careful with this pages.
If you where to start a new project i would consider seriously to start with HTTPS
Thanks a lot for the info
Interesting article. Thanks for sharing.
I switched to "https" on this site: https://www.kredittkort.reviews/ earlier this year, with small or no effect for the moment. I have had some problems building links as many sites often are preset for "http" urls/doesn't accept https-urls to be submitted. So my questions are:
1. Will https://www.kredittkort.reviews/ benefit for all the juice https://www.kredittkort.reviews/ get?
2. If I switch a http site to https, will the seo-juice follow or do one have to make redirects?
[links removed by editor]
Dr. Pete -- Out of that 30%, what percentage of sites that have migrated to HTTPS did it correctly and didn't screw it up by creating 4 versions of their websites?
A depressingly small percentage, I'm guessing :)
I can't say that my move to HTTPS was good for my SEO. Seems we have taken quite a hit over the past few months.
Seriously? If 30% of the Top ranking pages are HTTPS that means over 60% are HTTP pages.. In this case, I might argue that since there is an overwhelming majority of the Top pages that belongs to HTTP pages, HTTP pages are the way to go ;)
As I said in the article, it's the trend that matters. Yes, 2/3 of page-1 URLs are still "http:", but two years ago, 95% of them were. The balance is shifting, and this trend will continue. At some point, that means the disadvantage of not adopting HTTPS will increase.
Possible, but few other scenarios that are highly possible as well:
1. There is an increase in number http sites that are ranking high, simply because, there are more sites switching to https. Very likely these sites (like wikipedia that you mentioned) were already ranking at similar positions for those keywords and when they switched to https, definitely there will be more https sites showing up (but they were at the same ranking even before the switch)
2. Alot of sites that are switching to https are doing it for SEO reasons (my guess) and these are also the sites that are working the hardest on their SEO (if they are willing to go through the trouble to switch their site to https to improve their ranking, I'm willing to bet they are also doing alot more stuffs to improve their organic search ranking) and hence their ranking improvement.. BUT, the improvement in their search ranking for more likely due to the other works that they did.
Eventually, at the end of the day, if I am going consider implementing HTTPS for my site simply for SEO, I might ask myself, for the kind of efforts, costs and risks that are required to switch over to HTTPS is there any other SEO stuffs that if I focus on instead, that can yield higher SEO benefits (and for many sites, the answer is usually yes..).
**For my sites, I actually categorized switching over to HTTPS as high efforts and high risks project with potentially low benefits. And of course, this is highly subjective depending on your type of site and the technical skills you have..
I don't really disagree with (1) or (2) - I think that's consistent with what I said in the post. The overall trend indicates that sites are moving to HTTPS (and not that Google has rewarded HTTPS sites), and much of that is because people believe this will be of SEO benefit.
I think caution is perfectly reasonable. My concern, though, is that, as adoption increases, Google will eventually make a move that ups the stakes of not switching. My bigger concern is that that move is probably to happen sooner than we'd like.
Great post!! Goog job.Thanks and congratulation!!
Thanks for Sharing interesting topic, this is very important part thanks. :) Ordinarily we gain from these post , however infrequently thank you, today I picked up something more . Much obliged to you.
I think that the Arab web is not subject to these laws. My Site duration of his compound by the protocol and also pooped him but unfortunately I find sites using methods of circumventing the forefront of the results and we are in the final pages .
MY SITE: الصفحة العربية
Thanks for Sharing interesting topic