Archive for February, 2011

How to Make Sure People Don’t Use Your Web Site

Wednesday, February 23rd, 2011

By Nora McDougall-Collins

Let’s say that you want to learn something about a product you just bought; so you go to the company’s web site. That product could be a motorcycle part, a new computer, your credit card, etc.

Delivering product information on the web is a great tool for both the company and the client. It could mean less phone time for the company (save employee hours and $$$.) For the client it means not having to wait for business hours to get an answer, and not having to sit on hold, and not having to understand an unfamiliar accent, and not having to deal with untrained phone staff, and being able to go back and forth through the information, as needed.

But, unfortunately, it doesn’t work that way. I recently got my new NNFP phone (740-541-2857), which is from Alltel, and I needed to set up the voicemail. I hate waiting for phone prompts so I thought, “they probably have all the steps to set up voicemail on their web site!” Then I can just read and push buttons without waiting for the messages. I found out that their web site uses the typical barriers that keep people from using a web site. In my case, I went ahead and used the prompts, and I get to write this article about how they kept me out of their site!

Here is a screenshot of the Alltel web site:

They don’t really tell me on the front page what resources are available on their web site. I know who they are, but I don’t know “whatcha got.” I don’t have a log in. I don’t want to buy a Treo. I already have a phone in my hand; so, I don’t want to buy a new one. I’m not checking their models. I don’t need a prepaid plan. Since that about covers everything on their front page, they obviously don’t have the information I need on their web site. Well, actually, it’s entirely possible that they have spent a lot of $$$ making pages that explain their voicemail functions, but they have hidden them!

Here’s another one. SalesForce.com. This company has an online Contact Management Resource package. Sounds like a tool I would like to use! But I don’t know whether their software is easy to use or does what I want it to do. So, I look for a demo (the first thing you should do when looking for software.) But, like Alltel, they have put up a barrier to me, as a potential consumer. To get a demo, I have to fill out a form. Now, I understand that if I’m going to demo a car, they need to know who I am, in case I don’t bring it back! However, I’m not exactly going to run away with their online software. Not only do I get a demo, but I get a call, and I get an ongoing stream of spams from them. Oh, I guess it’s not spam, because they think that wanting to see the demo is the same as wanting an endless stream of emails.

Would you feel there was a barrier if your favorite clothes store made you fill out a form before they let you try on that nice fuzzy sweater? Well, I filled out their form, and I get the endless stream of emails, but their online demo was mostly a sales pitch, and not much of a demo! Like the Alltel site, SalesForce had the opportunity to make me think that their product was easily available and easy to use, but they pretty much made sure that I didn’t want to use their web site.

How do you avoid putting up barriers on your web site? First, be aware of the types of barriers that annoy you! Then have a few people (not your Mom) try specific tasks on your web site – like pretend they want to buy something! Ask them how many steps they had to take, and whether they found what they wanted!

Black Hat or White Hat?

Wednesday, February 23rd, 2011

Would you believe that even the Search Engine Optimization (SEO) industry has folks wearing black hats? These are the folks that will do anything they can to trick Google and other search engine into ranking their sites at the top. Instead of spending their time having a great site, they spend their time trying to get around the system with “Black Hat SEO.”

Here are some snippets of text from some of their sites:
“Are you prepared to use every cut-throat trick in the book to exploit the search engines and outrank your competitors?”
“… if you need to escape the White Hat SEO Whiners …”
“Black Hat SEO Techniques – Making Money Online by Exploiting the System”

So what is Black Hat SEO?
Others have done a great job of describing the tactics of Black Hat SEO. Here is an excerpt from an excellent article by George Ajazi:

“Keyword Stuffing – Literally the practice of repeating a keyword or words over and over again on a given web page. Google’s algorithms work very hard at trying to find pages that read like normal text, not like a broken record. And they are getting better at it all the time. If they suspect you are just trying to “stuff” the content of your site with keywords, there is a good chance they’ll penalize you for it.

Cloaking – Is a technique where a webmaster will have two versions of a given web page, one version that it shows the search engine spiders, and one version that it shows the regular web surfer. Highly frowned upon if the engines find out.

Invisible Text – (mentioned above) Filling a web page with text that is the same color as the background. I love this one.

Doorway Page – A highly optimized web page whose purpose is to direct traffic to other pages using either a redirect method or merely by being full of links that direct you to these other web pages.

