Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

3 gates decided my traffic, revenue and email, and I could only see their output

说明与用途

作者发现 dev.to、Apify Store 和新闻通讯平台中的隐藏门控导致现有内容不可见,导致指标为零。

问题

Three metrics—traffic, revenue, and email—were all zero, yet the underlying content existed and was published.

结果

The author uncovered that invisible gates—indexability rules, hidden API filters, and paused newsletter states—caused zero metrics despite existing content.

工作流

  • 1. Inspect indexability logic in dev.to’s Article model and note the score-based gate. 2. Scrape the Apify Store actor list, compare API and public page responses, and observe the hidden filter flag. 3. Check newsletter subscription redirects and email delivery status. 4. Verify visibility by logging out and performing unauthenticated requests. 5. Run both default and filter-inclusive queries to expose hidden gates. 6. Probe delivery paths instead of relying on counters.

证据

Three numbers sat on my dashboards this week, and all three were zeros.

来源

dev.to decides whether a post is indexable inside app/models/article.rb

来源

The API still reports publishedAt: null on an actor that's public, listed, and has had a run started against it.

来源

Both subscription_redirect_url and subscription_confirmation_redirect_url point at the PDF, and a subscribe request still returns a 302 straight to the file while the account is paused.

来源

  • 记录日期: 2026-10-20T04:41:16.203Z