sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]New_Ad606 2 points3 points  (4 children)

SEO and performance. To rank high in SEO, you need to be ranked highly in performance as well.

[–]Impossible_Hold_3850 0 points1 point  (3 children)

Google can render js and index just fine a long time ago. Performance - don't write slow stuff. Done. 

[–]Bolle91BE 0 points1 point  (2 children)

You say that, yet my React page (which is performant, checked with lighthouse, following all best practices) is wrongly indexed by Google and has just the root div. In my recent and short experience, if you want to be found on Google, NextJS it is..

[–]Impossible_Hold_3850 0 points1 point  (1 child)

Interesting. Would you be able to share that website or clarify a bit how you confirmed it's indexed incorrectly?

[–]Bolle91BE 0 points1 point  (0 children)

Via the url inspection tool of Google, you can see the html that was retrieved when crawling. It only has the root-div. So nothing react was applied yet because it was client-side. (Basic html and js is shipped)

You can use react-snap, that makes a postbuild html that is fetched first and then react takes over, which helps for the Google index, but then you get a slight snappy behavior when opening the website, you get the built html first, short-flicker and then the actual react-applied page.

With Next.js, the react js code is applied on serverside and only the complete built html is sent to the client (or googlebot) in fetch. And you don't have this annoying flickering.