The Internet Marketing Driver: Glenn Gabe's goal is to help marketers build powerful and measurable web marketing strategies.

Wednesday, December 17, 2008

The Connection Between SEO and Accessibility Standards, Why Keyword Prominence is Important For More Than Just Search Engine Optimization

SEO and Accessibility, Using Fire Vox as a Screen ReaderIf you’ve ever had a hard time browsing a website, then I’m here to tell you that everything is relative. Let me explain. Maybe you couldn’t find your way on a website, had a hard time buying something online, or couldn’t find a solid search result. Well, if you were visually impaired, you would have a whole new set of obstacles to deal with, right? Accessibility is currently a big problem on the web. Ask someone who uses a screen reader how browsing their favorite e-commerce website is and I’m sure you’ll get an earful!

Unfortunately, many people developing and designing websites don’t even think about accessibility during the planning process. I’ll admit it, I didn’t think about it as much as I should have when I was developing websites and web applications. It wasn’t until I started developing digital marketing strategies for clients that accessibility became a bigger (and more important) focus. In addition, I heavily focus on SEO, and I began to notice how much of an overlap there was with accessibility standards. For example, if make sure that your site is accessible, you’re knocking out a lot of SEO best practices while you’re at (such as creating descriptive title tags, headings, using text links, mapping out a robust text navigation, using alt text, etc.)

A Quick Side Note: Learn from Target
If you don’t think accessibility is important, just ask Target. They were sued by the National Federation of the Blind (NFB) in 2006 and settled for $6 Million in 2008. Yes, $6 Million… You can read more about the lawsuit here, but needless to say, you don’t want that happening to your company, and especially if you’re in control of internet marketing.

SEO Overlapping Accessibility, Enter Keyword Prominence
In SEO, keyword prominence is extremely important. The definition of keyword prominence is placing the right keywords and text in the most important html elements (and areas) on the page. For accessibility purposes, that’s extremely important too! For example, if I created a webpage about a specific topic, I would want to make sure I used a descriptive title tag, meta description, heading tags to break up the content, a descriptive text navigation, and alt text for any images used on the page.

So, mapping out descriptive html elements is great for SEO, but it’s outstanding for accessibility too. You’ll find out why this is great for accessibility soon…

My Accessibility Experiment:
I decided to research what a visually impaired person would experience while browsing the web. I wanted to see how different types of websites held up while using a screen reader (or a screen reader simulator). I also wanted to see the connection between SEO best practices and accessibility. For example, I visited blogs, search engines, ecommerce websites, flash sites, websites using AJAX, etc. and tried to accomplish specific tasks. My guess was that webpages with strong use of keyword prominence would be easier to navigate and read.

I COULD NOT BELIEVE WHAT I EXPERIENCED!
After going through several websites, all I can say is that my findings were jaw-dropping. I was shocked to see how inaccessible most websites were. And just to clarify, it’s not because they were horrible websites run by mean people that don’t care about accessibility. It’s just that accessibility was overlooked during the planning and development process.

Meet Fire Vox, a Screen Reader Simulator
Fire Vox is a text to speech addon for Firefox and it basically simulates a screen reader. It’s an excellent addon to install and enables you to check how visually impaired visitors experience your website. You can learn more about Fire Vox and download the addon here. It’s worth noting that Fire Vox isn’t exactly the same as going through a website using JAWS® or Window-Eyes, which are popular screen readers. Unfortunately, they are relatively expensive and don’t have elaborate trials… I used the free trial for JAWS® for certain websites, but you are limited to 40 minutes per session (and then need to reboot). I would have loved to have used them more for this experiment, though. So, my simple disclaimer is that my experience with Fire Vox may be slightly different from using JAWS® or Window-Eyes. That said, it was close enough for my purposes. I visited several types of websites and tried to accomplish a task on each site. I’ve detailed each visit below along with my commentary. Let’s get started.

The Fire Vox Tutorial Webpage:
I started with the Fire Vox tutorial webpage, since I knew it would go well! And it did. When using Fire Vox, you can click Control and Shift L to bring up a list of all elements on the page (headings links, images, forms, etc.) Then you can select them as Fire Vox reads them to you using a simulated voice. Since the page used a descriptive title tag, descriptive headings, and descriptive links, I found it easy to find what I was looking for. This is a good example of why adding descriptive title tags, headings, and links is important! Yes, SEO and accessibility overlapping… It was a great example of a page that works accessibility-wise. See screenshot below.

Viewing all links on a webpage using Fire Vox:
Displaying all elements on the page via Fire Vox.

Blogs
I checked out several top blogs (that obviously use full css layouts), and my experience overall was good. This shouldn’t be a shock, since blogs are text heavy, they frequently use headings to break up the page, have text links to each post, etc. I was able to navigate to various post pages, read the entire post and find my way back to the homepage. OK, two pretty good experiences. Let’s take a step further…

