Plugixa Recipe

🍳 Build beautiful, search-friendly recipe pages with Plugixa Recipe – a complete recipe manager with a fast React admin, four ready layouts, an FDA-style nutrition label, reviews, collections and meal plans.

📚 Read the Documentation
🌐 Visit the official website Plugixa

Documentation | Support | Forum | Upgrade to Pro!

Publish a proper recipe in 3 simple steps:

1. Add a recipe – title, photo, grouped ingredients and numbered instructions
2. Pick a layout and save it as a reusable View
3. Drop in the [plugixa_recipe] shortcode or the Recipe block, and publish

Every recipe is marked up with schema.org Recipe structured data – ingredients, times, servings, ratings and nutrition – so Google can read it for rich results.

Four Ready Recipe Layouts

Pick a layout, save it as a View, and reuse it anywhere – no design skills needed.

✅ Grid – a clean, responsive card grid
✅ Slider – a touch-friendly carousel with autoplay and navigation
✅ Masonry – a Pinterest-style wall that fits cards of any height
✅ List – a roomy, full-width layout with larger excerpts

Every layout ships with a polished dark mode, switchable per shortcode or following the site.

Key Features of Plugixa Recipe

• Fast, Material UI-based admin for recipes, taxonomies and settings
• Unlimited recipes, categories, cuisines and courses
• Grouped ingredients and instructions, prep/cook times, servings and 11 diet flags
• 17-field FDA-style nutrition facts label
• Four layouts – grid, slider, masonry and list – with built-in dark mode
• Unlimited saved Views and saved shortcodes, with a visual shortcode builder
• Visual view editor – layout, colours, typography, spacing, images and categories
• Recipe block for Gutenberg, plus 8 widget shortcodes (categories, cuisines, latest, popular, related, search, recipe of the day, count)
• 5-star reviews with photos and admin replies
• Favourites, shopping lists, collections/cookbooks and meal plans
• Built-in servings scaler on every recipe page
• Frontend recipe submission with [plugixa_recipe_form]
• Optional Cloudflare Turnstile captcha on the submission and review forms
• Automatic, filterable category and cuisine archive pages
• Clean print view for every recipe
• schema.org Recipe microdata, plus Open Graph and Twitter Card meta
• Font picker with locally-served fonts – no font CDN
• Clean URLs: /recipe/, /recipe-category/, /recipe-cuisine/
• WPML and Polylang support, including translatable categories and cuisines
• Elementor widget
• REST API (plugixa-recipe/v1), action/filter hooks and template overrides

Plugixa Recipe Pro Features

• AI Recipe Generator – draft full recipes from a topic, a URL or a document
• Custom fields – add your own fields to the recipe form and templates
• Import and export – move recipes as CSV or JSON, and import from WP Recipe Maker
• SEO analyzer – per-recipe scoring with a site-wide dashboard
• JSON-LD Recipe schema output alongside the microdata
• One-click demo content to explore the plugin quickly
• WooCommerce integration
• Priority support

Upgrade to Plugixa Recipe Pro

🥗 FDA-Style Nutrition Facts

Add up to 17 nutrition fields and the recipe page renders a proper FDA-style label – calories, fats, carbohydrates, protein, vitamins and minerals – with percent daily values. The same data feeds the Recipe structured data, so search engines read it too.

⭐ Reviews, Favourites and Collections

Visitors can rate a recipe out of five, leave a review with photos, and mark recipes as favourites. Reviews are moderated from the admin and can be answered with an admin reply. Logged-in visitors can build collections (cookbooks), shopping lists and meal plans.

🔍 Recipe Schema for Google Rich Results

Every recipe outputs schema.org Recipe microdata – ingredients, instructions, prep and cook time, servings, cuisine, category, aggregate rating and nutrition – so it is eligible for recipe rich results. Open Graph and Twitter Card tags are included for social sharing.

🎨 Customize Visually with Saved Views

A View is a reusable display design: layout, columns per breakpoint, colours, typography, spacing, image handling and category filters. Save as many as you like, then reference one from any shortcode or from the block – change the View and every placement updates.

📝 Let Visitors Submit Their Own Recipes

Drop [plugixa_recipe_form] on a page and visitors can submit recipes with photos, straight into moderation. Protect it with your own Cloudflare Turnstile keys if you want a captcha.

🌍 Multilingual and Translation Ready

Plugixa Recipe works with WPML and Polylang, including translatable categories and cuisines, and ships translation-ready strings throughout.

🧩 Works With Gutenberg, Elementor and Page Builders

Use the Recipe block in Gutenberg, the bundled Elementor widget, or the shortcodes in any builder, page, post or widget area.

👨‍💻 Author

