An SSL, or Secure Socket Layer, is technology that has been developed that allows web browsers and web servers to communicate over a secured connection.

The system uses cryptography that uses two keys to encrypt data  a public key known to everyone and a private or secret key known only to the recipient of the message. It’s a way to encrypt data, like credit cards numbers (as well other personally identifiable information), which prevents the "bad guys" from stealing your information for malicious intent.

The recently introduced SSL v3 improved upon SSL v2 by adding SHA-1 based ciphers, and support for certificate authentication. SSL v2 was known to be flawed in a variety of ways. Identical cryptographic keys are used for message authentication and encryption. The older version did not have any protection for the handshake, meaning a Man-in-the-middle downgrade attack could go undetected.

SSL has recently been succeeded by Transport Layer Security (TLS), which is based on SSL and is included as part of both the Microsoft and Netscape browsers and most Web server products. SSL uses the public-and-private key encryption system from RSA, which also includes the use of a digital certificate.

SSL-enabled client software can use standard techniques of public-key cryptography to check that a server's certificate and public ID are valid and have been issued by a certificate authority (CA) listed in the client's list of trusted CAs. Client authentication allows a server to confirm a user's identity. It’s a way to assure a client that they are dealing with the real server they intended to connect to. It can prevent any unauthorized clients from connecting to the server, preventing anyone from meddling with data going to or coming from the server.

From the very beginning SSL was designed to provide security between client and server, and to avoid any kind of 3-way man-in-the-middle attack.

Conceptually it’s quite simple: it negotiates the cryptography algorithms and keys between two sides of a communication, and establishes an encrypted tunnel through which other protocols (like HTTP) can be transported. It can also be easily passed through firewalls and proxies, as well as through NAT (Network Address Translation) without issues.

Last February, I received a call from a man in Wisconsin asking about my writing services. He was particularly interested in having me rewrite the copy on his Web site. I was very surprised and wondering how in the heck he got my name. Then he mentioned something about my being my Internet hosting service's "customer of the month." I was very pleasantly surprised. After I spoke with him, I logged onto my email and there was an e-newsletter from my host server. And, yes, I was the "customer of the month," and my Web site was the featured site for the month.

Of course, I quickly hastened to my site and checked the traffic. I was up to over 300 visits to my home page for the morning, and the day was to end with 796 visits! I don't believe I'll ever see numbers like that again. I also received several other calls from people interested in my services.

It wasn't a complete surprise that my site was featured. Last year, I had filled out a "success story" response form on the company's site. I was later interviewed and told that I would be used as a case study. But the case study never materialized so I had forgotten about it. Thus I was very pleased when my site landed in their e-newsletter as the featured site.

My host is one of many companies where you can register domain names and get your business online. They will build a site for you; or, if you are cheap like me, you can build your own.

When I began my business a few years ago, I waited a whole year for my brother who owns an ad agency in L.A. to professionally build my Web site for free. Now he's kind of successful, and he didn't get that way by doing a lot of free work for relatives. At the time, my server was doing a lot of radio advertising claiming you could "build your Web site in 20 minutes." One day after nagging my brother once more, he became exasperated and said, "Why don't you just build your own."

So I did. I called the company and they provided templates and lots of help. I chose an animated template with a layout ideal for showcasing a portfolio. There was a bit of a learning curve. I had to play around and call for help a few times. It took me longer than 20 minutes; yet, technically, the commercial was accurate: you could really get a home page up with your contact info in 20 minutes. I believe I spent about 20 hours to get my Web site to the point where I was willing to "publish" it.

One of the advantages I have found about building your own Web site is that you don't have to rely on an outside Web Master to update it. Sometimes those fellows are swamped and it can take awhile. If I want to put a new project in my online portfolio, I can do it in a few minutes. Or if I want to add something new to my list of services, I can quickly type it in and it's done.

I found a huge difference in how I was perceived in the business community once I had a Web presence. Suddenly, I was taken seriously. These days when someone asks, "What's your Web address?" you should have it ready. And it should never be "under construction." Visitors find that very irritating. It's really not that hard to get a presentable Web site up.

As I mentioned earlier, there are numerous places where you can go to build a Web site. Just Google "do it yourself Web site" and you will get numerous options.

It is very inexpensive. My site costs me less than $100 a year for 20 pages. Some places are even cheaper. Compared to the thousands of dollars one can pay a Web designer, it's a sweet deal.

That's not to say that I don't believe in professionally designed Web sites. I still want one with more bells and whistles. I'm just waiting on my brother.

(Since initially writing this piece, my server has made the process even better. It's more professional, a lot more pages available ... and more bells and whistles.)

Not every site needs a site map, they can certainly be a good idea. Site maps provide a dual purpose: They provide search engine spiders easy access to all of your site pages and they provide site visitors easy access to all of your site pages. The difference is that search engines and visitors access your site map differently and therefore there are different methods that need to be applied to creating site map(s) that are friendly for both engines and search spiders.

Small sites typically don't need a site map so long as all pages are linked in the main navigation. Once you get into main and sub-navigation menu's then site maps are helpful in allowing search engines and visitors to quickly find anything they are looking for within just a couple of clicks. A single site map can be used for both purposes or multiple site maps can be created. Here we'll address creating site maps for spiders and humans separately.

Site Map For Spiders

.xml file

An .xml document should be added to your site's root directory containing links to all site pages. This .xml file should then be referenced should be compiled and placed into a proper .xml document which should be uploaded into the root directory.

Robots.txt file

With your .xml site map file in place you must then make it accessible to search spiders. Reference the site map in your robots.txt file by adding a line for sitemap: URL (example: sitemap: http://www.polepositionmarketing.com/sitemap.xml)

Keep current

Be sure that your .xml file is updated and uploaded frequently, or at least as often as pages are added or removed from your site. Large sites should implement an automated site map update monthly or even weekly or daily.

Site Map For Visitors

Navigation links

A site map designed for human visitors is just like any other website page. Link to the site map page should be included in the primary navigation or the site's global footer. Visitors should be able to find this link without too much searching.

Additional page links

Site map should also be linked from various pages within the site such as Help pages and your custom 404-redirect page. This helps point visitors to the site map as a quick and easy means to find what they need.

Overview

It's helpful to provide a short overview paragraph at the top of your site map page. This can be a nice introduction should someone land on this page directly from a search engine or elsewhere.

Heading and layout

The layout of the site map should present a clear visual hierarchal structure or your website. Both headings and sub-headings should be used above properly grouped links.

Text links & descriptions

Site map should primarily use textual links and page should not be cluttered with images or other distractions. It is also a good idea to provide an additional short description (provided there is room) for each link that allows the visitor to better understand where each link will take them.

Keep current

Be sure that your site map is updated and uploaded frequently, or at least as often as pages are added or removed from your site.

As I said above, not every site needs a site map. But those that do should be sure that the site map(s) they create are actually benefiting them. And the best way to do that is to make sure your site maps provide maximum usability for visitors and search engine spiders.