Créer une experience robot autant optimisée que celle des utilisateurs.
Comment intégrer les Progressive Web Apps (PWA) avec le format AMP (Accelerated Mobile Pages) afin de créer une expérience utilisateur optimale, depuis les moteurs de recherche jusqu’à la conversion? Durant cette session, nous nous concentrerons sur les avantages, les limitations mais également sur l’implémentation technique des deux technologies sur les mêmes URLs. Le but ultime étant d’optimiser l’experience des robots (exploration, indexation) autant que l’experience utilisateur à travers un chargement rapide et des fonctionnalités avancées.
4. @maxxeight#SearchY2020
Une experience utilisateur… que Google peut comprendre.
• Pertinent
• Mobile-Friendly
• Rapide
• Securisé
• Populaire
Un bon référencement naturel est basé sur:
• Contenu
• Web Design
• Vitesse du site
• SSL/HTTPS
• Liens
5. @maxxeight#SearchY2020
Une experience utilisateur… que Google peut comprendre.
• Pertinent
• Mobile-Friendly
• Rapide
• Securisé
• Populaire
Un bon référencement naturel est basé sur:
• Contenu
• Web Design
• Vitesse du site
• SSL/HTTPS
• Liens
25. @maxxeight#SearchY2020
Combiner AMP et PWA
AMP comme
point d'entrée
dans la PWA
AMP comme
source de
données pour
la PWA
AMP avec des
fonctionnalités
PWA
33. @maxxeight#SearchY2020
Les page AMP ne sont pas rendues
• Bots voient seulement <amp-img> (vs. <img>)
• Pas d’access à l’URL dans src=“”
•
• Utilisez <noscript>
Les images AMP ne sont pas indexable
34. @maxxeight#SearchY2020
“Et pour le SEO?”
Les robots ne crawlent/indexent que la version AMP
Pas de gaspillage des resources (crawler plusieurs URLs avec le meme contenu)
Signaux clairs (pas de sourcis de balise canonical/alternate)
Les pages rapide et pre-chargées dans la SERP (AMP viewer ou “URL Réelle”)
Les pages sont “adaptées aux mobiles”
Why is the reach of web apps higher?
Search engines (vs. app stores).
Supported by all major browsers
Low cost of acquisition
Capabilities
Reliable and Fast
App shell cached locally (on 1st load): Fast loading when offline or with slow connection (on subsequent loads)
Mobile-friendly (responsive)
Secure (HTTPS)
Engaging
App icon on device’s home screen
Push notifications
Technically, any website can easily be turned into a PWA (service-worker + manifest)
But in general, a web app, a site built with a JS framework is the best candidate but become a PWA.
Building a web app to be fast: lazy loading, api based content (user click to load)
Refer to JS SEO Best practices
But expand on lazy loading – intersectionObserver – but lazyload attribute
AMP is fast for a lot of reasons that, technically, can be replicated outside of the AMP framework (lazy loading, limited JS, CDN, etc.)
BUT what AMP has that ”normal” pages don’t have is the pre-loading in the SERP (AMP viewer)
If Google start pre-rendering the ”10 blue links”, then AMP has not reason to be.
https://amp.dev/about/how-amp-works/
https://medium.com/@cramforce/why-amp-is-fast-7d2ff1f48597
Lazy loading
Extensive use of preconnect
Prefetching of lazy loaded resources
All async JavaScript
Inline style sheets
Zero HTTP requests block font downloads.
Instant loading through prerendering
Prerendering only downloads resources above the fold
Prerendering does not render things that might be expensive in terms of CPU
Intelligent resource prioritization
Uncoupling of document layout from resource downloads
Maximum size for style sheet
FastDOM-style DOM change batching
Optimized for low count of style recalculations and layout
Mitigations for third party JS worst-practices such as document.write
Runtime cost of analytics instrumentation is independent of number of used analytics providers
Extensions don’t block page layout
CDN delivery available to all AMP documents
All resources and the document are loaded from the same origin through the same HTTP 2.0 tunnel
Animations can be GPU accelerated
User gets the AMP from the SERP
Service worker is installed on device
Once activated, SW caches the “app shell” and initial data
User clicks on a (internal) link
Service worker “hijacks” the click
Pre-cached PWA loads instantly
ServiceWorker “hijacks” the click – Server handles the rest
ServiceWorker “hijacks” the click – Server handles the rest
Google and search engines only get the AMP version of your URLs/pages
- Not the canonical or “normal” URL where images (img + src) can be found
https://amp.dev/documentation/guides-and-tutorials/develop/media_iframes_3p/
https://amp.dev/documentation/guides-and-tutorials/optimize-and-measure/server-side-rendering/
Bots only crawl/index the AMP version of the site
No waste of crawling resources over multiple URLs for the same content
Clear signaling (i.e. don’t worry about all of those canonical/alternate tags)
Pages are fast and pre-loaded in the SERP (AMP viewer or “Real URL”)
Pages are mobile-friendly