Website Security: Why https:// Isn’t Enough

[Hunter]

So you’ve decided that you want a part of your site to be secure. Good for you. But how do you ensure that it stays secure?

Just in case you aren’t aware of it. Any time you see http:// in an URL, it means you are looking at a non-secure web page. By contrast, https:// denotes that the web page is secure. Typically, you’ll see the https:// in the URL on pay pages, whenever you are purchasing something and you need to give out credit card information or other personal data. If you don’t see the https:// on a page that asks for your personal or private information then run away. Don’t give up your information because it isn’t secure.

But there are other reasons for want to ensure certain web pages are secure. Maybe you have a membership site and you want to restrict access to the membership benefits of your site to your visitors who are not members. You may not necessarily need the https:// distinction in those pages, but you definitely should have a password system to give access to those site visitors who are members. But there are some other things you should do as well.

First, the danger of web security. You might make the mistake, if you are new to this area of webmastering, of leaving an unsecure link leading from the non-secure part of your site to the secure part of your site. If that happens then there is a hole in your security and anyone will be able to get in. To prevent that from happening you can add “nofollow” and “noindex” tags to your robots.txt file or meta tag. By keeping the search engine spiders from crawling your links and indexing your secure pages, you ensure that security holes are not leaked and that future searchers do not find your secure web pages in the SERPs. It’s a small measure you can take to ensure that the secure parts of your website remain secure.

Nick