Category Archives: Web Development

Where are the Women? Stack Overflow Developer Demographics

Women in Technology

  • Coder, Where Are You?
  • Aging Gracefully
  • The Gender Gap Narrows
  • Wild Horses vs. University-Trained
  • The Best Technology for Development

For two weeks in February, Stack Overflow polled its users, asking them almost 50 questions on subjects ranging from gender to job satisfaction, from coffee consumption to preferences for tabs or spaces. More than 26,000 coders from over 150 nations completed the survey. The result is perhaps the most thorough report on developer preferences and work lives that has ever been published.

Here are highlights specific to the demographic questions.

Bear in mind as you read these results that they are geographically biased, since Stack Overflow is more popular in certain countries than others.

Coder, Where Are You?

The top countries of poll participants are:

  1. United States – 4745 respondents
  2. India – 2461 respondents
  3. United Kingdom – 2402 respondents
  4. Germany – 1976 respondents
  5. Poland – 833 respondents
  6. Canada – 828 respondents

Those total figures are based in part on population, though. Per capita, the top development countries – listed as coders for every 1000 people – are:

  1. Luxembourg – 39.8
  2. Iceland – 35.0
  3. Sweden – 35.0
  4. Israel – 33.4
  5. Finland – 33.0
  6. Singapore – 31.7

Aging Gracefully

How old are developers? Well, many are just a few years out of college (or high school). “At the time of this writing, the average developer is 28.9 years old,” explains the report. “He or she was born in April 1986, just as IBM manufactured the first megabit chip.”

Top age brackets are as follows:

  1. 25-29 years old – 28.5%
  2. 20-24 years old – 24.5%
  3. 30-34 years old – 17.8%
  4. 35-39 years old – 9.1%
  5. Under 20 years old – 8.8%
  6. 40-50 years old – 7.6%

Where is the youth of development the most pronounced? Here is the average age of developers in the top six respondent countries:

  1. India – 25.0 years old
  2. Poland – 26.7 years old
  3. Germany – 29.0 years old
  4. United Kingdom – 30.3 years old
  5. Canada – 30.3 years old
  6. United States – 31.6 years old

The Gender Gap Narrows

Are there any women developing software? Not many. Gender results were as follows:

  1. Men – 92.1%
  2. Women – 5.8%

Clearly programming is lopsided toward the men, as anyone who has ever attended any tech convention can confirm. “Our internal stats suggest the imbalance isn’t quite as severe as the survey results would make it seem,” says Stack Overflow, “but there’s no doubt everyone who codes needs to be more proactive welcoming women into the field.”

We can actually better understand the current status of the gender gap by looking at experience in general vs. experience specifically of women. Top experience categories for the broad developer population are:

  1. 2-5 years – 32.4%
  2. 11+ years – 24.2%
  3. 6-10 years – 23.2%
  4. 1-2 years – 13.6%
  5. Under a year – 6.6%

This data makes sense given the incredibly fast expansion of the development industry. It becomes more obvious how inexperienced the typical developer is when you compare to another occupation. “In the United States, nearly 40% of doctors have 10+ years of professional experience,” says the report. “By contrast, only about 25% of developers worldwide have more than 10 years coding experience.”

Now let’s contrast that against the women’s experience:

  • Under two years – 37.1%
  • 2-5 years – 30.1%
  • 6-10 years – 15.1%
  • 11+ years – 9.5%

As you can see, the extent of inexperience is much more dramatic for women – and that’s a good thing. It suggests that more women are becoming developers, creating a better gender balance.

Where are the women? The top three nations for women programmers are:

  1. India – 15.1%
  2. United States – 4.8%
  3. Sweden – 2.3%

Wild Horses vs. University-Trained

The numbers on academic background underscore the similarities between development, art, and entrepreneurialism. As in those other fields, schooling is helpful but optional for coders. Top educational backgrounds are:

  1. Self-trained – 41.8%
  2. Computer science bachelor’s degree – 37.7%
  3. Acquired skills on the job – 36.7%
  4. Computer science master’s degree – 18.4%
  5. Online training – 17.8%
  6. Partial college completion – 16.7%

In other words, the way that people pick up their programming knowledge is diverse. Incredibly, a third of developers (33%) haven’t completed any college courses in computer science, while almost half (48%) lack a CS degree. “System administrators are most likely to be self-taught (52%),” says Stack Overflow, while “[m]achine learning developers and data scientists are 10 times more likely than any other developer type to have a PhD (15%).”

