What does Google say about SEO? /

Official statement

When a tweet is embedded on a third-party site, Google can technically treat the links in that tweet as part of the page. However, Twitter heavily uses nofollow: these links generally have no direct SEO impact, even if they show up in Search Console.
23:56
🎥 Source video

Extracted from a Google Search Central video

⏱ 55:02 💬 EN 📅 21/08/2020 ✂ 50 statements
Watch on YouTube (23:56) →
Other statements from this video 49
  1. 1:38 Does Google really track HTML links that are hidden by JavaScript?
  2. 1:46 Can JavaScript really hide your links from Google without destroying them?
  3. 3:43 Is it really necessary to optimize the first link on a page for SEO?
  4. 3:43 Does Google really combine signals from multiple links pointing to the same page?
  5. 5:20 Do site-wide links in the menu and footer really dilute the PageRank of your strategic pages?
  6. 6:22 Is it really necessary to nofollow site-wide links to your legal pages to optimize PageRank?
  7. 7:24 Should you really keep nofollow on your footer links and service pages?
  8. 10:10 Why does Google make it impossible to use Search Console Insights without Analytics?
  9. 11:08 Does Nofollow still affect crawling without passing on PageRank?
  10. 11:08 Does nofollow really block indexing, or can Google still crawl those URLs?
  11. 13:50 Why is Google so tight-lipped about its indexing incidents?
  12. 15:58 Should you really index all paged pages to optimize your SEO?
  13. 15:59 Is it really necessary to index all pagination pages to optimize your SEO?
  14. 19:53 Are URL parameters still an obstacle for organic search?
  15. 19:53 Are URL parameters really a non-issue for SEO anymore?
  16. 21:50 Is it true that Google is blocking the indexing of new sites?
  17. 25:33 Are sitemaps really essential for Google indexing?
  18. 26:03 How does Google really discover your new URLs?
  19. 27:28 Why does Google require a canonical on ALL AMP pages, including standalone ones?
  20. 27:40 Is the rel=canonical really mandatory on all AMP pages, even standalone ones?
  21. 28:09 Should you really implement hreflang across an entire multilingual site?
  22. 28:41 Should you really implement hreflang on every page of a multilingual website?
  23. 29:08 Is it true that AMP is a speed factor for Google?
  24. 29:16 Should you still invest in AMP to optimize speed and ranking?
  25. 29:50 Why does Google measure Core Web Vitals on the actual page version your visitors are really viewing?
  26. 30:20 Do Core Web Vitals really measure what your users actually see?
  27. 31:23 Should you manually deindex old pagination URLs after changing your site's architecture?
  28. 31:23 Is it really necessary to manually de-index your old pagination URLs?
  29. 32:08 Is advertising on your site harming your SEO?
  30. 32:48 Does having ads on your site really hurt your Google rankings?
  31. 34:47 Is rel=canonical in syndication really reliable for controlling indexing?
  32. 34:47 Does rel=canonical really protect your syndicated content from ranking theft?
  33. 38:14 Do security alerts in Search Console really block Google's crawling?
  34. 38:14 Can a hacked site lose its crawl budget due to Google security alerts?
  35. 39:20 Have links in guest posts really lost all SEO value?
  36. 39:20 Do guest post links really have no SEO value?
  37. 40:55 Why does Google ignore identical modification dates in your sitemaps?
  38. 40:55 Why does Google ignore the lastmod dates in your XML sitemap?
  39. 42:00 Should you really update the lastmod date of the sitemap for every minor change?
  40. 42:21 Does a poorly configured sitemap really diminish your crawl budget?
  41. 43:00 Can a misconfigured sitemap really cut down your crawl budget?
  42. 44:34 Should you really have to choose between reducing duplicate content and using canonical tags?
  43. 44:34 Is it really necessary to eliminate all duplicate content or should you rely on rel=canonical?
  44. 45:10 Should you really set a crawl limit in Search Console?
  45. 45:40 Should you really let Google decide your crawl limit?
  46. 47:08 Do internal 301 redirects really dilute PageRank?
  47. 47:48 Do cascading internal 301 redirects really drain SEO juice?
  48. 49:53 Can the JavaScript History API really force Google to change your canonical URL?
  49. 49:53 Can Google really treat URL changes made by JavaScript and the History API as redirects?
📅
Official statement from (5 years ago)
TL;DR