Spam Page – Basically a doorway page that is full of ads that a webmaster makes money off of if someone clicks on them. Very annoying pages.

Interlinking – Setting up multiple websites about a given topic and having them all link to each other in order to increase their relevance and subsequently their rankings in the search engines.

Selling PageRank – If you have a high PR website, you sell links from your site to another for cash. Helping their site rank higher in Google and in turn, making your wallet fatter.

Buying Expired Domains – Buying expired websites that had some decent PageRank in order to try and keep the site’s inbound links.”

The rest of the article is also great reading.

The unfortunate situation is that I hear these strategies being promoted by folks that don’t know any better. What do you tell another baseball parent when they are all excited about these new strategies they have learned? Another local gent is very generous and enthusiastic in passing these ideas on to others. In fact, I heard about him from other technical people several years before he showed up in one of my classes. Unfortunately, he doesn’t know about the loss of respect it has earned him in the technical community. I wish he were as enthusiastic about just plain having great web sites!

So, if it sounds like a gimmick, reconsider!
If you wouldn’t like to use web sites that have to con you there, don’t do it to others.
Spend your time building a great business name and a great business site that people will come back to!

From a proud White Hat SEO Whiner!

Your Web Host: Friend or Foe?

Wednesday, February 23rd, 2011

By Nora McDougall-Collins

There’s no way to get around it – your website has to be hosted somewhere. Finding a web host is like finding a mechanic when your car breaks down in a strange town. There are plenty of them, but which ones are fantastic, which ones are semi-competent, which ones are incompetent and which ones are pure thieves?

Before we launch into a discussion about good and bad web hosts, I should probably explain what a web host is. Every website has to be hosted on a web server somewhere. A web server is basically a computer with software that knows how 1) to take calls asking for web page, 2) package a web page for delivery, and 3) send the package to the right computer. Oh, and by the way, the web server needs to be able to tell the difference between a genuine web page request and one that is asking the computer to attack something. Believe it or not, there are bad guys out there trying to get web servers to do all kinds of bad things.

When you order a web hosting package from a web host. you get a place to store your web files where they are available to the public (storage.) You also get a certain amount of work that the computer can do, such as deliver web pages (transfer.) These are the main services you need, but there are other services, such as email and database, available too.

Here are some of my experiences with web hosts.
The first high-tech company I worked for was a web host, besides providing design, programming and some other web services to a particular industry. Not a single employee, including myself, had any formal training in web development or programming. We learned by the seat of our pants.

A lot of web hosts today are just someone who figures it’s just a quick way to turn a buck.

In our case, we weren’t credentialed, but we had a great customer service ethic, and if something went wrong we worked double time to fix the problem. But, one time a new tech guy completely deleted a new client’s web site. The words “off-site backup” took on new meaning!

What kind of backup system does your web host have? if the server with your website on it goes down, what will they do?

My next web hosting experience was with a great company, based in Missouri, called Communitech. Their system was great, and their support was even better. But, they were so good, a company called Interland bought them out. It was downhill from there. I teach web development classes, and I put all my course materials on my web site. Three times in one year, I got to class to find out that my site was not functional. When I would call, they would fix it, but their main emphasis was to try to get me to buy a new hosting package. Finally, late one night I got one of the original tech support guys on the line. He said that Interland was cutting back on all their resources, human and computer. All they really wanted was the client base!

So, I moved my site to a local, Missoula, web hosting company, called Modwest. And, I told them that, if they sell to Interland, I’m moving my site.

Do you have a list of other great web hosting companies, in case yours goes bad?

Another company I worked for hosted one of their sites with Interland. The company has a weekly emailed newsletter with links to various articles on their web site. A large portion of their weekly traffic comes on the day the newsletter goes out. About 3 or 4 weeks a year, the web site goes down on the day that the newsletter goes out. And they can’t seem to figure it out themselves. We had to call then to let them know that the server was down. I found out that their web servers are set up so that one site is only on one server. If that server goes down, all the sites are dead. Modwest has their web sites on clusters of servers. If one goes down, the others in the cluster pick up the load. You would think that at the very least, if the Interland servers go down, someone would be alerted and fix it before we have to call!

Look into your web host’s “configuration” before you sign up!

I wish that this were the end of my “bad experience stories,” but it’s not. If you have your own stories, I’d like to hear them!

So, What Were You Trying To Say?

Wednesday, February 23rd, 2011

By Nora McDougall-Collins for the National Network of Forest Practitioners