The Best Technology for Development

Cloud has always been sold on its speed and simplicity of deployment, along with its typically lower cost. However, as many developers are well aware, not all cloud is created the same. It’s best to choose the right cloud upfront.

At Superb Internet, we offer distributed storage rather than centralized storage – the latter a remnant of the mainframe era that is used by many cloud providers. With distributed storage, you can experience multiple node failures with no impact on performance.

Coupling distributed storage with the reduced latency of IB over 10 Gigabit Ethernet, we offer cloud that typically delivers fourfold the performance of Amazon Web Services for cloud instances with similar specs. Get started.

Tapping Innovation: How Developers Leverage Cloud

What, exactly, is the cloud?

  • Introduction: Developers Key in a Data-Infused World
  • Cloud as a Critical Tool for Development
  • The Role of Open Source
  • True Distributed Cloud for the Best Results

Introduction: Developers Key in a Data-Infused World

Developers are essential to the new economy. First, just think about the scale of data – even from a year ago:

  • Think your post is important? It’s got competition. Every minute, 2.5 million instances of Facebook sharing occur.
  • Do you think search engine optimization might be important? Do you think it might be getting more sophisticated? Every single minute, over 4 million search requests are placed with Google.
  • Do you want to make a living off of your YouTube show? So does your neighbor. Every minute, 72 hours of new video is uploaded to YouTube.

In other words, the sheer amount of raw activity occurring in the digital universe is staggering.

Because that activity is so intense, data is becoming more valuable all the time. Forbes Data Driven Business editor Howard Baldwin points out how powerful data is by looking at two companies, one that is data-based and one that is physical. Baldwin contrasts Facebook to a major airline, United Airlines, which he describes as “a company that actually owns things like airplanes and has licenses to lucrative things like airport facilities and transoceanic routes between the U.S. and Asia, among other places.” Facebook is worth an estimated $200 billion, while United is valued at $34 billion.

Cloud as a Critical Tool for Development

When we talk about developers, the special knowledge may make it seem like a niche profession, which is not at all the case. As data expanded, the job market expanded. There are now 18.5 million developers worldwide. All of these people want the best tools.

One tool that developers have found is obvious for many projects is cloud hosting, which means that you can get whatever resources you want with a credit card. That simple accessibility makes these systems immediately more user-friendly and accelerates projects.

Flexibility is another key benefit that developers get from the cloud, explains Megan Swanson in Wired. “The cloud … means that developers can quickly increase their demands on the infrastructure if they need to test some code or run much larger data sets than originally expected,” she notes. “The cloud is elastic and can accommodate almost unlimited demand.”

Before the cloud era, the challenge of creating applications to work on different types of servers slowed down the process for developers. Huge amount of time were lost as they figured out hardware specifications and molded apps to fit the infrastructure. Today, it’s a snap to get everything underway.

Plus, cloud is familiar to recent college graduates who have been working with the cloud already. It makes the transition easier when these young programmers start their own companies or jump into development positions.

Developers also don’t have to worry about security nearly as much when they work with a long-established and respected cloud provider. Rather than being fundamentally responsible for security in-house, their system is already protected by an organization whose reputation relies on its ability to ward off intrusion.

The Role of Open Source

Another aspect of development that is often part of cloud projects is open source, comments Swanson. “Sharing the code for operating systems and basic utilities, and contributing to debugging and trouble-shooting, means that individual developers can spend more effort on applications,” she says.

Open source is effectively the antithesis of vendor lock-in, making it much more possible to migrate to other hosting services. It is essentially coder-friendly, making it unnecessary to learn a comprehensive new set of rules when transitioning to another job or when a workplace decides to use a different host.

Open source, used in conjunction with cloud, unleashes the potential of your developers. Since they aren’t getting ensnared in hardware and networking concerns, they can center their efforts on building incredible programs to benefit users.

True Distributed Cloud for the Best Results

Cloudy itself is an incredibly powerful technology, as established above. As Swanson puts it, “The era of cloud computing has enhanced the epoch of the developer,” adding that the technology “lets [programmers] focus on making applications that create new functionality, new business opportunities and even new industries.”

You want to make sure that the cloud you use is truly cutting-edge, though. Distributed storage is absolutely essential, but centralized storage – a dinosaur remnant of the mainframe era – is used by the vast majority of cloud providers.