Google Search
This went relatively well, but I found sponsored search results mixed with organic results while using Fire Vox. For example, when I accessed all the headings and links on the page via Fire Vox, it was hard to decipher which ones were paid search ads and which ones were organic listings. I ended up following a paid search listing to the Apple Store when I was trying to find the specs for an ipod nano. I was able to at least find the links in each search result (and they were descriptive) and then I could link to each destination site. Finding the main Google search box was extremely easy by browsing the page’s form elements in Fire Vox. Then simply hitting Enter triggered the search. Other than the sponsored listing issue, my experience on Google was pretty good.

Finding the Google Search Box using Fire Vox:
Finding the Google Search Box using Fire Vox.
Yahoo Search

Searching on Yahoo went very well. Unlike Google, sponsored listings did not have headings associated with them, so if I accessed the page’s headings in Fire Vox, I was guaranteed organic results. The sponsored links were mixed with organic results, but at least I could check the headings to find only organic listings. My experience was pretty smooth and I conducted a number of searches. Also like Google, finding the search box was easy (via browsing form elements in Fire Vox).

And the experiment goes down hill…

Full Flash Sites
I heard the proverbial, “crickets chirping”. Wow, this didn’t go very well. I knew my experience wouldn’t be great on full flash sites, but this was ridiculous! I’ve written before about SEO and Flash, but this takes it to a whole new level. The pages loaded and the title tags were ok (thank goodness there were at least title tags!) Then crickets chirped. Nothing. I opened up the elements on the page (Control Shift L in Fire Vox), including headings, links, form elements, images, etc. I all I heard was “There are no such elements on the page.”

Side Note: Using SWFObject to provide alternative content will provide crawlable html for the search engines, but Fire Vox would not pick it up. During my tests, JAWS® did not pick up that content either. Just keep this in mind as you use SWFObject with your flash projects.

I could write an entire post about my Fire Vox experience with flash, but I’ll move on for now. It’s just another reason you should only use flash where its power is needed. Hello hybrid website! Read the next section below.

Fire Vox showing no links for a full flash website:
Finding no page elements on a full flash site using Fire Vox.

Hybrid Site (a mix of flash and html content)
If you are going to use flash, a hybrid website is the way to go (for seo, accessibility, and usability.) After loading a hybrid website, l easily found the text navigation below the flash movie in the header, there were headings on the page, and some additional descriptive text links. My experience wasn’t as strong as being on a blog, but I was able to navigate around the site. I also was able to find the html sitemap, which provided headings and links to each page on the site (this was a 25 page website using a mixture of flash and html). But keep in mind that the content contained within each flash movie was not accessible (at least via Fire Vox). Compare this experience to a full flash site and you’ll see why a recommend hybrid websites.

Website With Heavy Use of AJAX
The first website I tested used AJAX extensively to provide content. This was almost as bad as the full flash site I mentioned earlier. Fire Vox read almost nothing…since the data was loaded via AJAX from the start. Then, content that was loaded on-demand wasn’t picked up by Fire Vox either! Now, this might have been due to the way the site was coded, but there were no headings, images, or links accessible. They also used a flash navigation! Yes, flash navigation and content loaded via AJAX. Holy smokes, the SEO in me almost melted down! ;-) Checking other sites that use AJAX yielded varying results. Some sites that used AJAX sparingly were ok. I was able to at least read the initial data on the page and then maneuver to the loaded content to catch some of it. It wasn’t a great experience, but better than then first example listed above. Also, the sites that used headings properly made it much easier for me to find my way. For example, if there was a heading for product information and that div loaded content via AJAX, I could at least maneuver to the content and read what was loaded. So, similar to flash, I recommend using AJAX only when needed. BTW, that’s the same recommendation I make for SEO.

Note, there are ways to ensure your AJAX is crawlable for SEO and I'll be doing more testing to see if that also impacts accessibility. Look for future posts on this topic.

e-Commerce Websites
I checked out several top e-commerce websites and found myself running in circles most of the time. My favorite example was finding an image linking to men’s clothing that actually took me to maternity clothing! I tried this several times and found the same result. Yes, this was ridiculous, to say the least... Other e-commerce sites were ok, enabling me to find some of the items I was looking for, but the end result was typically the same. One problem that kept rearing its ugly head involved the product detail page functionality. As retailers include robust functionality for selecting color, size, etc. in your shopping cart, the functionality unfortunately doesn’t work so well accessibility-wise. I literally could not select certain attributes for the items I was buying. I sat in a shopping cart for 10 minutes trying to select the length for my pants and it just wouldn’t let me. I finally gave up and ended up with a 38 length (which for me would be like a 3 year old putting on his dad’s pants!) Thanks, now I get to step on my pants all day as I remember tinkering with a form on your website! How’s that for branding? :)

