https://news.ycombinator.com/item?id=7805144
What I'm wondering is, if you have a server than supports "both" methods (dynamic page and "fallback"), how do you know which one to serve? And should they be at different addresses? If they weren't, wouldn't this break caching? If they were, how can you redirect from a "noscript" tag if you have um, no script? Etc etc.
What I get from this announcement is that their crawler is becoming good enough at executing dynamic pages that having to serve a separate static version may soon become unnecessary.
[0] https://developers.google.com/webmasters/ajax-crawling/docs/...
...for the purposes of being indexed by Google.
I am always careful to build dynamic apps which render the HTML correctly on the server. Its handy not just for SEO. It also allows you to support legacy browsers and it dramatically decreases load times.
But if google is the only search engine you care about, and load times and legacy browsers don't matter to you, by all means, continue building one-page JS apps. There are often less headaches to be had when you go the simple route.
they mention some upcoming tooling that might help "To make things easier to debug, we're currently working on a tool for helping webmasters better understand how Google renders their site. We look forward to making it to available for you in the coming days in Webmaster Tools. "
