Effectively using subodomains on your website will decrease your page load time.  If your site is image-heavy your pages probably load slowly.  Web browsers load all elements of a page from one TCP connection stream and each TCP stream only gets so much bandwidth.  For example, if a page has thirty images to load, HTML content, java scripts, and flash elements, a web browser could have 40+ simultaneous TCP connections to a single URL.  This method might stall the loading of a page waiting for a large flash element. One major benefit of using multiple subdomains it that it allows content to load out of sequence.  You might have seen sites that stall until a flash piece is loaded before displaying the rest of the page content.  If the site would have called the flash piece from a subdomain, it would be loaded separately from the HTML and it wouldn’t stall the page load.

A good way to set this up is to write your homepage to call items from subdomains.  Upon the initial load of the website, a DNS query is made to get the IP address of the URL and then it’s cached.  If your homepage loads elements from multiple subdomains, all of those are cached and no further DNS queries need to be made.  If page load time is an issue for your site you could setup a subdomain for all javascript, images, flash, etc.  In this example queries for HTML are loaded from the main URL, javascript from js.example.com, images from i.example.com, flash from f.example.com.  If your site requires 30 TCP connections from one domain, the server handles those pretty much sequentially.  Splitting up the calls between subdomains divides the number of connections in the queue.  In this case you might have 2 connections to js.example.com, 1 connection to example.com (for content), 15 connections to i.example.com, and 2 connections to f.example.com.  Each set of connections is loaded simultaneously thus letting each connection take as long as needed without delaying loading of the elements farther down the list.  This is a bit complex so I’ve created an image to illustrate the point.

I have setup sites in this manner before to help overcome slow page-load times and saw a great increase.  The site was very image-heavy and it was nice to be able to call them from a separate subdomain so loading the images didn’t slow down the site.  If you have a page with tons of images, like thumbnails of products, you can split it up further by defining section-related subdomains on a page.  This would allow you to load all the thumbnails from separate subdomains and speed the page further.

Bookmark It

It’s happened to all of us.  We’ve been to a website that we expected to work correctly, but of course, it didn’t.  Who should we blame for these functionality problems?  The webmaster.  A webmaster is defined as “A technician who designs or maintains a website.”  Notice in that definition the mention of “designs.”  Almost all web designers forget about an extremely important part of their job: browser ubiquity testing.  I discussed this topic before, but I see so many silly mistakes on the web that the topic is always at the front of my mind.

A great example of a major web faux pas can be seen below.  Can you believe that Merrill Lynch calls Google Chrome an “incompatible browser?”  They say their compatible browsers are IE 5+, Netscape 7+ and Firefox 0.8+!  How long has it been since their webmaster actually thought about their site’s compatibility?  The Netscape browser isn’t available anymore, IE 5 is history, and Firefox has been through ELEVEN version updates since this message was implemented.  Where is the webmaster?!

Merrill Lynch has a webamateur!

This is just one example of a lazy or inept webmaster.  I’d estimate that 80% or more of the websites on the internet have some browser compatibility issues.  Website troubles are not limited to the small-budget businesses that throw together sites, as you can see in the example.  I wonder how much money Merrill Lynch spent on their website.  I wonder if they know their site still does browser detection for browsers that were released in early 2004 – SIX years ago.

Bookmark It

Valid HTML is the best practice when it comes to websites.  Though it can be difficult, it is worth the time.   If your code is valid, it won’t have to be auto-corrected by browsers and it won’t cause problems with search engine robots.

I’ve talked about browser ubiquity testing before and the importance of working out problems with code to make sure a site renders correctly in browsers.  To sum up, when code is written correctly a web browser doesn’t have to interpret and correct it.

If web browsers can do their own code correction, why is validating the code important?  Browsers can correct code, search engine robots cannot.  They are left to fend for themselves without that advanced feature.  This can cause problems with them parsing your site in full and finding all the content on a page.  The spiders may get stuck on a piece of messed up code and stall which will eat up the time they have to spend on your site.

