Validation site W14B
How LandexHub Consent behaves on a site like this
This is an ordinary WordPress site with the setup below. We install the plugin, visit the site as a new visitor and check, with three independent tools, what loads before and after a choice in the cookie banner.
How it works
LandexHub Consent with this theme, cache and tracking. GTM behind Cloudflare. Pages are cached at Cloudflare's edge (Cloudflare Free, Cache Rule "Eligible for cache" for HTML).
First visit, reject, accept, analytics only, withdraw, returning visitor.
Consent Monitor, Website Evidence Collector and a manual check against what the documentation promises.
What should happen here
No analytics or marketing cookies. Google sends only cookieless pings (gcs=G100). The Meta Pixel in GTM waits.
Same as before any choice; every Consent Mode signal is denied.
GA4 measures (gcs=G101); no marketing requests or cookies.
GA4 measures with full consent (gcs=G111). The Meta Pixel fires.
No new tracking starts; after a reload the site behaves as after Reject all.
A page served by Cloudflare behaves the same; one visitor’s choice never reaches another.
The Free plugin does not hold back iframes, as the documentation says. This site keeps a plain embed on purpose.
Try it yourself in a private window with your browser’s network tab open. Change your choice any time: Cookie settings