Date: 07/13/2026 - Upvotes : 61 - Words : 352
World Cup drives Google Search to record queries per second
World Cup drives Google Search to record queries per second
Source: https://www.cnbc.com/2026/07/08/world-cup-drives-google-search-to-record-queries-per-second.html
Argentina’s forward #10 Lionel Messi kicks the ball during the Qatar 2022 World Cup final football match between Argentina and France at Lusail Stadium in Lusail, north of Doha on December 18, 2022. Kirill Kudryavtsev | Afp | Getty ImagesAlphabet-owned Google broke a search record thanks to the World Cup international soccer tournament.During the knockout World Cup round Tuesday, Argentina’s national team mounted a late comeback where Cristian Romero scored a goal then Lionel Messi equalized with his own goal in the 83rd minute for the win.“Google Search broke all prior usage records and saw its highest usage in history right after Argentina scored their winning goal in yesterday’s match” wrote Nick Fox, head of Google’s Knowledge and Information unit Wednesday.A company spokesperson did not share specific numbers but told CNBC “we saw the most queries per second happen right after the winning goal.”The milestone comes as the company tries to prove its traditional search engine can keep its relevance in the age of AI, where chatbots have become more prevalent. Google still controls 90% of the search market, its stock price has more than doubled in the past year and revenue growth in the first quarter was the fastest for any period since 2022.Google said its top searched query after the game was “argentina vs egypt.”Globally, the company also saw people searching for things like “argentina x colombia” and “how many world cup goals does messi have.” Additional queries included “what is it called when a player hits another player in game” and “is it messi’s last world cup.”
🔐 Cryptographic Verification
Archived URL: https://www.cnbc.com/2026/07/08/world-cup-drives-google-search-to-record-queries-per-second.html
📄 CONTENT HASHES:
SHA-256: 333c094a0eeabd68242d810144be384b191e1c0a67b597a002ea8163f5a0defa
BLAKE2b: f93df4db4bfe28c5c4959b93b22ada6a3858f4ac0b567d1eacc4a6ef23d6bee4
MD5: 2dd2ac6707ed1fb7c999ed7c0cf2b9a2
📝 TITLE HASHES:
SHA-256: a3bbe34c93ad0d017223643f0f296af537d0ba033d8a8e00e5de6a9412ae94d9
BLAKE2b: b794c2fe6d9c0fcdb4200097850743a7091aab3aa5d6bcf80435ee3a7fd43c09
MD5: 473125b7901a2a9eb9fd5d93c4fe9c57
🔒 INTEGRITY HASHES:
SHA-256: f8c69e6d686643cdbc316435e0a78a97751237efc18b60b47102155e0272e068
BLAKE2b: 9ec7410bf44375dfe0949cfc3b622922ebbf576a794512413b20e5621a9d2b55
MD5: 246a4a547e040beb24a33e4239511950
Archived with ArcHive - Client-side cryptographic archival system
