CookieYes free plan limit
5,000 pageviews a month.
Then the banner
switches itself off.
CookieYes’s free plan covers 5,000 pageviews a month per website, or 15,000 for sites already on Free before 1 July 2025. Every load of a page with the CookieYes script counts, whether the visitor answers the banner or not. At 100%, CookieYes stops showing the banner until the count resets on your monthly cycle date, or until you upgrade; Free cannot buy extra pageviews. The next plan, Basic, is $10 a month for 100,000. Below: what the free plan includes, exactly what happens at the limit, a calculator for your cut-off day, the WordPress plugin’s way round the counter, and the alternatives, Builderify’s cookie banner included, with its own catch.
By the Builderify team
What do you get on the CookieYes free plan?
The banner, until the pageviews run out.
Free is a working consent platform: a banner with Accept and Reject, automatic blocking, Google Consent Mode v2, a scanner and a consent log. What it limits is reach. Every CookieYes plan is priced per website by pageviews, and Free has the smallest allowance and no way to buy more.
| CookieYes, per website | Free $0 for one site per account | Basic $10 a month, or $100 a year | Pro $25 a month, or $250 a year | Ultimate $55 a month, or $550 a year |
|---|---|---|---|---|
| Pageviews a month | 5,000 (15,000 if on Free before 1 July 2025) | 100,000 | 300,000 | Unlimited |
| Past the allowance | Banner off until the reset | $0.30 per 1,000 extra | $0.30 per 1,000 extra | Fair use |
| Pages per scan | 100, 5 scans a month | 600 | 4,000 | 8,000 |
| Consent log | Yes | Yes | Yes | Yes |
| Google Consent Mode v2 | Yes | Yes | Yes | Yes |
| Custom colours and CSS | No | Yes | Yes | Yes |
| Multilingual banner | No | Yes | Yes | Yes |
| Geo-targeting | No | No | Yes | Yes |
| IAB TCF and Global Privacy Control | No | No | Yes | Yes |
| Remove CookieYes branding | No | No | No | Yes |
What counts as a pageview
Each load or reload of a page that carries the CookieYes script, for every visitor, “regardless of their interaction with the cookie consent banner”. Known bots are left out. One reader browsing five posts is five pageviews.
When the count resets
Monthly, on the day your billing cycle began, not on the 1st. On Free that is the day you registered the site with CookieYes; register on the 25th and it resets on the 25th. Upgrading starts a new cycle that day.
5,000 or 15,000
Sites added to Free on or after 1 July 2025 get 5,000. So do sites that fall back to Free after the 14-day trial or a cancelled paid plan from that date. Sites already on Free before it keep 15,000.
Prices are CookieYes’s US-dollar prices on 15 October 2026, before tax, per website; annual billing is two months free. Only one free plan is allowed per account. Paid plans start with a 14-day trial.
What happens when you hit the CookieYes pageview limit?
The banner stops. The site doesn’t.
When you reach 100%, your cookie banner will no longer be displayed on your website and no new pageviews will be tracked.
Once the 100% limit is reached, the banner will be automatically disabled. After upgrading the plan, it will be reactivated.
Extra pageviews are not available on the Free plan.
One cycle on Free, in order
-
Day 1
The count starts again on your cycle date, the day you registered the site.
-
80% and 95%
An alert on the CookieYes dashboard and by email. Nothing changes on the site yet.
-
100%
The banner is no longer displayed and pageviews stop being counted. Visitors who arrive now are not asked.
-
Until the reset
On Free there is nothing to buy: you wait for the next cycle or move to a paid plan. Upgrading brings the banner back the same day.
-
Paid plans
Basic and Pro can bill $0.30 per 1,000 extra pageviews instead of stopping. That is on by default for accounts opened after 23 December 2025 and a setting for older ones.
Does anything still block the trackers?
CookieYes’s documentation describes the banner; it does not say whether its automatic blocking, or the Consent Mode defaults it sets for Google tags, keep running while the banner is suspended. Don’t assume either way. On a day the banner is off, open your site in a private window, then look in your browser’s developer tools under Application, Cookies. A _ga or _fbp cookie there means analytics or ad tags are running for visitors nobody asked.
Why it matters
In the UK and the EU, non-essential cookies need consent before they are set. The UK regulator, the ICO, is blunt about it: “you cannot set non-essential cookies on your website’s homepage before the user has consented to them.” The EDPB’s consent guidelines make the same point about any processing that relies on consent: it has to be asked for first. A switched-off banner changes none of that; it only stops asking. This is general information, not legal advice.
The safe reading: treat 100% as “no consent banner” and plan so you never reach it. If you run Google Analytics, whether GA is legal where you are and how Consent Mode v2 defaults work are worth ten minutes each.
When will I hit the CookieYes cap?
Your cut-off day, and what fits instead.
Take pageviews, not visitors, from your analytics or your host’s statistics, and remember that analytics behind a consent banner undercounts: CookieYes counts the visitors who never said yes. Round up if in doubt.
Each with the traffic above.
7,000 pageviews, 58% of the cycle’s traffic, would load with no banner on the page until the count resets.
- Cut-off
- Day 13
- No banner
- 7,000
- A day
- 400
Basic is the smallest plan that keeps the banner on all month.
Runs on your own WordPress server, so traffic never switches it off. Premium, from $59 a year for one site, adds records of consent, GeoIP, TCF and A/B tests.
Your traffic does not matter here; your number of pages does. Past 50 subpages the site needs Premium, billed by page count.
Covered by the 250 free credits a month, as long as nothing else on your widget uses them.
- CookieYes
- $100
- Complianz free
- $0
- Builderify
- $0
Assumes the same traffic on every site, spread evenly; real traffic comes in bursts, so a busy week brings the cut-off forward. CookieYes: US-dollar prices before tax, the cheapest plan that keeps the banner on, with extra pageviews at $0.30 per 1,000 once a site is more than 1,000 over, rounded up. Builderify: its rate card, 10 credits per 1,000 page loads of the widget that carries the banner, 250 free credits a month, 100 credits once for each website after the first, and one-time packs from $9. If a Builderify balance reaches zero, the banner stops too: read Know this first.
Does the CookieYes WordPress plugin
have a pageview limit?
Only when it is connected to the CookieYes web app. The plugin, on more than a million WordPress sites, runs in one of two modes. CookieYes’s setup guide says connecting is optional and recommended; the plugin’s own code shows what each mode does with the counter.
Connected to the web app
The free account most people sign up for
- Banner script
- Loaded from cdn-cookieyes.com
- Pageview limit
- Yes: 5,000 or 15,000 on Free
- Cookie scan
- Automatic, by CookieYes
- Consent log
- Kept by CookieYes, CSV export
- Cookie policy page
- Generated for you
- Settings
- Mostly at app.cookieyes.com
Plugin only, not connected
What the plugin calls standalone mode
- Banner script
- Served by the plugin from your site
- Pageview limit
- None: nothing is counted
- Cookie scan
- None: you list cookies yourself
- Consent log
- None: no local log exists
- Cookie policy page
- Not generated
- Settings
- In WordPress admin
So yes, a WordPress site can keep the CookieYes banner with no pageview cap by not connecting it. The price is the record. The GDPR asks you to be able to show that a visitor consented, and in plugin-only mode no consent is logged anywhere. If you want unlimited traffic and a log on WordPress, a self-hosted plugin such as Complianz, below, does both.
CookieYes banner not showing? Check these, in order.
The quota is the cause people suspect last, and it is the first to check. Test in a private window each time, so your own saved choice doesn’t hide the banner from you.
-
The pageview quota
Log in at app.cookieyes.com and open the dashboard’s pageviews. At 100% on Free, the banner is off until your cycle date. This applies to connected plugins and to any non-WordPress site using CookieYes.
-
A trial that ended
A paid trial you cancelled drops to Free when its 14 days are up, with 5,000 pageviews if that happened on or after 1 July 2025. A busy site can use those up within days.
-
Caching
The plugin’s own notes call caching the top cause of a banner that disappeared. Purge your caching plugin, your host’s cache and any CDN after every banner change.
-
The theme
The banner is printed by WordPress’s
wp_footerhook. A theme that never calls it, or a headless front end, shows no banner. -
A builder preview
The plugin hides the banner inside the Elementor and Divi editors and the Customizer. Check the live page instead.
CookieYes alternatives,
and what limits each free plan.
Every free consent tool is limited by something. CookieYes counts pageviews, Cookiebot counts pages, Complianz limits features, and Builderify counts credits. Which one bites depends on whether your site is busy, big, or both.
| On the free plan | CookieYes | Complianz | Cookiebot | Builderify |
|---|---|---|---|---|
| Limited by | 5,000 pageviews a month per site (15,000 if on Free before 1 July 2025) | Features, not traffic. The setup scan covers up to 50 posts | 50 subpages and one domain. No traffic limit | 250 credits a month; banner page loads cost 10 per 1,000, about 25,000 if nothing else uses them |
| When you outgrow it | Banner off until the cycle resets, or upgrade | Nothing switches off | Over 50 subpages, the site needs Premium | At a zero balance the widget, and the banner, stop loading |
| Consent records | Consent log in the web app; none in plugin-only mode | Proof of consent; records of consent are Premium | Not listed for Free; Premium includes consent record keeping | Log kept 24 months, IP truncated, CSV export |
| Region rules | Geo-targeting from Pro, $25 a month | Region banners; GeoIP detection is Premium | Geotargeting on Premium | Can ask opt-in or opt-out by the visitor’s time zone |
| Where it runs | CookieYes’s servers, or your site in plugin-only mode | Your WordPress server | Cookiebot’s servers | Builderify’s servers: a consent tag and the widget |
| Works on | WordPress, Shopify, Wix and any site | WordPress only | Any site; has a WordPress plugin | Any site; on WordPress, pasted with a snippet plugin |
| First paid step | Basic, $10 a month per site | Premium, $59 a year for one site | Premium Lite, €7 a month | One-time packs from $9, no subscription |
Complianz
The closest thing to “CookieYes without the counter” on WordPress. Complianz says neither its free nor its paid plans limit pageviews, and it runs on your own server. Premium is $59 a year for one site, $179 for five.
Cookiebot
Free for one small site: under 50 subpages, one domain, any amount of traffic. Past that, Premium is billed per domain by page count; Premium Lite, €7 a month, adds the paid features to a site under 50 subpages. The free banner is Cookiebot’s default design in one language, and a visitor’s consent lasts up to a month before they are asked again.
Anything else
We checked only these three for this guide. Before you move to any other consent tool, find out what its free tier counts, traffic, pages or consents, and what happens when you pass it, on its own pricing page.
Cookiebot prices are in euros, excluding VAT, per domain, and step up with your page count. Complianz Premium prices are per year with a year of updates and support.
A CookieYes alternative
with its own catch, up front.
Builderify Cookie Consent is a banner plus a small consent tag that goes first in your <head>. The tag sets Google Consent Mode’s seven signals before your Google tags run and updates them on every choice. Tags you connect by ID, Google Analytics 4 and Google Ads among them, load only after a yes. Global Privacy Control is honoured for marketing, and every decision is logged.
There is no pageview quota and no plan. The banner lives in the Builderify widget, and each page load of the widget is metered like any other: 10 credits per 1,000. The same widget carries everything else you switch on, from popups to visitor journey analytics, which can wait for cookie consent if you turn that on.
Know this first
-
1
Builderify switches off too, today.
If your credit balance reaches zero, the widget stops loading on your site, and the banner with it, until you add credits or your 250 free credits renew on your monthly date. The consent tag keeps running. Where you ask before tracking, new visitors stay at denied and see no way to say yes. Where you use opt-out, the tag defaults to granted and nobody sees a banner or a way to opt out. A fix that keeps the banner up without credits is being worked on; it is not released. Until it is, treat a zero balance the way you would treat CookieYes’s 100%.
-
2
Every widget page load counts.
Like CookieYes, Builderify counts page loads whether or not the visitor answers. Other modules on the same widget spend the same credits, so 25,000 free page loads is the most you get when the banner is all you run.
-
3
Not a Google-certified CMP, and no IAB TCF.
If you show Google ads on your own site through AdSense, Ad Manager or AdMob to visitors in Europe, Google asks for a certified consent platform. CookieYes and Complianz say they are certified; pick one of them for that.
-
4
No WordPress plugin yet.
You paste two snippets, the consent tag first in <head> and then the widget, with a plugin such as WPCode or Code Snippets. Edits to a theme’s header.php are lost when the theme updates, and block themes have no header.php at all.
Juggling a consent plugin, a stats plugin and a popup plugin? The guide to too many WordPress plugins covers what one script tag can replace, and the Jetpack Stats alternative guide does the same for traffic numbers.
Stay on CookieYes Free, upgrade,
or switch?
Your site stays well under 5,000 pageviews a month, about 160 a day, even in a good week.
Stay on CookieYes Free. It does the job. Keep an eye on the 80% email, and know your cycle date.
You like CookieYes and your traffic is over the limit.
CookieYes Basic. $10 a month, or $100 a year, for 100,000 pageviews, with extra pageviews billed instead of the banner stopping. Pro at $25 adds geo-targeting.
You are on WordPress and want no counter at all, with a consent record.
Complianz’s free plugin. No pageview limit on any plan, and it runs on your own server. Records of consent and GeoIP are Premium, from $59 a year.
Your site is small in pages, under 50, but busy.
Cookiebot Free. Traffic is not counted. Accept its default banner, one language and consent that lasts up to a month.
You run Google ads on your own site to visitors in Europe.
A Google-certified platform: CookieYes, Complianz or Cookiebot. Not Builderify, which is not certified.
You want the banner in the same script as popups, chat or journey analytics, and pay per page load with no subscription.
Builderify. 25,000 banner-only page loads a month on the free credits, then one-time packs from $9. Watch the balance: at zero, the banner stops until you top up.
CookieYes's free plan, before you ask.
Yes. CookieYes has a free plan for one website per account, with a banner, automatic blocking, Google Consent Mode v2, a scanner of 100 pages and a consent log. It covers 5,000 pageviews a month for sites added on or after 1 July 2025, or 15,000 for sites already on Free before then. Paid plans start at $10 a month per site for 100,000 pageviews.
At 100% of the monthly allowance, CookieYes stops displaying the banner and stops counting pageviews until the count resets on your cycle date, which on Free is the day you registered the site, or until you upgrade. Free plans cannot buy extra pageviews. Basic and Pro can instead bill $0.30 per 1,000 extra pageviews so the banner stays on.
First check the pageview count on your CookieYes dashboard: at 100% on Free the banner is switched off until the cycle resets. Then check whether a cancelled paid trial dropped the site to the 5,000-pageview Free plan, purge every cache and CDN, make sure your theme calls wp_footer, and test the live page in a private window rather than a page-builder preview.
Yes, by not connecting it to the CookieYes web app. In that plugin-only mode the banner script is served from your own site and nothing is counted. The trade-off is that no consent log is kept and no automatic cookie scan runs, so you list cookies yourself and have no record of who consented.
On WordPress, Complianz says neither its free nor its paid plans limit pageviews, and it runs on your own server. Cookiebot Free does not count traffic but is limited to one domain under 50 subpages. Builderify has no pageview quota and charges 10 credits per 1,000 widget page loads from 250 free credits a month, but if the balance reaches zero the banner currently stops loading until you top up.
Sources
Vendor pages, regulators and the plugin’s own code. Read on 15 October 2026.
- CookieYes Pageviews: what counts, the free plan limit, what happens at 100%
- CookieYes Pageview pricing: resets, extra pageviews, suspended banners
- CookieYes What happens if we exceed the monthly page views quota?
- CookieYes Pricing and plan comparison
- CookieYes How to install and set up the WordPress plugin
- WordPress.org CookieYes plugin, 1+ million active installations
- WordPress.org SVN CookieYes plugin 3.5.7, AGENTS.md: standalone and connected modes
- WordPress.org Complianz plugin: free features and Premium
- Complianz Pricing: Personal, Professional, Agency
- Cookiebot Pricing: Free and Premium plans
- ICO Cookies and similar technologies (PECR guidance)
- EDPB Guidelines 05/2020 on consent under Regulation 2016/679
- EUR-Lex GDPR, Article 7: conditions for consent
Stop losing the visitors
you already paid for.
More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.