~/talk

Demystifying discoverable web apps

Talkat FrontEnd Con 2018 · 2018-12-04..12-05· [web-platform, web-performance]
slides:none on file

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

  1. 0:00Intro
  2. 0:18I'm Martin Splitt
  3. 7:59Let's talk about Googlebot!
  4. 10:46How modern Googlebot works
  5. 13:36g.co/mobile-friendly Are there mobile issues?
  6. 15:25Googlebot runs Chrome 41 Released 2015
  7. 17:27Dynamic rendering tools (examples)
  8. 20:43Use proper link markup!
  9. 23:57History API ftw
  10. 31:42Takeaways, summarised 1. Consider hybrid rendering
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.