by
Work More
0 (0 reviews)
WorkMore Cookie Crumb – Cookie Consent Banner
Cookie consent banner that blocks tracking scripts until visitors agree, with a cookie scanner, a consent log and Google Consent Mode v2.
WorkMore Cookie Crumb ranks #55,061 among WordPress.org plugins with 0+ active installations, and was last updated Oct 19, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.0.6
Current Version v1.0.6
Updated 1 week ago
Last Update on 19 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
Downloads -80% this week
Actively maintained
Rank
#55,061
—
No change
Active Installs
0+
—
No change
KW Avg Position
14
—
No change
Downloads
138
+5 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
27,493
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
#55,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
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.6
- Last Updated
- Oct 19, 2026
- Requires WP
- 6.5+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- Work More
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 Now
Frequently Asked Questions
Common questions about WorkMore Cookie Crumb – Cookie Consent Banner
It is free, with no limit: no account to open, no page view quota, no visitor count that stops the banner. Everything this plugin does runs on your own site. A separate Pro add-on exists for those who want more (see "Pro add-on" above); nothing in this plugin is locked without it.
No plugin can promise that by itself — compliance depends on what your site does, the law that applies to it and how you set things up. What this plugin gives you are the tools those laws ask for: consent before tracking (opt-in), a "Reject all" as easy as "Accept all", consent by category, a way to change the answer at any time, and a record of each answer. It is not legal advice.
Yes. An embedded YouTube video, Google Map or Facebook post does not load before the visitor allows its category; a placeholder with a button stands in its place, and the button allows it. Any other embed can be held back by a rule with a piece of its address.
Yes. It recognises WooCommerce's own cookies (cart, session) and its order attribution (sbjs_*), the cookie scan reads a shop's own pages, and the WP Consent API tells WooCommerce what the visitor allowed.
Yes. The server sends the same page to every visitor and never reads the visitor's answer; what runs is decided in the browser. Publishing the banner asks the cache plugins and hosts the plugin knows to clear their page cache (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, Cache Enabler, WP-Optimize, Autoptimize, Breeze, Hummingbird, Comet Cache, SiteGround Optimizer, Nginx Helper, WP Engine, Pantheon); for any other cache, clear it after publishing. Plugins that combine, defer or delay scripts are asked — by marks on its tag that Autoptimize, LiteSpeed Cache, WP Rocket and Cloudflare's Rocket Loader read — to leave the plugin's first script where it is: it has to run before every other script of the page.
Yes. Before a visitor answers, the plugin sets the Consent Mode v2 signals to "denied" — the advertising signals follow your marketing category, the analytics signal your analytics category — and updates them with each answer; an event named wmcc_consent is pushed to the data layer as well. You choose how Tag Manager itself is treated: listed under a category, the container waits for that category like any other script; left out of the list, it loads and its tags follow the Consent Mode signals.
Google Analytics, Google Tag Manager, Google Ads, YouTube, Google Maps, Meta Pixel and Facebook embeds, and the cookies WordPress and WooCommerce set themselves. A recognised service gets its category suggested, and its cookies listed with what they are for. Anything else the scan finds is shown as not known: you choose its category. A script is held back by a rule that looks for a piece of its address, so any script can be listed.
When you press "Scan the site", the screen opens a sample of your pages — the front page, the newest entry of each kind of content, a shop's own pages, and addresses you add — in your own browser, served the way a visitor who is not logged in gets them. The server notes the cookies it sets and what stands in each page's markup; a small script in the page notes the cookies scripts set and everything the page loads. Nothing is sent to an outside service, and nothing is added to your cookie list until you choose it. A scan cannot see what loads only after a click or a purchase, what an ad blocker in your browser stops, or the cookies another site keeps on its own domain; those are listed where the service is known. While it runs, your pages' own trackers run once in your browser, as they would for a visitor who allowed everything — in a browser that is logged in to your site, and including trackers your site leaves out for administrators.
Scripts and embedded frames always can, and images and loading hints when they stand in the page's markup. What a script that is already running sends by itself or writes into the page as markup, and style sheets and fonts loaded from another site, cannot be held back by a rule: hold back the script that does it, or serve the file from your own site. After you publish, the scan lists whatever still reaches another site before a visitor answers, and says for each whether a rule can hold it.
By default a small round button stays in a corner of every page and opens the cookie settings window. Instead of it, or as well, any link to #cookie-settings opens the window — in a menu, a footer or a page — and so does the [wmcc_settings] shortcode. Withdrawing consent deletes the listed cookies your site set and loads the page again without the scripts. Cookies another site keeps on its own domain, and cookies no script can read, cannot be deleted from a page.