The darker side of AJAX
AJAX is all beautiful and good and you can use it to build wonderful applications, but it’s important for web site designers to keep in mind one very important customer: search engines. You want to get good, content into Google and Yahoo so they can find your site, don’t you? Well AJAX is not good for that. Search engines attempt to treat all web applications the same and I’d be surprised if any of them actually attempted to index a site based that was built with AJAX, I suppose Google could somehow attempt to, but I doubt they can do it well.
Part of what makes AJAX applications so powerful is the ability to build responsive contextual applications. Search engines typically operate on a page by page basis and don’t really remember the context of what a user is doing when they find a new page and index it. It doesn’t really make sense for them to index highly contextual information, because then the search engine user would have to follow the same path to get to that page.
So what do you do to build an AJAX application which can be indexed by the major search engines? I’m not sure, you probably don’t want to go to the extreme of building two separate sites, or serving up special content just for search engines. Google has said they put a significant penalty on sites that cloak(give different content to search engines than to regular browsers) because it’s so often abused by search engine optimizers.
