$.02 about Web 2.0 and AJAX
There are some problems with AJAX that lots of people complain about. For instance, it’s very unfriendly to people with accessibility needs and browsers on mobile platforms. It also breaks the back button (although that’s a pretty much solved problem at this point). Adam Alex Bosworth made a good list of other tricky issues.
But there are some others that are pretty tricky and not for obvious technical reasons.
AJAX and Ads
If you’re building a business around a web site that offers a free service you’re probably relying on at least some income from banner advertising. Guess what? The banner ad network thinks you’re only getting one page hit per user session even though you’re getting 100′s of clicks. None of those clicks triggers a new page load since your site is all AJAXified so the ad servers don’t know about them. You get paid for a single impression even though the user’s been pounding away on your sever resourcs for six hours.
Aint that a bitch. You want to use AJAX but it kills your ad impressions. It took like ten years for internet ad firms to come up with standards like CPM and banner ad sizes. How the hell are they going to figure out what to pay you for a “tab switch” or “scroll down” click? An AJAX action that repaints 25% of the visible pixels in the browser window should get you 25% of a page view? Good luck trying to bill them for it.
- Forbes: Nielsen/NetRatings doesn’t know how to measure your AJAX traffic.
- AJAX Counting Nightmares – This guy Eric Picard has been writing about the problem for a while.
There’s another problem which componds the first but it might be easier to deal with since it doesn’t require the internet advertising industry to agree on something.
AJAX and SEO
You want to drive lots of traffic to your site from search engines. The best way to do this is to doll up your site for when googlebot comes strollin’ by. He’s got strange taste so that means doing some odd things to your html. Odd things that most people don’t want to see or know about. This is known as the black art of Search Engine Optimization or SEO for short. (Put on your boots because the BS gets thick around the “SEO Expert” crowd. It’s like real estate investment seminars or multilevel marketing, but with a highly technical twist.)
How is AJAX problematic for SEO?
Your javascript widget generates html inside the browser window. You want google to know about this html content so it will point people to your site. But GoogleBot doesn’t run the javascript that generates the html content in your widget, so it never sees that content and never indexes it. You must make this content appealing to Monsieur GoogleBot, and he likes static links to static-looking resources. Javascript ain’t so static looking to him so you have to slap some makeup on it to make it look that way.
Some interesting thoughts on how AJAX and SEO might play together nicely:
- SEO Considerations for AJAX Development
- AJAX and SEO- includes a demo of how to make AJAX links look more static
mmm ‘Alex’ Bosworth not Adam :/
Alex Bosworth
8 Jun 06 at 10:39 pm
Whoops! Sorry ‘bout that (does that happen often?).
Swik is pretty slick, btw.
banksean
9 Jun 06 at 5:52 am
Ajax applications should be kept for very specialized situations.
One example could be PHPMyAdmin. Since people already know about PHPMYADMIN, the phpmyadmin user interface does not really need to be indexed by google.
The pages that advertise and comment on PhpMyAdmin should be kept as html documents that can be parsed by google.
I think all websites therefore should remain AJAX free unless the website has a special purpose.
The other sad thing about AJax is the fact that one could just design a thin client that runs natively on the desktop. The only real disadvantage of making a thin client application is that it must be compiled on each CPU architecture (unless it is interpretted, s such as Java).
An alternative to Ajax would be a “thin client browser” that allowed one to download thin client plug-ins from within the web browser. Instead of downloading an AJAX application, the visitor would download a DLL/DSO/EXE/ELF file and load it right on screen inside a special browser. The huge problem with this is security.
The more power an application has - the less secure it is. HTML has never been very powerful adn this is why it is so secure.
Lars
16 Sep 06 at 6:08 pm
Hey Sean,
Great post. This whole Ajax vs. SEO thing is something my development team has been wrestling with for a while now. It’s a headache, so we’ve been doing our homework to find solutions. I’m starting to see a light at the end of the tunnel and now I think there are some good solutions. I just recently read a really good article on Ajax and SEO that you might want to check out. Ajax does rock, but none of my developers even thought of SEO ramifications when they started. Anyway, hope this thing gets easier, for ALL of us.
Brian London
26 Jun 07 at 1:03 pm