aurman commited on
Commit
0a1a907
·
verified ·
1 Parent(s): e08b144

Create README.md

Browse files
Files changed (1) hide show
  1. README.md +200 -0
README.md ADDED
@@ -0,0 +1,200 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: cc-by-4.0
3
+ task_categories:
4
+ - text-classification
5
+ - time-series-forecasting
6
+ language:
7
+ - en
8
+ - multilingual
9
+ tags:
10
+ - google-trends
11
+ - trending-now
12
+ - attention-dynamics
13
+ - information-diffusion
14
+ - temporal-analysis
15
+ - search-trends
16
+ size_categories:
17
+ - 1M<n<10M
18
+ pretty_name: Google Trend Archive
19
+ ---
20
+
21
+ # Google Trend Archive: Global Real-Time Search Trends (2024-2026)
22
+
23
+ ## Dataset Details
24
+
25
+ ### Dataset Description
26
+
27
+ This dataset contains over **7.6 million trending search instances** from Google's Trending Now feature, collected continuously from November 28, 2024 to January 3, 2026 across all available geographic locations (200+ countries/regions). Unlike aggregated retrospective tools like Google Trends, Trending Now captures search queries experiencing real-time surges, offering unprecedented temporal granularity for studying collective attention dynamics.
28
+
29
+ Each instance represents a moment when specific search terms or query clusters became "trending" according to Google's algorithm, complete with search volume buckets, precise timestamps, trend durations, geographic locations, and related query variations.
30
+
31
+ - **Curated by:** Aleksandra Urman, Anikó Hannák, Joachim Baumann (Social Computing Group, University of Zurich & Stanford Artificial Intelligence Laboratory)
32
+ - **Language(s):** Multilingual
33
+ - **License:** CC-BY-4.0
34
+ - **DOI:** https://doi.org/10.57967/hf/7531
35
+
36
+ ### Dataset Sources
37
+
38
+ - **Repository:** https://huggingface.co/datasets/aurman/GoogleTrendArchive
39
+ - **Contact:** urman@ifi.uzh.ch
40
+
41
+ ## Uses
42
+
43
+ ### Direct Use
44
+
45
+ This dataset enables research across multiple domains:
46
+
47
+ - **Information Diffusion Modeling**: Track how topics cascade across geographic regions and analyze diffusion pathways
48
+ - **Event Detection**: Identify breaking news, crises, and significant events from search surge patterns
49
+ - **Comparative Cultural Studies**: Analyze differences in collective attention across countries and cultures
50
+ - **Crisis Communication**: Understand information needs during emergencies
51
+ - **Temporal Pattern Analysis**: Study daily, weekly, and seasonal rhythms in collective attention
52
+ - **Predictive Modeling**: Develop models to forecast trend emergence, duration, and spread
53
+ - **Media Ecosystem Analysis**: Compare search trends with social media and news coverage
54
+ - **Political Communication**: Examine attention to political topics across different political systems
55
+
56
+ ### Out-of-Scope Use
57
+
58
+ The dataset should **not** be used for:
59
+
60
+ - **Surveillance or monitoring** of specific populations
61
+ - **Marketing or commercial targeting** (intended for academic research only)
62
+ - **Drawing deterministic conclusions** about population beliefs (search shows information-seeking, not settled beliefs)
63
+ - **Identifying or tracking individuals** (data is aggregated, but de-anonymization attempts would violate ethical norms)
64
+ - **Training models for harmful applications** (discrimination, manipulation, surveillance)
65
+
66
+ ## Dataset Structure
67
+
68
+ Each instance contains six fields:
69
+
70
+ 1. **Trend Identifier**: The search query or representative term for a cluster of related queries (e.g., "man united vs bodø/glimt")
71
+ 2. **Search Volume**: Bucketed traffic ranges (e.g., "100+", "50K+", "2M+") indicating approximate search volume
72
+ 3. **Start Timestamp**: When Google's system first flagged the trend as emerging (ISO format with timezone)
73
+ 4. **End Timestamp**: When the trend ended and returned to baseline (ISO format with timezone)
74
+ 5. **Trend Breakdown**: Comma-separated list of related query variations that Google clustered together
75
+ 6. **Explore Link**: URL to the corresponding Google Trends page for further investigation
76
+
77
+ **Total Instances**: 7,600,000+ trending searches
78
+ **Temporal Coverage**: November 28, 2024 - January 3, 2026 (with ~14 days of gaps due to technical issues)
79
+ **Geographic Coverage**: 1358 countries and regions
80
+ **Format**: CSV files with UTF-8 encoding
81
+
82
+ ## Dataset Creation
83
+
84
+ ### Curation Rationale
85
+
86
+ This dataset is a comprehensive archive of Google Trending Now data spanning over one year (from November 28, 2024 to January 3, 2026) across all available geographic locations. Unlike aggregated retrospective tools like Google Trends, Trending Now captures search queries experiencing real-time surges, offering temporal granularity for studying collective attention dynamics --- however, this data is not available retrospectively through Google directly. Our dataset addresses this gap by presenting an archive of Trending Now data.
87
+
88
+ ### Source Data
89
+
90
+ #### Data Collection and Processing
91
+
92
+ Data was collected using automated software that continuously monitored Google Trends Trending Now pages (e.g., https://trends.google.com/trending?geo=US) for all available geographic locations from November 28, 2024 onward.
93
+
94
+ **Validation procedures included:**
95
+ - Automated checks for data completeness across time periods and locations
96
+ - Verification of timestamp consistency
97
+ - Deduplication to handle multiply-collected trends
98
+ - Comparison against manually spot-checked trends
99
+ - Logging of collection failures (~14 days of gaps)
100
+
101
+ **Preprocessing steps:**
102
+ - Timestamp standardization to ISO 8601 format with timezone information
103
+ - Duration calculation from start/end timestamps
104
+ - Geographic code standardization
105
+ - Format consolidation from daily files into unified dataset
106
+ - Data validation and quality checks
107
+
108
+ All preprocessing code and raw data files are available in the repository for transparency and replication.
109
+
110
+ #### Who are the source data producers?
111
+
112
+ Google's Trending Now system, which aggregates and anonymizes search activity from Google users worldwide.
113
+
114
+ ### Personal and Sensitive Information
115
+
116
+ **No personally identifiable information is included.**
117
+
118
+ ## Bias, Risks, and Limitations
119
+
120
+ **Technical Limitations:**
121
+ - Search volumes provided in buckets rather than exact counts
122
+ - Google's trend identification algorithm is proprietary (clustering and thresholding decisions not transparent)
123
+ - ~14 days of missing data due to technical collection issues
124
+ - Trends represent relative surges, not absolute search volumes
125
+ - Some trends may have estimated rather than actual end dates
126
+
127
+ **Representativeness Issues:**
128
+ - Search behavior does not uniformly represent entire populations
129
+ - Digital divides and varying internet penetration mean certain demographics are over/underrepresented
130
+ - Search engine market share varies by country (Google dominance differs across regions)
131
+ - Geographic coverage limited to locations where Google provides Trending Now data
132
+
133
+ **Algorithmic Mediation:**
134
+ - Google determines what qualifies as "trending" using proprietary algorithms
135
+ - Content filtering based on Google's policies may exclude certain trends
136
+ - Reflects Google's selection of notable search spikes, not all search activity
137
+
138
+ **Interpretation Risks:**
139
+ - Search trends show what people search for, not why they search or what they conclude
140
+ - Risk of drawing inappropriate generalizations or stereotypes about populations
141
+ - Patterns in sensitive topics (health, politics) could stigmatize communities
142
+ - Missing social context can lead to misinterpretation
143
+
144
+ ### Recommendations
145
+
146
+ Users should:
147
+ - Acknowledge representativeness limitations in cross-country comparisons
148
+ - Account for structural inequalities in internet access when interpreting patterns
149
+ - Avoid causal claims without additional evidence
150
+ - Exercise caution when analyzing/presenting sensitive topics
151
+ - Consider social context when interpreting collective attention patterns
152
+ - Present findings with appropriate epistemic humility
153
+ - Recognize this represents one platform's perspective on collective attention
154
+
155
+ ## Citation
156
+
157
+ **BibTeX:**
158
+ ```bibtex
159
+ @dataset{urman2026googletrendarchive,
160
+ title={Google Trend Archive: Global Real-Time Search Trends},
161
+ author={Urman, Aleksandra and Hann{\'a}k, Anik{\'o} and Baumann, Joachim},
162
+ year={2026},
163
+ publisher={Hugging Face},
164
+ doi={10.57967/hf/7531},
165
+ url={https://huggingface.co/datasets/aurman/GoogleTrendArchive}
166
+ }
167
+ ```
168
+
169
+ **APA:**
170
+
171
+ Urman, A., Hannák, A., & Baumann, J. (2026). *Google Trend Archive: Global Real-Time Search Trends* [Dataset]. Hugging Face. https://doi.org/10.57967/hf/7531
172
+
173
+ ## More Information
174
+
175
+ ### Funding
176
+
177
+ Research activities during dataset construction received support from:
178
+ - Swiss National Science Foundation – PostDoc Mobility fellowship P500-2 235328 (JB)
179
+ - SNSF Project Grant 215354 (AU and AH)
180
+
181
+ ### Maintenance
182
+
183
+ The dataset is hosted on Hugging Face and maintained by the authors. The current release represents a snapshot from November 28, 2024 to January 3, 2026. **Updates are planned every 2-3 months** as data collection is ongoing, communicated through changelogs in the repository.
184
+
185
+ All versions will be permanently archived and accessible through Hugging Face's versioning system to ensure reproducibility.
186
+
187
+ ### Contributions
188
+
189
+ We welcome community contributions:
190
+ - **Derived datasets**: Researchers adding annotations or features are encouraged to share as separate datasets with attribution
191
+ - **Corrections**: Report errors to urman@ifi.uzh.ch for review and incorporation into updated versions
192
+ - **Extensions**: Researchers collecting additional data using our methodology may collaborate on future releases
193
+
194
+ ## Dataset Card Authors
195
+
196
+ Aleksandra Urman, Anikó Hannák, Joachim Baumann
197
+
198
+ ## Dataset Card Contact
199
+
200
+ urman@ifi.uzh.ch