FIRST!!! Before you do anything on your web site, stop and ask yourself what your message is! Then figure out who you want to deliver it to. If you have a web site, show it to someone who doesn’t know your organization and ask them to look at your site and tell you what you do, based on the information on your web site.

I’d like to thank Harry Groot, who has given me permission to use the Blue Ridge Woodland Coop web site as a case study in our efforts to help our forest practitioner organizations and businesses have successful web sites. First, notice that their site has a great visual design:

However, the question is, what is the message of this home page? Viewers will decide whether they like your site in less time than it takes to blink and eye*. If the home page doesn’t show them what they want, people aren’t likely to click to your inside pages. Do you click on sites that don’t have what you want on the home page?

The main message of the Blue Ridge Woodland Coop is that their members have wood products for sale. Then the underlying message is that they are a community effort, etc. The images currently on the home page are more like a site promoting real estate or travel in the area, where the natural beauty is what the visitor is buying. It all goes back to “What are you trying to say?”

SECOND!!! Figure out who cares about (or should care about) what you are trying to sell, and what is important to them? If your site is about selling flooring, what do those folks care about? Well, first they care about what the floor will look like. So, they want to see it – not the boards, the floor! Then, they care about how well it will wear when someone walks across it with their muddy boots (horrors) or drives Tonka trucks over it (the little darlings.) Finally, they want to brag about how much better their wood flooring is than all their friends floors because it comes from sustainably harvested trees, etc. “And, by the way, I can show you a picture of the guys who grew the trees, cut the trees and made the flooring right on this web site!” So, where can I get a floor like that???? Can’t let my golfing/gardening/business/etc. acquaintance have a better floor than I do!

YOUR WEB SITE HAS TO SAY ALL THAT IN A FEW PHOTOS AND TEXT ON YOUR HOME PAGE. After the photos hook them, the specific details follow on inside pages, but the front page has to hook them. Notice that they don’t really care about how wonderful your organization is until after they see what they want? Your inside pages should also reflect how wonderful each of your members is, as well. Make a personal connection, and folks will come back.

So, should they start the Blue Ridge Forest Cooperative site over? Absolutely not! They just need to make some adjustments. Somewhere the web developer didn’t get the message. When you are looking for a web developer, the people you interview should be spending as much time asking about what you do, and what your message is, as you do asking them questions. That person should tell you how they are going to get your message across, not just how beautiful your site will be.

What is the old saying,” Beauty is as beauty does.” It applies to websites too!

I look forward to seeing the website changes that Blue Ridge Forest Co-op will be making in-house, as I work with them by phone and webinar! They already have some high quality photos taken of their members and their products through the People and Land project. NNFP is proud to be working with great grassroots organizations!

*Article about Canadian Research on how long it takes someone to make a decision about a web site. “Gitte Lindgaard of Carleton University in Ottawa, Canada, and lead researcher of the paper expressed her surprise at the results.”

Finding a High Quality Web Developer: What you Need to Ask Them

Wednesday, February 23rd, 2011

By Nora McDougall-Collins for the National Network of Forest Practitioners

Once you have a preliminary plan for your website project, it is time to start looking for a developer who can take your project through the rest of the planning and production. Even people with technical backgrounds can hire the wrong developer; so, for those without web technical experience, the risks are even higher. However, you are more likely to find a good developer, if you take the time to do your homework.
Many businesses hire the most convenient person for the job. This person might be “the kid down the street” or the “great package” on a website. Without checking further, you may be buying yourself a nightmare. So, take a good look under the hood before buying.

The developer can make or break a project for many reasons, including:
1. Quality of communication between you and the developer.
2. Amount of time the developer has available for your project.
3. Hiring a developer with the right skill set for your project.
4. The developers work habits – what good does it do to get a great site, if it’s impossible to maintain later
5. Matching your style with the developer’s style

Finding Web Developers to Interview
1. Make a list of ten sites that you like. Find 5 sites in your industry and 5 sites that have features you need on your site, which aren’t in your industry. Record the addresses of those sites with a comment about why you chose that site.
2. Ask your business acquaintances for web developer recommendations. Ask them why they recommended that person or company. Ask them about costs and communications.
3. Ask your business acquaintances for web development horror stories. Find out specifically why it was a bad experience. Your situation may be entirely different, but the information will help you understand what can go wrong.
4. Based on these recommendations (and other services you may find out about,) call at least 5 developers and ask about their availability. It doesn’t matter how good they are, if they can’t fit you in, they can’t fit you in.
5. Set up meetings with the developers to discuss your project. You may need to pay for their time because, if they are any good, they will be giving you some expert advice as part of the discussion. Everything you learn now, will make the project cheaper later.
6. If a developer tells you that more planning needs to be done, you are probably speaking to a good developer.