Google can technically crawl the links present in an embedded tweet on your site, but Twitter systematically applies the nofollow attribute to these links. The result: no transfer of PageRank, even if Search Console displays them in your backlinks. So don't count on Twitter embeds to boost your link profile — their direct SEO value is nil.

What you need to understand

How does Google handle an embedded tweet on a webpage?

When you embed a tweet via the code provided by Twitter, Google crawls the content of that embed as if it were an integral part of your page. The bot can read the text of the tweet, access the images, and discover the links contained within.

Technically, these links thus become crawlable elements of your HTML. You might even find them in your Search Console reports under the external links section — which can be confusing. But this technical visibility doesn’t mean they pass on any SEO juice.

Why do these links have no impact on your ranking?

Twitter systematically applies the rel="nofollow" attribute to all links posted in tweets, whether viewed directly on twitter.com or embedded elsewhere. This marking explicitly tells Google not to follow these links for PageRank calculation.

Even if the link appears in your source code and Search Console surfaces it in your data, it does not pass any authority to you. It’s a dead link from an SEO perspective, no matter how visible it is in your backlink reports. The nuance is crucial: technical presence ≠ algorithmic value.

What’s the difference with a standard link in your editorial content?

A link you manually add to your article — without nofollow — can pass PageRank and strengthen thematic relevance between two pages. A link in an embedded tweet will never do that, regardless of its position on the page or how many tweets you include.

The Twitter embed acts more like enriched content (social proof, real-time news, expert quotes) but does not serve as a netlinking lever. If your goal is to create an effective linking structure, always prioritize native editorial links within your paragraphs.

  • Google can crawl links in embedded tweets, they technically appear in the page's DOM
  • Twitter systematically applies rel="nofollow" to all its links, including in embeds
  • No PageRank transfer occurs, even if Search Console displays these links in your reports
  • Twitter embeds provide editorial value (social proof, freshness) but no direct SEO value in terms of ranking
  • For netlinking, always favor native editorial links without the nofollow attribute in your main content

SEO Expert opinion

Is this statement consistent with field observations?

Yes, absolutely. It has been observed for years that Twitter has never played the open PageRank game. The platform has consistently locked its links with nofollow to avoid becoming a link farm or draining its authority to external destinations uncontrolled.

SEOs who relied on Twitter embeds to improve their backlink profile have always been mistaken — and Mueller confirms this outright. What may be surprising is that Search Console sometimes displays these links in reports, creating confusion between "technically present link" and "SEO-active link." Let’s be clear: one does not imply the other.

What nuances are to be added to this general rule?

Mueller uses the term "generally no impact" — which leaves a door slightly open. In very rare cases, a nofollow link may still be followed by Google if the algorithm deems it provides strong contextual value (this is the principle of the "hint" introduced in 2019 with the evolution of nofollow). But don’t count on that for Twitter.

Furthermore, indirect impact does indeed exist. An embedded tweet that generates qualified traffic, increases time spent on the page, or enhances editorial credibility can positively influence your UX metrics — and thus, indirectly, your SEO. But this is a side effect, not a direct ranking mechanism linked to the link itself. [To be verified]: if the Twitter embed substantially alters the bounce rate or CTR in the SERPs, it could weigh on your behavioral signals.

In what cases does this information change your content strategy?

If you were embedding tweets in hopes of

Practical impact and recommendations

Que faut-il faire concrètement avec les tweets embarqués sur votre site ?

D'abord, ne les supprimez pas par principe si vous les utilisez déjà. Ils apportent une valeur éditoriale réelle : preuve sociale, citations d'autorité, actualité en temps réel. Gardez-les quand ils enrichissent véritablement votre contenu et améliorent l'expérience utilisateur.

Ensuite, optimisez leur impact indirect. Placez les embeds Twitter près de vos appels à action ou de vos liens internes stratégiques pour profiter de l'effet « attention captée ». Un témoignage client en tweet peut renforcer la conversion, même si le lien qu'il contient est nofollow. L'objectif : transformer la preuve sociale en engagement, pas en PageRank.

Quelles erreurs éviter absolument avec les embeds Twitter ?

Ne multipliez pas les embeds dans l'espoir de « gonfler artificiellement » votre profil de backlinks. Search Console peut afficher ces liens, mais ils ne vous servent à rien pour le ranking. Vous alourdissez votre page pour un bénéfice SEO nul.

