3 ms·
Given the prevalence of client-side rendering, I think all the major players have learned to circumvent this. They can run a full headless browser instead of ju
by _bxg1 8y ago
Given the prevalence of client-side rendering, I think all the major players have learned to circumvent this. They can run a full headless browser instead of just looking at the raw HTML, and detect when the JavaScript seems to have rendered the content.
That said, user experience (in this case site speed) can be a factor in how Google actually ranks pages, so that could be another motivation.
- jypepin 8y agoWell... as everything else with how Google's crawler and algorithms work, there are no official or definitive answer, but what has been communicated is that it could work but definitely more difficult and can lead to more issues. Knowing a bit about SEO, if you want to invest in your ranking, I wouldn't go without server-side rendering.
- _bxg1 8y agoStill, the two buckets I described above hold true. If someone is returning to your web app - Slack, or Trello, for example - you don't care as much about SEO because most of your visitors are return visitors. Your splash page, on the other hand, needs to be optimized for SEO but won't have much interactive complexity, so it doesn't need client-side rendering.
- davidjnelson 8y agoA lot of seo data is meta tags in the head. These aren’t going to render client side.
- walshemj 8y agoYeh they use a two stage process now but client side is still best - look at the recent JavaScript series on googles webmaster chanel.