Semantic Page Titles Improve Search Engine Optimization
There is a lot of discussion about the ultimate title for webpages. Of course much of this discussion is about Search Engine Optimization (SEO). Having read Mark Jaquith’s WordPress tip on the subject I thought that I would add my own tip via the comments.
Here’s what I wrote;
Personally I use ‘%post_title% presented by %blog_title%’ or ‘%post_title% on %blog_title%’ via the All In One SEO plugin for WordPress.
This makes the title element a sentence that is easier to read and probably scores lots of points for accessibility. I read somewhere that page readers (for the blind) read the separators that so many of use have used in our title tags.
For example this page’s title [on Mark's website] would be read out, “wordpress tip colon reorder your title tag left-pointing double angle quotation mark mark on wordpress.” How annoying is that?
Another comment, by Lodewijk gave another useful WordPress tip, it read;
And while you’re at it, you could also simply replace with your own blog name. It will reduce the amount of queries to the database by one for every pageview.
All he means by this is to replace %blog_title% with actual title of your blog. A simple suggestion but not good for distributed themes!
Think about the different places that the contents between the tags are shown. Most obviously, they appear at the top of the browser window. If readers use tabs with their web browser software, titles are shown there too. Bookmark a page and the title is used as a reference to where that bookmark points. The same applies to online bookmarking like del.icio.us and similar web services like digg.com and reddit.com. Drag a URL from a browser to your desktop and the title will be used.
For these reasons webpage titles must be descriptive and relevant to the page content. Ideally they will not contain separators such as colons ‘:’, pipes ‘|’, left ‘«’ or right-pointing double angle quotation marks ‘»’ and the like. Omitting these improves accessibility and, I would imagine, probably improve your SEO.
After Mark Jaquith’s tip links led me to the following SEO articles, all of which are worth reading if you want to optimize your website or blog for the search engines:
Semantic Header Markup Means Search Engines Will Understand Too
The Simplest Most Effective SEO Move You Can Make
Magnetic Headlines
The Sound of the Accessible Title Tag Separator
Update added on April 25, 2008
As mentioned in Phil Nash’s comment below screen reader users are used to punctuation being read out and the less verbose delimiters are acceptable. He uses double colons ‘::’, as I have done in the past, and I think that this is a suitable and acceptable delimiter, if required.
Conclusion
If you wanted to use your blog’s name and the post’s title along with a keyword or category then consider these three ways of formatting that information between the title tags.
Bad Title:
♦♦♦ $BlogName » $Category » $PostTitle ♦♦♦
Good Title:
$PostTitle :: $Category :: $BlogName
Screen Read Friendly Title:
$PostTitle presented by $BlogName and filed under $Category
Last 3 posts in Blogging
- Blogging Within Firefox With ScribeFire - September 10th, 2008
- Some Amusing Spam Comments Caught By Akismet - August 17th, 2008
- WordPress 2.6 Released - July 16th, 2008
Last 3 posts in Web
- Your Music Anywhere Via The Web With blueTunes - September 26th, 2008
- Twitter Client using Fluid and Hahlo with Growl - September 5th, 2008
- UserVoice: Customer Feedback Web App - September 5th, 2008
Last 3 posts in WordPress
- Blogging Within Firefox With ScribeFire - September 10th, 2008
- Some Amusing Spam Comments Caught By Akismet - August 17th, 2008
- WordPress 2.6 Released - July 16th, 2008


April 25th, 2008 at 10:37 am
Hey Chris, thanks for the link!
I appreciate the call to not use punctuation characters for the gap between post name and blog name when you set up the title, but I don’t think you have to be as strict as never using them. I like what you have done with yours and admittedly my double colon is the best of delimiters, but I think you really should only avoid the very verbose named characters. Anyone using a screen reader is used to punctuation being read out, but no-one wants to sit through “left-pointing double angle quotation mark”. I think things like colons, hyphens and other short delimiters are ok. There was a discussion about this a long while ago and this is the only link I could find on it: http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/
April 25th, 2008 at 1:25 pm
Thank you Phil for taking the time to comment. I have updated the post with your thoughts in mind.
April 25th, 2008 at 1:51 pm
Thanks for the link Chris!
My suggestion is no good for distributed themes, that’s true. But the people making those, usually know their stuff.
This was a helpful tip by the way, never thought about screen readers before. I’ll keep those in mind from now on, reading all the punctuation out loud can be really annoying.
How do they handle smilies? That would be really annoying, if those too were read out loud as punctuation!
April 25th, 2008 at 4:28 pm
Lodewijk, all a smiley is is punctuation, so a
will be read out literally as “colon dash right parentheses”. Horrible, but check out the ASCII art example on this page: http://tlt.psu.edu/suggestions/accessibility/images.html#ascii !!!
I just noticed that this blog turns smilies into images, but the alt text is the punctuation characters, so it is just as bad. Perhaps it would be beneficial to write a plugin or something that explained a smiley better for alt text. Anyone good at PHP?