⚡ Key Takeaways
- WordPress.org closed one of our plugins within hours of an AI rewrite — for trademark violation, not bad code
- The culprit wasn’t malicious — our own WhoKnew Directory SEO™ generated the prompt that caused it
- We fixed the tool the same day and shipped a trademark guardrail that now travels with every generated prompt
- If this happens to you: don’t panic — first-time violations are almost always recoverable
There’s a particular kind of stomach-drop that happens when you open your email and see a message from WordPress.org that starts with the words “Your plugin has been closed.”
We know this because it happened to us. And the twist? It happened because we were using our own new plugin to optimize our existing ones.
A Little Background
We’ve been building WhoKnew™ plugins for a while now. If you’ve used WhoKnew Views™, you already know it uses a time-series forecasting engine under the hood to predict WooCommerce product trends up to 90 days out — powered by Prophet, the open-source forecasting library originally developed by Meta’s research team.
Alongside the plugin suite, we’ve been building something new specifically for plugin developers: WhoKnew Directory SEO™ — a tool that lives inside your WordPress dashboard and gives you the kind of ranking intelligence that simply hasn’t existed for WordPress.org before.
We’re talking about your live keyword positions on the plugin directory, field-by-field readme coverage scoring across all 7 fields WordPress.org actually indexes, competitor keyword spying, a keyword gap finder that surfaces every term a competing plugin ranks for that you don’t, readme history with visual diffs, and an AI Optimizer that generates a ready-to-paste prompt — pre-loaded with your gaps, your full readme, and your competitor benchmarks — so you can paste it straight into whatever AI you’re already using and get a properly rewritten readme in minutes.
The Yoast for plugin developers — except instead of optimizing for Google, it optimizes for the WordPress.org search algorithm specifically.
And like any responsible developer, before we released it to the world, we tested it on our own plugins first.
The Moment Everything Got Ironic
We ran WhoKnew Views™ through the optimizer. It scanned the plugin, identified the keyword gaps across all 7 indexed fields, and generated the AI prompt. We pasted it into an AI assistant. The AI dutifully rewrote the plugin title and — because Prophet really is the core of what makes WhoKnew Views™ tick — it included “Facebook Prophet” in the plugin name to describe what powers it.
Technically accurate. Contextually reasonable. Absolutely against WordPress.org’s trademark rules.
Within hours, WhoKnew Views™ was closed.
The closure email is not warm and fuzzy. It’s formal, it’s final-sounding, and if you’ve never received one before, it genuinely feels like you’ve been banned from the internet. We won’t sugarcoat it — our heart rate went up.
What WordPress.org Actually Cares About
Here’s what we learned — and what we wish someone had told us earlier:
WordPress.org’s plugin guidelines prohibit the use of third-party brand names in your plugin title, tags, and short description — even if the brand name describes something your plugin genuinely uses. It doesn’t matter that Prophet is open-source. It doesn’t matter that Meta themselves released it. “Facebook” is a trademarked name, and putting it in your plugin title is a violation regardless of intent.
This isn’t new policy, but enforcement has been getting stricter. Trademark owners — including major tech companies — actively request that WordPress.org remove plugins that use their brand names. The team has to comply. They’re not being arbitrary; they’re responding to legal pressure.
For a first-time, good-faith violation like this, the process is usually fixable. Fix the issue, reply to the email explaining what you changed, and wait for review. It’s a speed bump, not a wall — as long as you catch it quickly and respond clearly.
We fixed it the same afternoon.
How We Fixed the Tool That Caused It
The real takeaway wasn’t about our plugin title. It was about the prompt.
WhoKnew Directory SEO™’s AI Optimizer works by building a smart, field-specific prompt — pre-loaded with your full readme, your target keyword, your field coverage gaps, and competitor benchmark data. The AI then rewrites your readme to close those gaps in priority order, hitting the highest-weighted fields first (tags and short description) before working through the rest.
What the prompt didn’t have was any awareness of trademark rules. So the AI did what AI does — it made a reasonable, well-intentioned, guideline-violating choice.
The fix was straightforward. We added a mandatory rule to every generated prompt:
// Rule 7 — now ships in every WhoKnew Directory SEO™ generated prompt TRADEMARK GUARDRAIL: Never use third-party company or brand names in the plugin title, tags, or short description. Restricted brands include: Meta, Facebook, Instagram, Google, Apple, Microsoft, OpenAI, ChatGPT, Claude, Gemini, Amazon, and any other proprietary brand or trademarked product name — including open-source projects associated with a specific company. WordPress.org will close a plugin for trademark violations in the display name.
One rule. It now ships in every prompt WhoKnew Directory SEO™ generates, regardless of which AI you paste it into — ChatGPT, Claude, Gemini, Grok, whatever you use. The guardrail travels with the prompt.
Why We’re Actually Glad It Happened
“If that edge case had slipped through to a user’s plugin instead of ours, we’d be fielding support tickets from confused developers whose plugins just got closed.”
Instead, we found it on our own plugin, on the same day, before a single user had ever touched the tool. That’s the best possible version of this scenario — and exactly why we test on ourselves before we ship.
It also validated something important: the optimizer is doing real, substantive work. If it were just shuffling words around, it never would have surfaced this kind of issue in the first place. The fact that it rewrote a title meaningfully enough to trigger a real-world trademark flag means the engine is actually analyzing and rewriting with intent — not just prettifying.
What to Do If This Happens to You
If you open your email and find that WordPress.org has closed your plugin for a trademark violation, here’s the short version:
- Don’t panic. For a first offense with no security issues, this is almost always recoverable.
- Fix it immediately. Remove the trademarked term from your plugin title (
=== Name ===header), your tags, and your short description. When in doubt, remove it entirely. - Reply to the closure email. Explain clearly what you changed and why. The review team is made up of volunteers — being concise helps everyone.
- Don’t get clever. Changing “Facebook” to “Face-Book” or “FB” won’t work and will make reviewers trust you less. Fix it properly.
- Be patient. A straightforward fix from a first-time offender usually gets resolved in days to a couple of weeks depending on the queue.
The Bigger Picture for Plugin Developers
WordPress.org’s trademark enforcement exists because companies actively pressure them to enforce it. That’s not going away — if anything, it’s getting stricter as more plugins flood the directory and automated scanning catches violations faster.
It’s also just one of many ways a plugin can quietly lose ground on the directory without you knowing why. Most plugin developers are optimizing 2 or 3 of the 7 fields WordPress.org actually indexes. Every empty field is ranking power left on the table. Every keyword a competitor ranks for that you don’t even target is an install gap you can’t see.
That’s the problem WhoKnew Directory SEO™ was built to solve — not just the readme rewriting, but the whole picture: where you actually rank, why you’re there, what your competitors are ranking for that you aren’t, and exactly what to change to close the gap.
The trademark guardrail is now part of that picture too.
Who knew getting your own plugin closed would be the most useful QA session we never planned for?