News Websites
News websites that utilize full css layouts made it relatively easy to find what I needed. The only problem was the sheer amount of links on the page! That said, compared to other experiences listed in my post, I’ll take it! CNN, for example, was easy to navigate, easy to identify articles you wanted to read, etc. Once in an article, I could easily read the content and then move on to something else. However, other news sites weren’t as clean. I found myself scrolling through tons of links, some of which took me to weird places. Then I couldn’t find my way back. It wasn’t fun… Another thing that bothered me once I found an article was the placement of social bookmarking links. Depending on where these elements were located, it got really frustrating to get through them. I sometimes had to scroll through each one in Fire Vox before getting to the actual text of the article!

So What Should You Do About Accessibility?
I can picture those of you who are web designers and web developers right now. You are either scared to death, in denial, or you want to reach through the screen and strangle me. I understand, so I’m here to help. The first thing you should do is to download Fire Vox and test your site. Identify the problematic areas of your site from an accessibility standpoint and create a remediation plan. And while you’re at it, you can definitely make some changes for SEO too. That’s the great part about developing a site using accessibility standards, you can also knock out some SEO best practices while you’re at it (as mentioned earlier in the post). I highly recommend testing at intervals as you develop to ensure someone who is visually impaired can navigate your website. The interesting side effect is that you might make it easier for everyone to get through your site (including Googlebot!)

Sure Glenn, But What About Creative Backlash?
I know…your designers and developers might be gathering outside your office holding torches and pitchforks wanting to oust you from web marketing leadership. :) Here’s an idea. Challenge them. Hand them blindfolds and have them go through your website using Fire Vox. Give them specific tasks like I used for my experiment. If they don’t quickly understand the problems with your site accessibility-wise, then you either have the most accessible website in the world or you have designers and developers in denial. Unfortunately, this is just the way the web is right now.

Summary and Some Accessibility Links:
Quickly summarizing my blog post, my goal was to reveal a few core things about accessibility.

I wanted to:

1. Introduce the challenges with accessibility on the web today.
2. Explain what screen readers were and focus on a free Firefox addon called Fire Vox.
3. Make the connection between accessibility and SEO.
4. Provide you a quick look at how various types of websites held up while using Fire Vox and provide some recommendations for making changes.

OK, you’re only a 30 second download from trying Fire Vox and testing it out on your own website. So hold onto your hats, you’re about to be shocked (and probably not in a good way!) At least you’ll be able to find your way to the Firefox addon. I can’t say as much for your travels after you start using it... :)

GG

Related Links:
Section 508, The Road to Accessibility

Americans With Disabilities Act

JAWS® Screen Reader

Window-Eyes Screen Reader

Labels: , , ,

Thursday, October 09, 2008

6 Questions You Should Ask During a Website Redesign That Can Save Your Search Engine Rankings

Questions to ask during your next website redesign or update.If you are currently involved in or are planning a website redesign, then I’m sure the title of my post caught your attention. I’m not one to strike fear into people about SEO, but in my experience, website redesigns (or even website updates) have a knack for hurting Natural Search rankings. It actually makes a lot of sense if you think about it. During website redesigns, many companies try to make noticeable and impactful changes. You might add more interactivity and rich media, you might use the latest coding techniques to enhance the user experience, you might remove older webpages that you don’t believe need to be on the site anymore, you might change your URL structure, so on and so forth. But, and this a significant but, if you don’t look at your redesign through the lens of SEO, then you have a distinct possibility of hurting your search rankings. Actually, you can crush your rankings if you aren’t careful.

So, I decided to write this post to help you stand out as the person that saves the day. The person that flies in with SEO on your chest, swoops down and identifies SEO issues with your redesign and then corrects a potential disaster in the making.
--BTW, these are actual SEO scenarios I have come across. Also, there are many more issues that can pop up, but I decided to focus on these 6 for the post. And don’t laugh when you read each item, this might be happening as part of your next redesign. :-)

Without further ado, here are 6 questions you can ask during your website redesign that can save your search engine rankings:

1. Are we using Flash in the right ways and only when we need its unique power?
If you know me at all, then you know I’m a big advocate of Flash (having developed with it for over 10 years). But, replacing HTML content with full Flash pages or a significant amount of Flash can really cause problems SEO-wise. Run a cache command on a full flash webpage and you’ll see the problem quickly. That is unless you want to rank for “big blank white space”! ;-) If you do add more flash content to your site, then definitely utilize SWFObject 2.0 to provide search engine friendly alternative HTML content. I’ve written an in depth post about how to use SWFObject 2.0 here. And for those of you that are saying, “We’ll be ok since the engines are now crawling flash...”, please read my other post about Google crawling flash. There are several variables that can impact how Google and Yahoo crawl your swfs (the two engines working with Adobe now). My tests and recommendations were backed up this week at SMX during the Flash and SEO session with Adobe, Google, Yahoo, and Live Search. What’s my rule of thumb with Flash? Use it where you need the unique power of Flash. Do not, I repeat, do not use Flash for your entire site or for entire pages of content. Use it for webpage elements only.

2. Did we analyze the Search Equity of webpages marked for removal?
If you will be removing content from your site, make sure you determine the Search Equity of your pages. Your current rankings are heavily based on the quality and relevance of your inbound links. You’ve worked hard to build those links, so why would you throw them away?? This happens all too often when you don’t take into account which pages are important from a Natural Search standpoint.

