News for hackers. Stuff that matters.
Re: Understand the JavaScript SEO basics by hazz99 on Friday July 19, 2019 @08:24PM (#20483470)
Yes, I agree - server side rendering is likely better for SEO in most scenarios, and so I should consider it in a business context where SEO is essential.

This isn't everyone.

The comment I replied to said that Google should "delist client side rendered web pages", which is a terrible idea. Maybe I'm OK with the SEO hit? Maybe I've architectured my SPA so that it can be indexed? (At least to some degree)

> The bigger question is why you think an spa should rank well in general. It's only one page.

SPAs can have multiple pages (despite the name). Check out react-router [0]. Browser history can be manipulated to give the same "back button/forward button" functionality between logical pages. This is done for you by whatever framework you use.

For my use case, having the browser reload every time a page is changed would severely interrupt UX.

[0] https://reacttraining.com/react-router/web/guides/quick-star...

Re: Understand the JavaScript SEO basics by edoceo on Friday July 19, 2019 @09:14PM (#20483623)
But to a crawler it's one "page". To humans it's different, but not to robot. Crawler still (mostly) "page" == GET
Re: Understand the JavaScript SEO basics by hombre_fatal on Friday July 19, 2019 @10:16PM (#20483784)
Yet here we are discussing TFA that says otherwise, and crawlers are only going to be become better at it.

This is a beautiful part of the new web: indexable applications.

Re: Understand the JavaScript SEO basics by wolco on Saturday July 20, 2019 @09:36AM (#20485666)
Crawlers were suppose to have this down in 2012 (at least google),now they recommend a sitemap page.