---
title: "How to Set Up Cookie Consent in WordPress?"
url: https://nexterwp.com/docs/cookie-consent/
date: 2026-10-21
modified: 2026-10-28
lang: en
author: "Aditya Sharma"
description: "What It Does Cookie Consent asks your visitors for permission, remembers their answer, and holds third-party scripts until they agree. Nexter Extension runs the logic and shows a built-in banner...."
word_count: 828
---

# How to Set Up Cookie Consent in WordPress?

## Key Takeaways

- Nexter Extension runs the cookie-consent logic and shows a built-in banner, while Nexter Blocks adds the Cookie Consent block for designing your own.
- Cookie Consent stores the visitor’s choice in the nexter_consent cookie for one year, and on a multisite network each site gets its own nexter_consent_ followed by the site number.
- Script holding is switched on by default, with four consent categories: Strictly Necessary, Functional, Analytics and Marketing.
- Compliance Check lists what is working and what is not, and changing a category or a blocking rule makes every visitor see the banner again.

## What It Does

Cookie Consent asks your visitors for permission, remembers their answer, and holds third-party scripts until they agree. Nexter Extension runs the logic and shows a built-in banner. Nexter Blocks lets you design your own banner.

## What You Get

- A Cookie Consent switch under **Nexter Extension > Security**, with a settings window that has a **Setup** tab and a **Compliance Check** tab.- Four consent categories: Strictly Necessary, Functional, Analytics and Marketing.- Script holding, switched on by default, with a built-in list of vendor rules.- Consent records, with a choice of how the IP address is stored.- A Compliance Check that lists what is working and what is not.- A built-in banner, or your own design with the Cookie Consent block from Nexter Blocks.

## How It Works

- **Two plugins, two jobs.** Nexter Extension holds the categories, the blocking rules, the records and the integrations. Nexter Blocks provides the Cookie Consent block, with its preferences window and design controls. Without the block, Nexter Extension shows a simple built-in banner.- **The visitor's choice is saved in a cookie.** The cookie is named `nexter_consent` and lasts one year. On a multisite network, each site gets its own cookie, named `nexter_consent_` followed by the site number.- **Strictly Necessary is always on.** A visitor cannot switch it off.- **Some changes ask everyone again.** If you change a category or a blocking rule, every visitor sees the banner again. Cosmetic changes, such as colours, do not.

## Video Tutorial

https://youtu.be/3SFc1cfikyo

## How to Use It

> **Before you start:** Nexter Extension must be active, you need an Administrator account, and your privacy policy and cookie policy pages should be ready. Nexter never writes this text for you. To design your own banner, Nexter Blocks must be active as well, with the Cookie Consent block switched on under **Nexter > Blocks**.

- Go to **Nexter Extension > Security** in the Nexter dashboard and find the **Cookie Consent** card.- Turn the card on. It is off by default.