Campaign landing pages are a great example of this. Let’s say you launch a new product and use a wide range of marketing channels to promote the new product and landing page. When the campaign ends, you decide the page isn’t needed anymore, so you just delete it. But hold on… if you had taken a look at the Search Equity of the page, you would have realized it built more than 5000 links for you, mostly from industry-relevant blogs and websites! It earned a Pagerank 5 and you just threw away all of those links by deleting the page! I hate when I see this happen. Do your homework before deleting pages.

So what should you do? You should either keep the page as-is or 301 redirect the page to a corresponding page on your site. That might be the product category page or a similar product page. 301 redirects are the proper way to pass link power from one URL to another. It’s a permanent redirect and tells the engines that Page A has moved permanently to a new location (Page B). Tip: Do not use 302 redirects when you remove a page. 302's are temporary redirects and are not search engine friendly. I can write an entire post about redirects, but just remember that 301’s are good and 302’s are bad.

3. Are we changing our URL structure during the redesign? If we are, did we make sure the engines know where the old pages will reside on the new website?
Similar to the bullet above, be careful if you decide to change your URL structure. If you change a URL from abcd.asp to efgh.asp, the engines will look at the page as NEW, even though the same content has been around for a long time (and has built up links and search power). Basically, the new page won’t automatically inherit the search power of the original page. Now imagine the impact if you change thousands of URL’s, tens of thousands of URL’s or even more?

For example, let’s say you decide to include target keywords in your URL’s, such as a product name and category. The old URL’s that have built up a nice amount of Search Equity will all be changed to your new taxonomy during the redesign. That’s great, but again, all of that search power will unfortunately be lost unless you tell the engines where the new URL’s are. Based on what I mentioned above, you can probably guess that it’s Mr. 301 redirect to the rescue again. You can redirect your old URL’s to your new ones and safely pass their link power. I’ve seen this overlooked plenty of times, and again, the results can be devastating.

4. Are we using Vanity URL’s or custom domains for our campaign microsites?
Note, this doesn't fall under something that will crush your current rankings, but it sure can impact how your site builds more power based on your hard work.

Let's say you have a new marketing campaign going live soon and someone on your team wants to register a bunch of new domain names for the microsite. You know, something like www.TheBestDarnBagelOnThePlanet.com or something catchy like that… Here’s the problem. It will be a brand new domain that needs to build its own search power versus inheriting the trust from your core domain, which is why I’m a bigger fan of using subdirectories, such as yourdomain.com/campaigntitle. Then your campaign will leverage your trusted domain, rank faster, and help build links for your trusted domain. It’s a win-win.

5. Are we replacing keyword-rich text content with images or Flash in order to achieve an aesthetic advantage? AKA, we want things to look pretty…
Your design team went nuts with the redesign, the new site looks incredible, and it uses all sorts of images and flash content in place of text content. You know, because the standard browser fonts aren’t sexy enough. I get that, I really do... but the SEO impact can be serious. For example, taking keyword rich text content on each page and throwing it into images to get a desired look. Taking your text navigation and placing it in Flash or in images. Again, this happens all too often. Text links are still the best way to get the bots to all of your content. And, using descriptive anchor text, you can tell the engines what they will find at the other end of the link. For example, using a text link with the anchor text Adidas Running Sneakers is much more powerful than using an image that holds the text Adidas Running Sneakers. Even if you use alt text with that image, it’s a much better idea to use descriptive text links. And, if you use Flash, then you’ll run into even more problems, which is why you should use SWFObject to provide an HTML version of your navigation. And for those of you who are saying, “I’ll just provide an xml sitemap to the engines and I’ll be fine”, keep in mind that the optimal way to get the engines to your pages is via a traditional crawl (as noted by a Google engineer at SMX this week). :) XML Sitemaps are a great supplement and help with more than just content discovery, but they don’t replace text links and navigation as the best way to get the bots to your website pages.

6. Did we do such as a good job at coding that we essentially removed key pages from our website? i.e. Where one page now handles the equivalent of 10 pages. The URL doesn’t change, but the content does big time!
Your developers did a great job of streamlining your code. They did such as good job, that 10 pages of content can now be handled dynamically by just one page. That one page posts back to itself and dynamically provides the content of 10 pages from your old site. Code-wise this might be outstanding, SEO-wise, it’s a nightmare. Beyond removing 10 pages from your site that might have built up Search Equity, you cannot optimize a page for each of the 10 items that will be presented on the fly. You are going to have a heck of a time getting those products to rank if they cannot be crawled! In addition, you cannot optimize the typical HTML elements like you normally would. For example, the title tag, h1, h2, body copy, inline links, etc. since the information will be loaded dynamically. Coming from a development background, I totally understand why you would want to code this way. However, from an SEO-standpoint, it can cause all sorts of issues. I would make sure you can present each of the 10 pieces of content in an optimized webpage with a distinct URL. You can still use code to streamline the process and delivery, but try not to handle everything at one URL.

