Official statement
Promises and WebAssembly work effectively for Google rendering as long as they execute on the main thread. Google waits for the main thread's task queue to be empty, and promises add elements to it.
Other statements from this video 8 ▾
- □ Does Google really ignore web workers in its rendering process?
- □ Why has the Featured Snippet shifted from 'Position 0' to 'Position 1'?
- □ How does Google adapt to user preferences for universal results?
- □ Is ranking now just a matter of bidding?
- □ How does Google's 'Universal Mixer' influence your SEO strategy?
- □ Why does Google share its systems between ads and SEO crawling?
- □ Should You Rethink How You Track Clicks with Search Console?
- □ How does Google truly rank images based on their destination pages?
Official statement from
(4 years ago)
TL;DR
Promises and WebAssembly function correctly for Google rendering as long as they run on the main thread. They add tasks to the queue that Google needs to clear.
❓ Frequently Asked Questions
Les promises impactent-elles directement le SEO ?
Oui, car elles influencent le rendu des pages par Googlebot.
Que se passe-t-il si la file d'attente n'est pas vide ?
Google pourrait ne pas indexer correctement les éléments dépendants des promises.
Comment Google gère-t-il WebAssembly ?
WebAssembly est traité comme une tâche JavaScript dans le thread principal.
🎥 From the same video 8
Other SEO insights extracted from this same Google Search Central video · published on 29/07/2021
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.