Propeller Websites | Graphic Design | Email

In the face of increasing perversion of search results by black-hat SEO ‘experts’, one year on Google is now taking further steps towards rewarding high-quality sites and penalising ‘over optimised’ websites.

When deciding to get your company an online presence many business owners make the mistake of purchasing just a single domain name. Over time this can prove costly for a number of reasons. Instead business owners should obtain a variety of domain names for their company.

Google have today rolled out their new high-quality sites algorithm to all English-language Google users.

According to Google, these changes are designed to help provide the most relevant answers as quickly as possible.

I don’t normally re-post articles regarding website data-entry and styling but I find myself having to re-iterate warnings against the over-use of uppercase or block-caps to clients continually, so this article from Roger Johansson, one of the web’s foremost authorities on accessibility issues, was nicely timed.

We reported back in April that Google’s Webmaster Central Blog had confirmed Google’s intention to factor page loading speed into its search ranking algorithms’.

Not many people realise it but websites have traditionally been bound by the regular fonts installed on the users computer. Hence until recently web designers have been restricted to a rather small list of around 8-10 fonts which can reasonably be expected to be present on most users’ machines.

Google announced on Friday 9th April via its Webmaster Central Blog that website page loading speed is now to be factored into its search results and Pagerank.

A recent Webcopyplus online poll has revealed that almost 25% of web users surveyed indicated “poor visual presentation” along with 50.9% of users indicating “slow load times” were the main reasons to abandon a website. “Weak web copy” sat alongside design as a major factor.

Whilst ‘click-here’ and ‘more >>’ may be fairly obvious to most web users, its’ certainly not best practice. It can be difficult to avoid…