Demystifying discoverable web apps
summary
Googlebot executes JavaScript but often defers rendering (minutes to days) using an older engine (Chrome 41), so purely client-side apps can be discovered slowly or not at all. Use Puppeteer or Rendertron for dynamic rendering, test pages with the Mobile-Friendly Test and Search Console, and monitor automatic alerts. Update titles/meta (react-helmet, Angular title service), use real anchor hrefs and the History API instead of hash routing, and return correct HTTP status codes for reliable indexing.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:18I'm Martin Splitt
- 7:59Let's talk about Googlebot!
- 10:46How modern Googlebot works
- 13:36g.co/mobile-friendly Are there mobile issues?
- 15:25Googlebot runs Chrome 41 Released 2015
- 17:27Dynamic rendering tools (examples)
- 20:43Use proper link markup!
- 23:57History API ftw
- 31:42Takeaways, summarised 1. Consider hybrid rendering
related talks
36mSemantic, Searchable Webapps with Angular
25mMaking Modern Web Content Discoverable for Search
35mTechnical SEO Demystified
30mDazzingly discoverable, furiously fast web apps with Angular
12m3x3 SEO tips for JavaScript web apps
39mSearch and JavaScript Sites
28mTechnical SEO 101 for React Developers
34mDeliver search-friendly JavaScript-powered websites
