Ordelix Consent cleaner consent system with real control and proof.

WordPress consent, without the CMP mess

Google Site Kit-first
Self-hosted by default
Accessibility and translation ready
Evidence exports built in
Site Kit-first by design, self-hosted by default, and honest about what is supported. Ordelix combines deterministic consent contracts, bounded adapters, scanner-led remediation, and exportable evidence into one lightweight WordPress-native consent layer.

It does not fake full-script magic. It gives teams a consent model they can trust under review.

Ordelix stays strongest on deterministic paths: Site Kit, explicit scripts, handle-based gating, bounded adapters, remediation guidance, and export-ready technical evidence.
Bounded vendor adapters for supported WP-native output paths
Scanner, vendor inventory, and remediation guidance for real-world stacks
Audit, compliance, and customer evidence exports from inside WordPress

What makes it different

Everything teams need to run consent inside WordPress without losing control.

Feature surface

Site Kit-first Google consent

Built around Google Site Kit and WP Consent API so Google tags follow consent choices without duplicate consent-mode scripts.

Explicit consent contracts

Supports consent-gated scripts, handle-based gating, and replay-ready iframe, image, and HTML placeholders.

Bounded vendor adapters

Supports selected WordPress-enqueued paths for Meta Pixel, TikTok Pixel, Hotjar, LinkedIn Insight, and Microsoft Clarity.

Scanner and remediation guidance

Detects common tracker stacks and guides operators toward supported contracts instead of pretending every live script is already controlled.

Audit and evidence exports

Generate audit packages, compliance exports, vendor inventory reports, and customer evidence bundles directly from WordPress.

Privacy, accessibility, and translation ready

Self-hosted by default, accessibility-checked on the frontend banner, and translation-ready for teams that need to localize.

A sharper workflow from implementation to proof.

How teams use it

Ordelix is strongest when teams stay on deterministic paths: Site Kit for Google tags, explicit consent contracts for custom scripts, and exportable evidence when internal or client review starts.

01. Connect the right stack

Use Google Site Kit with WP Consent API for the cleanest Google-tag path, or move custom services onto explicit gated contracts.

02. Collect consent clearly

Show a modern banner with strict opt-in defaults, accessible preference controls, and a reopen button that stays useful instead of getting in the way.

03. Document the outcome

Export audit data, compliance packs, vendor inventory, and customer evidence whenever legal, procurement, or client teams ask for proof.

Why teams choose Ordelix over noisy consent stacks

Built for Site Kit, not against it

Ordelix works with Site Kit’s consent path instead of layering duplicate Google logic that becomes harder to trust and maintain.

Honest about enforcement boundaries

It supports deterministic contracts where behavior can be proven and surfaces migration guidance when a stack falls outside the trusted surface.

Buyer-ready evidence built in

Audit export, compliance pack, vendor inventory, evidence bundle, and release-gated diagnostics are already part of the product surface.

Run consent the WordPress-native way.

Use the cleanest path for Site Kit, keep control inside WordPress, and move unsupported tracker paths onto explicit, testable contracts.
Start testing