Machine-readable rights for
everyday websites.
ADPC for WordPress shows how rights-first communication can be built into one of the world’s most widely used website ecosystems. A CMS-level implementation makes Article 88b-style consent practical for organisations that cannot build custom infrastructure from scratch.
Four things the WordPress
implementation does
From serving consent requests to logging incoming signals, the plugin covers the full website-side exchange.
Serve consent requests
The plugin exposes a machine-readable consent-requests resource at a well-known path, ready for ADPC-capable browsers and operating systems to read.
Announce via HTTP headers
Response headers notify ADPC-capable software that the site supports the protocol, enabling automatic discovery without requiring user action.
Receive and apply choices
When a visitor sends an ADPC signal, the plugin reads it, maps it to the site’s consent categories, and applies the decision immediately.
Log signals in WP Admin
Incoming ADPC choices are recorded in the WordPress administration area, giving site owners an audit-ready record without extra tooling.
Works with existing CMPs
The plugin bridges ADPC signals into major WordPress CMP plugins so that choices are enforced at the purpose level, not just stored as metadata.
Suppresses unnecessary banners
When a valid ADPC choice is available, the consent banner is not shown. The difference between hiding a banner and actually applying a choice.
Bridge to existing CMP workflows
ADPC connects to existing consent infrastructure rather than replacing it, so the user’s decision flows through to scripts and purposes.
Detect the signal
The plugin reads the ADPC header or API response and confirms the signal is valid, current, and applicable to this site’s consent categories.
Map to CMP categories
ADPC purposes are mapped to the CMP’s consent categories. Consent, refusal, withdrawal, and partial choices are all represented correctly.
Apply and suppress banner
Scripts and vendors are enabled or denied through the CMP’s own consent state API. The banner is suppressed only after the choice is actually applied.
Lowering the barrier for adoption
A standard becomes real when it can be adopted without rebuilding the whole web. WordPress powers more than 40 percent of all websites. A CMS-level implementation brings ADPC within reach of SMEs, publishers, NGOs, public-interest projects, and agencies that cannot build custom infrastructure.
For policymakers, it provides a concrete example of how Article 88b can move from legal text to operational compliance through existing software ecosystems.
What a good CMS integration looks like
- Clear request configuration for site owners
- Stable, interoperable purpose identifiers
- Integration with existing CMP consent state APIs
- Audit-friendly logs, no excessive data collection
- No new dark patterns introduced
The WordPress implementation is a reference model. The same approach can be extended to Drupal, TYPO3, Joomla, headless CMSs, and public-sector web stacks.
Make your CMS ADPC-capable
Use the WordPress implementation as a reference model. Extend ADPC to the CMS ecosystem you work with.