Why is distributed storage preferable?

  1. No single point of failure – Even multiple node failures have no impact on performance.
  2. No bottlenecks – The design of distributed storage is simply superior.
  3. Much, much faster – Local disk I/O that puts centralized storage to shame.

By combining distributed storage with InfiniBand networking technology, Superb Internet offers cloud the way it should be – typically delivering 4 times better performance than AWS plans with similar specs. Get “100% true HA” cloud today.

By Kent Roberts

How to Leverage Salesforce and Vertical Response to Manage Email Subscribers

email world

  • Highlevel Overview
  • Understanding the Difficult Part
  • Conclusion

Highlevel Overview

It has been proven that of all the marketing activities a company can engage in, email campaigns bring the highest return on investment in the shortest amount of time. Salesforce allows a company to track leads with the goal of converting those leads to customers. Vertical Response Classic has the ability to integrate with a Salesforce Sales Campaign so that the success of an email campaign can easily be tracked and verified with real metrics.

In order to run a Salesforce Vertical Response Classic email campaign effectively the following setup tasks are recommended:

  • Create a custom field in the Lead object to hold your email campaign name
  • Route the leads generated from your sales campaign to their own Salesforce queue
  • Make the leads read only so they cannot be altered between the time they are created and the proposed email campaign

Understanding the Difficult Part

There are many ways to get a lead into Salesforce. An easy way to achieve that goal is to use the web to leads form generator in Salesforce and embed that on your website. A more difficult but powerful approach is to use python beatbox. Remember that if you are going to use the salesforce api to do the following:

  • Setup a salesforce sandbox and test there first!
  • Obtain a security token both in the sandbox and the production Salesforce areas

When creating the lead be sure to populate the custom field you created for your Email Campaign Field. It is then possible to create an assignment rule to automatically change the owner of the generated lead to a queue of your choice. One of the problems that can arise when using Salesforce, is the lack of a full time Salesforce administrator or fully trained sales people. It is imperative that the lead not be moved from your original queue or altered prior to your email campaign execution. There is a very simple way to prevent your valuable email campaign lead from being altered. All that is necessary is to add a validation rule that prevents an Email Campaign Lead from being altered. The actual validation rules is:

  PRIORVALUE( Email_Campaign_Name__c) == "your_campaign_name"

Here is a screenshot of how I did it:

Read only Salesforce lead validation rule
Read only Salesforce lead validation rule

Conclusion

Using Vertical Response Classic in Salesforce to create effective email campaigns that prove return on investment through solid metrics does not have to be hard. Simply adding a custom field to the Salesforce lead object to hold your email campaign name, creation of an email campaign queue, an automatic assignment rule to move the lead to the email campaign queue, and a simple validation rule are all that is necessary! Once you have set this up, just go into Vertical Response and build your email campaign list by searching for leads with the email campaign name in the custom field you created to hold it.

SSL Certificates, SHA-2 & Why Should I Upgrade?

SHA-2 Compression Family Tree
When you order an SSL certificate for your website, your certificate is signed with a cryptographic hash algorithm that ensures the validity of the signed SSL certificate. In the distant past, SSL certificates were signed with an MD5 hash, but as computational power increased, MD5 became insecure. SHA-1 signing then became the new industry standard. However, SHA-1 has also become technologically insecure.

Sunsetting SHA-1

US NIST has recommended that SHA-1 no longer be used, and as of late 2014, the SSL Certification Authority industry has moved quickly to discontinue use of the SHA-1 hashing mechanism for SSL certificate signing in favor of SHA-2.

In order to facilitate this transition, major browser vendors, including Mozilla, Google, and Microsoft have announced relatively fast deprecation policies for SHA-1 signed certificates.

  • Microsoft will stop trusting any SHA-1 signed certificates after January 1, 2017. [1]
  • As of Chrome 41 (Mar 2015), Google Chrome will show SHA-1 certificates that expire after January 1, 2017, as insecure. SHA-1 certificates that expire between Jan 1 – Dec. 31, 2016, will be shown as “secure with minor errors”. [2]
  • Firefox will display a warning for SHA-1 certs after January 1, 2016, and stop trusting them after January 1, 2017. [3]

Using SHA-2

SHA-2 is actually a crypto family that includes six different hash functions, including SHA-224, SHA-256, SHA-384, SHA-512, etc. For SSL certificates, SHA-256 is what is used, so for the purposes of this article, SHA2 and SHA256 will be used interchangeably.

Issuing

