Semantic, Searchable Webapps with Angular
summary
Shows that Google does two‑stage indexing: the crawler indexes raw HTML first and delays costly rendering, so client‑side apps can miss the first wave unless server‑side rendering is used. Demonstrates using Angular Universal with an Express/ngExpressEngine setup to produce crawlable HTML (example: a dog‑rating SPA that becomes discoverable), warns that the web is huge — ~160 trillion documents — and recommends concrete tools: mobile‑friendly test, structured data tester, and Search Console to verify indexing and debug failures.
AI-written summary · about
chapters (17)
- 0:00Intro
- 3:00Disclaimer
- 7:46Indexing 1/3
- 9:48Important note
- 12:43Googlebot, for real
- 13:15Rendering
- 18:24Add dependencies $ ng generate universal --client-project doggos-rating $ npn install nguniversal/express-engine
- 18:37Create the server
- 19:40The result
- 21:51Tip 1: Good URLS
- 26:55Tip 2: Meaningful markup
- 31:21Avoid sneaky 404s • Use URL rewriting . Do not hijack 404 logic • Test in incognito window
- 34:49Add markup to your page
- 37:06Mobile-friendly test
- 39:06Structured Data Testing Tool
- 39:49Search Console
- 42:08Tips, summarised
related talks
36mSemantic, Searchable Webapps with Angular
30mDazzingly discoverable, furiously fast web apps with Angular
22m5 must-dos to make your JS app search engine friendly (#7 will shock you!)
33mDemystifying discoverable web apps
28mBuilding search engine friendly web UIs with JavaScript
26mServer Side Rendering with Angular Universal
51mThe Jedi Path to Angular Universal
30mSetting Up SEO for Single-Page Angular Applications