A quick example would be a category page that dynamically presents each product within that category. This might happen when you click each product image (and this all happens at at one URL). The engines would only see one URL and crawl the initial content. Not good.

So there you have it, 6 ways you can save the day during your next website redesign or website update. Keep in mind that you will probably have a challenging time when you first introduce these questions. There will be pushback and requests to back up your recommendations. But once you do, and everyone involved starts to understand SEO best practices, the problems I mentioned will be less likely to occur. If they are less likely to occur, then you have a better chance of keeping your organic search power. If you keep your organic search power then you can keep driving natural search traffic to your site. If you keep driving natural search traffic to your site, then you can reap the benefits of that traffic, which can be increased exposure, customers, and revenue.

So don't be afraid to speak up!

GG

Labels: , , , ,

Tuesday, January 08, 2008

301 Redirect HTML Files Without Using ISAPI Rewrite

Using 301 Redirects When All Else FailsWhen you run a website, there are times that you'll need to redirect older webpages to newer webpages or you might want to redirect multiple domain names to a single domain name. There are two key ways to accomplish this task, issuing a 301 redirect or a 302 redirect. What you might not know is that a 301 redirect is search engine friendly and a 302 redirect is not. 301’s will safely tell the search engines that one page has been permanently moved to a new location, while 302’s tell the search engines that it’s a temporary redirect (which can cause problems down the line.) This shouldn’t be news for anyone working in the search industry, but might be news for website owners outside of the industry. My post today isn’t about what 301’s and 302’s are, but it’s about a unique challenge I ran into recently with one of my clients. We needed to 301 redirect several HTML files to new pages on the website without using the standard methods of issuing a 301 redirect. Also, the website was running on a shared server, which was an added barrier. By writing this post, my hope is that I can help some of you who might run into the same situation. More on this soon. Let’s start with a quick review of redirects.

Let’s Define 301 and 302 redirects:
A 301 redirect is a permanent redirect and tells the search engines that the old webpage has been permanently moved to a new location. It basically tells Google and the other engines that you have permanently moved one page from HERE to THERE. If you need to redirect a file on your website, then you should always use a 301 redirect.

A 302 redirect is a temporary redirect, and is not search engine friendly. It basically tells Google and the other engines that the file in question has temporarily moved from HERE to THERE. There have been vulnerabilities in the past with using 302 redirects, which is a reason that 302’s aren’t trusted. If you need to redirect one page to another on your website, then don’t use a 302. Always use a 301 redirect when possible.

The 301 Challenge
Back to the redirect challenge that I recently faced. Again, my hope is that the solution can help some of you who might run into the same situation. One of my clients has a website that’s running on a windows server and contains a combination of HTML, ASP, and ASP.net files. We needed to redirect several older HTML pages to new ASP.net pages, which at first glance would be relatively simple to do. If you are on a windows server, I highly recommend using ISAPI rewrite to issue 301 redirects. This is similar to using an .htaccess file on a linux or unix server. You can issue one line commands using a text file named httpd.ini that sits at the root level of your website. It easily enables you to issue 301 redirects, rewrite URLs, etc. It’s a great utility to have installed…

The Shared Server Problem
Here was the problem. We couldn’t use ISAPI rewrite. The website was running on a shared server and the web hosting company would not install ISAPI rewrite on the server. Some hosting companies will and others won’t…this specific hosting provider wouldn’t after several requests to do so.

Issue the 301 Via ASP.net Code
So, my next move was to issue the 301 redirects via code (either through ASP or ASP.net). There was also a problem with using this technique. The files we needed to redirect were HTML files and not ASP or ASP.net files, so I couldn’t add the necessary VB or VBScript code to the pages that needed to be redirected. Moving on…

Run HTML Files Through ASP.net
My third idea was to run all HTML files on the website through ASP.net, which would enable me to add ASP.net code to each of the HTML files. Basically, when an HTML file is requested, it would run through the ASP.net engine. Then I could issue the 301 redirect via ASP.net code instead of using ISAPI rewrite. Cool, right? The hosting provider made the change on the server (running HTML files through ASP.net), but to our dismay, some of the HTML files on the site were not rendering properly. So, we reverted back to the original setup (where HTML files were not run through ASP.net). Again, moving on…

The Fourth Time is a Charm…
My fourth idea finally worked. The hosting provider basically said we were out of luck, but I wasn’t ready to give up so fast… I knew that Classic ASP is still supported on windows server, even when running ASP.net. Classic ASP was the original version of Microsoft’s server side scripting framework. The next version of the framework was ASP.net, which has also gone through its own upgrades over the years. So, I posed the question…couldn’t we try and run HTML files through Classic ASP instead of ASP.net? My client’s hosting provider made the change and bingo, it worked like a charm. We can now issue search engine friendly 301 redirects on HTML pages. Just to clarify, this meant that I could add Classic ASP code to any HTML file running on the website. For our purposes, I could issue a 301 redirect via Classic ASP code, the HTML file would be run through the Classic ASP engine, and everyone would be happy. :)

