On the official Google blog there is a new announcement that the Beta version of an encrypted Google search is ready for use by general web users.

In a nutshell, by visiting https://www.google.com (rather than http://www.google.com) an encrypted connection is put in place which means third parties are not able to see the search terms you use and search results you view.

Immediate differences between the standard and more secure versions of Google are highlighted in the blog post: “The service includes a modified logo to help indicate that you’re searching using SSL and that you may encounter a somewhat different Google search experience, but as always, remember to check the start of the address bar for “https” and your browser lock indicators: Today’s release comes with a “beta” label for a few reasons. First, it currently covers only the core Google web search product. To help avoid misunderstanding, when you search using SSL, you won’t see links to offerings like Image Search and Maps that, for the most part, don’t support SSL at this time. Also, since SSL connections require additional time to set up the encryption between your browser and the remote web server, your experience with search over SSL might be slightly slower than your regular Google search experience. What won’t change is that you will still get the same great search results.”

The article also states “Google will still maintain search data to improve your search quality and to provide better service. Searching over SSL doesn’t reduce the data sent to Google — it only hides that data from third parties who seek it. And clicking on any of the web results, including Google universal search results for unsupported services like Google Images, could take you out of SSL mode. Our hope is that more websites and services will add support for SSL to help create a better and more consistent experience for you.”

This has been implemented after Google suffered recent criticism over data security when it collected information from open Wi-Fi connections. How the general public will react to encrypted Google search and how large the uptake will be is anyone's guess, though it is easy to see, even within a day of release, that this will make life more challenging for website owners and search engine marketers.

Early tests show that in the website analytics data, the referrer field isn’t complete when vistors come from the https version of Google. This means that the more people use encrypted search, the less you know about where they came from and the keywords used to bring them to your site.

It looks like Google has listened to recent feedback that many Pay Per Click account managers, including ourselves, have passed on regarding the quality of broad match in AdWords. For a while now we have been concerned with the way Google uses broad match keywords as many clients have been appearing for totally unrelated terms, due to Google believing the words were related. An example being a Solicitor client of ours bidding on the broad match keywords “immigration lawyer” and appearing for the search query “homeoffice”.

In the interest of only exposing clients to traffic that is relevant, we have started shying away from broad match and sticking more with “phrase” and [exact] match terms. Either that or spend half our time adding in scores of negative keywords. This might not be needed now, as Google has announced the introduction of ‘modified broad match’ on its blog, here.

By placing a + sign in front of the words, you can now tell AdWords to only show your advert for very closely related searches. The blog post states that “close variants include misspellings, singular/plural forms, abbreviations and acronyms, and stemmings (like “floor” and “flooring”). Synonyms (like “quick” and “fast”) and related searches (like “flowers” and “tulips”) aren't considered close variants”.

This is a big step in the right direction and something we look forward to working with.

In the first case of its kind, a UK citizen has just been fined £1000 after one of his tweets landed him in hot water.

Back in January, upon hearing the news that Robin Hood Airport was closing due to snow, angry Twitter user, Paul Chambers vented his anger by posting: "C**p! Robin Hood airport is closed. You've got a week and a bit to get your s**t together, otherwise I'm blowing the airport sky high!!"

Whilst the airport themselves didn’t take the joke seriously, the police did and this week he was fined £1,000 due to the post being "grossly offensive or of an indecent, obscene or menacing character”.

On top of the fine, Mr Chambers was given a criminal record and also had his computer confiscated. This hasn’t stopped him using the micro-blogging site as since he has commented on the judgment with "I'd like to thank the CPS (Crown Prosecution Service) for their level-best efforts in f**king up the life of an ordinary citizen. I love Britain."

Mr Chambers is now considering launching an appeal, something which other Twitterers, including well known user Steven Fry, have said they would help fund.