Urgent.News

What's breaking now, across hundreds of outlets.

Tech

How to track what is trending on Google right now, per country

You want to know what people in a given country are searching for right now, so you can write about a topic or time a campaign while it is rising. Google publishes this as an RSS feed per country, and you can read it with the Python standard library. The feed GET https://trends.google.com/trending/rss?geo=US returns RSS 2.0 with an extra ht: namespace ( https://trends.google.com/trending/rss ).…

To track trending topics on Google by country, follow these steps:

1. Use the RSS feed provided by Google at https://trends.google.com/trending/rss?geo=US, replacing 'US' with the desired country code (e.g., GB for United Kingdom, DE for Germany, JP for Japan).

2. Read the RSS feed using Python's standard library, specifically the urllib.request and xml.etree.ElementTree modules.

3. Each RSS item contains the search query (title), traffic estimate (approx_traffic), publish date (pubDate), plus up to three associated news stories with their titles, URLs, sources, and images.

4. The traffic estimate is represented as a bucket label (e.g., "200+", "20K+", "1M+"), which the traffic() function converts into its lower bound (e.g., 200, 20,000, 1,000,000).

5. Parse the pubDate to convert it to UTC using Python's datetime module. The feed is sorted by start time, with the newest trends appearing first.

6. Only the 10 most recent trends per country are returned in each feed. Polling the feed every 15 to 30 minutes ensures you don't miss any trends, as the feed is updated frequently.

7. Note that the feed does not include category information, end time, growth figures, related queries, or rank based on popularity; it is sorted only by recency.

8. Keep in mind that the feed may return varying numbers of trends (e.g., 10 trends in one pull, 3 trends in another).

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Headless UI for Beginners: Accessible Components Without the Styling

Building a dropdown or a modal sounds simple until you try to do it properly. Keyboard navigation, focus trapping, screen reader announcements, closing on Escape — accessibility is a long checklist.

  • Headless UI provides accessible components without styling.
  • Implement dropdown using Menu, Menu.Button, Menu.Items, Menu.Item components.
  • Headless UI handles keyboard interactions automatically.

I let a script audit my own product copy — it caught three lies

I run a small store that sells digital kits for people running LLM agents — eval suites, ops runbooks, prompt libraries. Every product page makes claims: "62 prompts," "10 skills," "12 runbooks." Last…

  • Store owner wrote script to audit product copy
  • Found three instances of false claims in descriptions
  • Audit process compares numbers in copy to actual files

No Algorithm Lock-In: Why a Chronological On-Chain Feed Is Regulation-Proof by Design

Governments are moving to force social platforms to offer a chronological, non-algorithmic feed option. On iBird, chronology is not a compliance setting — it is the substrate.

  • iBird platform on Hedera offers chronological feed unaltered by algorithms
  • Each post includes consensus timestamp and immutable sequence number
  • Consensus layer ensures publicly verifiable, non-revocable chronological feed

Large log records in Dynatrace: limits, native support and best practices

A ticket lands: « the partner call is cut off halfway through in the logs ». You open the record and it simply stops. The payload crossed a limit somewhere.

  • Default log entry body limit is 10 MB for Grail path, 512 kB for Classic pipeline
  • API requests limited to 10 MB, batch over 16 MB after preprocessing results in HTTP 413 error
  • OpenPipeline expands record size limit to 16 MB, 50,000 attributes per log with 32 kB cap

More from Saturday 21 November →