All the major Certificate Authorities are now issuing SHA-2 certificates, but not necessarily by default. Some will give you SHA-2 by default. Some of them will allow you to choose SHA-1 or SHA-2 at the time of certificate ordering. Others will give you a SHA-1 or SHA-2 certificate depending on how you sign the CSR (with either a SHA-1 or SHA-2 signature) that you submit to them.

When you order an SSL certificate, in order to ensure that the CA receives a SHA-256-signed CSR from you, which will usually be a “signal” for them to issue you a SHA-256 cert, you need to use the “-sha256” flag during CSR generation, instead of the “-sha1” flag, like so:

openssl req -new -out www.domain.com.csr -key www.domain.com.key -sha256

Re-issuing

If you have a current SHA-1 certificate that expires after January 1, 2017, you’re probably going to want to reissue it with a SHA-2 signature, due to the web browsers eventually showing it as insecure. If you have an existing cert that expires in 2016, you may also want to reissue that, because of the security warnings that browsers will display.

Installing and Using

SHA-2 certificates are installed the same way as any SSL certificate, using Apache directives like this:

SSLCertificateFile /path/to/www.domain.com.crt
SSLCertificateKeyfile /path/to/www.domain.com.key
SSLCertificateChainFile /path/to/intermediate_cert.crt

One thing to be aware of is that SHA-2 certificates are usually signed by separate SHA-2 intermediate certs which are different from the SHA-1 intermediate certs that you may have seen or used previously. Therefore, it’s very important to make sure you obtain and install the correct intermediate certificate. SHA-2 intermediate certs ensure that there is a SHA-2 secured trust chain all the way to the root certificate (root certificates are mostly SHA-1 at this point, and that is not a problem since SSL roots are trusted by their identity, and not by their signature; essentially, signatures are not used for anything on root certificates).

Once installed, you can (and should) test that the certificate chain has been constructed correctly by testing it here:
https://www.sslshopper.com/ssl-checker.html

Testing

You can test your SSL certificate installation to see if it has SHA-2 signatures all the way to the root with this tool:

https://shaaaaaaaaaaaaa.com/

You can check any individual cert or CSR that you have to see if it was generated with a SHA-2 signature by pasting it into this tool:

https://certlogik.com/decoder/

Look for the field called “Signature Algorithm”, which will tell you if it’s SHA-1 or SHA-256.

Server requirements

On the server, you need a TLS/SSL stack that supports SHA-2 hashing, both for CSR generation, and for certificate reading/serving. Usually the server software (Apache, etc.) relies entirely on the encryption stack/OS to handle the hashing functions, so there’s nothing specific in software that needs to be updated, just the OS and/or SSL tools.

  • OpenSSL 0.9.8 or later (although 0.9.8o (or 0.9.8e-18 on CentOS 5) may be required for full compatibility with all applications)

The stock OpenSSL included in CentOS 5.0 or later includes support for SHA-2.

  • Windows Server 2003 with SP2 and KB2868626
  • Windows Server 2008 or later

Client requirements

On the client side, you also need a compatible OS and web browser that can properly understand SHA-2-hashed certificates.

Operating Systems

  • Windows XP SP3 or later
  • Mac OS X 10.5 Leopard or later

Desktop Browsers

Basically, if you’re using any modern browser, you should be fine.

Highlights:

  • Internet Explorer 6 or later (with SP3 when using XP)
  • Firefox 1.5 or later
  • Chrome 26 or later
  • Safari 3.0 or later

Mobile Browsers

  • iOS 3.0 or later
  • Android 2.3 or later
  • Windows Phone 7 or later

Tools/Libraries

  • libcurl / cURL 7.19.6 or later
  • Java 1.4.2 or later
  • Python 2.6.6 or later

By Todd Bangerter

Image via Wikipedia

Content Amplification and Delivery Networks – Use the Force for Good, Not Evil

Everyone has gone content crazy, and those who manage, sell, and produce content are scrambling to keep pace with the business opportunity. As indicated by Kieran Flanagan of HubSpot, statistics for the search terms “content marketing” and “link building” paint a 20/20 picture: while link building is steadily descending, content marketing is shooting upward in 2014. Statistics show that 7 out of 10 B2B content marketers are creating more content today versus 12 months ago, while 6 out of 10 B2B marketers plan to increase their spending on content throughout the next year.

Caitlin Roberson of Skyword notes that many content marketers do not understand content strategy. In fact, a 2013 Forbes article notes that only 15% of content professionals are able to define the business value of their services in real numbers. Roberson argues that understanding and implementing amplification techniques can help to set your content apart from the competition. We will look at her ideas below.

