Official statement
Web workers are executed and registered by Google, but the rendering system does not properly wait for events occurring in their separate environment. If a web worker makes a network request, Google does not necessarily wait for the response and the return to the main thread.
Other statements from this video 8 ▾
- □ How do Promises and WebAssembly impact SEO rendering?
- □ 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)
⚠ A more recent statement exists on this topic
Is Google struggling to properly index sites that use Web Workers?
View statement →
TL;DR
Google executes web workers but doesn’t wait for network responses from their separate environment, which can impact rendering. For SEO, make sure critical scripts do not rely solely on web workers.
❓ Frequently Asked Questions
Les web workers impactent-ils l'indexation ?
Potentiellement oui, surtout si le contenu vital s'appuie uniquement sur eux pour son affichage ou son exécution.
Googlebot exécute-t-il les web workers ?
Il les exécute, mais ne garantit pas d'attendre leurs retours réseau dans le rendu final.
Quels types de contenus sont à risque avec les web workers ?
Tout contenu critique chargé exclusivement par des web workers pourrait passer inaperçu dans le rendu initial de Google.
🎥 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.