Co-founder @1492_vision | Research Google Discover Student korean & Japanese language. Google's Bug Hunter 🐛 Python Developer. 😍 Korea & Japan

鹿児島市
Joined September 2023
We published a detailed article on how Google Discover changed its cards in 2026, from 7 months of monitoring: See here 👇 linkedin.com/pulse/inside-go… 🧩 one Knowledge Graph entity picked per reader 🔎 rotating topics from Google's public taxonomy 🔁 a September shift in the related feed 📈 which score now predicts the click A RT or a share would mean a lot: this was months of R&D and real work 🙏 CC @gaganghotra_ @glenngabe @rustybrick @lilyraynyc @fabienr34 @VorticonCmdr @suganthan #googlediscover
4
15
2
29
4,766
Damien Andell retweeted
🆕 We've published a comprehensive article (we've been working on it for weeks) on @1492_Vision about SDF: Google Discover removes outdated articles before even ranking them. A Google paper for the CIKM 2026 conference describes this system, SDF, as "fully deployed in Google Discover." We compared it to our Discover data 👇 1492.vision/research/discove… What the paper describes: 🔁 Filter 1: An article is removed when a newer article on the same topic replaces it, like a pre-game preview once the result is known. ⏳ Filter 2: A model predicts the proportion of its lifetime traffic that an article has already received. At 90%, the article is removed. 📉 Only one filter is needed, and the article never makes it to ranking. In two years, "outdated" reports have decreased by 54.9%. What we see in our data: 🏀 Some still get through: pre-game content for the Michigan-UConn final was served more than 15 hours after the game ended. 📅 The articles displayed are rarely more than two days old, and their audience drops off after three days. Regarding scores: 🎯 A score called topic potential (from 0 to 1) seems to estimate the engagement an article can expect, across all readers. It depends more on the topic than the publisher and says nothing about quality. 🚪 It acts as an entry threshold: below approximately 0.10 to 0.12, an article was rarely amplified before July. Predicted engagement scores, specific to each reader, then determine the level of amplification. 📊 During the week of June 30th, several Discover scores changed, and the potential score dropped by about a quarter until October. This coincides with the beginning of the decline in reach noted in our logbook. 🧭 SDF was already running at the beginning of 2026: on its own, it doesn't fully explain this decline. It sheds light on its form: the articles retain their best day but lose their end-of-life. CC @gaganghotra_ @VorticonCmdr @nicola_agius @ClaraSoteras #googlediscover
A pre-game card, served three minutes after the result and more than fifteen hours after the final buzzer. Google's own paper describes the Discover filter meant to catch it, and we compared it with our feeds. 1492.vision/research/discove… The paper: two models. One spots the article a newer story has replaced, the other removes an article once it has received 90% of its expected lifetime traffic. Stale reports fell by 54.9% over two years. Our feeds: an article's audience drops after its third day. For the same publisher, the peak audience per article fell by about a third between May-June and August-September (0.68 in our English-language feeds). The topic potential score we track lost a quarter from the week of June 29, when several Discover scores changed at once. The filter already ran in early 2026, so it explains little of the drop on its own. It matches its shape: articles keep their best day and lose the days after it. Six takeaways for publishers, including: publish the update yourself, and keep "tonight" for news content.
5
10
757
A pre-game card, served three minutes after the result and more than fifteen hours after the final buzzer. Google's own paper describes the Discover filter meant to catch it, and we compared it with our feeds. 1492.vision/research/discove… The paper: two models. One spots the article a newer story has replaced, the other removes an article once it has received 90% of its expected lifetime traffic. Stale reports fell by 54.9% over two years. Our feeds: an article's audience drops after its third day. For the same publisher, the peak audience per article fell by about a third between May-June and August-September (0.68 in our English-language feeds). The topic potential score we track lost a quarter from the week of June 29, when several Discover scores changed at once. The filter already ran in early 2026, so it explains little of the drop on its own. It matches its shape: articles keep their best day and lose the days after it. Six takeaways for publishers, including: publish the update yourself, and keep "tonight" for news content.
3
1
6
10,997
🆕 We've published a comprehensive article (we've been working on it for weeks) on @1492_Vision about SDF: Google Discover removes outdated articles before even ranking them. A Google paper for the CIKM 2026 conference describes this system, SDF, as "fully deployed in Google Discover." We compared it to our Discover data 👇 1492.vision/research/discove… What the paper describes: 🔁 Filter 1: An article is removed when a newer article on the same topic replaces it, like a pre-game preview once the result is known. ⏳ Filter 2: A model predicts the proportion of its lifetime traffic that an article has already received. At 90%, the article is removed. 📉 Only one filter is needed, and the article never makes it to ranking. In two years, "outdated" reports have decreased by 54.9%. What we see in our data: 🏀 Some still get through: pre-game content for the Michigan-UConn final was served more than 15 hours after the game ended. 📅 The articles displayed are rarely more than two days old, and their audience drops off after three days. Regarding scores: 🎯 A score called topic potential (from 0 to 1) seems to estimate the engagement an article can expect, across all readers. It depends more on the topic than the publisher and says nothing about quality. 🚪 It acts as an entry threshold: below approximately 0.10 to 0.12, an article was rarely amplified before July. Predicted engagement scores, specific to each reader, then determine the level of amplification. 📊 During the week of June 30th, several Discover scores changed, and the potential score dropped by about a quarter until October. This coincides with the beginning of the decline in reach noted in our logbook. 🧭 SDF was already running at the beginning of 2026: on its own, it doesn't fully explain this decline. It sheds light on its form: the articles retain their best day but lose their end-of-life. CC @gaganghotra_ @VorticonCmdr @nicola_agius @ClaraSoteras #googlediscover
A pre-game card, served three minutes after the result and more than fifteen hours after the final buzzer. Google's own paper describes the Discover filter meant to catch it, and we compared it with our feeds. 1492.vision/research/discove… The paper: two models. One spots the article a newer story has replaced, the other removes an article once it has received 90% of its expected lifetime traffic. Stale reports fell by 54.9% over two years. Our feeds: an article's audience drops after its third day. For the same publisher, the peak audience per article fell by about a third between May-June and August-September (0.68 in our English-language feeds). The topic potential score we track lost a quarter from the week of June 29, when several Discover scores changed at once. The filter already ran in early 2026, so it explains little of the drop on its own. It matches its shape: articles keep their best day and lose the days after it. Six takeaways for publishers, including: publish the update yourself, and keep "tonight" for news content.
5
10
757
Damien Andell retweeted
Google just doesn’t even care anymore
Google Discover has just started a test on AI summaries: Disabling clicks on sources. Behavior before this test: Clicking on the sources at the bottom of an AI summary card opened a mini-feed with articles from the sources of the AI ​​summary. With the test, we have the flag: disable_aio_sources_button_tap This disables clicks on sources and no longer opens the mini-feed with articles from the AI ​​summary's sources. CC @gaganghotra_ @rustybrick @nicola_agius #googlediscover
7
8
1
74
6,971
Google Discover has just started a test on AI summaries: Disabling clicks on sources. Behavior before this test: Clicking on the sources at the bottom of an AI summary card opened a mini-feed with articles from the sources of the AI ​​summary. With the test, we have the flag: disable_aio_sources_button_tap This disables clicks on sources and no longer opens the mini-feed with articles from the AI ​​summary's sources. CC @gaganghotra_ @rustybrick @nicola_agius #googlediscover
3
9
3
35
9,485
New paper and analisis #Discover about SDF 1492.vision/research/discove… ✍️ @AndellDam
Et si le problème de Google #Discover n'était pas seulement d'obtenir de la visibilité, mais de la conserver ? Les observations de cet outil posent LA question sur la durée d'exposition des articles. J'ai confronté données aux travaux publiés par Google. Quelques surprises 👇
1
1
5
284
🆕 On a publié un gros article complet (on y travaille depuis des semaines) sur @1492_Vision sur le SDF : Google Discover retire les articles périmés avant même de les classer. Un papier de Google pour la conférence CIKM 2026 décrit ce système, SDF, « fully deployed in Google Discover ». On l'a confronté à nos données Discover 👇 1492.vision/research/discove… Ce que décrit le papier : 🔁 Filtre 1 : un article est retiré quand un article plus récent sur le même sujet le remplace, comme un avant-match une fois le résultat connu. ⏳ Filtre 2 : un modèle prédit la part de son trafic de vie qu'un article a déjà reçue. À 90 %, l'article est retiré. 📉 Un seul filtre suffit, et l'article n'arrive jamais au classement. En deux ans, les signalements « périmé » ont baissé de 54,9 %. Ce qu'on voit dans nos données : 🏀 Certains passent quand même : des avant-matchs de la finale Michigan-UConn ont été servis plus de 15 heures après la fin du match. 📅 Les articles affichés ont rarement plus de deux jours, et leur audience décroche après trois jours. Côté scores : 🎯 Un score qu'on appelle potentiel de sujet (de 0 à 1) semble estimer l'engagement qu'un article peut attendre, tous lecteurs confondus. Il dépend plus du sujet que de l'éditeur, et ne dit rien de la qualité. 🚪 Il fonctionne comme un seuil d'entrée : sous 0,10 à 0,12 environ, un article était rarement amplifié avant juillet. Les scores d'engagement prédit, propres à chaque lecteur, fixent ensuite le niveau d'amplification. 📊 La semaine du 30 juin, plusieurs scores de Discover changent, et le score de potentiel baisse d'environ un quart jusqu'en octobre. Cela coïncide avec le début de la baisse de portée relevée par notre journal de bord. 🧭 SDF tournait déjà début 2026 : seul, il explique mal cette baisse. Il en éclaire la forme : les articles gardent leur meilleur jour et perdent leur fin de vie. #googlediscover
Google décrit dans un papier le filtre qui retire de Discover les articles périmés, avant même le classement. Nous l'avons confronté à nos fils Discover, et nos données vont plus loin que le papier. 1492.vision/research/discove… Le papier : deux modèles. L'un repère l'article qu'une actualité plus récente a remplacé, l'autre retire un article dès qu'il a reçu 90 % de son trafic prévu. Les signalements « périmé » ont baissé de 54,9 % en deux ans. Nos fils : l'audience d'un article décroche après le troisième jour. Chez un même éditeur, l'audience maximale d'un article a baissé d'un tiers entre mai-juin et août-septembre. Le score de potentiel que nous suivons a perdu un quart à partir de la semaine du 29 juin, quand plusieurs scores de Discover ont changé en même temps. Le filtre a ses ratés : dans un fil américain, un avant-match servi trois minutes après le résultat, plus de quinze heures après la fin du match. Six pistes pour les éditeurs, un extrait : publiez vous-même la mise à jour, et réservez « ce soir » aux contenus d'actualité.
4
2
5
1,090
🆕 Our research on Google Discover cards in 2026 is now on @1492_Vision. First published on LinkedIn on October 15, here with a reviewed, clearer text 👇 1492.vision/research/discove… What we found after 7 months of monitoring: 🧩 One entity per reader: same article, same day, two readers get a different Knowledge Graph entity in 65% of cases. It follows their reading history (63%) far more than their declared interests (4%). 🌐 Chrome sync: visited pages are tagged at two levels, detailed entities (Microsoft, Linux...) and broad topic categories (Software, Security...). Only the categories are synced with your history, from a score of 85/100. Detailed entities never are. The per-reader entity is almost always a detailed one. 🔎 Rotating topics: up to five topics per card, from Google's public taxonomy (the one used by Ads, Trends and the Natural Language API). The first topic holds, ranks 4 and 5 rotate over time. 📈 Click prediction: among the prediction scores on each card, one we read as an engagement score (f22.8) is now the best click predictor in our panel. The score most tied to the boost (f22.2) is no longer the one that best follows clicks. 🔁 Related feed: in September, a related pipeline answered likes and see mores for three weeks, then stopped. The click is still what opens the classic related cards. CC @gaganghotra_ @rustybrick @VorticonCmdr @nicola_agius #googlediscover
2
7
16
931
Interestingly, Google is changing the documentation for Tailor Your Feed on Google Discover: The title, "Get started with Tailor your feed in Google Discover," is now "Add topics to your Discover feed using your own words." So the term "Tailor Your feed" is no longer used. Then, they're changing the phrases "ask for a new topic, more info..." to "add, refine, remove topics or content types." This is to make it clear that you can also remove content you don't like from the Discover feed via their AI chat. In fact, the term "chatbot" is now "AI chat agent." CC @gaganghotra_ @rustybrick #googlediscover
1
2
1
14
1,568
Damien Andell retweeted
Wooow !! allé laaaaa ! Notre dernière vidéo @obistrotech avec @AndellDam apparait dans le flux discover ! DINGUE ! Vous l'avez pas encore vu ? Vous devriez... 😉
La vidéo @obistrotech sur Google Discover
2
2
6
520
Pour la faille Gooogle Discover dont je parle sur la vidéo avec @obistrotech Voici en image ce que cela donne sur la search console de google pour discover : Impressions 54K Clics 54k CTR 100%
1
3
1
25
2,058
Cool cette apparition de Damien en public. Un maestro en R&D Google Discover. Comptes X à suivre xitter.cf/AndellDam et xitter.cf/SylvainDeaure Google Discover : il trouve une faille… et la signale à Google | Bistro ... youtu.be/tXlnKZ_kKHQ?si=cDo6… via @YouTube
2
2
7
189
Demain la vidéo sort chez @obistrotech Je discute avec @kaostyl et @sidequestforevr sur : - Les entités - Google Discover (scoring, ranking) - Faille discover - Google Images Etc ...
Les Amis demain on vous sort @obistrotech un espèce de podcast avec @AndellDam (Co créateur de @1492_Vision) et @sidequestforevr sur le sujet Google Discover je pense que vous allez vous Ré Ga Ler !! Soyez la c'est demain Midi sur la chaine @obistrotech !! Et franchement c'est une Exclu d'avoir Damien en Podcast 😍 Merci encore @AndellDam d'avoir répondu présent c'était trop trop cool !
4
1
2
24
2,156
Demain la vidéo sort chez @obistrotech Je discute avec @kaostyl et @sidequestforevr sur : - Les entités - Google Discover (scoring, ranking) - Faille discover - Google Images Etc ...
1
2
7
857
Le podcast tourné ce matin vas être mémorable ! On a eu l'honneur d'accueillir le boss de discover @AndellDam dans le @obistrotech qui sort demain 🤩💪 Merci pour la confiance et pour nous avoir fait le plaisir de ça présence lui qui est (trop) peu présent sur la scène public Franchement ya du niveau ! Impatient d'avoir vos retours
1
3
15
617
I can confirm that Google Discover is having trouble classifying the language of Threads posts. Using actu.fr, on a Discover feed configured for English only, I'm getting a French Threads post, and when I look at how Google identifies the card's language, it says: Content Language = EN CC @gaganghotra_ @rustybrick @nicola_agius #googlediscover
Google Discover is having trouble detecting the language of some Threads posts. We've been seeing this for several days now: in a 100% English Discover feed, French cards are appearing where they shouldn't. This is happening mainly with publishers followed via the "search profile". #googlediscover
2
1
7
828
Just to clarify, the problem comes from the "search profile" because I "follow" the site @actufr so it offers Threads posts on my feed because it identifies these posts as being in English.
1
148