by
jmwatee
0 (0 reviews)
Lexiscript Consent & Privacy
Blocks non-essential trackers until your visitor consents, applying the consent model of their own region. Free for one website.
Lexiscript Consent & Privacy ranks #67,469 among WordPress.org plugins with 0+ active installations, is #3,855 of 5,058 in the Security category, and was last updated Oct 29, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.0.1
Current Version v1.0.1
Updated 3 days ago
Last Update on 29 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
#3,855 of 5,058 in Security
Downloads -64.6% this week
Actively maintained
Rank
#67,469
—
No change
Active Installs
0+
—
No change
KW Avg Position
N/A
—
No change
Downloads
118
+1 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
39,901
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 9 more installs to reach 10+
Rank Changes
Current
#67,469
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
0.0
0 reviews
Overall
0%
5
0
(0%)
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
- 1.0.1
- Last Updated
- Oct 29, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- jmwatee
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#8
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#18
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#33
WP Super Cache
1M+ installs
#36
Frequently Asked Questions
Common questions about Lexiscript Consent & Privacy
Not for one website. Creating an account, adding a site, scanning it, reading every finding with the evidence behind it, and running the consent widget on it are all free. A paid plan covers additional websites, adds an automatic monthly re-scan of each, and generates a privacy notice per region.
Because it has to. The widget works by intercepting the browser APIs that scripts use to insert themselves, which only affects scripts that load after it. The plugin registers the widget with wp_register_script() and then prints that one handle at wp_head priority 0, rather than letting it print with the rest of the queue at priority 9 — several tag-manager plugins deliberately hook earlier than 9, and anything that loads first wins. It is not blocking my Google Tag Manager container Check that no other plugin or your theme is printing a tag above this one. This plugin prints at wp_head priority 0, which is earlier than anything using the default priority, but code hooked at priority 0 before it, or hard-coded directly into header.php above wp_head(), will still win. Move it below wp_head() and it will be caught.
The widget is a single small JavaScript file. It is loaded synchronously and deliberately so: a deferred or asynchronous script cannot intercept tags that have already started loading, which would defeat the point.
Yes. The tag is static markup, so it caches like the rest of the page. The consent decision itself is made in the visitor's browser, not on your server, so a cached page serves the correct behaviour to every visitor regardless of where they are.
Yes. Each site in the network has its own site key, set on that site's own settings screen.
Yes, for self-hosted or staging deployments, by defining a constant in wp-config.php: define( 'LEXISCRIPT_WIDGET_HOST', 'https://widget.example.com' ); It is deliberately not a setting. The value decides the origin of a script that runs on every page of your site, so it belongs with your deployment constants rather than in a form.
The tag stops being printed and trackers run as they did before. Your settings are kept in case you reactivate; deleting the plugin removes them.
