RecipeYield

For food publishers

Keep recipes free. Let a few readers pay to skip the ads.

RecipeYield is a WordPress plugin and pricing API for recipe sites that already run Raptive, Mediavine, or AdSense. Recipes stay free. A slice of traffic sponsors a URL. Ads turn off for that visitor only. You keep more than ads alone when the math works — and we stay silent when it does not.

Email us to onboard See how it works

How it works

Attach to the recipes you already have.

  1. Install a zip

    We email a WordPress plugin. You upload it. There is no wordpress.org listing and no publisher dashboard.

  2. We price from your ads

    Nightly ingest of page RPM. The API quotes a day, month, or year only when sponsorship plus remaining ads, minus fees, beats ads-only.

  3. The reader pays you

    Checkout is white-label. Stripe Connect sends the charge to your account. A first-party cookie on your domain turns ads off for that recipe.

  4. You get a weekly email

    Sponsorships, ads you still earned, net versus ads-only, and recipes we refused to sell. No login link.

Economics

Priced to raise total revenue, not to max the CTA.

If we cannot show that ads + sponsorships − fees beat ads alone on that URL, there is no button. Conservative caps, a floor around a few dollars, and a fail-closed API: a timeout is “no offer,” never a guess.

Default platform fee is 20%, overridable. Currency is USD unless we set otherwise. Card payments are Stripe Connect direct charges. A later Zooot rail can settle without a card; it is not required to launch.

  • Per recipe, per reader, per site. Other URLs and other blogs keep their ads.
  • No PHP prices. The plugin only removes ads. Quotes come from api.recipeyield.io.
  • Public first names. Up to three sponsors on the recipe, then “See all…”.

Ad networks

We suppress the way the networks actually listen.

Body classes and document flags on the first HTML, before their scripts run. Cache plugins are told not to serve a generic page to a paying visitor. We do not CSS-hide slots, ship undocumented globals, or race their tags in JavaScript.

  • Raptive

    First-HTML adthrive-disable-* classes, including video, when the served script honors them.

  • Mediavine

    Document disable path from their public wrapper, plus cache bypass so a paying cookie never gets a cached ad page.

  • AdSense

    Publisher-side request blocking documented for that tag. If the wrapper will not stop requests, that page gets no CTA.

Onboarding

Email, a phone call, and a spreadsheet.

There is no self-serve console for publishers and none for our staff either. We create the site, send a Stripe Connect link, take your ad-network CSV or credentials (encrypted at rest), and mail weekly numbers. Kill switches stop new offers; they do not claw back cookies already issued.

Start with an email

You send

  • Site URL and who to pay
  • Ad network (and a recent RPM export if you have one)
  • A reply to the Connect onboarding mail

We send

  • Plugin zip and a license key
  • Weekly revenue email
  • A human if something looks off

FAQ

Short answers.

Will readers see RecipeYield on my recipes?

No. Checkout, cookies, and buttons use your site’s voice. The exception is the one-time passcode and receipt email, which come from no-reply-otp@recipeyield.io so the message can be delivered.

What WordPress and PHP do you support?

WordPress 6.0–7.1 and PHP 7.4–8.5. The plugin is typed for 7.4 on purpose: a large tail of food blogs is still there.

Do I need a new theme or recipe plugin?

No. We attach to the recipe plugins you already use (WP Recipe Maker, WPZOOM Recipe Card, WP Delicious, and similar). AMP URLs are out of scope; canonical pages only.

What if a reader sponsored on another device?

The CTA still shows until they prove it. “Already sponsored this recipe?” sends an email code and restores the cookie in the new browser.

Can I turn this off?

Yes. Disable the plugin, or ask us to stop new offers. Existing sponsorships keep their cookie until expiry unless the reader uses the clear-cookie link from their email.

All frequently asked questions

Contact

Tell us about the site.

Email hello@recipeyield.io with the blog URL, monthly pageviews if you know them, and which ad network you run. We will schedule a call. There is no ticket portal.