There are several tools available to help validate your code and the best one comes from the W3C (World Wide Web Consortium).   The W3C is in charge of writing standards for web code and has played a key role in the development of the internet as we know it.  They know what they are talking about.

Correcting the code can be a real headache if you’re not really good at coding so I recommend contracting a web developer to help.  A good web developer is an expert in this kind of thing and the process will take a lot less time than a novice trying to work it out.

Bookmark It

Another new client comes on and reminds me of the importance of the basics.  The site I’m reviewing for the first time has almost 500 broken links.  That’s right, five HUNDRED.  The client came on reporting virtually no representation in the search engines.  I’m starting to see why.  Code that doesn’t validate, content in iframes, and a ton of broken links.  Though there are a lot of factors that I think are keeping them down, I’m just going to focus on broken links in this post though.

What are broken links and how do you find them?  Broken links are any kind of link that doesn’t deliver the expected page.  The link could fail because of a typo or because the target page has moved.  There are two major problems with having a lot of broken links on a website;  1. The users can’t get to content you want them to find and,  2.  The search engines get stuck in these “spider traps” and burn all their time waiting for a 404, 403, or 500a response.  Both problems affect a site’s positioning in the index because the search engines want to present their users with sites that work.  Also, the search engine bots will never discover all of your site’s content if they are stuck waiting for an error from a broken link.

In the case of my new client, there’s no way to go through it by hand to find every broken link.  It would take weeks.  The best way to do find them is to run a spider against the site, like Xenu, and let it do all the checking for you.  (I’ll write another post about Xenu at some point with tips on it’s operation, but for now I’ll say that you shouldn’t run it full-throttle against a site because your IP might get blocked for a DOS attack.)  Xenu will check every link to see if it works and will report the response.  After the report runs, you’ll have a nice list of broken links and the pages where they are listed.  Keep in mind though that Xenu doesn’t click on every link.  Some older versions won’t work with java onclick attributes and Xenu certainly won’t click in flash elements.

Now that you’ve got your broken link report, what should you do?  Fix them!  You have to go through each link and try to figure out what went wrong with that link.  Was the HTML fat-fingered?  Was the link copied incorrectly from a browser address bar?  Was the page moved?  What error does the server deliver?  Once you’ve figured out what is wrong with the broken link, you can try to fix it.  If the HTML was fat-fingered, just correct the problem and you should be good.  If something else happened to the link, try to find the correct target and replace it.  If you were deep-linking and the target no longer exists, try to find it on the site in an archive.  If you were citing another site’s article and that article no longer exists, it’s still good practice to give a link to their homepage as credit for the citation.

If you’re an SEO correcting links for a client, it’s important to have a good report for them including recommendations for what they should change in their site editing / page creation policies to prevent it from happening again.  Oh, and don’t forget to run Xenu against the site after the corrections have been made.  If they got messed up one time, they could get messed up again.

Bookmark It

When planning a link campaign it’s important to set some goals for the campaign so you can accurately track progress.  You can’t just wing it.  You need to be precise in how you target your campaign or else it will look artificial, or worse yet, spammy.

The best method for tracking your link campaign, as far as I’m concerned, is a good excel spreadsheet.  You should track where you found the link partner, what date you requested a link, when the link went live, the URL of the actual linking page, link type, the advertiser network (if relevant), and the last date you checked the link.  I found this to be quite useful when I had a text link campaign from a third party.  We would periodically review the campaign to make sure the links were live and found that we were paying a lot of money every month for links that were no on sites even though their system told them they were.

As the link campaign builds steam it’s important that you maintain the same pace throughout the campaign.  The number of link acquisitions in a period is tracked by Google and it’s best to keep the linking campaign on a steady pace with no spikes or lags in activity.  This is why I keep a separate spreadsheet containing the number of links for a site on a given day and update that sheet daily.  Using the data I’ve collected I have excel create a line chart of the number of links over time, then apply a trend-line to it to set a goal for the campaign.  The trend-line will show if you are making the progress needed or not.

