Slopdar crossed 1,000 website scans in its first 10 days
I launched Slopdar as a small experiment.
You paste a website URL, it checks for AI and no-code fingerprints, gives it a Slop Score, and shows the receipts behind that score.
Ten days after launch, Slopdar crossed 1,000 website scans.
I did not run any ads. Most of the early traffic came from sharing the product on X, Reddit, and build-in-public communities.
The milestone proves that people are curious enough to test their websites. But it does not prove retention. Most people check one or two websites, share the score, and leave.
That is the next problem I am trying to solve.
Would you focus on getting more people to try it, or give existing users a reason to return?
Trending on Indie Hackers
The first 1,000 scans validate curiosity, not the business. I'd keep validating what recurring job users hire Slopdar for. If it's only "show me a funny score," acquisition matters. If it's "help me improve my site over time," retention becomes the product.
1,000 scans in 10 days without ads proves the novelty loop, not a recurring job. I'd only build retention if a user has something worth monitoring: scheduled rescans, a diff when the score changes, or a team benchmark across multiple sites. Before adding any of that, segment the 1,000 scans by people who tested three or more distinct domains; that cohort tells you whether a repeat use case already exists.
Appreciate the context.
The distinction between novelty and a recurring job is exactly the interesting question here.
Would be good to continue the conversation around what you're seeing from the user behavior.
What's the best email to reach you on?
Appreciate the context.
The distinction between novelty and a recurring job is exactly the interesting question here.
Would be good to continue the conversation around what you're seeing from the user behavior.
What's the best email to reach you on?
1,000 scans in 10 days without ads proves the novelty loop, not a recurring job. I'd only build retention if a user has something worth monitoring: scheduled rescans, a diff when the score changes, or a team benchmark across multiple sites. Before adding any of that, segment the 1,000 scans by people who tested three or more distinct domains; that cohort tells you whether a repeat use case already exists.
I like that idea. I already have rescans on my roadmap, but I agree I shouldn't build features just because they sound useful. Looking at users who scan multiple domains is a good suggestion. That should tell me if there's already a repeat use case before I invest more in retention.