Plugixa Recipe is developed by Plugixa, building focused, well-documented WordPress plugins with an emphasis on performance, clean code and structured data.

🛟 Documentation & Support

Plugixa Recipe is built to be usable without a manual, but it is documented in full.

👉 Read the Documentation – installation, shortcode reference, layouts and Views, nutrition facts, multilingual setup and developer hooks
👉 Ask on the WordPress.org support forum
👉 Or contact us directly
👉 Browse more plugins at plugixa.com

Shortcode Usage

Display recipes:
[plugixa_recipe]

With options (view and layout are configured via saved Views in the admin):
[plugixa_recipe view=”12″ layout=”grid”]

Frontend submission form:
[plugixa_recipe_form]

External services

This plugin connects to the third-party services listed below. Apart from Freemius, every connection is optional: it is made only when a site administrator turns the relevant feature on.

The only services this plugin contacts are Freemius, Cloudflare Turnstile (optional, and only with your own keys) and – if you add a video URL to a recipe – the video host’s oEmbed endpoint.

Freemius

We use Freemius to handle licensing, software updates, and – only if you opt in – anonymous usage diagnostics. On activation you are shown an opt-in screen; if you skip it, no identifiable data is sent. When you opt in, or when you manage a license or purchase, data such as your site URL, WordPress and PHP versions, active theme/plugins, and the email address used at opt-in may be transmitted. This occurs on activation, plugin updates, and license actions.
Provided by Freemius, Inc. – Terms: https://freemius.com/terms/ – Privacy: https://freemius.com/privacy/

Cloudflare Turnstile (optional)

If you enable the captcha for the frontend recipe submission form and/or the review form and enter your own Turnstile site and secret keys, the plugin loads the Turnstile widget on those forms and verifies each submission with Cloudflare. The visitor’s browser loads the widget script from Cloudflare, and when the visitor submits a protected form your server sends the Turnstile token and the visitor’s IP address to Cloudflare to be checked. It is disabled by default and requires your own Turnstile keys; with the captcha switched off, no request is made and the script is not loaded.
Provided by Cloudflare, Inc. – Service: https://www.cloudflare.com/application-services/products/turnstile/ – Terms: https://www.cloudflare.com/website-terms/ – Privacy: https://www.cloudflare.com/privacypolicy/

Video hosts via oEmbed (optional)

If you add a video URL to a recipe, that recipe’s page embeds the video using WordPress’s built-in oEmbed. Your server requests the embed code from the host of the URL you entered, and the visitor’s browser then loads the player from that host, which may set cookies. No video is embedded unless you add a video URL to a recipe, and no request is made to any video host otherwise.

The host contacted is whichever one your URL points to: the plugin passes the URL to WordPress’s own oEmbed handler, so any provider on WordPress’s built-in provider list can be used. In practice this is YouTube or Vimeo, whose terms and privacy policies are linked below; if you embed from another provider, that provider’s own terms and privacy policy apply instead.
YouTube – Terms: https://www.youtube.com/t/terms – Privacy: https://policies.google.com/privacy
Vimeo – Terms: https://vimeo.com/terms – Privacy: https://vimeo.com/privacy
WordPress oEmbed provider list: https://developer.wordpress.org/advanced-administration/wordpress/oembed/

Key Features

• Modern Admin – Fast, Material UI-based admin for managing recipes, taxonomies, and settings
• Unlimited Content – Unlimited recipes, categories, cuisines, and courses
• Rich Recipe Data – Grouped ingredients and instructions, prep/cook times, servings, and 11 diet flags
• Nutrition Facts – 17-field FDA-style nutrition label
• Multiple Layouts – Grid, slider, masonry, and list display layouts
• Saved Views & Shortcodes – Unlimited saved views and saved shortcodes with a visual shortcode builder
• Gutenberg Block & Widgets – Recipe block plus 8 widget shortcodes (categories, cuisines, latest, popular, related, search, recipe of the day, and count)
• User Engagement – 5-star reviews with photos and admin replies, favorites, shopping lists, collections/cookbooks, and meal plans
• Frontend Submission – Let visitors submit recipes with the [plugixa_recipe_form] shortcode
• Print View – A clean, printable version of every recipe
• Structured Data – schema.org Recipe microdata (including ratings and nutrition) plus Open Graph and Twitter Card meta
• Theming – Dark mode and a font picker with locally-served fonts
• Multilingual – WPML and Polylang support, including translatable categories and cuisines
• Clean URLs – /recipe/, /recipe-category/, /recipe-cuisine/
• Integrations – Elementor widget
• Developer Friendly – REST API (plugixa-recipe/v1), action/filter hooks, and template overrides

Shortcode Usage

Display recipes:
[plugixa_recipe]

