4 ms·
Tangentially related, and agree with the complexity and churn that Next introduces, but curious: If am building a product where SEO matters, does SEO still real
by lf-non 3y ago
Tangentially related, and agree with the complexity and churn that Next introduces, but curious: If am building a product where SEO matters, does SEO still really suffer in absence of SSR?
Sure TTFB (& potentially other web vitals) are better with SSR, but I still keep hearing SEO friendliness as a primary reason for SSR though prevalent crawlers like Google/Bing can index js loaded content.
- SwiftyBug 3y agoThis guy from egghead.io learned how much SSR actually matters for SEO: """ figured out what ruined egghead's SEO and dropped our monthly traffic 90%... broken SSR anybody that tells you search bots don't require SSR is full of shit """ https://twitter.com/jhooks/status/1757086865348522109 https://twitter.com/jhooks/status/1757086865348522109
- lf-non 3y agoInteresting. Thanks for sharing.
- OJFord 3y agoGoogle says: > Dynamic rendering was a workaround and not a long-term solution for problems with JavaScript-generated content in search engines. Instead, we recommend that you use server-side rendering, static rendering, or hydration as a solution. https://developers.google.com/search/docs/crawling-indexing/javascript/dynamic-rendering https://developers.google.com/search/docs/crawling-indexing/... and: > Crawlers may understand JavaScript, but there are often limitations worth being aware of in how they render. Client-side rendering can work, but often not without additional testing and leg-work. https://web.dev/articles/rendering-on-the-web#seo_considerations https://web.dev/articles/rendering-on-the-web#seo_considerat...