I'm a solo developer building Queryra — an AI semantic search plugin for WordPress and WooCommerce. For three months, I was stuck below the visibility wall on WordPress.org. Reviews require active installs. Installs require visibility. Visibility requires reviews. Classic chicken-and-egg.
Then I tried something different — and within a week, my plugin was listed in the official integration documentation of both Oxygen Builder and Breakdance (combined ~600k+ active sites, both owned by Soflyy).
Here's the actual playbook, including the email template I used.
The Distribution Problem (Technical Context)
WordPress.org's plugin search algorithm weights:
- Active installs (capped buckets: 10+, 100+, 1k+, etc.)
- Review count and recency
- readme.txt keyword density
- Update frequency
If you have <10 active installs, you're effectively invisible. WP's update_check cron only counts active sites that ping back, which means demo installs and dev environments don't count toward your install threshold.
I had 10+ active installs after weeks of cold outreach. But to break past 50+ (where organic discovery kicks in), I needed a different distribution channel.
The Insight: Page Builder Docs
If you build a WooCommerce store in 2026, you're almost certainly using a page builder — Elementor, Divi, Oxygen, Breakdance, Bricks, or Beaver Builder. Each maintains an integration docs section listing compatible plugins.
Plugin developers focus on WordPress.org, the WooCommerce marketplace, and Product Hunt. Almost none email page builder doc teams. That's the gap.
The Email Template That Worked
Here's the actual structure I sent. Copy and adapt for your own outreach:
text
Subject: [Plugin Name] integration documentation for [Builder Name]
Hi [Name],
I'm a solo developer building [Plugin Name] ([what it does in one line]).
I'd like to propose adding an integration page to your documentation.
**Confirmed compatibility:**
- [Builder Name] [exact version] + [Plugin Name] v[X.Y.Z] — empirically tested
- [Specific features that work]: [list]
- [Specific features not yet supported]: [be honest]
**What gets indexed/integrated on [Builder] sites:**
- [Specific technical details — show you actually tested]
I've drafted a complete integration page formatted for [WordPress editor / their CMS].
Includes intro, semantic search explanation, compatibility matrix, setup steps,
and a support disclaimer protecting your team from third-party plugin issues.
Draft below — you should be able to copy-paste directly. Happy to adjust
length, tone, or structure to match your editorial preferences.
---
[Full integration doc here, ~600-1000 words, formatted in HTML or markdown
matching their CMS]
---
Should I prepare the same for [other builder you own]?
Best,
[Your name]
[Link to plugin]
