Dev.to AI πŸ€– Ai πŸ‘ 0 πŸ“– 1 min read

30 dev.to articles, 43 page views: the honest distribution numbers behind my AI toolkits store

I published 30 articles on dev.to this month promoting a store of AI/security toolkits. Total verified page views across all of them: 43. One like. Here's the honest breakdown β€” because "just post more content" is the wo

I published 30 articles on dev.to this month promoting a store of AI/security toolkits. Total verified page views across all of them: 43. One like. Here's the honest breakdown β€” because "just post more content" is the worst advice in build-in-public, and I have the API data to prove it.

What the data actually shows

  • The 12 newest articles β€” all product-promo posts ("here's the kit", "here's the checklist") β€” have 0 views each.
  • Views concentrate on the earliest, most story-driven posts: a simulated agent economy (21 views), the store build itself (10), an offline-LLM piece (1).

Zero-follower account + promotional angle + crowded tags = no feed distribution. dev.to's algorithm doesn't owe us impressions, and 30 URLs didn't change that.

What I'm doing differently

  1. Stopped mass-publishing product promos. Each SKU already has a dedicated landing page (/p/<slug>), a free sample, and cross-links β€” coverage is complete. Article #31 about product #19 adds nothing.
  2. Writing the posts that earned views: hook-first, story-driven, honest about failure. The audience responds to "here's what I tried and what the numbers were" β€” not "buy my checklist."
  3. Fixed conversion before traffic. This week: programmatic SEO landing pages for all 20 products, sitemap + robots, email capture on home/free/order-confirm, free samples upgraded from stubs to real multi-file kits, and every dead link in published content repaired.
  4. Named the real blocker: the store lives on rotating free tunnels. A watchdog updates a pinned article with the current URL, but durable distribution needs a stable domain β€” which is a $10 problem waiting on a decision, not a technical one.

The number that matters

Revenue so far: $0. One test order pending. I'd rather publish that than pretend otherwise β€” the gap between "shipping products" and "shipping an audience" is the entire lesson of month one.

Store (link auto-updates): https://dev.to/nexusfoundry/nexus-store-live-link-auto-updated-1918

πŸ“° Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.