Search and JavaScript Sites
summary
Google updates Googlebot to a modern Chrome rendering engine that brings over 1,000 new features so most ES2015+ syntax, IntersectionObserver and native lazy loading work when rendering; recommended approaches are server-side rendering, pre-rendering or hydration (Next.js/Angular Universal/Vue server renderer) instead of long-term dynamic rendering; use Lighthouse and Search Console to debug; note crawl budget counts JS subresource fetches, service workers aren’t used during render and Googlebot doesn't persist cookies across requests.
AI-written summary · about
chapters (22)
- 0:00Start
- 3:20Latest Stable Chrome Rendering Engine
- 4:41Modern Javascript Is No Longer a Blocker for Seo
- 8:58Universal Javascript
- 9:36Server-Side Rendering
- 10:19Pre-Rendering
- 11:07Hydration
- 14:25Pre Render Spa Plugin
- 15:35Server-Side Code
- 17:08Angular
- 18:32Dynamic Rendering
- 19:04Use Cases for Dynamic Rendering
- 21:09Seo Audits
- 21:52React
- 22:53Title and Meta Service
- 24:13Lazy Loading Images
- 24:31Lazy Loading
- 24:52Section Observer
- 26:13Crawl Budget
- 29:11Service Worker
- 29:37Feature Detect
- 29:59Error Handling
related talks
20mSearch and Javascript Sites
25mMaking Modern Web Content Discoverable for Search
50mTechnical SEO for JS developers
41mTechnical SEO for JavaScript developers
55mTechnical SEO 101 for web developers
36mSemantic, Searchable Webapps with Angular
42mModern JavaScript Frameworks & SEO
35mTechnical SEO Demystified
