all you need to know about domain names
(and some you don't need to know, but is interesting anyway)
CHAPTER 1.13
BEYOND THE DOMAIN NAME - GOOD PRACTICE IN URL CONSTRUCTION
It might be a reasonable argument that this section is not actually about domain names because a domain name can be a URL but a URL is not necessarily a domain name. For example, www.alancharlesworth.eu is both a domain name and a URL. www.alancharlesworth.eu/contact.html is a URL but it is not a domain name. However, as domain names and URLs are inextricably linked, I've included this section because it has relevance to some aspects of domain name use.
For most techies and programmers, directory and file names are just something they use to segregate one from another - hence you get URLs that are full of numbers, question marks, tildes (that squiggly thing '~') and heroes from their favourite virtual-world game. I say that as subdirectory and file names come after the domain name suffix, they are part of the web page's address - and so they are part of the communications of the publishing organization. And as communications is part of marketing, getting the full URL right is important.
The first point is to make the navigation of the site obvious - in web development this is called usability. Take this URL, for example:
www.alancharlesworth.com/interesting-articles/branding.html.
It's hardly rocket science to work out what the content of that page is about. Perhaps more importantly, in an e-commerce environment:
www.atrustingbusiness.com/men/shirts/casual/polo.html
tells the user what page they are on or if it is a link, going to. OK, so what? You might ask, and it might not make a big difference in the great scheme of things - but some things are just better if they are done right. But wait, I have another argument up my sleeve. As we saw in the previous section, search engines like to find keywords in domain names - and supporters of that notion say that it also applies to the full URL. Only the engineers at Google, Yahoo!, Bing et al can say if I am right, but surely a search engine would look at:
www.atrustingbusiness.com/men/shirts/polo.html
and think that something on that page should match the needs of a searcher who types "men's polo shirt" into the search box? Secondly, if you are going to match web page URLs with their content, stick to characters that make sense. I would argue that you should use only those characters that are allowed in a domain name - and this includes the 'no-spaces' rule (a space in a URL can show in browser navigation bars as '%20'). Within the directories and files, I would use hyphens to distinguish the words rather than 'all-one-word', e.g. 'interesting-articles' rather than 'interestingarticles' in my earlier example. Avoiding upper-case letters is also a good idea. It's not a big issue if the URL is a link, but as far as computer files are concerned 'InterestingArticles' is a different file name to 'interestingarticles' (try it with your own word documents). Depending on your PC's operating system - or that of your site's host - the URL may or may not be case sensitive, so I say, don't take the chance, put them all in lower case. And finally, don't use the underscore (_) in anything related to the Internet. The simple reason for this is that when a link appears on a web page, the default setting is for that to be in bold, blue and underlined - and if a file name with an underscore is underlined, the underscore looks like a space (eg interesting_articles /
interesting_articles).
Go to the next section, return to the contents page