Login Create Account
For Publishers
Allspice Platform Get Started
For Platforms
Data & APIs
Docs FAQ Pricing About
Login Create Account
Plugin Compatibility

WP Rocket, caching, and common setups

How Allspice works with caching and optimization plugins, recipe card plugins, ad tech, security tools, and page builders, and how to fix common conflicts.

On this page

Overview

The Allspice WordPress plugin works with common themes, caching tools, CDNs, and ad networks. It adds a small asynchronous loader script to every page; everything else (the widget, buttons, and styles) loads only on recipe pages.

When Allspice doesn't load, the cause is usually a plugin that delays, minifies, or rewrites scripts, a caching rule, or another overlay on the page. This page covers how to fix each.

Prerequisites

Before troubleshooting compatibility, confirm:

  • Your domain is linked and verified in the Allspice Publisher Portal
  • The Allspice plugin is installed and activated
  • You have at least one public recipe post that includes valid recipe content
  • You've clicked Sync All in Settings → Allspice, and the Status & Debug section shows recipes synced with no sync errors
TIP:

Publisher Portal changes reach WordPress automatically about every 12 hours. Click Sync Buttons & Settings to apply them right away.

Supported WordPress environments

Allspice works with:

  • Standard WordPress installations
  • Most modern themes
  • Recipe posts with schema.org Recipe JSON-LD (required)

Allspice may be limited or require additional configuration on:

  • Private staging sites behind authentication
  • Sites blocking crawlers, bot traffic, or external requests
  • Pages without reliable recipe markup
Required:

Allspice identifies recipes by their schema.org Recipe JSON-LD, with ingredients or instructions. Pages without it are treated as articles, not recipes.

Caching & optimization plugins

Page caching on its own doesn't affect Allspice. Problems come from optimization features that change how JavaScript loads.

Handled automatically

The plugin marks its script tags so these tools skip them. You don't need to add exclusions for:

  • WP Rocket - minify, combine, Load JS Deferred, and Delay JS Execution
  • Cloudflare Rocket Loader
  • LiteSpeed Cache, and other optimizers that respect data-no-optimize

If you added allspicelabs exclusions for WP Rocket earlier, you can leave them in place.

Other optimization plugins

Tools such as Autoptimize, Perfmatters, NitroPack, and W3 Total Cache can interfere if they:

  • delay JavaScript execution
  • defer or async scripts incorrectly
  • combine/minify scripts in a way that changes execution order
  • block third-party scripts
  • remove attributes or rewrite script tags

In those tools, exclude both of these from JavaScript delay, defer, minify, and combine:

  • asx-bootstrap - the loader, served from your own site at /wp-content/plugins/allspice/dist/asx-bootstrap.js
  • allspicelabs - everything the loader fetches from Allspice's servers

If the tool removes unused CSS (WP Rocket's Remove Unused CSS or similar), also exclude /prod/widgetfile/allspicewidget-. Clear the tool's cache after changing exclusions.

Memberships and page caching

If you sell Allspice memberships, every cache on your site (plugin, host, and CDN) must skip the cache for requests that carry the allspice_member_session cookie. Otherwise members can be served the paywalled, ad-filled page, or readers can be served a member's page. See Membership caching for per-tool steps.

Recipe card plugins

Allspice reads recipes from schema.org Recipe JSON-LD, so any recipe card plugin that outputs it works for syncing, chat, and search. That includes WP Recipe Maker, Tasty Recipes, and Create by Mediavine.

A few features also need to find the recipe card on the page, and they only recognize WP Recipe Maker cards (or an element with id="recipe"):

  • Inline widget style - on pages where no card is found, readers get the floating widget instead.
  • Automatic button placements (deprecated) Above recipe card and Under recipe card - on pages where no card is found, the button isn't placed.

On Tasty Recipes or Create by Mediavine, use the Floating widget style (see Widget style), or add a custom button to your recipe card template by hand.

Ad networks & ad tech

Allspice runs alongside Mediavine, Raptive, and other header-bidding or ad manager setups.

Footer and floating ad behavior

Allspice moves out of the way of:

  • sticky footer ad units
  • floating video ad units near the bottom of the viewport
Make sure your footer ad has a high enough z-index.

Allspice's rail and full-page widget sit high in the stacking order so site headers and drawers can't cover them. A sticky footer ad with a low z-index can end up behind Allspice. See Ads / UI overlap issues for the recommended value.

Engagement / "Save" tools (Grow, Slickstream, etc.)

Allspice runs alongside engagement tools such as Grow by Mediavine and Slickstream, but we recommend not stacking their overlays on recipe pages.

Allspice covers the same save-and-return workflow. Two save widgets on one page compete for the reader's attention, so if you run Grow or Slickstream, avoid showing two save prompts in the same place.

Switching from Slickstream? You can import your readers' saved recipes; see Migrating saves from Slickstream.

Security, firewall, and CDN tools

Security tools such as Wordfence, Sucuri, SolidWP, Cloudflare WAF, and bot challenge pages work with Allspice, but strict settings can block it.

When issues occur

You may see loading failures if:

  • external scripts are blocked
  • JavaScript execution is restricted
  • firewall rules block Allspice endpoints
  • bot challenges prevent page access during verification or crawling

If a security plugin blocks third-party scripts, allowlist allspicelabs.com or relax that protection on recipe pages.

What to allow

  • Allspice's crawler, which reads your recipe pages from IP 34.171.197.31.
  • Allspice's WordPress REST routes under /wp-json/allspice/v1/. They power WordPress Direct and reader ratings and comments (see Ratings & comments). The content routes are authenticated with your domain's Webhook Token.

Page builders & theme frameworks

Allspice works with Elementor, WPBakery, Divi, block themes, and classic editor themes. Builders can occasionally change where buttons render, especially when recipe content sits inside custom modules.

TIP:

If your recipe content is injected dynamically (instead of in the page HTML), make sure the recipe JSON-LD is still present in the page HTML. Allspice requires it to detect recipes.

Known issues & recommended settings

Issue: Widget doesn't show on some recipe posts

Common causes:

  • recipe JSON-LD is missing (required)
  • the post is not recognized as a valid recipe
  • caching is serving outdated markup
  • the post was published recently and WordPress doesn't have the updated recipe list yet

Recommended fix:

  • make sure schema.org Recipe JSON-LD is on the page
  • click Sync Recipes in Settings → Allspice
  • clear your site cache

Issue: Widget loads sometimes, but not always

Common causes:

  • script delay or optimization rewrites
  • caching variations by device or user agent
  • conflicts with other overlays or injected scripts

Recommended fix:

Issue: Custom button actions don't trigger

Common causes:

  • the data-allspice-id attribute is missing or has the wrong button ID
  • no action selected for the button in the Publisher Portal
  • changes not synced yet

Recommended fix:

  • confirm the action is selected in the Publisher Portal
  • click Sync Buttons & Settings in Settings → Allspice
  • check the element's data-allspice-id matches the button ID in the Publisher Portal

When to contact support

If Allspice still isn't working after the steps above, open Support in the Publisher Portal and file a ticket.

Up Next: Troubleshooting