The Added Benefits of Using This Solution:
The obvious benefit is that we can now use 301 redirects with any HTML file on the website, when needed. The added benefit is that we can now also use Classic ASP code within any HTML file running on the website. Typically, HTML files can only contain HTML code (no server side functionality.) But with this solution, I can make database calls, provide dynamic content, use session variables, and any other Classic ASP functionality available. It’s a flexible solution, to say the least.

In closing, please remember the following items when you need to redirect HTML files on your website:

1. If you need to redirect a webpage or domain name, use a 301 redirect.

2. Don’t use 302 redirects. If you do, use them at your own peril. {cue mad scientist laughter}.

3. If your website is hosted on a windows server, use ISAPI rewrite to issue your 301 redirects. It's a great utility.

4. If you can’t use ISAPI rewrite and you are in a shared environment, try and issue the redirect via ASP or ASP.net code. If you are trying to redirect HTML files, you’ll need to skip to #5 below.

5. If you can’t add ASP.net or Classic ASP code because you are working with HTML files, then try running your HTML files through the ASP.net or Classic ASP engine. Then you’ll be able to add the 301 redirect code to your HTML files.

Happy Redirecting!

GG

Labels: , , , ,

Monday, March 26, 2007

Why is My Homepage Bounce Rate So High?

Dealing with homepage bounce rate!
Over the past few months, I've received dozens of questions about homepage bounce rate so I decided to dedicate a blog post to it. I'm glad to see executives and marketers getting more involved with website optimization. I think it shows the true evolution of web marketing.

Let's start with a definition of Bounce Rate:
The percentage of visitors that visit one page on your website that exit the site before visiting another page.

Hence the word "bounce"... Here's a quick example. Tom sees a paid search advertisement for xyz company. He clicks through the ad and hits the homepage (more about why this could be a problem later.) He quickly scans the page and doesn't find a call to action to what he's looking for and promptly goes back to the paid search listings. That's a bounce.

I figured that providing a list of some of the most common problems would be a smart way to build this post. So without further ado: (in no specific order...)

1. Your homepage doesn't speak to your personas (types of buyers)
I have mentioned this about a dozens times in related posts, but in my opinion, the best way to optimize your website is to determine your customer personas (types of buyers) and then build persuasive scenarios based on those personas. The days of pointing visitors to a website and simply listing a navigation and a quick intro are gone... I gave a quick example of persona development in my last post (HD TV buyers) if want to reference it.

2. Confusing Homepage Layout and Content, So What Exactly Do You Sell??
Let's say you are speaking to your personas (as mentioned above) and you still experience a high bounce rate. If that's the case, then there's a good chance that your homepage isn't laid out properly. As part of an abbreviated persona development project, my client learned that their customers tend to look for a search box when they hit the homepage of an e-commerce site. As a result, they moved their search box to a more prominent location on the page, improved their search algorithm, and improved the way their search results are displayed. Now, that's a great example of learning from your customers and making the appropriate changes to your website structure. And, they utilize a robust web analytics package to analyze their site activity to ensure the changes they made to the site are working. It's a constant evolution. That's just one example, but you should look at how you introduce your company, your text navigation, the visuals you have on the homepage, the lingo you utilize in the copy, the dimensions of your site as compared to your average visitor (via your analytics package), how quickly your page loads, etc.

3. External Campaigns Driving Visitors to Your Homepage
This can inaccurately bump up your homepage bounce rate and is a common problem that I see in web marketing. For example, paid search campaigns that lead to the homepage of your website, email marketing for a specific promotion that lead to your homepage, banners (yes, unfortunately some web marketers still use banners) that lead to your homepage, etc. I understand if you are undermanned and cannot build campaign landing pages, but I cannot emphasize how this can help your campaigns on multiple dimensions. You can split test landing pages, you can talk specifically to the campaign recipients, you can provide unique content for the promotion visitors, and you can track that landing page at a granular level. In addition, you can utilize your web analytics package to view clickstream reports to see where visitors go after viewing that specific landing page. I can keep going here, but I think you get the gist of why landing pages are important. Using landing pages will also give you a more accurate bounce rate for your homepage. Maybe 7% of your homepage bounce rate was from external campaigns. But please, don't go and refine your homepage until you have accurate data.

3. Ranking in Natural Search for Keywords that Aren't Directly Related to Your Company
If you haven't optimized your website for search, your homepage might actually be ranking for keywords that don't directly relate to your business. Typically, this isn't a big driver of traffic, unless you've really added content and phrases on your homepage that can be interpreted by the search engines as something else. This is something you can easily find via your web analytics program. Just pop into Natural Search and view the top keywords from each search engine. You'll be surprised what you find. For example, if you wrote a book on starting a golf instruction business and you get a few thousand people per month visiting your site by entering the keyword "best ways to increase the distance of your drive", then your homepage bounce rate might be inflated. Figure out why you are ranking for that keyword and then form a strategy for ranking for keywords that directly relate to your business. If you don't have the skill-set in house, then hire a Search Engine Optimization (SEO) specialist.

