As much as anything this post is a note to my self for future reference.

When using the WP_Query() routine in Wordpress to create custom blog post loops, quite often there are issues with the formatting and rather than just showing your post content before the 'read more' link it shows the whole post even though you have the code in place to cut the post off at 'read more'. Read the rest of this entry »

SIMONR85 over in the affiliates4u forum posted a PHP related query. He initially wanted to show 3 products from a database then when a user clicks a "show more" link 30 products would be visible. This can be acheived quite easily in PHP but I personally think jQuery would be much more suited to the job. Using jQuery would cut down on server calls while at the same time presenting more information for search engines.

So here is a crude example:

Read the rest of this entry »

I sent an email to someone today to explain what advantage a good, relevant, keyword rich domain name is when trying to be number one on Google for a search term such as "Charlie Bears". So I thought I would share this information.

Search engines look at both the website address and inbound links to a website when deciding what the sites content is about. So to a search engine and anyone that doesn't know any better a website address like www.charliebearsuk.com or www.charliebears.uk.com looks like a pretty official website about Charlie Bears.

Here are a few examples to help explain what I mean by inbound links:

1) www.charliebears.com (This would be an inbound link to "http://www.charliebears.com" with the link text "www.charliebears.com")
2) Charlie Bears (This would be an inbound link to "http://www.corfebears.co.uk/osc-22-Charlie-Bears.php" with the link text "Charlie Bears")
3) look at this bear website (This is an inbound link to "http://www.charliebears.com" with the link text "look at this bear website")

When Google decides which websites should be at the top of the listings for a "Charlie Bears" search the main thing they look at is inbound links and the link text that is used. So simply speaking the more a site has links to them using the link text "Charlie Bears" (plus variations that include those words), the higher up the listings they will go.

When websites naturally acquire links from directories, blogs or any other websites a variety of link text will be used. Things like "view the website", " view site", "click here" and in many cases the whole website address. This is where having the website address www.charliebearsuk.com , www.charliebears.com or www.charliebears.uk.com is very beneficial. Sites with a website address that include the words "Charlie Bears" stand a much better chance of obtaining more inbound links with that link text and therefore be listed higher for that phrase when people search on Google.

Notes/disclaimer:

I understand Google says there are 200 factors that dictate which site is the most relevant to a phrase like "Charlie Bears" but inbound links with good anchor text trump every other factor in my opinion.

Using link text such as "view the website", " view site" and "click here" is not good practice. Use descriptive link text where possible.

www.charliebears.com is the official Charlie Bears website.

SDinternet promotes the www.CorfeBears.co.uk website.

In an effort to improve usability and reduce server calls on a complex form, I've been implementing jQuery's validation plugin.  jQuery makes it extremely easy to validate a form with minimal code.  I wasn't happy with the default style of error message, I  didn't want a large line of error text disrupting the structure of my form. I wanted a simple icon to indicate there was an error and when the user hovers over the icon I wanted to utilise jQueries tooltip plugin to explain the error. I had a good search on the internet but couldn’t find a solution. What I did find was lots of other people in the same situation.

Now I've successfully managed to combine jQuery validation with the tooltip plugin I thought I had better share it.
Read the rest of this entry »

I’ve noticed a few blog posts recently regarding the reliability of the relatively new canonical element. This element or meta tag can be used to resolve duplicate content issues where web based content can be accessed from a variety of URL’s.

For instance your website homepage could possibly be viewed by navigating to www.site.com/ or www.site.com/default.php or even www.site.com/default.php?action=home. Internal and external links could point to all variations making it difficult for search engines to determine the primary document. This can lead to a fragmented internal link profile and possible penalties for duplicate content.

Implementing the canonical element in the offending page allows you to indicate the primary document.

I tested this on a clients site, where the homepage was indexed in Google under two different URL’s. It was a great success; within 24 hours of the homepage being spidered the duplicate page was dropped!

The other day I did a quick tweet (post on twitter.com) about an e-commerce site that I'm marketing. Today I looked at the back links to the e-commerce site and the twitter link is being recognised by Google (from my Twitter profile page).

I expected to get the odd link from syndicators of twitter but I thought twitter added nofollow to outbound links.

Nowadays mobiles don't seem to be getting any smaller, instead they are becoming more powerful, almost like tiny laptops. With mobile download speeds improving massively and networks including unlimited data on some tariffs, internet usage on mobile devices is only going to increase. GPS, high resolution cameras, accelerometers, 8GB + memory, wifi, permanent internet connectivity; the application potential is enormous.

Mobile applications will see explosive growth in the next few years.

I created a web statistics application a few years back, it was quite a big application and sometimes needed certain functionality on another server. To request this functionality I would use the PHP require() function to execute the remote file

require("http://www.remoteurl.com/generateStatsSummary.php?accountID=$ID&useDate=2007-11-20");

Then a few days back the main server this application is hosted on got hacked into and had to be rebuilt with new versions of MySQL and PHP installed. The application then decided to stop working, in the end I worked out that the more recent versions of PHP don’t allow you to pass query strings to remote files using the require() or include() functions; you must use file_get_contents() instead!

Here is the PHP function I used to collect email addresses from my Outlook express sent items data file. You pass it text and it will return an array of all email addresses that are in the text. Enjoy!

function extract_emails_from($string){
preg_match_all("/[._a-zA-Z0-9-]+@[._a-zA-Z0-9-]+/i", $string, $matches);
return $matches[0];
}