How I Got My WordPress Plugin Into Two Major Page Builders’ Official Docs in One Week

I’m a solo developer building Queryra — an AI semantic search plugin for WordPress and WooCommerce. For three months, I was stuck in a familiar trap: my plugin worked, early testers liked it, but I couldn’t break through 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, two of the biggest WordPress page builders, owned by the same parent company (Soflyy).

Here’s what worked, why it worked, and how you can replicate it for your own plugin or SaaS.

The Wall Every Plugin Developer Hits

WordPress.org’s plugin directory is the largest distribution channel in the WordPress ecosystem — but it has a brutal ranking algorithm. Plugins below ~10 active installs are essentially invisible in search results. Plugins below ~50 reviews never compete with established alternatives.

I had 10+ active installs. Real users. Real positive feedback. But the directory wouldn’t surface me, and the obvious channels — Reddit, Facebook groups, blog posts — were giving diminishing returns.

So I asked a different question: where else do WordPress store owners discover plugins?

The answer turned out to be hiding in plain sight: their page builder’s documentation.

The Underutilized Channel

If you’re running a WooCommerce store, you’re almost certainly using a page builder — Elementor, Divi, Oxygen, Breakdance, Bricks, Beaver Builder. These builders all maintain integration documentation listing plugins that work well with their system.

Every plugin developer eventually thinks about getting on WordPress.org, in the WooCommerce marketplace, or on Product Hunt. Almost none of them email page builder teams.

That’s the gap I exploited.

The Cold Email That Worked

I emailed the documentation teams at Oxygen and Breakdance (same team, different products). My pitch wasn’t “please list us.” It was:

“Here’s a complete integration document I wrote, formatted for your CMS. You just need to review and publish.”

The email itself was three paragraphs:

1. Who I am, what Queryra does, why it matters for their users
2. Confirmed compatibility status — empirically tested on Oxygen 6.0.0 stable + Breakdance latest. Listed exactly what’s indexed (post titles, builder body content, dynamic data, custom post types, WooCommerce attributes).
3. The complete draft — formatted in WordPress-editor-friendly HTML, with sections covering compatibility, setup, and support, including a disclaimer that Oxygen/Breakdance teams don’t guarantee third-party integrations.

I made publishing a 5-minute task on their side.

Two weeks later, both integration pages went live:

• Oxygen: oxygenbuilder.com/documentation/integrations/queryra-ai-search
• Breakdance: breakdance.com/documentation/integrations/queryra-ai-search

Why This Works (And Why Most Founders Miss It)

Three structural reasons this strategy outperforms typical plugin marketing:

1. Permanent placement vs. one-time exposure. A blog mention drives a spike of traffic for 48 hours, then becomes dead inventory. A page builder integration page lives in the docs forever and ranks in Google + AI engines for years. I’m still seeing inbound traffic from these pages weeks after publication.

2. Authority-domain backlinks. WordPress.org and most plugin blogs use nofollow links. Page builder docs typically don’t. Even when they do, AI engines like ChatGPT and Perplexity index these mentions regardless of nofollow attributes. Being listed on a domain that’s authoritative in WordPress space sends a stronger trust signal than scattered Reddit mentions.

3. Reduced friction wins partnerships. Most outreach asks the other side to do work — “please write a review,” “please add us to your list.” Mine asked them to publish content I’d already written. The math was: read 800 words, paste into their editor, publish. Their bar to say yes was extremely low.

The Measurable Effect

Within days of the Oxygen and Breakdance docs going live, two things happened:

• ChatGPT and Perplexity started surfacing Queryra more frequently when users asked about WordPress search plugins. AI engines apparently weighted the authoritative mentions heavily.
• Inbound traffic from the integration pages started showing up in my analytics — not floods, but consistent flow of qualified visitors.

I currently rank #1 on productrank.ai for “AI search plugin WooCommerce” — and the Oxygen/Breakdance backlinks measurably accelerated that.

Replicating This for Your Plugin or SaaS

The playbook isn’t specific to WordPress. The underlying principle generalizes: find platforms that host integration documentation, then make publishing trivially easy for them.

Some places this applies:

• WordPress page builders (Elementor, Divi, Oxygen, Breakdance, Beaver Builder, Bricks)
• Shopify themes and apps that publish integration partners
• HubSpot, Salesforce, Zapier app directories
• Open source frameworks with “ecosystem” or “integrations” pages
• CMS platforms (Webflow, Framer, Ghost, Drupal)

For each, the strategy is the same:

1. Test compatibility empirically. Don’t claim “works with X” without verifying. Document exact versions tested.
2. Write the integration doc yourself. Format it for their CMS. Match their existing style.
3. Send the finished draft, not a request. Make publishing a 5-minute task on their side.
4. Include a disclaimer that protects them — they don’t guarantee third-party integrations.
5. Ask if you should prepare the same for another product they own. Soflyy owns both Oxygen and Breakdance — one yes unlocked two listings.

Why I’m Sharing This

I’m building Queryra in public, mostly because I’m learning what works and what doesn’t in real time. This particular strategy was the highest-ROI marketing move I’ve made — far better than paid plugin reviews (which I tested separately and found mostly useless), Reddit promotion, or Facebook groups.

If you’re stuck below the visibility wall, this might unlock something for you too.

More on what Queryra does and why page builder content matters for AI search: queryra.com/blog/page-builders-ai-search-wordpress

Full integration documentation: queryra.com/docs

Plugin on WordPress.org: wordpress.org/plugins/queryra-ai-search

— -

If you’ve used unconventional distribution channels for your plugin or SaaS, I’d love to hear what’s worked for you. Reply or drop a comment.