WeePie Cookie Allow is a WordPress plugin that handles cookie consent and third-party cookie blocking for sites that need to satisfy European and Californian privacy rules. It places a configurable notice bar or box on the site, prevents privacy-sensitive cookies from loading before a visitor agrees, and records what each visitor chose. It suits site owners who want a one-off purchase rather than a monthly consent-management subscription, and who are comfortable configuring a plugin themselves.
What the plugin actually does for a site owner
The core job is straightforward: stop cookies that track or identify people from firing until the visitor has given permission, then keep a record of that permission. WeePie approaches this by automatically blocking a list of common third-party services before consent is given. The vendor maintains that list and invites customers to request additions. For a typical site running analytics, embedded video and social widgets, that covers most of the practical exposure without the owner having to identify each script by hand.
On top of the blocking layer sits the notice itself. The bar or box can carry a link to a cookie policy page, an icon that opens a settings pop-up, an accept button and a decline button. The decline path matters more than it first appears: a notice that only offers “accept” is not valid consent under GDPR, so having a genuine refusal option built in is a baseline requirement rather than a nice extra.
Several capabilities go beyond the minimum. Consent logging stores both acceptances and refusals, which is the evidence a site owner needs if a visitor later asks what they agreed to. Visitors can change their mind through a settings option, and there is a reset button that clears a previous choice — the plugin’s answer to the right to withdraw consent and the right to erasure. A placeholder system lets a site show custom content in the space where blocked cookie content would normally appear, so a blocked YouTube embed does not simply leave a blank gap in the layout.
Geographic targeting is handled per region. The consent bar can be shown only to visitors from the EU and UK, and a separate notice with an opt-out path can be shown only to visitors from California. That combination addresses the structural difference between GDPR, which requires prior consent, and CCPA, which is built around notice and the right to opt out of the sale of personal information. The plugin also supports Google Consent Mode v2, which means the consent choice can be passed to Google Tag Manager so that Google’s own tags adjust their behaviour accordingly — increasingly necessary for sites running Google Ads or GA4.
Configuration and compatibility round out the picture. There are styling options for the notice, WPML support for multilingual sites, declared compatibility with common caching plugins such as WP Rocket, WP Fastest Cache and LiteSpeed Cache, and multisite support within a single domain under one licence. The plugin is declared compatible with WordPress 6.0 through 6.9 and the major browsers. Source files are included, which matters to agencies that need to audit or extend code.
Where this fits, and where it does not
The strongest fit is a small or mid-sized WordPress site — a business site, a blog, a brochure site with a contact form — run by an owner or a freelancer who wants to handle consent once and move on. The flat $25 price with no recurring fee is the main draw for that audience. A single-site owner who would otherwise pay a monthly consent platform fee will find the economics obvious.
Multisite networks within one domain are another reasonable fit, since one licence covers the network. Agencies building client sites can also use it, provided they buy a licence per domain, which the vendor states explicitly.
There are situations where this is the wrong tool. A large publisher or an e-commerce operation with dozens of third-party scripts, a legal team, and a formal data protection impact assessment will likely need a consent platform that offers vendor-level granularity, automated cookie scanning, and audit reporting. WeePie’s automatic block list is maintained by the vendor rather than discovered by scanning the site, so a site with unusual or custom trackers will need manual work. Anyone who wants a fully managed compliance service, rather than a plugin to configure, should look elsewhere.
Strengths and honest limitations
Strengths
- One-time cost with no subscription, which is unusual in the consent-management category.
- Automatic blocking of common third-party cookies before consent, rather than relying on the site owner to find every script.
- Separate handling for EU/UK visitors and California visitors, reflecting the different legal models.
- Consent logging and a consent-reset option, covering the record-keeping and withdrawal requirements.
- Google Consent Mode v2 support, which is now a practical requirement for sites running Google advertising or analytics.
- Declared compatibility with WPML, major caching plugins and WordPress Multisite, plus source files included.
- A track record: 6,703 sales and a 4.55 out of 5 rating across 128 reviews.
Limitations
- The automatic block list is vendor-curated. If a site loads a tracker that is not on that list, the owner has to notice the gap and request an addition or handle it manually. There is no automated site scan that discovers cookies for you.
- Compliance is configuration-dependent. The plugin provides the mechanisms — geo-targeting, logging, opt-out — but the vendor does not state that any particular configuration is legally sufficient, and it cannot be. Getting the settings wrong produces a notice that looks compliant but is not.
- Support is limited to six months from purchase. After that, ongoing help presumably requires renewal, so the “no annual costs” claim applies to the licence rather than to support.
- Licensing is per unique domain. A developer running twenty client sites needs twenty licences, which changes the cost calculation considerably.
- The vendor does not publish a definitive count of pre-blocked third parties in the listing, so buyers cannot assess coverage before purchase without checking the demo.
How it compares with the wider consent-plugin category
Cookie consent tools on WordPress generally fall into three groups. At one end are free plugins that display a notice and little else — they satisfy the appearance of compliance without blocking scripts or logging consent. At the other end are hosted consent platforms that scan a site automatically, catalogue every cookie and vendor, provide granular per-purpose consent, and charge monthly. WeePie sits in the middle, and deliberately so.
Against the free tier, the meaningful difference is the blocking engine and the logging. A notice bar alone does not prevent cookies from being set, and under GDPR the setting of the cookie is the act that requires consent. That distinction is the reason a paid plugin of this type exists at all.
Against hosted platforms, the trade-off runs the other way. WeePie gives up automated scanning, deep vendor-level controls and managed support in exchange for a flat fee and full control of the data, since consent records live in the site’s own database rather than a third-party service. For a site with a modest script footprint, that is a reasonable exchange. For a site with a complex ad stack, the missing granularity becomes a real problem rather than a minor gap.
The practical question is not which category is better but how many third parties a given site actually loads. Counting them before buying is the sensible first step.
Frequently Asked Questions
Does this plugin block cookies automatically before a visitor accepts?
Yes. WeePie blocks a set of common third-party cookies before consent is given, so tracking scripts do not fire on page load. The list is maintained by the developer rather than generated by scanning the site, so unusual or custom trackers may need to be added manually or requested from the vendor.
Can the cookie banner be shown only to visitors from the EU and UK?
Yes, the plugin supports geographic targeting. The consent bar can be limited to EU and UK visitors, and a separate notice with an opt-out option can be shown only to visitors from California. This lets a site apply the consent model that matches each region’s rules instead of showing one notice worldwide.
Is WeePie Cookie Allow compatible with Google Consent Mode v2?
Yes. The plugin is declared compatible with Google Consent Mode v2, which allows a visitor’s consent choice to be passed to Google Tag Manager so Google’s own tags adjust accordingly. Sites running Google Analytics 4 or Google Ads generally need this to keep their measurement working lawfully.
How many WordPress sites can be covered by one licence?
One licence covers one unique domain name. Multisite installations within the same domain are covered by a single licence, but each additional domain requires its own licence. Agencies managing multiple client sites should factor that into the total cost before purchasing.
Verdict
WeePie Cookie Allow is a sensible purchase for a site owner or freelancer running a WordPress site with a moderate number of third-party scripts who wants consent handled without a recurring bill. The combination of automatic blocking, regional targeting, consent logging and Consent Mode v2 support covers the practical requirements most small sites face, and the sales volume and rating suggest the plugin does what it claims for a large number of buyers. It is a weaker fit for publishers, large e-commerce operations, or anyone who needs automated cookie scanning and vendor-level granularity, because the block list is curated rather than discovered and the plugin leaves compliance decisions in the owner’s hands. Buyers should also weigh the per-domain licensing and the six-month support window against the headline price. For straightforward sites, the calculation usually comes out in the plugin’s favour.