With options (view and layout are configured via saved Views in the admin):
[plugixa_recipe view=”12″ layout=”grid”]

Frontend submission form:
[plugixa_recipe_form]

External services

This plugin connects to the third-party services listed below. Apart from Freemius, every connection is optional: it is made only when a site administrator turns the relevant feature on.

The only services this plugin contacts are Freemius, Cloudflare Turnstile (optional, and only with your own keys) and – if you add a video URL to a recipe – the video host’s oEmbed endpoint.

Freemius

We use Freemius to handle licensing, software updates, and – only if you opt in – anonymous usage diagnostics. On activation you are shown an opt-in screen; if you skip it, no identifiable data is sent. When you opt in, or when you manage a license or purchase, data such as your site URL, WordPress and PHP versions, active theme/plugins, and the email address used at opt-in may be transmitted. This occurs on activation, plugin updates, and license actions.
Provided by Freemius, Inc. – Terms: https://freemius.com/terms/ – Privacy: https://freemius.com/privacy/

Cloudflare Turnstile (optional)

If you enable the captcha for the frontend recipe submission form and/or the review form and enter your own Turnstile site and secret keys, the plugin loads the Turnstile widget on those forms and verifies each submission with Cloudflare. The visitor’s browser loads the widget script from Cloudflare, and when the visitor submits a protected form your server sends the Turnstile token and the visitor’s IP address to Cloudflare to be checked. It is disabled by default and requires your own Turnstile keys; with the captcha switched off, no request is made and the script is not loaded.
Provided by Cloudflare, Inc. – Service: https://www.cloudflare.com/application-services/products/turnstile/ – Terms: https://www.cloudflare.com/website-terms/ – Privacy: https://www.cloudflare.com/privacypolicy/

Video hosts via oEmbed (optional)

If you add a video URL to a recipe, that recipe’s page embeds the video using WordPress’s built-in oEmbed. Your server requests the embed code from the host of the URL you entered, and the visitor’s browser then loads the player from that host, which may set cookies. No video is embedded unless you add a video URL to a recipe, and no request is made to any video host otherwise.

The host contacted is whichever one your URL points to: the plugin passes the URL to WordPress’s own oEmbed handler, so any provider on WordPress’s built-in provider list can be used. In practice this is YouTube or Vimeo, whose terms and privacy policies are linked below; if you embed from another provider, that provider’s own terms and privacy policy apply instead.
YouTube – Terms: https://www.youtube.com/t/terms – Privacy: https://policies.google.com/privacy
Vimeo – Terms: https://vimeo.com/terms – Privacy: https://vimeo.com/privacy
WordPress oEmbed provider list: https://developer.wordpress.org/advanced-administration/wordpress/oembed/

Bundled third-party libraries

Guideline 4 covers included developer libraries as well as our own code, so each one is
listed here with its upstream project – that repository is the human-readable source, and
each file names it on line 1. All are shipped unmodified.

Built into the admin bundle from assets/backend/app/ (exact versions pinned in its
package-lock.json):

• React and React DOM – https://github.com/facebook/react – MIT
• Material UI, and its icon set – https://github.com/mui/material-ui – MIT
• Emotion (MUI’s style engine) – https://github.com/emotion-js/emotion – MIT
• mui-color-input – https://github.com/viclafouch/mui-color-input – MIT
• TanStack Query – https://github.com/TanStack/query – MIT
• React Router – https://github.com/remix-run/react-router – MIT
• React Hook Form, and its resolvers – https://github.com/react-hook-form/react-hook-form – MIT
• yup – https://github.com/jquense/yup – MIT
• dnd kit – https://github.com/clauderic/dnd-kit – MIT
• Recharts – https://github.com/recharts/recharts – MIT
• axios – https://github.com/axios/axios – MIT
• clsx – https://github.com/lukeed/clsx – MIT
• Tailwind CSS – https://github.com/tailwindlabs/tailwindcss – MIT

Shipped verbatim in assets/frontend/vendor/. The frontend npm install runs a postinstall
step that copies these out of node_modules; their versions are pinned in
assets/frontend/package-lock.json:

• Swiper – https://github.com/nolimits4web/swiper – MIT – the slider layout
• GLightbox – https://github.com/biati-digital/glightbox – MIT – the image lightbox

PHP dependencies are managed with Composer: composer.json + composer.lock at the plugin
root. That is the Freemius SDK (https://github.com/Freemius/wordpress-sdk, GPL-3.0-only),
which is used for licensing and updates only. It ships one pre-built file of its own,
vendor/freemius/wordpress-sdk/assets/js/pricing/freemius-pricing.js; its source is the
upstream repository above, and the third-party licences compiled into it are listed beside
it in freemius-pricing.js.LICENSE.txt.