
Apple iWeb 09 is a great tool. I was able to build a pretty
nice looking site for our flat in Borovets in just a week-end. Apple emphasis has always been on ease of use and good design and here again iWeb does not disappoint. The new version even allows the creation of somewhat dynamic content (comments on blogs and photo libraries for example).
I had started using Google Sites but realized very rapidly that building a site with flair would be an immense challenge. Graphics and fonts are just too difficult to deal with in Sites. But what I gained in look and feel by moving to iWeb, I lost in marketability. Having iWeb sites rank properly is notoriously difficult. The sites are hard to index because the main navigation is JavaScript based and text content is often converted to images. And inserting tracking code to monitor your site performance is just not possible without clumsy workarounds.
To improve ranking, I suggest those 3 easy steps:
- Some people have suggested rewriting the navigation toolbar manually. Another option is to make sure that no page is left orphan on your site, i.e. there is a link on the home page to another page in your site that in turns contains a link to a third page and so forth. That allows crawlers to find all the pages of your site since the navigation bar will not fulfil that role.
- Create a sitemap, either manually or if you have followed my previous advice by using an online tool such as XML-Sitemaps. Then you should upload it to Google with Google Webmaster Tools. If you have a blog on your site, don't forget to add a sitemap for its RSS feed as well. Blogs are crawled a lot more often.
- Make sure that the font you are using is not converted into an image upon publishing. The easiest way to check is to turn on image indicators in the preference pane. Once you have done that, any text content that will be converted to an image will show with a small image icon on it's top right. In some instances however (especially for titles) you might want to use that special font that you know will most probably not be available on the client computer. In that case you can force conversion to graphics by selecting the text and applying a 1% drop shadow.
Installing tracking code for Google Analytics (or any other tracking code) is the hardest part. Some people have suggested that
inserting the code in an HTML snippet on each of your pages will work. And indeed it does. But in such a limited way that's it's almost useless. Because all inserted HTML code is actually created in an iframe and not the page itself, all information about the source of the clicks is lost. If you use Adwords, all the clicks will appear as direct. And if someone falls on your page through a search engine query, the keywords as well as the referrer details would be lost as well. The only workaround is to inject the Javascript code directly into the pages created by iWeb (and do it again for every change in the site). Fortunately there are tools that allow for some automation of this process. One such tool which has the merit of being freeware is
iWeb SEO Tools. You can use it to inject javascript automatically into your site after every change. You should use it with caution however as it only works on static pages. Attempting to amend any blog page for example will completely
break them!
Also, you should remember that if you use adwords, you need to specify the landing page to be the page that has the Google Analytics code in it and not the main web site for example. Such a redirect would again
fail to allow for proper capture of CPC information.
Yes, it's a bit clumsy, but I have no doubt that Apple is aware of those limitations and hopefully by next version of iWeb this will become just a painful memory...