4. Website Visitor Expectations are Not Met Properly (This also relates to the external campaign listing above...)
If you set expectations too high in an advertisement and suddenly you receive a lot of traffic from that advertisement, there's a chance a good portion of that traffic could bounce. If you sell Samsung TV's, but don't sell Panasonic TV's and your ad claims that you have the widest selection on the face of the earth, then it shouldn't be a shock when people looking for Panasonic TV's bounce off your site! One of the best lessons I learned regarding marketing copy was from John Caples (probably the most famous advertising copywriter ever). Keep it specific and keep it realistic. For example, "We provide a wide selection of Widescreen HD TV's from Samsung, Sony, Pioneer, and LG in sizes ranging from 26" to 50". Compare that to "We have the widest selection of HD TV's in North America and we must move our inventory today! We have every size imaginable!" If someone visits your site from the second ad and they are looking for a 60" Toshiba, they will probably bounce.

So, how do you fix your website bounce rate problem?
1. Track everything via a robust web analytics package and start analyzing the results (where are visitors coming from, which links on the homepage are most active, which real estate areas on the homepage are most accessed, is on-site search easily accessible, etc.)
2. Determine your personas and map out a plan for speaking to those personas right on your homepage (and in your navigation). This involves speaking with your customers, using web surveys, and speaking with your customer service people.
3. Split test changes to determine if they are working for you. If you don't have a benchmark, then how will you know if you are improving anything?
4. Run clickstream reporting to see where people are going (after you make changes based on your persona development). This will enable you to see which elements drive the most sales. In addition, it will enable you to see which elements drive the highest abandonment rate. For example, you might find that 45% of the people that click through your "New Additions" link leave the site on the next page.

And as usual in web marketing, be creative, be analytical, listen to your customers, listen to your customer service people, and track everything. It's definitely not easy, but if you utilize a structured approach, it could chop your homepage bounce rate down to a reasonable number!

GG

Labels: , , , , , , ,

Thursday, March 22, 2007

Web Marketing Surveys, The Value in Gaining Customer Feedback

Online Marketing Surveys and Gaining Valuable Customer Feedback
More and more, companies are looking to make important changes to their websites in order to increase conversion. A few years ago, most website changes were about look and feel or functionality, where today I hear the word "conversion" much more (and especially at the executive level). It makes sense, doesn't it? Web Analytics packages have evolved and web marketers can now view their data easier and faster than ever before. That said, where do you start? Should you use a structured process like the steps in Persuasion Architecture or use another approach that you've utilized in the past? Regardless, finding out what your customers think is essential. There are many ways to accomplish this from focus groups to usability testing to online surveys.

In my opinion, all should be used to gain important feedback prior to mapping out the blueprint for change. For this post, I've decided to target website-based surveys. In my experience with helping clients launch online marketing surveys, the first step is typically the hardest. "Well, what are we going to ask them and why?" is what I typically hear. At this stage it's important to think about your customers and the types of buyers that will be visiting your site. Based on personas that you map out, you can start to flesh out the questions that will enable you to make key decisions about the changes to your website. For example, if you sell HD TV's, two possible personas that come to mind are:

1. The Cutting Edge Buyer - He always wants the latest and greatest equipment.
2. The Discount Shopper - She wants an HD TV, but cannot afford the latest and greatest. She wants the best possible TV for the budget she has.

Keep in mind, there are probably 4-5 other potential types of buyers for this category, but I wanted to give you some quick examples. Note, these are not demographic-based, they are buyer process-based. There's a big difference between the two (and why I believe Persuasion Architecture is a strong process to go through.)

So What Do We Ask Them?
Now you can start to flesh out your questions for each persona. So, for the two sample personas I listed above, what do you want to learn from them? Maybe how important product visuals are, product reviews, or if they would use a forum for customer support? Maybe you want to see if they will read your blog, participate in the blog, or if they cannot stand blogs. You will be surprised what you find. Think about the Discount Shopper persona, maybe they want to access a sales-only page where they can sort products to their heart's delight. Or, maybe they want to subscribe to RSS feeds for the latest sales. My point here is that you should not answer the questions...but that your goal is to learn from your customers. Don't try and answer your own questions, chances are you are too close to the product line, website, and company. You might be right 20% of the time, but 20% won't earn you a promotion...

Survey Monkey, A Great Online Survey Solution
Now that you have your questions, how do you go about setting up the survey? At this point, everyone involved will have a different opinion on how you go about launching the survey. Should the IT department set it up, should you go with a free survey solution, or should you go with a paid service. I almost always recommend the latter. I really like Survey Monkey and several of my clients have taken my recommendation to use their service. The professional subscription is only $19.95 per month and you get a robust online survey solution that's customizable to boot. You can read their online survey features here, but they should cover ~99% of what you want to achieve. The reporting is strong and offers an excellent export feature so you can import the data into Excel (or whichever data analysis program you use). Anyway, I have found it to be a solid solution for launching and tracking online surveys. And, it's fast.

