by
sliStudios Web Development
5 (1 reviews)
Consentinel Cookie Consent
Cookie consent built US-first: Blocks trackers before they run, for CIPA defense, with a built-in tracker scanner. CCPA/CPRA and GDPR ready.
Consentinel Cookie Consent ranks #36,061 among WordPress.org plugins with 0+ active installations, a 5/5 rating from 1 reviews, and was last updated Sep 17, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.2
v0.2.81
Current Version v0.2.81
Updated 6 days ago
Last Update on 17 Sep, 2026
Refreshed 8 hours ago
Last Refreshed on
Downloads +39.2% this week
Actively maintained
Rank
#36,061
—
No change
Active Installs
0+
—
No change
KW Avg Position
75.5
24.5 better
Downloads
173
+1 today
Support Resolved
0%
—
No change
Rating
100%
Review 5 out of 5
5
(1 reviews)
Next Milestone 10
0+
10+
16,321
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 4 more installs to reach 10+
Rank Changes
Current
#36,061
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
1 reviews
Overall
100%
5
1
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.2.81
- Last Updated
- Sep 17, 2026
- Requires WP
- 6.8+
- Tested Up To
- 7.1.2
- PHP Version
- 7.4 or higher
- Author
- sliStudios Web Development
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 1
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Consentinel Cookie Consent
Not the fetch, no. Consentinel gates what WordPress renders, and it runs before anything else on the page. A script injected after WordPress finishes — Cloudflare's /cdn-cgi/ features such as Web Analytics, Rocket Loader or Zaraz, or an equivalent from your host or firewall — is added to the response on its way to the visitor, so no plugin running on your server can see or gate it. Consentinel still blocks what such a script transmits once it runs, because it patches the browser's network APIs before any of it executes. But it cannot stop the browser fetching the file. If you need pre-consent silence there, turn the feature off at the CDN.
Yes, completely. The banner, the blocking engine, the tracker scanner, the consent log, Global Privacy Control and Google Consent Mode all run on your own server with no account and no outbound connection to us.
No plugin can do that, and any that claims otherwise is overselling. Consentinel blocks what can be blocked from a WordPress site, records what your visitors chose, and is explicit about what it cannot reach. Compliance also depends on your own policies, your server-side tracking, and advice from your counsel. This plugin is compliance tooling, not legal advice.
Three things, stated plainly. Trackers injected by Google Tag Manager at runtime are invisible to the file and page scanner, though the blocking engine still intercepts their network requests. Server-side tracking — Meta Conversions API, server-side GTM, log-based analytics — never touches the browser, so no consent tool sees it. And anything injected by your CDN after WordPress has finished, such as Cloudflare's own scripts, is out of reach of any WordPress plugin.
Web fonts and icon kits arrive as a stylesheet, which the browser fetches through a path JavaScript cannot intercept — no consent tool can stop that in the browser. Consentinel stops them on the server instead, but only for Always block: A stylesheet cannot be restored after consent, so blocking it "until consent" would leave your fonts broken permanently. The Tracker scan tab says so where you set the mode.
The banner is about 20 KB of vanilla JavaScript and CSS with no jQuery and no external dependencies. The blocking engine runs before your trackers so it does not wait on anything. The tracker scan runs weekly in the background, never during a visitor's page load.
They are kept. The consent log survives uninstall unless you explicitly opt in to deleting it, under Consent log → Data on uninstall. Consent records are evidence, so the default is to preserve them.
Yes, per site. Each site in the network has its own settings, scan results and consent log.