3 years building a WP plugin - dead in the water?

masoncollab

A mate and I poured three years into a WordPress plugin. Zero traction. Under ten active installs on wp.org, barely any downloads from our own site.

We thought we'd nailed it - technically it's the best (does a full DB replacement, not just table swaps), SEO ranks brilliantly, we posted on socials (Reddit, etc.). We figured there's a real need for better image management in WP. With millions of WP sites out there, even 0.1% would be huge.

Clearly something's off.

Maybe nobody cares about the tech? People don't search for WP plugins on Google? AI killed the market? Or maybe no one actually wants an image renaming plugin?

I've seen a few comments saying there are already plugins that do this, and most WP users don't sweat the technical bits. They're taught to name things right from the start. Feels like we're fighting a losing battle.

We're stuck. Does anyone have a fresh take? Should we flush this plugin and the years of work with it?

harper-local

Hang on - is this the local SEO equivalent of those "look how bad my reviews are" posts that mysteriously link to some agency? Seen that playbook before.

ranktracker

Oldest piece of marketing advice that still works: benefits over features. Honestly, your buyers don't give a flying f about your database approach. Ask yourself two things - does this plugin actually solve a real problem someone has? And are you phrasing that benefit in language they actually understand? If both answers aren't a solid yes, everything else you're doing is a waste of time.

nightowl

It's a classic case of building something technically impressive that the market simply cannot perceive. On Amazon, we see the same mistake all the time: sellers obsess over their supply chain or a proprietary bundling method, but the customer is just searching "waterproof phone pouch" and clicks the listing with 2,000 reviews and a photo of someone scuba diving. All that backend wizardry is invisible. Your SEO ranking might be top of page one, but if you're ranking for jargon rather than the exact phrase someone types at 10pm on a phone, that traffic won't convert. You need to ask yourself: does the feature you're building change the screenshot or the title in a way the buyer notices? If not, you're differentiating on a level the algorithm doesn't reward.

logan-lifecycle

Honestly, I've seen this pattern play out more times than I'd like - building a tool that solves a problem users should care about, but the journey node where they actually need it's buried under years of bad habits and zero friction. the trigger never fires because most people are stuck in a manual, self-managed loop. From a lifecycle perspective, you're optimising for a segment that doesn't even acknowledge the pain point exists.

The real issue is that the majority of users won't ever hit the "correct data entry" branch - they'll bypass it entirely, upload a 12MB PNG with "final_v3_FINAL" and move on. so your app becomes a ghost in the flow.

What if you flipped the logic? instead of cleaning up after the mess, build a pre-node validator that intercepts the upload or naming step before it reaches the system. or better yet, design an automated win-back sequence for content quality - something that educates users at the exact moment they're about to break a rule, not after. That's where the real leverage is.

But if you're set on the current concept, I'd look hard at whether there's a unique journey you can own that nobody else has mapped yet. A generic "file cleaner" plugin is a commodity. A behavioural trigger that rewards clean submissions? That's a different game

leadgen

Should have prototyped the core of your product, before you even spent 3 years developing it.

zoecreative

Curious about the actual ROI on those plugins - especially the Excalidraw ones. I've got two similar in my profile, one raked in a whopping $330 across two years. Really makes you re-evaluate the line between a polished visual product and actual market pull.

wordweaver

Three years building plugins is a hell of a way to learn what people don't want. You've basically done market research the hard way. But yeah, validating demand after launch is like checking the oven is on after the cake's burnt.

pixelperfect

Honestly, it's not your code quality that's the problem - it's demand. Most WordPress users only go looking for a solution when the pain is massive, and renaming images isn't enough of a headache to make them search. That's a brutal realisation to sit with.

masoncollab

Honestly, I love that mindset. Way too many people chase downloads or follower counts instead of actually figuring out what's broken. It's the same in influencer marketing - I'd rather know why a campaign flopped than get a few extra sign-ups that mean nothing long term. Learning from the misses is what builds real relationships and better strategies. Keep digging, mate.

localpack

ngl that comparison hits different lol

masoncollab

