And here come the answers.
Managing Partner, Marketing Factory GmbH
Managing Director, Trust Agents
There are opportunities in that now you don’t have two separate programming worlds (e.g. for escaped fragments), letting you focus on clean code and a clean web environment. As long as developers consider progressive enhancement and develop their web applications accordingly, Google should be able to cope just fine.
Before a relaunch, a careful decision should be made on the framework to be used. Crawlability and performance should both be considered. Ideally, a test environment should be created that makes it possible to test the current development from outside, if client side rendering is being used. That said, I would highly recommend also using server side rendering. This impacts the server performance, but should minimize risks. Above all, you really have to test, test and test, using fetch & render to see what the Googlebot finds, indexes and crawls.
If Google does finally switch to a Chrome version higher than V49, then we could use headless Chrome in combination with something like Rendertron to create test environments that let us simulate a setup similar to that of the Googlebot. This would help us better understand how and what Google can interpret. This would make things a lot easier for us SEOs
Co-Founder & Head of SEO, Elephate
Founder & Managing Director, Trust Agents
SEO Consultant, leap.de
Besides the fact that I don’t expect Google to communicate the web rendering update very well to webmasters, I expect the main thing that will change will be the susceptibility to errors. Chrome and the frameworks develop really quickly, and with the new versions, new bugs are likely to come into the RWS.
A few things are sure to be processed more quickly or rendered more cleanly. But the main problem stay the same. Error-ridden code (from the point of view of the engine in use) cannot be interpreted. We have to find out how the engine interprets our code. During development, this changes the tool we have to use for debugging. But if you have your most important assets as quick-loading HTML (etc.) files, then you needn’t worry – you can concentrate on proper SEO work.
Director of Professional Services, Searchmetrics
Above all, I expect faster, more efficient rendering to come from Chrome 59, moving towards performance on a par with pure HTML. Only tests will tell if this really happens.