The simplest route is a consent-management plugin: install CookieYes from Plugins > Add New, choose the laws and regions you serve, configure the banner and cookie categories, then verify that non-essential scripts stay blocked until a visitor makes the relevant choice. A popup alone is not consent management; your configuration must also provide meaningful choices, record consent and let visitors change their minds.
Choose a WordPress implementation
Plugin route: easiest for most sites
In the WordPress dashboard, open Plugins > Add New, search for CookieYes, select the plugin, choose Install Now, and activate it. Its WordPress listing says a banner appears immediately after activation. Treat that first display as a starting point, not proof that blocking or legal settings are correct.
Manual installation route
CookieYes also documents a hosted setup. Create and customize the banner in CookieYes, copy the installation code, and place it in the theme header between <head> and </head>, before other scripts. If you do not edit theme files, use a reputable header/footer insertion plugin and paste the code into its Header section. CookieYes warns that code placed after other custom scripts can stop automatic blocking from working as intended. Use its Verify control after installation.
Do not use both routes unless the vendor specifically instructs you to; duplicate consent scripts can produce conflicting banners or inconsistent blocking.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Configure the legal scope and visitor targeting
In CookieYes settings, select the template that matches your audience: GDPR, US State Laws, or a combined template. If requirements should differ by visitor location, enable geo-targeting and assign the appropriate template to each region. These choices are configuration tools, not a legal determination of which laws apply to your business.
Set how long consent remains valid and decide whether the page reloads after a visitor accepts, rejects or saves preferences. Choose an expiration period that matches your policy and operational needs, then document the setting so it can be reviewed when your privacy practices change.
Design a banner with real choices
CookieYes documents three layouts: Box, Banner and Popup. Its documentation lists the Popup layout as available in Pro and Ultimate plans, so confirm that your selected plan includes it before designing around that layout.
Edit the title and explanatory message, then configure the controls your visitors need:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches- Accept All to allow every optional category presented.
- Reject All to refuse optional categories without forcing a visitor to open a second screen.
- Customize to make category-level choices.
- A close control only if its effect is clear and does not silently count as consent.
- A Read More link to the current privacy or cookie-policy page.
Explain the purposes of optional cookies in plain language. Keep the policy link visible, and provide a persistent way—such as a footer control or floating icon—for visitors to reopen preferences and withdraw or change consent.
#1 Best Overall
Set categories and block cookies before consent
Separate cookies by purpose instead of treating every cookie as optional or every cookie as necessary. Necessary cookies may remain active when they are genuinely required for a requested service, security or core site operation. Analytics, advertising, embedded-video and similar non-essential technologies should wait for consent for the relevant category.
CookieYes warns that enabling categories to load before consent, or hiding categories visitors need to control, can make the setup non-compliant. Review every category against what your site actually loads:
- Analytics and measurement tags
- Advertising and conversion tags
- Video, map, social and other embedded content
- Chat, personalization and marketing tools
- Essential security, session and preference cookies
Blocking must occur before those scripts execute. A banner that appears after an analytics or advertising tag has already run does not provide the same control as a banner that prevents the tag from loading.
Scan the site and build an accurate policy
Run CookieYes’s site scan, review the detected cookies and assign each one to the correct category. The scanner can support consent records and cookie-policy generation, but its output still needs human review. Compare the results with your active plugins, theme features, analytics configuration, advertising tags, page-builder widgets and third-party embeds.
Your policy should identify cookie names where applicable, their purposes, providers and retention periods. Remove entries for services you no longer use and add services that a scan missed. A generated policy is useful only when it describes the cookies your site really sets.
Test every consent path before publishing
Use a fresh browser profile or clear the site’s cookies between tests. The following procedure checks behavior rather than merely the banner’s appearance:
- Open the public site in a private window and confirm the banner appears before optional tags run.
- Inspect the initial state. Confirm that non-essential analytics, advertising and embeds are blocked until a choice is made.
- Select Accept All. Confirm that the permitted categories activate and that the choice is recorded.
- Clear consent and select Reject All. Confirm that optional categories remain blocked.
- Clear consent again, open Customize, allow one category and deny another, and verify that only the allowed category activates.
- Use the site’s revisit-consent control to reopen the panel, change a decision and confirm that the new state takes effect.
- Open the policy link and check that it works on mobile and desktop.
- Use CookieYes’s Verify control where available, and inspect browser network activity or tag-debugging tools for scripts that should be blocked.
These checks should be repeated after adding a plugin, changing a tag manager configuration, embedding new media or switching themes. A consent system can regress when site code changes.
CookieYes compared with other plugin routes
The best plugin depends on the controls your site needs, not on the presence of a popup alone. Compare candidates using the following capabilities:
| Capability | Why it matters | Evidence described for the tools |
|---|---|---|
| Automatic blocking before consent | Prevents optional scripts from running prematurely. | CookieYes documents automatic blocking; Cookie Consent documents script blocking. |
| Cookie scanning and categorization | Helps maintain an inventory that matches the live site. | CookieYes and Cookie Consent document scanning; results still require review. |
| Consent logs and export | Provides an auditable record of choices. | CookieYes documents consent logging; Cookie Consent documents consent logs. |
| Policy generation | Creates a starting point for a cookie policy. | CookieYes documents Cookie Policy generation; verify accuracy before publishing. |
| Regional targeting | Shows different controls where laws or business requirements differ. | CookieYes supports GDPR, US State Laws and combined templates with geo-targeting; Complianz documents broad regional-law targeting. |
| Integrations and design compatibility | Reduces conflicts with tag managers, page builders and multilingual sites. | Complianz documents integrations and consent records; Cookie Consent documents Elementor-based design options. Confirm current compatibility for your stack. |
| Popup layouts and plan limits | Prevents selecting a design that your subscription does not include. | CookieYes lists Box and Banner layouts, with Popup documented for Pro and Ultimate. |
For a straightforward WordPress installation, CookieYes is a practical starting point because its documented workflow combines banner configuration, blocking, scanning, logging and policy generation. Complianz is worth evaluating when you need broad jurisdiction support or extensive integrations. Check current plan features, pricing, update history and compatibility before committing; those details can change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common problems and fixes
The popup appears, but analytics still fires
Check script placement and loading order first. With the manual method, put the CookieYes code in the document head before custom scripts. Then review category assignments, caching, tag-manager triggers and consent-state conditions. Purge page, CDN and browser caches after correcting the configuration.
Visitors cannot reject optional cookies
Add a clearly visible Reject All control and ensure optional categories are not pre-enabled or hidden. A close button should not silently become acceptance.
A category is missing from the preference screen
Review whether the category was hidden in settings. CookieYes warns against hiding categories visitors need to control. Rescan after enabling the category and inspect the services assigned to it.
The policy lists the wrong cookies
Reconcile the scan with the current plugin, theme and third-party service inventory. Delete retired services, classify newly added cookies and update retention and provider details.
The banner keeps returning
Check consent expiration, domain and subdomain settings, caching, and whether the site is loading more than one consent script. Test in a clean browser after saving settings.
What a plugin can—and cannot—do
CookieYes states: “No plugin can guarantee compliance. CookieYes helps you meet the cookie consent requirements of major privacy laws, but you need to assess how your own site uses cookies and configure the plugin correctly.” Your responsibility remains to identify the laws and audiences relevant to the site, classify technologies accurately, publish truthful policy information and verify that blocking matches the choices shown to visitors.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
