| SEO Comparison of Joomla 1.0 and 1.5 |
|
| Thursday, 25 October 2007 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
After the big chart earlier this week comparing the Search Engine Friendly URL Components for Joomla, I wanted to take a similar approach and compare the SEO features of Joomla 1.0 and 1.5. What's On the Chart?On the chart is a rundown of all the key on-page SEO factors. We can't help you when it comes to building links or writing articles people want to read, but we can advise on the technical stuff. Who May Find This Useful
Hopefully this chart will help people who:
The Small Print
Joomla 1.0 and 1.5 SEO Features
Bookmark
Email this
Comments (18)
![]() Right on Steve! This is an excellent comparison that tells it all. This is a great post! The comparison is just what I've been looking for to help me to decide when to make to switch. Have you had a chance to review Charl van Niekerk's xHTML project from SOC 2007? Charl indicated it would be released with v 1.5 stable, but, it's available now to download and review (and to adapt/use now, as many of us are). It directly addresses many of the items on your list. (In fact, it goes well beyond these traditional SEO areas and advances into Microformats, a topic I expect to hear a lot of you SEO experts to blog about during 2008.) Steve - just to clarify, Charl's work is for semantic improvements in Joomla! v 1.5 across the board (i.e., standard tagging, improved meta data, removing tables, validating to strict xHTML), in addition to the introduction of Microformats, where appropriate. It will likely be core v 1.6 which will be fantastic news for everyone! It's no wonder they have asked him to join the developer team. Interesting analysis, I think there is more under the surface though.... Hello everybody, and thanks for the well written article and for the comparision charts. I am still using 1.0 because of this reason, but the main drawback with joomla, plus in version 1.5 is the code structure. I see more themes coming out now placing the main content at the top of the page using CSS, but this should have been worked into the core code, or at least thought about. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||






