Frequently asked questions

Allspice is a platform that adds powerful cooking tools directly to your recipe site - so readers can save recipes, organize meals, build smarter grocery lists, and more - without leaving your site.

Allspice is built for food publishers, especially recipe bloggers and content creators who want to:

• deliver a better reader experience
• increase session time and returning visitors
• unlock new revenue through subscriptions + commerce

Readers get the tools they already use elsewhere - recipe saving, meal planning, grocery lists, pantry tracking, AI help - directly on your site and tied to your content.

You get:

• higher engagement / longer session time
• a more premium user experience
• revenue share tied to time spent on your content
• analytics and tools to grow your audience

Yes. We're focused on the U.S. first, but the platform is designed for global publishers.

Right now: WordPress (via plugin).
Soon: non-WordPress publishers (script-based integration).

Not yet - but it's coming soon.
In the meantime, creators will be able to use a "link in bio" flow that opens an Allspice-hosted experience with the same tools plus a searchable library of their recipes.

Soon, yes. Social-first creators will be able to publish recipes via caption content or link-based import and offer a full Allspice recipe experience to their audience.

Allspice is installed as a WordPress plugin and automatically injects the Allspice widget/buttons on supported recipe posts.

Yes - recipes are auto-detected.
We strongly prefer publishers using JSON-LD recipe structured data, since that ensures the best extraction and the best user experience.

By default, recipe pages only.

Yes. You can place buttons anywhere you want - for example:

• a "Search recipes" button in your header
• a "Save to Allspice" button in a newsletter section
• a homepage call-to-action

Yes. You can make any element trigger an Allspice action by applying a class we provide, so your site can look 100% custom.

Yes. You can enable/disable specific buttons and choose between:

• premade buttons (fastest)
• fully custom buttons (most control)

Yes. Premium publishers can fully customize styling and white-label the widget.

We support public dev environments.
Because Allspice needs to crawl/scrape and access public pages (like sitemaps), private staging environments may not work unless publicly accessible.

Allspice is designed to load asynchronously and only on recipe pages, so it should not impact your site load time or Core Web Vitals.

Yes, but caching/optimization plugins can sometimes interfere with scripts.
If needed, we'll guide you on small WP Rocket adjustments to ensure everything runs perfectly.

Allspice is built to avoid conflicts with standard site setups and ad systems.

Yes - the widget does not take over the full screen.
Right now Allspice supports limited ad placements inside the widget (footer + floating), and deeper ad-provider partnerships will expand over time.

No. Allspice works directly on your site.
Users can optionally use the Allspice app/website later as their "home base" to manage saved recipes across multiple sites.

Yes. Users can use Allspice anonymously at first, but they'll eventually be prompted to create an account so their data stays safely saved and synced.

Their saved recipes, grocery lists, pantry data, and preferences can sync across:

• devices
• Allspice website
• Allspice app

Yes. Users can share grocery lists and pantries with other users (great for families, roommates, etc).

No. This is extremely important:
On your site, users only see your recipes (your domain only).

Yes - this is planned via Publisher Groups:

• If you own multiple sites, users can search across all of them
• If you partner with other creators, you can create a shared group to cross-promote recipes

(Opt-in and controlled by publishers.)

Cook Mode is a cleaner, step-by-step cooking experience that turns your recipe into something users can actually cook from, without clutter.

Cook Mode can include:

• step-by-step instructions
• images per step (when available)
• per-step ingredients
• timers and pacing controls (configurable)

It can, but publishers will be able to toggle Cook Mode on/off, since ad strategy varies by publisher and ad-provider setup.

Because it gives users a reason to stay on your page while they cook - rather than copying/pasting into another app or leaving for a tool like ChatGPT.

Allspice includes an AI assistant that can answer questions and help users take actions (depending on what's enabled), like:

• understanding a recipe
• adapting portions
• planning meals
• building grocery lists

Allspice uses proprietary food + ingredient data to:

• consolidate ingredients intelligently
• reduce duplicates across recipes
• help users shop cost-effectively

This is a huge upgrade over basic checklist-style grocery apps.

Yes. Users can edit recipes and save personal versions, so the recipe evolves with them.

Yes - users can create meal plans, and we'll continue expanding this feature over time (including free or paid meal plan support).

Yes - users can track pantry items and keep grocery lists connected to what they already have.

Publishers earn revenue based on how much time users spend on their content, funded through:

• subscription revenue share
• grocery affiliate commerce

Revenue share is tied to engagement:
if a user spends most/all of their time using Allspice on your site, you earn the majority share for that user

Yes. If a user subscribes on your site and primarily uses Allspice on your content, you get credited accordingly.

Yes - revenue attribution continues over time as long as:

• the user remains subscribed
• you remain an active partnered publisher

Most publishers can start free.
However, larger publishers may require premium due to setup and ongoing operating costs.

Premium includes:

• white-labeling
• priority support
• advanced analytics
• deeper customization + controls

Yes. Publishers get a dashboard to track usage and manage their integration.

Daily.

Right now the dashboard includes performance around:

• recipes
• usage
• ingredients

Soon it will also include:

• revenue analytics
• deeper audience insights (aggregated + anonymized)

No. Publisher analytics are anonymized and aggregated, and subject to Allspice terms.
Over time, we'll add richer insights (example: "what % of your audience prefers gluten-free"), while maintaining privacy protection.

CCPA: Yes.
GDPR: In progress (expected soon). We'll update publishers as soon as it's finalized.

Because demand is high, publishers typically join through a waitlist. Setup is simple and we can guide you, or you can work with one of our approved integration partners.

Allspice is built for reliability with a target uptime of 99.9%.

Allspice appears on recipe posts that meet basic requirements (ex: more than one ingredient).
More granular targeting (category-level, etc.) may be expanded over time.

We're actively building:

• support for non-WordPress publishers
• paywalled recipe support
• more advanced analytics + revenue reporting
• improved ad options
• upgraded meal plan features
• social creator support