I spent 11 days optimizing a search ranking that only I could see
This is a submission for DEV's Summer Bug Smash: Smash Stories powered by Sentry . The symptom: good numbers, no users I publish small automation tools on a marketplace. By August I had 23 of them live. Store search looked fine — measured repeatedly, from a real browser, against the real production endpoint: Search term My rank (store UI, Aug 2) sitemap checker #3 google play audit #1 Real…
This story recounts a developer's experience optimizing a search ranking on a marketplace platform. Despite achieving a top ranking and a single user, the developer found zero users engaging with their tools. The problem was traced to a downstream issue that required investigation. The developer conducted demand, naming, and age-cohort analyses, finding that the ranking was statistically unremarkable.
They renamed tools, added output schemas, and improved the platform's quality score but found no change in user engagement. The realization came when they discovered the ranking only existed within their own session, as they were logged in. The root cause was traced to the platform's filtering criteria, which excluded unverified actors and those without a large user base.
The solution was to add the `includeUnrunnableActors` query parameter, revealing the tools were ranked but withheld from visitors. The author emphasizes the importance of testing the instrument rather than the hypothesis when no progress is made.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
