JavaScript SEO (The "Right" Way)
summary
Claims that server-side pre-rendering of SPAs yields better Google rankings than the fragment/hashbang approach and that headless-browser snapshots (PhantomJS) are too resource intensive and stale when crawled frequently. Cites gethuman traffic (one in eight US users last year), performance targets (<=200 ms server response, <=2 s full load), tools tried (PhantomJS, pre-render.io, Brombone, React, Ember, Express, Angular UI Router), the ad hoc duplicate-render demo that works in production but motivates moving to isomorphic controllers and templates.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:16GetHuman
- 2:34Matt Cutts
- 3:46PogoSticking
- 4:56Performance
- 6:18Social Proof
- 7:04OnPage SEO
- 7:58The Truth
- 9:10The Problem
- 10:49Humans Care About URLs
- 11:43Cloaking
- 13:34Headless Browser
- 16:12What if Google
- 17:16Server Prerendering
- 18:12Twitter
- 20:55Routing
- 22:22Controller duplication
- 23:00Custom templating
- 23:22Demo
- 24:45Next
- 25:25Recap
- 27:09Blog Post
related talks
41mTechnical SEO for JavaScript developers
07mTechnical SEO & JavaScript
35mTechnical SEO Demystified
39mTowards Universal JavaScript
39mSearch and JavaScript Sites
06mDemystifying server-rendered React apps: Performance & Security
33mDemystifying discoverable web apps
12m3x3 SEO tips for JavaScript web apps