Beyond the thoughts expressed by Roberson, content delivery networks (CDN) represent an amazing tool to amplify the effectiveness of your content (and obviously, like Roberson, I’m using a broader understanding of content amplification than connecting it with paid media). Just how powerful are CDN’s? Well, ask the Dark Side. A security study from Blue Coat Systems released in August (2014) found that most websites are “one-day wonders,” sprinting to the top of the charts like Mott the Hoople with “All the Young Dudes,” propelled by the power of web optimization apps and content delivery networks. As the title suggests, content amplification is the thunder hammer of Thor: use it for good, not evil.

Content Amplification Definition

As indicated above, content amplification is a buzzword, but different bloggers and thought leaders are using it in different ways. Some see it strictly in terms of connecting content marketing strategies with paid media, so that would be something like a Google +Post ad (and props to me for thinking of that example before realizing the slogan for that product is, “Amplify your content and create conversations across the web”).

Rather than looking at amplification in terms of one fairly specific application, Roberson sees it more broadly, agreeing with the following definitions:

  • The use of strategies that increase traffic rapidly and affordably (Convince & Convert).
  • Methods that create social traction and website traffic, giving you a better chance at conversion (Brandpoint).

In other words, from a broad perspective, we can think of content amplification in terms of search engine optimization, content delivery networks, whatever – anything that increases your reach.

Content Amplification Strategies

Here are four quick tips from Roberson, followed by a discussion of the Dark Side of amplification efforts.

  1. Search engine optimization is still a thing – Roberson typed into Google, “how to submit to,” and one of the suggestions that popped up, directly below “how to submit to your husband” (I’m not making that up, although I wish I were), was “how to submit to product hunt.” Unfamiliar with Product Hunt, she proceeded to download the app, a case in point that search analytics can help to amplify.
  2. Integration with sales – Roberson says to strive for “horizontal buy-in” of content from your salespeople. Get them involved. Get them to tell you stories. Profile them in the blog. Transcribe insightful interactions. Shoot out easily shareable emails with an @mention of any sales parties involved.
  3. Broaden your appeal – Your buyer personas may be too narrow. How do you get to other types of decision-makers? Consider working together with other marketing teams to access each other’s base. You might also want to start an additional site that blogs on a theme that appeals to your base but isn’t directly related.
  4. Get your halo effect on – Network throughout your company and externally. Create connections by finding subject matter experts (SMEs) in your ranks and elsewhere in the business world. Take individual customer experiences and turn them into educational content. Feature partners and experts.

Content Amplification – The Dark Side

Referencing the Blue Coat Systems study, Ellen Messmer of NetworkWorld described the Internet as “endless bubbles popping to the surface for only a day, then vanishing.” Sites that are here today and gone tomorrow present confusing potential security threats.

Security company Blue Coat looked at over 600 million hostnames over a period of three months. Amazingly, 71% of those sites were only active for 24 hours.

The report noted that the sites are effectively using content delivery networks to access traffic. CDN’s are fast and incredibly reliable, and that makes them popular with goodhearted and malicious parties alike. Unique subdomains are used to organize content for one particular request or session or user, after which it is dropped: “A by-product of these CDN architectures is the proliferation of One-Day Wonders.”

Blue Coat reported that of the 50 highest trafficked domains, one in five were fronts for malware. One of the .info sites was the home of a Trojan dialer, just a simple “surprise” site. It had over 1 million subdomains. Beyond content delivery networks, the other primary strategies used were riding on blogging sites such as Tumblr and running web optimization software.

Content Amplification – The Light Side

Don’t be a bad guy. Just create great content and spread it rapidly across the globe. The Superb Content Delivery Network (CDN) speeds up your site by distributing your content to 172 data centers in 43 nations. Chat with an expert now.

By Kent Roberts

Image Credit: Today.com

People Only Buy from Sites Secured by SSL Certificates

SSL Certificate

SSL encryption has always been essential for e-commerce sites and any sites that process sensitive personal information. Google’s recent announcement that SSL improves search ranking gives website owners one more reason to adopt it.

The focus on SSL (which enables the secure “HTTPS” protocol in browsers) is part of a larger campaign by Google to improve security across the Web. As Mashable reported in July, Google has also introduced a new program called Project Zero. Project Zero will be a new subdivision of the company, populated by hackers who will work full-time to enhance security throughout the Web. It is an attempt to reduce the extent to which companies and independent users are vulnerable to malicious attempts and software bugs.

