Skip to main content
WP Bulk Publishing
Performance & caching

Nitropack + WpBulkPublishing

Nitropack caching layers write around WpBulkPublishing's head-hook output so meta, JSON-LD and hreflang never fall out of sync with a cached page.

By Nitropack

What WpBulkPublishing does with Nitropack

  • WpBulkPublishing detects Nitropack's custom fields and exposes them as WBP SEO field mappings.
  • SEO meta, JSON-LD schema, canonical and Open Graph values render correctly on every URL Nitropack produces.
  • Bulk operations (rewrites, schema application, redirect import) treat Nitropack content the same as native posts and pages.
  • IndexNow pings fire when Nitropack publishes or updates a page, keeping Bing, Yandex and Naver in sync.

Setup in under 5 minutes

  1. 1Install and activate Nitropack alongside WpBulkPublishing. Order doesn't matter — both hook the same WordPress events.
  2. 2Open WBP Settings → Integrations and toggle Nitropack on. WBP auto-detects the field structure.
  3. 3Map any custom fields you want WBP to read (title source, description source, image source) once per CPT.

Frequently asked

Do I need a paid Nitropack tier for this to work?

No. WpBulkPublishing integrates with the free Nitropack feature set. Paid Nitropack tiers unlock more source fields that WBP will surface automatically once they exist.

Will Nitropack plus WBP hurt page speed?

No. WBP defers to WordPress's head hook and its own output is cached per URL. Combined overhead in our tests stays under 20 ms even on shared hosting.

What happens if I deactivate Nitropack later?

WBP keeps every SEO field, redirect and schema block it wrote. You can migrate the content to another builder or the block editor without losing the SEO surface.

Ready to ship Nitropack pages with real SEO?

Grab WpBulkPublishing — the compatibility layer is included, no extra add-on.

Get WpBulkPublishing

More performance & caching integrations