[terra_t]

love it love it love it love it love it

i just love it when competitors hide their web sites behind 'romulan cloaking devices' that make their content invisible to search engines!

more traffic for me!

bwa ha ha ha ha ha!

[threepointone]

From what I understand (and this is heresy) google waits a couple of microseconds and lets a page generate content before it crawls it.

That being said, if you follow google's rules as specified here - http://code.google.com/web/ajaxcrawling/docs/getting-started... , it will crawl your ajax pages, no problem.

Finally, please be a little civil. Thanks.

[antichaos]

Did you read the article? The single-page web app degrades to linked pages when JavaScript is disabled, and it's fully indexable by search engines.

[kls]

It's actually simpler than that now days, you simple set up a server with a headless web browser on it and route all old-browser and crawlers to that box. They get the same functionality but with-in a page post model. There are a few architectural adherence but for the most part it works pretty well.

[maushu]

I always wondered about this, how does Google prevent this type of behavior? Like serving specific content to search engines and show other content to users... do they check using camouflaged bots?

[kls]

It is not a matter of preventing it, Google is the one that actually conceived of and is promoting this approach.

[simonw]

That's simple? Do you know of any sites that actually do that?

[kls]

Here is the Google page on the subject:

http://code.google.com/web/ajaxcrawling/docs/faq.html

All of the apps I am currently working on do not have a SEO or old browser requirement, but I have used this technique in the past.

[mmorris]

Actually the article describes specifically how to do this while avoiding SEO (and no-JS) problems.

As with AJAX, the typical philosophy is to design for elegant degradation -- plan the site, then build it to work without JS, then add in the "fancy" stuff.