Why switch from CookieYes to CookieConsentHQ?
CookieConsentHQ keeps its banner and automatic blocking of known trackers running after the monthly pageview allowance is used up, without overage fees. CookieYes's pageview documentation says its banner is disabled at the plan limit, and its paid plans offer extra pageviews at $0.30 per 1,000.
Both count pageviews, so the plans line up directly. List prices checked on 20 October 2026:
| CookieYes | CookieConsentHQ | |
|---|---|---|
| Free | 5k pageviews | 25k pageviews |
| First paid plan | Basic, $10/month, 100k pageviews | Starter, $8/month, 150k pageviews |
| Next paid plan | Pro, $25/month, 300k pageviews | Growth, $18/month, 750k pageviews |
| Top single-site plan | Ultimate, $55/month, unlimited pageviews | Business, $39/month, 5M pageviews |
| Global Privacy Control | From Pro | Every plan |
| At the pageview limit | Banner disabled unless extra pageviews are bought | Banner and automatic blocking keep working |
A site with 80,000 monthly pageviews fits CookieYes Basic at $10/month or CookieConsentHQ Starter at $8/month. At 120,000 pageviews, CookieYes Basic's allowance runs out, while CookieConsentHQ Starter still covers the traffic for $8/month.
The CookieYes comparison covers the product differences, and the pageview-limit guide works through the limit in detail.
What should I prepare before removing CookieYes?
Create a free CookieConsentHQ account, add your domain and prepare the new banner before you change the published website. Run a cookie scan and review the categories so you know what the new banner will describe.
Follow these steps:
- Create a free CookieConsentHQ account.
- Add the website domain.
- Run a cookie scan.
- Review the cookies found and their categories.
- Choose a regional consent preset.
- Edit the banner text.
- Publish the new banner configuration.
CookieConsentHQ has three regional presets on every plan: a mixed global setup, opt-in everywhere and US opt-out everywhere.
The banner comes in seven languages: English, German, French, Spanish, Italian, Dutch and Portuguese.
The cookie scanner loads public pages before consent and revisits the first few after acceptance. Free scans cover up to 50 pages and paid scans up to 150.
With the settings ready, the swap itself takes only a few minutes.
How do I replace the CookieYes script or WordPress plugin?
Remove the existing CookieYes installation and place the CookieConsentHQ loader first inside <head>, before analytics and advertising tags. Load it synchronously, without async or defer, and never run both banners together.
For a direct script installation:
- Find the CookieYes script on the site.
- Remove it.
- Copy the new snippet from the CookieConsentHQ Install tab.
- Place it first inside
<head>. - Publish the changes.
The new snippet looks like this:
<script src="https://cdn.cookieconsenthq.com/s/YOUR_SITE_KEY.js"></script>
On WordPress, deactivate and remove the CookieYes plugin if it shows the current banner, then install the CookieConsentHQ plugin. Download its ZIP and upload it under Plugins, Add New, Upload Plugin.
The WordPress integration explains its settings and WP Consent API behavior. Other platforms follow the installation guides.
How do I replace cookie tables and preference links?
Replace CookieYes-specific cookie declaration elements with the CookieConsentHQ table placeholder or WordPress shortcode. Then point your cookie-preference links at CookieConsentHQ's preferences.
On an HTML cookie policy page, use:
<div data-cchq-cookie-table></div>
On WordPress with the CookieConsentHQ plugin, use:
[cchq_cookie_table]
The table fills from the scanner's categorized cookie list.
A preference link should call CCHQ.showPreferences(), so visitors can return to their choices later.
The JavaScript API also provides CCHQ.getConsent() for reading the current consent state. To link a privacy request to a stored record, the site can read CCHQ.getConsent().id and include it in the request.
The banner does not show the consent ID. The site owner uses it to open the record in the dashboard.
What happens to existing CookieYes consent records?
CookieConsentHQ cannot import consent records from CookieYes, and its banner does not read the choices CookieYes stored. Visitors will be asked to choose again after the switch.
Before closing the CookieYes account, decide which historical records you need to keep and for how long. Keep them available through whatever export or access your CookieYes plan provides.
The new CookieConsentHQ log only holds choices made through its own banner. The consent log records a consent ID, UTC timestamp, action, categories, banner configuration version and location.
Retention is one year on Free, three years on Starter and five years on Growth and higher plans.
On Free, new records pause after 25,000 monthly pageviews until the next month. The banner and automatic blocking stay on.
How do I check the site after switching?
Open the published website and confirm that CookieConsentHQ is the only consent banner. Then run the free checker to inspect one page for cookies set before consent, hardcoded tracker tags and Consent Mode v2 defaults.
The checker recognizes 22 consent tools, CookieYes among them, so it will flag a leftover CookieYes script. Recognizing a tool does not mean importing anything from it.
Look at the script order on the published page, especially where analytics or advertising tags are written straight into the HTML. The CookieConsentHQ loader needs to run first for early blocking to work.
For hardcoded scripts you can edit, use type="text/plain" with data-cchq="marketing", analytics or functional to stop early requests.
The checker covers one public page. Scheduled scans cover more of the site.
When is keeping CookieYes the better choice?
Keep CookieYes when its current setup meets your needs and the manual move costs more time than it saves. Staying also makes sense when you need its features that CookieConsentHQ lacks.
CookieConsentHQ does not offer automated migration, IAB TCF, IAB GPP, a Google-certified CMP or policy generation. CookieYes also scans more pages per scan than CookieConsentHQ's 50 or 150. Any of these can make a switch the wrong move.
CookieConsentHQ's main differences are its larger pageview allowances, a banner that stays on past the allowance and GPC on every plan.
Weigh those against the time it takes to set up and test the new installation.
CookieYes facts are as listed on its website on 20 October 2026. This page describes a technical migration, does not establish legal compliance and is not legal advice.