[Eric_WVGG]

I’m as big an Angular evangelist as anyone, but that bit about search rankings is an absolute killer.

You talk about these server-side webkit parsers as tricks that “slow things down,” which indicates that you at least ultimately got them working. I never got that far.

[untog]

As someone who is familiar with AngularJS but hasn't used it much, the idea that the best answer running WebKit on the server, indexing your client-side generated pages and dumping them out into a Google-indexable static resource just blows my mind.

[cozuya]

What's really interesting is that "google" didn't see this coming - they made angular, they should in theory be huge advocates of SPA, but in reality their primary product doesn't support it well at all.

[onedognight]

Googlebot renders client side JS just fine. Notice how the OP didn't list them and instead listed FB/Twitter.

[caitp]

The angularjs.org sites are indexed, just by using a trivial nginx directive to selectively serve partials to crawlers. All of the angularjs.org apps still rank fairly well using this strategy.

This isn't always appropriate of course, those apps aren't really relying on data from a database, they're proper SPAs. But as noted by others, there are ways to fool crawlers if it's something you want to do.

Generally though, the feeling is that crawlers not executing JS is going to end, and the problem will go away on its own.

[est]

> dumping them out into a Google-indexable static resource just blows my mind.

You can do that, however if you dump static page to Google bot IP only it's an SEO cheating.

[spicyj]

No, this is explicitly endorsed by Google:

https://developers.google.com/webmasters/ajax-crawling/

[jbeja]

I heard something similar in a Reactjs conference by Pete Hunt, at the time i was like , "huh?".

[gildas]

If you're OK to delegate the scraping process to a SaaS then you may be interested by SEO4Ajax [1] which will make it much simpler. Disclaimer: I'm one of the co-founder.

[1] http://www.seo4ajax.com