Another important thing to look at is the number and types of links that your competitors have.  Once you’ve established what they have you can try to build a similar campaign.  You should evaluate the number of links from each different PR, ie., 340 links from PR 2 pages, 400 from PR 0 pages, 65 from PR 5 pages, etc.  The goal is to make your link base look as natural as possible, yet still competitive, to avoid unwanted attention from Google.  Remember:  All sites will have a number of “nofollow” links pointing to them.  Best to keep that number on par also.

The last factor I’ll mention here is link decay.  A Google patent application I read mentioned the fact that Google evaluates the decay rate of a site’s link base.  You need to make sure that your decay rate isn’t too high.  Link decay is when Google can’t find a link on a page anymore.  This can happen when a blog entry that links to you moves off of the homepage and Google doesn’t see it anymore.

A sustainable link campaign is critical to long-term success of your SEO efforts.

Bookmark It

Content Management Systems (CMS) can make life easier for businesses that have no webmaster, or have thousands of pages that they need to organize.  However, a CMS comes at a steep price, both monetarily, and in restrictions.  There are so many inherent problems that choosing the right one is critical for the success of your website. I could go on and on and on about the problems I’ve had with CMSs over the years, but suffice it to say they are a total pain in the neck.

In the interest of keeping this somewhat short and not a soapbox rant, I will stick to a bullet-pointed list of things to think about when selecting a CMS.

• Look for hidden fees for:
  • Page Editing
  • New Page Creation
  • File Uploads
  • Image Creation
  • Phone Tech Support
  • Email Tech Support
  • Yearly Licensing Fees
  • Software Update Fees
  • Bandwidth Overages
• Do not work with a company that refuses to give you full admin rights.
• Demand FTP access.
• You must be able to edit the HTML of the pages and the page components. Period.  The only reason they wouldn’t want you to is so they can charge you to do it for you.
• Do they own the artwork they create?
• Ask for examples of current clients and have an SEO inspect their HTML.
• Test the page-load times of the example websites.  If you don’t know how, your SEO will.
• Don’t sign anything unless you get everything you want in writing.
• Remember, if you design a site in a CMS, they’ve got you. There’s no leaving without a complete recoding of the site and potential loss of database info.
• Will the CMS cost more than a good webmaster?
• If your CMS is a hosted solution, make them give you a Service Level Agreement (SLA) in writing to guarentee uptime.
• Beware of built-in SEO packages. They are usually designed by a programmer that has “some” SEO knowledge and not a true expert.  Bolt-on SEO packages never, ever, work well.
• Ask for a demo of their product as you would see it and in a working environment. A CMS company will often let you test a feature-rich version of the software on their fastest server. The version and server you get may be significantly different.
• Do you really need a CMS or are you being sold a CMS? Ask a professional SEO.
• Have an IT guy check out their system. If you don’t have an IT guy, get one. A real one.
• You should have contracted a professional SEO by now, get them involved before you buy.
• Ask about guarenteed response times to support issues. If they don’t guarentee a resolution time, your issue may languish in tech support for months.
• Ask who your main point of contact will be. It sure won’t be the salesman you’re talking to. Ask to speak with that rep and see if you can understand them. You know what I mean.
• Ask about system backups.
• Ask about system redundancy.
• Ask about connection redundancy.
• Ask about the project workflow for the site design.
• Get a guaranteed completion date.
• Ask to see their designer’s other work.
• Make sure you aren’t limited to the number of design concepts you can go through. You may only get two, and if two isn’t enough, you will have to pay more.
• Ask how their testing environment works. You need a production area to test pages before pushing them live.

There are good CMSs out there, but as a layperson they are hard to identify.  A CMS may be a very good fit for your company, but too often the decision to buy a CMS is made without consulting anyone “technical.”    If you are relying on the CMS company to be your technical person, remember, they are selling you a product.  You need an independent opinion.  When you’re talking to the CMS company you’re not talking to a technical person looking out for your company’s best interests, you’re talking to a salesman working for a commission.

Bookmark It