Évitez aussi de surcharger vos articles avec trop d'embeds. Chaque script Twitter ajoute du poids, du JavaScript, et potentiellement du Cumulative Layout Shift (CLS) si le chargement décale votre mise en page. Testez vos Core Web Vitals après intégration et limitez-vous aux embeds vraiment pertinents. Si vous en avez 5 ou 6 par article, vous avez probablement un problème de stratégie éditoriale.

Comment vérifier que vos embeds Twitter ne nuisent pas à vos performances ?

Utilisez PageSpeed Insights et Lighthouse pour mesurer l'impact des scripts Twitter sur vos temps de chargement. Si votre LCP (Largest Contentful Paint) ou votre CLS explosent à cause des embeds, envisagez un chargement lazy (différé) ou une solution de prévisualisation statique cliquable.

Surveillez aussi vos métriques d'engagement dans Google Analytics : temps moyen sur la page, taux de rebond, profondeur de scroll. Si les embeds Twitter améliorent ces signaux, ils valent la peine d'être conservés — même sans bénéfice SEO direct lié aux liens. Si au contraire ils alourdissent la page sans améliorer l'UX, élaguez.

  • Ne comptez jamais sur les embeds Twitter pour votre stratégie de backlinks — leur valeur SEO directe est nulle
  • Limitez le nombre d'embeds par page pour préserver vos Core Web Vitals (LCP, CLS)
  • Placez les embeds stratégiquement près de vos CTA ou liens internes pour capter l'attention
  • Testez vos performances avec PageSpeed Insights après intégration d'un embed Twitter
  • Privilégiez le lazy loading si vous devez conserver plusieurs embeds pour des raisons éditoriales
  • Suivez vos métriques d'engagement dans Analytics pour valider l'impact indirect sur l'UX
Les embeds Twitter n'apportent aucun PageRank à votre site, même si Google les crawle et que Search Console les affiche. Leur valeur est purement éditoriale : preuve sociale, citation d'expert, fraîcheur du contenu. Utilisez-les avec parcimonie pour éviter de dégrader vos performances techniques. Si vous cherchez à structurer une stratégie de netlinking efficace tout en préservant vos Core Web Vitals, ces arbitrages peuvent s'avérer complexes à piloter seul — faire appel à une agence SEO spécialisée permet souvent d'identifier les bons leviers et d'éviter les fausses bonnes idées qui plombent votre budget crawl sans retour sur investissement.

❓ Frequently Asked Questions

Un lien dans un tweet embarqué apparaît dans Search Console, est-ce qu'il compte pour mon SEO ?
Non. Google peut techniquement crawler ce lien et l'afficher dans vos rapports, mais Twitter applique systématiquement rel="nofollow" sur tous ses liens. Aucun PageRank n'est transmis, même si le lien est visible dans vos données Search Console.
Les embeds Twitter ont-ils un impact indirect sur mon ranking ?
Potentiellement oui, via les signaux UX. Si un tweet embarqué améliore le temps passé sur la page, réduit le taux de rebond ou renforce la crédibilité éditoriale, cela peut influencer positivement votre SEO. Mais ce n'est pas un effet lié au lien lui-même.
Dois-je supprimer tous les tweets embarqués de mon site ?
Non, sauf s'ils alourdissent vos pages sans apporter de valeur éditoriale. Gardez les embeds qui enrichissent votre contenu (citations d'experts, témoignages, preuves sociales) mais éliminez ceux qui sont là uniquement pour « faire du lien ».
Les embeds Twitter ralentissent-ils mes Core Web Vitals ?
Oui, s'ils sont nombreux ou mal optimisés. Chaque embed charge du JavaScript et peut provoquer du Cumulative Layout Shift (CLS). Testez avec PageSpeed Insights et privilégiez le lazy loading si nécessaire.
Google traite-t-il différemment les liens nofollow depuis 2019 ?
Depuis 2019, Google considère rel="nofollow" comme un « hint » (indice) plutôt qu'une directive absolue. En théorie, Google peut choisir de suivre un lien nofollow s'il le juge pertinent. Mais en pratique, Twitter reste verrouillé et ces liens ne transmettent aucun PageRank observable.

🎥 From the same video 49

Other SEO insights extracted from this same Google Search Central video · duration 55 min · published on 21/08/2020

🎥 Watch the full video on YouTube →

💬 Comments (0)

Be the first to comment.

2000 characters remaining
🔔

Get real-time analysis of the latest Google SEO declarations

Be the first to know every time a new official Google statement drops — with full expert analysis.

No spam. Unsubscribe in one click.