Make Sure You Sweeten the Offer
In order to increase response rate, I highly recommend including an incentive for filling out the survey. And I'm not talking about a $5 gift card to Starbucks. Offer something of worth or you risk having an extremely low response rate. For example, I have a consumer products client that offered their customers 15% off their next purchase. That could translate into $15-20 off their next purchase. The incentive completely depends on your customer base. A quick brainstorm session would yield a dozen or so incentives that you can use.

Analyze the Data
After the survey is over, take the time to analyze the data from several viewpoints. The open-ended questions sometimes yield incredible information. Think about it, if someone took the time to actually type in a response, it's probably worth reading, right? Some people even include their contact information, which can help you build focus groups down the line. It depends on how passionate the customer is and how much they want you to change!

Closed Loop Communication
Last, but not least, let the respondents know what you are doing based on their feedback! This is probably the most overlooked step in the process. Your customers will likely feel as if they didn't waste their time and that you take their feedback seriously. Also, it's a great opportunity to look for customers for focus groups or even word of mouth marketing campaigns.

In closing, online marketing surveys can help you understand how your customers really feel about your products and website, and can help you make decisions based on data versus your own opinion. Use a solid solution for launching surveys and analyze the data fully before making any decisions. Then follow up with the people that responded. You can start to foster a stronger relationship with your customers, which can lead to loyal customers and hopefully increased revenue. And, isn't that what it's all about?

GG

Labels: , , , , ,

Wednesday, March 14, 2007

When Website Redesigns Attack! A Gripping Story of Vanishing Search Engine Rankings

When Website Redesigns Attack, Search Engine Rankings Drop
This is a story of a website going full circle, and not in a good way... If you are thinking about redesigning your website and you believe that search traffic is important to your business, then this post is for you. Read on...

First, my purpose is not to focus on the company or website I refer to below, but to focus on the concept of redesigning a website without fully understanding the impact it will have on natural search. This is not a rare occurrence...it unfortunately happens all of the time.

Help, Google Doesn't Like Us!
Almost two years ago, I assisted a company that hit rock bottom from an organic search standpoint. They went through a complete website redesign and started to notice that their search engine rankings dropped off of a table. This had gone on for about a year prior to my showing up. The first thing the CEO asked me to do (and the term "ask" is being nice..) was to get the site ranking in the search engines as quickly as possible. The site was essentially non-existent in the engines and nobody at the company knew why. The site was a Pagerank 0, with old content indexed in Google, and the site wasn't ranking for any competitive keywords. So, I was handed a budget and launched a major SEO initiative to turn things around. After making significant changes to the site architecture, content, and navigation, we went live with a new codebase. Four months later, the site had over 65,000 pages indexed in Google, earned a Pagerank 7, and began ranking for dozens of competitive keywords, including hundreds of long tail terms. The site did a 180 and was humming from a natural search standpoint. I wish the story ended here...

Flash Forward to Today...
I noticed that the site was recently redesigned again. It was actually more of a refresh than a redesign. As I browsed the site, it didn't take long for me to notice some serious problems... Some of the most important changes that were made for organic search were now gone. Important keywords were missing from the site, title tags weren't optimized on key landing pages, and I could tell that nobody focused on SEO when mapping out the redesign. Uh oh. So I started testing some competitive keywords that the site was once ranking for...the site was no longer ranking for them... So, what will happen to some of their natural search traffic? Well, it will probably go to a competitor's website.

The Danger of the Website Redesign
I'd love to say that this is a rare occurrence, but it's not. When redesigning a website, it's critically important to have key people from a wide range of roles involved during the process. This starts with the web marketing team to map out the strategy and blueprint for the redesign. Then, the programmers and designers should be involved in the storyboard and prototype process. Also, you should include any specialists along the way, like search specialists and rich media specialists to ensure the entire project will go smoothly and achieve the goals of the redesign.

Don't Skimp Over Strategy
Sometimes (ok, often), the strategy piece is briefly completed and the designers and programmers run with the latest and greatest technology to wow visitors (or worse, to gain experience with new technology). When this happens (from a search standpoint) search rankings tend to go down. For example, that really cool, dynamic navigation isn't being indexed by Google, the new code is so smart that it's 302 redirecting visitors all over the place, and someone forgot to add descriptive title tags, description tags, and descriptive links on the site.

So, What Should You Do?
If you are planning a redesign, ensure you use a structured approach that includes key people from a wide range of roles in the process. This is one of the reasons I truly believe in Persuasion Architecture. Your web strategy is fully mapped out prior to designers and programmers getting involved.

My guess is that the CEO will pick up on the lower traffic levels and start asking questions. I wouldn't want to be in the room when that happens. :-()

GG

Labels: , , ,