Should I use www in my URLs or not?

The short answer is: it doesn’t really matter! Some people will argue that it has become a standard on the internet to use www in your URLs, others will say that it is useless and should therefore be avoided. Personally I think it doesn’t matter! What matters is to make a choice since the very start and to stick to it! I chose to go for the version without www simply because my domain name is already quite long so I wanted to avoid too long URLs appearing in search results. So my preferred domain is http://picturesfromearth.com

301 redirects to your preferred domain.

So why is it so important to choose a preferred domain and to stick to it? For search engines the two versions of the URL will be considered as different. So to avoid confusing search engines with different versions that it would consider as duplicate, it is better to stick to just one. Start this good habit since the beginning in the way you link internally to your site and always use the same version. Unfortunately, you can’t force other people to link to you to the right version. Some will probably use the www version or the non-www version even though you never do. It is to avoid diluting or losing these links that it is wise to make a 301 redirect to your preferred domain version. You can achieve this very easily through the .htaccess file on the root of your server.

.htaccess 301 redirect.

To create a 301 redirect to your preferred domain, add it to your .htaccess file on the root of your site (or create a file that you name .htaccess and place it to the root of your site on your server). The code will vary according to the preferred domain you chose:

If your preferred domain is the non-www version ( you want to redirect www to non-www version):

Options +FollowSymLinks
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} !^domain\.com$ [NC]
RewriteRule ^(.*)$ http://domain.com/$1 [R=301,L]

Replace “domain” with your domain name.

If your preferred domain is the www version ( you then want to redirect non-www to www):

Options +FollowSymLinks
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} !^(.*)\.domain\.com$ [NC]
RewriteRule ^(.*)$ http://www.domain.com/$1 [R=301,L]

What if I have subdomains?

The code will cause problems if you have subdomains so you need to exclude them from the above code. I had the problem for my blog.picturesfromearth.com which was causing errors. To avoid this, simply add this code above the RewriteCond (and under “RewriteBase /”):
# Stop mod_rewrite processing if “example” subdomain requested
RewriteCond %{HTTP_HOST} ^example\.domain\.com
RewriteRule .* - [L]

There you go! This should not have taken you very long to implement but it will prove very valuable for you in the future!

At first, I joined flickr. I think these guys did a great job to create a lively community. It’s also great to find pictures if you search directly from their site. However, for other search engines, I think it is a disaster. As an example, just look at the URL of my most popular picture on flickr: http://www.flickr.com/photos/fanz/134271077/. I mean what does this tell users about my picture? Lions? Africa? I don’t think /134271077/ tells them much! When surfing I saw plenty of examples like that and decided I wanted to try something else.

I wanted to create a simple site, but made for the internet, users and understandable by search engines. I want my URLs to be descriptive, my pages to have a nice title and a little description of the picture. But I don’t want to spend hours coding every page manually either!

So I went looking around and decided to give Plogger a try. It looks extremely simple and promises SEO friendly URLs. That’s a good start! So far I have been very happy with my choice, but I had to do a few tweaks to make it look exactly how I wanted it.

The first thing I did was to enable the option “Generate Cruft-Free URLs”, to have SEO-friendly URLS. However my first problem with that was that URLs were ending with the extension of the picture (.jpg) which I didn’t like since these are html pages and should not be labeled wrongly. To fix this I used this simple tweak:
http://dev.plogger.org/changeset/528

After that I was left with URLs without trailing slashes which annoyed me as well, so I applied this two revisions:
http://dev.plogger.org/changeset/546
http://dev.plogger.org/changeset/547
To apply these just download the zip archives at the bottom and replace the relevant files on your server.

Now my URLs look a lot more like I wanted them to look. Check this one for example:
http://picturesfromearth.com/travel/madagascar/grand-tsingy-national-park-valley/

Isn’t that much clearer?