How the installation works
- 1
Install and activate the plugin
It ships as a standard WordPress plugin with no build step.
- 2
Generate a pairing code
Create a one-use code in the workspace and enter it in WordPress. The site claims itself, and from then on it holds its own credentials.
- 3
Confirm the connection
The plugin sends periodic heartbeats, so the workspace can tell you whether an installation is healthy rather than guessing.
- 4
Configure and verify
Map technologies to categories in the workspace, publish, then run a browser verification scan.
The plugin can interoperate with the separately installed WordPress Consent API, an ecosystem API that compatible plugins can read. The API does not itself block third parties, and only plugins that implement it correctly will react to the state. Verify each plugin; incompatible loaders still need direct gating or removal.
What else is loading
WordPress sites accumulate. A form plugin adds a reCAPTCHA, an SEO plugin adds a verification tag, a theme bundles a slider that pulls a font from a CDN, an analytics plugin adds its own snippet, and somebody once pasted a Facebook pixel into a widget.
- Scan the rendered page rather than reading the theme: plugins inject at runtime
- Check a post, a page and any form-bearing template; plugin output is often template-specific
- Look specifically for a second consent plugin; leftovers from a previous one are common
- Self-host web fonts where practical. A remote stylesheet can be gated only if it is omitted initially and inserted conditionally; a consent runtime cannot undo a link the browser already parsed
Caching and consent do not conflict, if you set it up right
The decision is client-side, so the page can stay cacheable
The runtime resolves the configuration and the visitor’s decision in the browser, which means the HTML does not need to vary per visitor. A page cache and a consent banner coexist without a vary header, as long as nothing server-side is rendering different markup for consenting and non-consenting visitors.
Common questions
Does it work with WooCommerce?
Yes. WooCommerce is a WordPress plugin, and the consent plugin covers the whole site. The store-specific considerations are on the WooCommerce page.
What PHP and WordPress versions are supported?
WordPress 6.2 and above, PHP 7.4 and above. There is no build step: what ships is what runs.
Will it conflict with another consent plugin?
Yes, and that conflict is worth resolving before anything else. Two banners produce contradictory states and records that cannot be explained afterwards.
Sources and verification
Verified on . Product-behaviour statements were checked against the current implementation and tests. The links below are the verification basis recorded for this article. They support the stated facts, not a legal conclusion for every site or configuration; recheck changing vendor behaviour before relying on it in production.
- WP Consent API project documentation
Official documentation
Checked
- StrongPrivacy documentation
Product documentation
Checked
See what your own site is loading
A browser scan reports the requests and storage it observed during the sampled journey. Use configured workspace scans to compare the states and pages that matter to your implementation.