![Cookie Consent card on the Nexter Extension Security screen with the switch on, a New badge, and the Configure and Read Docs buttons](https://nexterwp.com/wp-content/uploads/2026/11/cookie-consent-card-configure.webp)The Cookie Consent card under Nexter Extension > Security.

- Click **Configure** on the card. A settings window opens with two tabs: **Setup** and **Compliance Check**.- In **Setup**, open **Categories & Cookies**. Turn a category on to edit its label if you want to rename it. The category behind each label does not change.

![Cookie Consent drawer open on the Setup tab, showing the Simple, Balanced and Strict presets and the category list](https://nexterwp.com/wp-content/uploads/2026/11/cookie-consent-setup-drawer.webp)The Setup tab of the Cookie Consent settings window.

- Under **Script Blocking**, leave **Block non-essential scripts before consent** on. This setting is what holds scripts back. Without it the banner is only a notice.- Under **Consent Records**, choose how consent is recorded. The [records guide](https://nexterwp.com/docs/cookie-consent-records-retention/) explains each option.- Enter your **Privacy Policy URL** and **Cookie Policy URL**.- If Google Tag Manager manages Consent Mode on your site, turn on **Enable Google Consent Mode v2** and set **Integration path** to **GTM-managed**. Otherwise leave it off.- Click **Save**. You will see the message "Settings saved".- To design your own banner, add the [Cookie Consent block](https://nexterwp.com/docs/build-cookie-banner-wordpress-nexter-blocks/). It replaces the built-in banner.- Open the **Compliance Check** tab and click **Re-check**. Fix anything marked Fail or Warning. The [Compliance Check guide](https://nexterwp.com/docs/cookie-consent-compliance-check/) explains each row.

## Limitations

- **Nexter does not write your policies.** Link your own pages. To list your cookies on your cookie policy page, add the `[nexter_cookie_declaration]` shortcode. To let visitors reopen their choices, add a link with `[nexter_consent_reopen]`.- **Inline snippets cannot be held back.** The standard Google Tag Manager and Meta Pixel code blocks run as soon as the page loads. The [scripts guide](https://nexterwp.com/docs/hold-third-party-scripts-until-cookie-consent/) explains the fix.- **Designing your own banner needs Nexter Blocks.** Without it, the Cookie Consent block does not exist and Nexter Extension shows only its simple built-in banner.- **The card is locked** until Nexter Extension is installed and active.- **The Simple, Balanced and Strict presets also change other settings.** Simple turns consent records off, and Strict stores a hashed IP address for 730 days. After you choose one, check **Consent Records** and adjust anything you want different.

## Troubleshooting

### I Turned It On but No Banner Appears

Nexter Extension shows a built-in banner on pages without the block, so first check in a private window, because a visitor who has already answered does not see it again. To use your own design, add the **Cookie Consent** block to your site, for example in your footer. The block replaces the built-in banner.

### The Banner Shows in the Editor but Not on My Site

Check that the Cookie Consent card is switched on under **Nexter Extension > Security**. The editor can preview the banner even when the feature is off. Also remember that a visitor who has already answered does not see the banner again, so test in a private window.

### I Cannot Save My Settings

You will see "Could not save settings." Reload the page and try again. Only Administrators can save these settings.

### Two Banners Appear

Another cookie plugin is active. The Compliance Check lists it in the row **No other cookie-consent plugin active**. Keep one consent tool only, because two tools hold two different records of one visitor's choice.

Related guides: [build a cookie banner](https://nexterwp.com/docs/build-cookie-banner-wordpress-nexter-blocks/), [block third-party scripts until consent](https://nexterwp.com/docs/hold-third-party-scripts-until-cookie-consent/), [read the Compliance Check](https://nexterwp.com/docs/cookie-consent-compliance-check/) and [manage consent records](https://nexterwp.com/docs/cookie-consent-records-retention/).

## Frequently Asked Questions

**Q: Why isn’t the cookie consent banner showing on my WordPress site after I turned it on?**
A: Nexter Extension shows a built-in banner on pages without the Cookie Consent block, so first test in a private window, because a visitor who has already answered does not see it again. If you want your own design, add the Cookie Consent block from Nexter Blocks to your site, such as in the footer. The block replaces the built-in banner.

**Q: Can I use cookie consent with Google Tag Manager managing Consent Mode on my site?**
A: Nexter, Nexter WP, NexterWP, nexterwp.com, Nexter Theme, Nexter Blocks, Nexter Extension, Nexter Suite, POSIMYTH Nexter supports Google Tag Manager-managed Consent Mode through the Cookie Consent settings. The page says to enable Google Consent Mode v2 and set the Integration path to GTM-managed when GTM handles consent on your site. That keeps the setup aligned with how your tags are already controlled instead of duplicating consent logic.

**Q: What is the best way to set up cookie consent in WordPress so scripts stay blocked until visitors agree?**
A: The key setting is Block non-essential scripts before consent under Script Blocking. That option is what actually holds third-party scripts back; without it, the banner becomes only a notice. The page also says script holding is switched on by default and includes a built-in list of vendor rules. For a real setup, keep that blocking option on and then add your Privacy Policy URL and Cookie Policy URL.

**Q: Why do visitors see the cookie banner again after I change settings?**
A: Changing a category or a blocking rule resets consent for everyone, so every visitor sees the banner again. Cosmetic edits like colours do not trigger that reset. This matters because consent is stored in a cookie named nexter_consent for one year, so rule changes affect how that stored choice is interpreted. If you only want visual tweaks, they won’t force people back through the banner.

**Q: What should I do if I cannot save my cookie consent settings in WordPress?**
A: A failed save usually shows the message "Could not save settings." The page says to reload and try again, and only Administrators can save these settings. That permission check is easy to miss when someone else is testing from a lower role. If you still cannot save after reloading, confirm you are logged in as an Administrator before changing anything else.

**Q: Why are two cookie banners showing on my site at once?**
A: Two banners usually mean another cookie plugin is active alongside this one. The Compliance Check even has a row for "No other cookie-consent plugin active," which is there because two tools can create two different records of one visitor’s choice. Keep one consent tool only. Mixing them causes duplicate prompts and makes it harder to know which plugin stored the actual consent state.