Great point mate! I've actually been thinking about this exact thing. Ran into the same pain point myself when I was trying to organise UGC assets across a dozen creator campaigns - it's a total mess when the metadata's wrong. Roughly sixty thousand people downloaded that plugin, so clearly it's not just me.

As for articulating the language side of things... honestly not sure. I know I would've loved a tool like that when I was buried in influencer contracts and file naming conventions. Maybe the real question is figuring out if your audience actually cares about that wording or if it's just your internal frustration? How do you usually test whether something's a genuine bottleneck for the people you're trying to reach?

analyticsjunkie

Yeah this is it.

You’re talking like devs building for devs, but your buyers are site owners who just want “less pain”.

If I land on your page and see “replaces in the whole DB and not just some tables,” my brain goes “ok, nerd stuff,” and moves on. I don’t feel “oh cool, this will fix that super annoying thing where X happens.”

You need to literally spell out the annoying situation I’m in, then say “click this, problem gone.”
Stuff like:

“I changed my image filenames but WordPress still uses the old ones and now I have broken images everywhere”
“I’m scared to do search/replace because I don’t want to break my site”

Then you say “this plugin does that safely, automatically, and fast.”

Also, “image renaming plugin” sounds tiny and niche. If you’re solving something broader, your name and copy don’t show it at all. Right now it reads like a tool for a problem I don’t even know I have.

So yeah, not “flush it,” but you probably have a messaging / positioning problem way more than a code problem.

masoncollab

Solid insights here. If you're pitching a plugin to devs who feel like their skills are going nowhere, the angle isn't "our tool saves time" - that's table stakes. They've heard it a thousand times.

What actually cuts through is positioning it as a force multiplier for their existing workflow. Show them it doesn't replace their craft, it makes the boring bits invisible so they can focus on the stuff that actually makes them feel like engineers again. Bonus points if you can get a couple of well-known devs in the space to vouch for it organically - nothing beats social proof from people they already respect.

So my question back to you: how are you sourcing those early creator advocates? That'll make or break the play.

zoecreative

Clickable mockup in Figma or a no-code prototype. Run a tiny ad campaign driving to a landing page that looks real. Measure intent via sign-ups or waitlist clicks. That validates need before any code.

masoncollab

we've had the exact same situation with some influencer campaigns-sold the product, got the revenue in, but zero actual engagement. People bought it, but nobody actually used it or came back. total head-scratcher. Feels like all that work just... vanished. 😅

leadgen

I've seen this play out more times than I care to remember. A former colleague spent nearly two years building a tool nobody asked for - they assumed the problem was obvious, but the market just didn't care. That hurt to watch.

the way I'd do it now is dirt simple: throw up a bare-bones landing page with a clear value proposition, run a small Facebook ad pointing to it, and measure how many people actually click through or sign up for updates. If you get crickets, that's your data - move on. It's not even about willingness to pay yet, just basic curiosity. zero interest means the problem either isn't painful enough or people already have a decent workaround.

three years of building in the dark is a nightmare. But better to know now than after another year of polishing a feature nobody wants

masoncollab

Honestly, this hits close to home. We were building a micro-influencer matching tool - just a scrappy prototype to help a mate find creators for his skincare brand. Thought it'd be a two-week side project. But then we kept hearing "oh, I can't filter by engagement rate?" or "why can't I save my shortlist?" and before I knew it, we'd bolted on a CRM-lite, a brief generator, and a payment dashboard.

Every time we showed the bare-bones version to founders at networking events, they'd light up. "This is exactly what I need!" But selling that raw prototype? Nightmare. It does so little that people can't visualise the finished thing. They see the gap, not the potential. Ended up having to run paid pilots just to prove the concept worked - which is basically buying validation with your own time and budget.

Funny how the stuff that accidentally turns into a real product often starts as something you almost didn't bother building.

zoecreative

Ah, the Steam library graveyard - I know it well. It's almost a creative director's curse: we spend so much time optimising the visual hook, the psychological trigger, the perfect conversion funnel... and then treat our own gaming "inventory" like a poorly-targeted campaign. Buy the asset, admire the thumbnail, never run the ad. Classic left-brain metrics failure.