5 ms·
Look at the pages indexed in google: https://www.google.pt/search?q=inurl%3Ahttp%3A%2F%2Fwww.learn-angular.org%2F https://www.google.pt/search?q=inurl%3Ahttp%3A
by ttty 12y ago
Look at the pages indexed in google: https://www.google.pt/search?q=inurl%3Ahttp%3A%2F%2Fwww.learn-angular.org%2F https://www.google.pt/search?q=inurl%3Ahttp%3A%2F%2Fwww.lear...
Now look at the source with ctrl+u. (example url: view-source:http://www.learn-angular.org/#!/lessons/binding-css-classes http://www.learn-angular.org/#!/lessons/binding-css-classes)
Now you know why he needs server side rendering (:
Anyway I never tried angular, and this tutorial made me try it. Is explains very very well how to get started, that's true.
- clubhi 12y agoSeeing how I figured out how to index angularjs pages for searching myself in one evening I imagine it won't be too long before google improves on this.
- andybak 12y agoI'm not sure it's Google's job to. Or rather - even if Google figures out how to index these pages, why should every other consumer of web content have to also figure it out when it's the fault of the content itself. i.e. don't break the web.
- twerquie 12y agoI would argue that Google's job now includes executing javascript and evaluating dynamically loaded content. Break the web.
- andybak 12y agoBe careful what you wish for.
- dlsym 12y agoFlash. shiver
- devNoise 12y agoI would tend to agree that google needs to solve this problem for indexing. They were the source for angular.js and they must realize that stuff they want to index will be buried in one page javascript apps going forward.