by
landexhub
1 (0 reviews)
LandexHub Consent – Cookie Banner, GDPR & Google Consent Mode v2
Cookie banner for GDPR with Google Consent Mode v2, script gating, site diagnostics and consent logging. No cloud service required.
LandexHub Consent ranks #56,088 among WordPress.org plugins with 1+ active installations, a 1/5 rating from 0 reviews, and was last updated Oct 25, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v0.9.4
Current Version v0.9.4
Updated 1 week ago
Last Update on 25 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
Downloads -77.7% this week
Actively maintained
Rank
#56,088
—
No change
Active Installs
1+
—
No change
KW Avg Position
N/A
—
No change
Downloads
204
+2 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
43,151
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 7 more installs to reach 10+
Rank Changes
Current
#56,088
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
1.0
0 reviews
Overall
20%
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
- 0.9.4
- Last Updated
- Oct 25, 2026
- Requires WP
- 6.3+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- landexhub
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- 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 LandexHub Consent – Cookie Banner, GDPR & Google Consent Mode v2
Not in the consent log. It is privacy-minimal: it stores a random consent identifier, the chosen categories, a timestamp, the page path and a fingerprint of the bar texts. To limit abuse of the recording, a request counter is kept under a salted hash of the visitor's IP address; it expires after 10 minutes.
A record of an anonymous visitor has no IP address, e-mail or other identifier besides its random consent ID, so the log alone cannot tie it to a person (GDPR art. 11). A visitor can identify their own records with their consent ID, shown at the bottom of the consent settings dialog. Search the Consent log for that ID to show or export the records; an erase button deletes them. Logged-in users are covered by the standard WordPress Export/Erase Personal Data tools.
The plugin itself sends nothing: no telemetry, and consent records stay in your WordPress. If you configure a GTM container or a Google measurement ID, your visitors' browsers load those Google tags and they communicate with Google — see External services. Scripts you gate run only after consent and then talk to their own providers.
Yes, in advanced mode (the default) or basic mode. In advanced mode Google tags load before consent and send cookieless signals until the visitor agrees; in basic mode the gtag.js ID set in this plugin loads only after consent. The denied default is printed before the GTM container or gtag.js set in this plugin. If you set your own consent default elsewhere, turn the plugin's default off with the landexhub_consent_emit_consent_default filter; it is not detected automatically.
Mark the script tag with type="text/plain" data-consent-category="marketing"; for an external script also move its address from src to data-src. Or gate an enqueued script with the LandexHub_Consent::block_handle( $handle, 'marketing' ) PHP helper. Google tags loaded through GTM or gtag.js follow Google Consent Mode, so they are usually not blocked; make sure the tags in your GTM container use consent settings — Custom HTML tags and non-Google tags in a container do not follow Consent Mode by themselves. Guide: Blocking scripts.
Yes, always. By default a "Cookie settings" link is printed in the site footer; you can switch to a floating icon instead, place the [landexhub_consent_settings] shortcode or the "Cookie settings link" block anywhere, or call LandexHubConsent.openSettings() from your own link. A change updates Google Consent Mode and the WP Consent API immediately. One technical honesty note: a third-party script that already ran on the current page cannot be un-run — after a withdrawal it stays inactive from the next page load on.
It fetches your own front page (a request to your own server) and lists the third-party scripts, embedded frames and known tracking pixels it recognises in the HTML, who adds each of them and whether consent governs it. For every source that loads before consent it shows how to gate it by hand. It only sees the front page — a source that loads only on a subpage does not show up there.
Through two channels. When the free WP Consent API plugin is installed, the plugin publishes the visitor's decision on that shared standard, both in the browser and for wp_has_consent() in PHP, so plugins that read it can follow it. Google tags added by other plugins follow the Google Consent Mode v2 signals the plugin sends, as long as they load after its default. Tested end to end (first visit, accept, reload, withdrawal, consent reset): Site Kit by Google with its own Consent Mode on (it then reads the WP Consent API) and off (its Google tag follows Consent Mode), and MonsterInsights with a manually entered GA4 ID (its tag follows Consent Mode; it does not read the WP Consent API). Other plugins were not tested; check them on your site.
Yes — put the [landexhub_consent_services] shortcode (or the "Services & cookies overview" block) on your cookie policy page. It renders a table of the services found on your front page and the ones in your services list, with consent category, known cookies and privacy policy links. It is generated technical data, not legal advice.
No plugin can do that on its own. LandexHub Consent provides the technical tools — consent banner, script gating, proof of consent, data export and erasure. Whether your site complies depends on how it is configured and on what it does; that responsibility stays with the site owner.