Hibernation

It’s time to come out of hibernation, remove the tompian from my arse and have a look around for a good ol’ meal. My tummy is rumbling and the legs are a bit shaky, but dozing in a dark cave is getting a bit lonely and my mind needs a challenge again.

Standardzilla packed it in for a while and I haven’t posted anything new since the end of last year. There have been many reasons for this, including:

Site Design
The site is falling apart… I don’t mean visually but I kind of designed and developed this blog with no idea how I was going to use it or what kind of content I was going to publish. This means publishing a post is a painful hack of inline styles and fishing around for common code patterns I have found useful. A redesign is in order here to keep me sane.
Getting Hitched
I got married. I often thought this wouldn’t consume my life but it actually did as it was overseas and I was, well, quite into it. So a few things dropped in priorities and lots of that was web related.
Lacking Mojo
I lost it for a while there. I don’t know where it went or how it happened but the comedown from Web Directions South last year saw me getting a little sick of all things web-related. I had to just retreat and stop being consumed by this online lifestyle and lose myself in things non-web related and re-evaluate my passion for what I do for a living.

You will be glad to know it’s coming back slowly, with a new focus on what’s important and what I want to get from this industry and how I want to approach things, including this blog. Standardzilla 2008 season is open and there will be more to come (for those who haven’t ditched me from there readers yet).

Stay tuned for more details in the weeks and months to come, I just have to go out and get myself a snack… I haven’t eaten in months.

Comments (3)

Subdomains and Google

Recently, Google has announced a change in its treatment of subdomains and how they are represented in their search result pages.

In the past, subdomains such as:


example.com
phones.example.com
furniture.example.com
yoyos.example.com

have all been treated as separate hostnames. To explain why this might be an advantage to you the website owner, you need to know how Google have treated these separate hostnames in the past.

Subdomains vs. Subdirectories

When Google displays the results of a search query, it will only return a maximum of two relevant searches results per hostname. This behaviour is called ‘host crowding’ and it means the user will have exposure to more than a single website for a search term.

A subdirectory, or a folder, will be considered part of the top level domain so this additional content or categories will still only show two results per search term on the result page.

Subdomains however, get around this limitation because they are being treated as a unique hostname. This means one top level domain can potentially dominate search engine result pages with all of their own content, depending on how many subdomains they might have that are relevant to the search term.

What does this actually mean?

This is another great move by Google to enhance the usability of the search engine user by trying to eliminate people from gaming the system.

In many instances, websites with multiple subdomains are not actually causing a problem and apparently won’t be filtered by this new algorithm change. (these have been classed as ‘exceptions’ by Google).

Websites such as Ebay or About.com that are extremely large and categorise their content with the logical architecture of subdomains. These categories will not always compete for every search query, so they can potentially return relevant results for the user.

Who this will target is the SEOs and websites owners who have been on to this ‘white hat’ technique for years. Websites with URLs such as:


example.com
brand1.example.com
brand2.example.com
brand3.example.com

that produce duplicate or syndicated content across several subdomains will start to feel the filtering affects of this algorithm.

Using subdomains to distribute content that is not different or categorised in a logical manner will now cause you to have less control in the way that Google will display the results of your website to potential users.

Who benefits from this?

I think a few people will benefit from this and it’s a good move if implemented correctly and does not filter out relevant websites that use subdomains correctly.

Smaller websites have often been disadvantaged by the treatment of subdomains by Google. I have worked with many websites that didn’t have enough content to be splitting it up with subdomains, but were often bound by third party contracts or server configurations.

This change will mean that those websites that have been diluting their Page Rank for so long will have a bit more clout with the search engines as a single hostname for all of their content. These small websites might be able to think about using subdomains to retain simplicity and enhance branding without worrying about this Page Rank issue anymore.

The user also benefits from a more concise, accurate search result provided by Google who continues to impress me with concern for the individual search engine user. It’s a real pain for some SEOs and website owners whenever Google changes it’s algorithms like this, but I am still convinced it’s for a good reason.

As with anything SEO related, if you use subdomains strictly to create more visibility in the search engines for your website, then you are probably using them for the wrong reason.

Comments (2)

HTML Email Standards

Every couple of months or so, developers at work have to rebuild some HTML email templates and turn to my team and ask the inevitable question, “Do we have HTML email standards?”.

“They aren’t complete” is my usual answer as I flashback to my last attempt at painfully coding up an HTML template and trying to figure out the best format for maximum consistency across the multitude of email clients.

The next step is to usually forget it ever happened and move on to something else. In the end all of us developers usually end up collecting half complete, partially working templates that hibernate on our local drives and never really see the light of day.

I am relieved to see someone finally confronting those demons and starting some definitive email standards documentation in one central repository as well as developing some great testing and benchmarking for current email clients.

Brought to you by Fresh View, Luke Stevens and Mark Wyner. These guys have kicked off a project that will hopefully raise awareness of the need for web standards and accessibility in email and to also try to change things on the email client developers side…

The Email Standards Project works with email client developers and the design community to improve web standards support and accessibility in email.

Awesome work guys, head on over to the Email Standards Project and show your support for this great project.

Comments (1)

« Previous entries