Urgent.News

What's breaking now, across thousands of outlets.

Tech

My most-read page has 1,322,170 reads. My site has had 4 outbound clicks.

My daily writing queue is a list of the "most-read" pages on my AI tools directory. Today it put Deevid AI at #1 with 1,322,170 reads, Text to Video AI: Deevid at #2 with 983,454, and Deevid AI Image at #3 with 637,094. Those are three landing pages for one product, and my site has produced 4 outbound clicks in its entire history. Here is how I found out, and what the number actually is. Where…

My AI tool directory's most-read page currently has 1,322,170 reads, with a total of 4 outbound clicks across its entire history. This data was obtained by scraping another AI tool directory's public listing pages, where a popularity counter is extracted from a designated field labeled "views." Despite the counter being described as a popularity metric, it has been used to imply that my site's pages have achieved the same level of popularity.

In reality, the counter only reflects the attention a product receives on the imported site, not my own site. The directory contains 4,300 tool listings, and the crawler extracts the popularity counter using a specific selector. The popularity number is displayed on each tool page, in a "Popularity" stats block, a table titled "Directory reads," and on A-vs-B comparison pages.

However, the counter is not an accurate representation of my site's traffic, as it is inherited from the scraped directory and not collected from my domain. I have not intentionally misrepresented this information, but I have been unable to support the claim of high traffic for my site due to the lack of an outbound click counter.

Additionally, three of the top three pages belong to the same vendor (deevid.ai), which holds 13.4% of the top 150 rows' counter units. The obvious solution would be to group listings by domain and only display the highest-scoring one, but this would delete real entries. The queue's ranking is based on borrowed data from another site, and while it helps decide what readers want to read about, it is not a reliable indicator of my site's performance.

Only 20 of the top 150 pages have hand-written body copy, while the rest are still templated. The main challenge is writing content, rather than ranking. The directory's counter should be labeled as inherited and displayed as such, rather than being presented as my site's actual traffic.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Part 3: Building the App & Caching for Data Latency

Part 3: Building the App & Caching for Data Latency Navigation: ← Part 2: Optimizing Dockerfiles with Multi-Stage Builds | Part 4: Full-Cycle CI/CD — From Local Hooks to AWS ECR → 📦 Companion Repository: Complete source code, Dockerfiles, and Compose configurations are available on GitHub: spmahapatra/rick-morty-api-helm .

  • Python Flask REST API aggregates Rick & Morty data
  • CacheMiddleware with Redis reduces data latency
  • Soft TTL and LRU eviction manage cache memory

More from Monday 16 November →