<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: carlos-calatayud</title>
    <description>The latest articles on DEV Community by carlos-calatayud (@carloscalatayud).</description>
    <link>https://dev.to/carloscalatayud</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4194833%2F083573db-879e-495f-8add-e2c8f51120dc.png</url>
      <title>DEV Community: carlos-calatayud</title>
      <link>https://dev.to/carloscalatayud</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/carloscalatayud"/>
    <language>en</language>
    <item>
      <title>How to compare 100 Google Trends keywords on one 0-100 scale (beyond the 5-term limit)</title>
      <dc:creator>carlos-calatayud</dc:creator>
      <pubDate>Mon, 19 Oct 2026 19:53:26 +0000</pubDate>
      <link>https://dev.to/carloscalatayud/how-to-compare-100-google-trends-keywords-on-one-0-100-scale-beyond-the-5-term-limit-1fii</link>
      <guid>https://dev.to/carloscalatayud/how-to-compare-100-google-trends-keywords-on-one-0-100-scale-beyond-the-5-term-limit-1fii</guid>
      <description>&lt;p&gt;Google Trends is the go-to free source for "which of these is more popular?". But it has two limits that break any serious keyword research:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Max 5 terms per comparison.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Each request is rescaled to its own maximum = 100.&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;So if you export 20 batches of 5 keywords and paste them together, a "50" in batch 1 and a "50" in batch 7 are different things. In a simulation with known ground truth (Google-style rescaling + integer rounding), that naive concatenation was off by &lt;strong&gt;more than 20 index points&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The method: anchor chaining
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Query the first 5 keywords and pick a &lt;strong&gt;mid-popularity anchor&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Query every other keyword as &lt;em&gt;anchor + 4 others&lt;/em&gt;. The anchor gives you the ratio between batches.&lt;/li&gt;
&lt;li&gt;Problem: if a keyword is 1,000x smaller than the anchor, Google rounds it to 0 or "&amp;lt;1". So keywords with poor precision are &lt;strong&gt;re-measured in overlapping batches&lt;/strong&gt; with keywords of similar size, building a chain of anchors.&lt;/li&gt;
&lt;li&gt;Solve &lt;strong&gt;one scale factor per batch with weighted least squares&lt;/strong&gt; over all shared keywords (weights come from rounding precision, so a series summing to 3 counts far less than one summing to 3,000).&lt;/li&gt;
&lt;li&gt;Rescale so the global maximum is 100.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Self-check:&lt;/strong&gt; take 5 keywords that were measured in different batches, query them directly together and compare with the chained values.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Measured accuracy (real runs)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fs7okhpmwh5olhoxmm3cq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fs7okhpmwh5olhoxmm3cq.png" alt="6 of 100 keywords on one Google Trends scale" width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Run&lt;/th&gt;
&lt;th&gt;Keywords&lt;/th&gt;
&lt;th&gt;Self-check mean abs. error (0-100)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Worldwide, 5 years&lt;/td&gt;
&lt;td&gt;100&lt;/td&gt;
&lt;td&gt;0.187 points (max 1.01)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;US-CA, 2024, YouTube&lt;/td&gt;
&lt;td&gt;25&lt;/td&gt;
&lt;td&gt;0.149 points&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;US, 12 months, cloud + residential proxy&lt;/td&gt;
&lt;td&gt;25&lt;/td&gt;
&lt;td&gt;0.592 points&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Under 1 point on a 0-100 scale, versus 20+ points for naive concatenation. Google samples its data, so a small error is expected even between two identical queries.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;I packaged this as an Apify Actor: &lt;strong&gt;&lt;a href="https://apify.com/satin_armeria/google-trends-advanced-comparator" rel="noopener noreferrer"&gt;Google Trends Scraper – Compare 100 Keywords&lt;/a&gt;&lt;/strong&gt;. Country/region/metro, preset or custom dates, Web/YouTube/News/Images/Shopping, CSV/JSON output, and the self-check report in every run.&lt;/p&gt;

&lt;p&gt;A minimal Python example (12 keywords, prints the self-check error and saves a chart) is on GitHub: &lt;strong&gt;&lt;a href="https://github.com/carlos-calatayud/google-trends-compare-100-keywords" rel="noopener noreferrer"&gt;https://github.com/carlos-calatayud/google-trends-compare-100-keywords&lt;/a&gt;&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;from&lt;/span&gt; &lt;span class="n"&gt;apify_client&lt;/span&gt; &lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;ApifyClient&lt;/span&gt;
&lt;span class="n"&gt;client&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;ApifyClient&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;&amp;lt;YOUR_APIFY_TOKEN&amp;gt;&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;run&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;actor&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;satin_armeria/google-trends-advanced-comparator&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;call&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;run_input&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;keywords&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;chatgpt&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;claude&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;gemini&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;perplexity&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;copilot&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;midjourney&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;geo&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;""&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;timeframe&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;today 12-m&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;})&lt;/span&gt;
&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;row&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;dataset&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;run&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;defaultDatasetId&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]).&lt;/span&gt;&lt;span class="nf"&gt;iterate_items&lt;/span&gt;&lt;span class="p"&gt;():&lt;/span&gt;
    &lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;row&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What it costs
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;$4 per 1,000 keywords compared&lt;/strong&gt; ($0.004 each) plus a $0.00005 start fee. Keywords that fail or return no data are not charged. 100 keywords ≈ $0.40; the 12-keyword example ≈ $0.05. Apify's free plan includes $5/month of credit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limitations (honest)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Not an official Google API; data is sampled and can vary slightly between runs.&lt;/li&gt;
&lt;li&gt;Extremely small keywords next to huge ones may still return "no data".&lt;/li&gt;
&lt;li&gt;A 100-keyword run takes a few minutes because requests are throttled politely to avoid rate limits.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Feedback on the method is welcome — especially edge cases where the chain breaks.&lt;/p&gt;

</description>
      <category>python</category>
      <category>seo</category>
      <category>datascience</category>
      <category>webscraping</category>
    </item>
  </channel>
</rss>