HTTPS Everywhere (also called SSL Everywhere, or AOSSL for Always On SSL) has been a rallying cry from the SSL certificate community for years; however, for certificate authorities (CA’s) such as Symantec and DigiCert, blanketing the Internet with SSL is tied to a profit motive. That’s why Google’s announcement was such a game-changer. To be clear, SSL everywhere is not just about having standardized encryption (which itself is virtually hacker-proof) on more sites. It’s about having it, well, everywhere – on every page of a site, rather than just pages where people fill in passwords or payment data.

Project Zero and Google’s newfound commitment to HTTPS everywhere are part of a continuing response by the Internet infrastructural elite to the discovery of the Heartbleed bug earlier this year. Heartbleed is a major vulnerability in OpenSSL, a tool that had been trusted as a core protection for sensitive user data on major websites including Facebook, Netflix, and Google (yes, that’s right, Google… hmmm, is it possible this renewed focus on security is a form of penance?).

Heartbleed allowed any Internet user to retrieve a portion of the memory from servers on which OpenSSL was installed. Although there was confusion at first related to the cryptographic keys themselves, security and content delivery powerhouse Cloudflare demonstrated in April (through its Heartbleed Challenge) that the keys could be stolen as well, giving intruders unlimited access to ingoing and outgoing data.

SSL now improves SEO

As you can imagine, once Google announced its commitment to the AOSSL concept, two activities quickly began:

  1. Impromptu parties at all of the SSL CA’s and resellers;
  2. debate over whether it had been built into the algorithm as a ranking factor, or not.

Fast-forward from April to August 6, and the second activity ended (although the first one grew more boisterous): Google announced on its Webmaster Central blog that the company was going live with HTTPS as a factor in search engine rank. Since April, the tech giant had completed a series of tests to determine SSL encryption through its Web-crawling spider. The tests were successful, and given wider concern among industry professionals in 2014 for security, Google moved forward with inclusion of SSL.

Don’t worry if you do not yet have SSL on your website, though. Google mentioned that the factor is “lightweight” at the outset, impacting under 1 out of every 100 searches worldwide. Content remains a much stronger element than security at this point, so that website administrators have a reasonable opportunity to install SSL rather than being caught off-guard by the new policy.

Samantha Murphy Kelly of Mashable noted that preparation is, in many cases, less involved: SSL is currently installed on more than half of sites Internet-wide – 56%. Now all those sites need to do is distribute the HTTPS protocol throughout all pages, making it adherent to the SSL everywhere movement.

Sales Dominance & EV SSL

SSL has been a recognized standard to protect customers for many years. Numerous case studies have been completed by certificate authorities showing the value of SSL, usually with emphasis on the high-end extended validation (EV) certificates. The EV certificate, which marks most Internet browsers as green – for “go” – in the address bar, is a thorough domain and organization validation protocol. It was developed by the Certificate Authority & Browser Forum, to allow companies (after going through a more rigorous vetting process) to show off their credibility directly within the browser.

Various certificate authorities have published case studies of the extent to which extended validation increases conversions. For example, GeoTrust claims their EV SSL certificate improves sales 20%, while a VeriSign (now called Norton Secured – which, like GeoTrust, is a Symantec brand) EV case study revealed 30% higher conversions.

Google Best Practices

Following the announcement that Google was including SSL in its algorithm, Search Engine Land summarized the company’s best practices for SSL adoption:

  • Figure out what type of certificate is best for your site: single (which covers one domain or subdomain), wildcard (which covers all subdomains), or multi-domain (which covers numerous sites under one umbrella).
  • Choose the highest available encryption rate of 2048 bits.
  • Relative URLs should be used for any files within one HTTPS domain.
  • Protocol relative URLs should be used for any additional domains.
  • Switch your site to the secure protocol, with instructions by Google.
  • Make sure your site does not prevent crawling with robots.txt.
  • Make it possible for Google to index your pages, noting that the noindex robots tag makes a page invisible to the search engine.

Conclusion

Needless to say, security is not the only concern for building and maintaining online prominence. You need a web hosting solution that is affordable, while delivering content reliably and lightning-fast (also a ranking signal). Why choose Superb Internet? In business since 1996, we take confusion out of the cloud. Compare our hosting plans now.

By Kent Roberts

Image credit: Praxis Web Design