Check off list for your Conversations
Here are some of the things that should be included in your conversations: These aren’t black and white questions. They are designed to help you get a well-rounded picture of each potential developer.

There probably isn’t a developer out there who will be perfect for you in each item. For example, in projects that require high quality graphics, I recommend that prospective clients hire a graphic designer for that part of a website, because I don’t have graphic design training and abilities.
1. Explain your project to the potential developer. As part of the process, show the developer the sites you chose from the previous section and your thoughts.
2. Ask the developer how he would go about building such a site with that information.
3. Did the developer give you plain English explanations to support the suggestions?
4. Did the developer spend a lot of time asking you about your needs, listening carefully and making suggestions?
5. Make a list of the skills and experience the developer has, including what software packages she would use to develop your site.
6. Is there a match between the skills of the developer and your website needs?
7. Find out whether your developer is available for a long term business relationship.
8. Will it be easy to find someone else who knows those software packages, should that developer become unavailable later on (you will have to verify this by asking others?)
9. What pricing system does the developer use?
10. Do the sites the developer has previously created match your style and needs?
11. What types of responses did you receive from the developer’s references?

If you are new to these topics, be extra careful. Each of these topics is a potential breaking point for your project. Look for a developer who will take the time to help you understand the topic. Each of these questions will be discussed further in future articles.

Managing Photo Files for Your Gallery

Friday, February 4th, 2011

By Christy McDougall for the National Network of Forest Practitioners

You are an artisan, and your wood products are beautiful and well made. Naturally you want to show them off on your website! You dream about having such a wonderful gallery that people will be contacting you daily, eager to get their hands on what they see there.

So, because you are intrepid, you find the perfect online gallery yourself, and you click the little “Browse…” button that lets you upload your pictures. And what you see makes your brain spin. You see a long list of the photographs you took last month, all in weird little photograph icons, all labeled “img085,” “img243,” “img047.” What picture is what? Where’s that magnificent picture you took of your son at work on that oak log?

A look at bad organization for images on your computer

Or maybe you’re busy, so you hire a web developer to put your gallery together for you. You put all your photographs on a CD and send it to her, and the next day she emails you with a dozen questions. “Can you tell me about your pictures? What are these cabinets made out of? If you want them divided up into albums, can you tell me which go in which albums? I don’t know what fir looks like, so can you tell me which ones are fir and which ones are Ponderosa pine?” So now you have to write a very long email explaining all the pictures in detail rather than doing what you really want to do, like finishing that cabinet your client is antsy about.

The answer to both these problems is quite simple, and it involves managing and organizing your product photos from the very beginning. As soon as you sit down to put your pictures on your computer from your camera, follow these steps, and it will make your website work or your developer’s website work much more simple:

1) Look through your pictures and name them. Give them very specific names that tell exactly what they’re about, such as, FSCCertifiedKitchenFirCabinet. You’ll notice that this name has no spaces and the first letters of all its words are capitalized. This is called Camel Case and is the best way to name the images that you’re going to put online. Having very clear names for your pictures helps both you and your web developer understand what the picture is about, causing less confusion on her part.

2.) Create a ProductImages folder and copy all your pictures into it. By copying them rather than cutting and pasting, you’re saving yourself a backup, in case anything happens to any of the pictures. The name of the folder you create should also be in Camel Case, so that it will work with the browser if it ever goes online.

3.) Create subfolders and give them appropriate, Camel-Cased names. If you have a lot of pictures of tables you have created, group all your table pictures in a Table folder in the ProductImages folder. If you want to group your cherry tables apart from your walnut tables, create one folder called CherryTables and one called WalnutTables and separate the pictures accordingly. By doing this, you will nearly always know where to find any particular photo.

By organizing and renaming from the beginning, you will save yourself a lot of time and your web developer a lot of confusion. When you go to upload to your gallery, you’ll see instantly what each photo is and know which album it should go in. Or when you send them to your web developer, she’ll already know how you want them grouped and what their names should be, and her long email full of questions will be greatly reduced. It can be a rather annoying task if you’re not used to it, but in the long run, this will save you