Cookie consent on WordPressCore is clean, your plugins are not
Reviewed · 6 sources
WordPress's own cookie list contains only login, admin-settings and commenter cookies. A default install sets nothing on a visitor who just reads a page, so on its own it needs no cookie banner.
Almost no real site stays that way. An analytics plugin, a pixel plugin, a theme that loads fonts from Google, or a YouTube embed each start sending visitor data to third parties, and none of them wait for consent unless you make them.
Check your WordPress site
See every cookie it sets before consent, after Reject and after Accept.
What WordPress setsOn its own
wordpress_test_cookieSet on the login page to check that the browser accepts cookies.No consent neededwordpress_logged_in_*Keeps a logged-in user signed in. Only for people who log in.No consent neededwp-settings-*Stores a logged-in user's admin interface preferences.No consent neededcomment_author_*Remembers a commenter's name, email and website for a little under a year, only if they tick the opt-in box (added in WordPress 4.9.6).No consent neededwp_langSession cookie set at login when a language is chosen.No consent needed
From the official WordPress cookie list. Commenter cookies are set only after the visitor ticks the checkbox under the comment form.
Built-in consent tools
No banner in core, a shared consent signal as a plugin
WordPress has no built-in cookie banner. Consent is handled by a plugin such as Complianz, CookieYes, Borlabs Cookie or Real Cookie Banner.
The WP Consent API plugin gives consent plugins and other plugins one place to exchange the visitor's choice, in five categories (functional, preferences, statistics, statistics-anonymous, marketing). It does not show a banner and does nothing on its own: a consent plugin has to set the categories, and each tracking plugin has to read them. Its plugin page lists Complianz and CookieYes among the compatible consent plugins.
Where the cookies come fromThe ones that need consent
Google Site Kit
Places Google Analytics and Ads tags. Its consent mode only works when the WP Consent API plugin and a consent management plugin are both installed and configured.
Jetpack Stats
Sets no visitor cookie, but still collects IP address, user agent, URL and referrer. From Jetpack 16.4 it counts a visit only after statistics consent, if the WP Consent API plugin is active. Without that plugin it counts everyone.
Google Fonts loaded from Google
Many themes and page builders load fonts from Google's servers, which sends each visitor's IP address to Google. A Munich regional court awarded a visitor €100 for exactly this in January 2022 (LG München I, 3 O 17493/20, a single first-instance ruling). Hosting the fonts on your own server avoids the transfer.
Embeds and pixel plugins
YouTube, Google Maps, social feeds and Meta or TikTok pixel plugins contact third parties as soon as the page loads, unless your consent plugin is set up to hold them back.
Make WordPress compliantIn 5 steps
- 1
Find what your site really sets
Scan the site, or open it in a private window and read the cookies and network requests before you click anything in the banner.
- 2
Install one consent plugin and let it block
Pick a consent plugin that blocks scripts before consent, not one that only shows a notice. Run its cookie scan and assign every service to a category.
- 3
Connect your tracking plugins to it
Install WP Consent API if your consent plugin and tracking plugins support it, and turn on consent mode in Site Kit. Check each plugin's settings: support is per plugin.
- 4
Remove what you can
Host fonts locally, replace embeds with click-to-load placeholders, and delete plugins you no longer use. Every removed tracker is one less thing to get consent for.
- 5
Test Reject
Reject in a private window and confirm no analytics or marketing cookie is stored. Repeat after every plugin or theme update.
// Requires the WP Consent API plugin and a consent plugin that sets categories.
if ( function_exists( 'wp_has_consent' ) && wp_has_consent( 'marketing' ) ) {
// Output your marketing tag here.
}Without the WP Consent API plugin the function does not exist, so the tag stays off.
Tools that help: tracking script blocker · Consent Mode v2 generator · cookie reference
Common mistakesOn WordPress sites
A banner that only informs
A notice with an OK button that blocks nothing is the most common WordPress setup. The cookies are already set by the time the visitor reads it.
Two consent plugins at once
Left over from a migration, they show two banners or overwrite each other's settings. Keep one.
A new plugin after the cookie scan
Consent plugins block the services they know about. A plugin added later runs unblocked until you scan again and categorise it.
Caching the banner state
A page cache that stores the page with the tags already printed serves them to visitors who rejected. Test with the cache on.
Checklist for WordPress sites
- No analytics or marketing cookie before a choice in the banner
- Reject on the first layer, as prominent as Accept
- Site Kit consent mode on, with WP Consent API and a consent plugin
- Fonts served from your own domain
- YouTube, Maps and social embeds load only after consent
- Cookie policy lists every cookie by name, provider and lifetime
- Re-scan after each plugin, theme or tag change
QuestionsAnd short answers
- Does WordPress need a cookie banner?
- A default install that sets only login and commenter cookies does not. As soon as a plugin, theme or embed sets analytics or marketing cookies, or sends visitor data to a third party, you need consent before that happens.
- Which WordPress cookies are exempt from consent?
- The login and session cookies (wordpress_logged_in_*, wordpress_test_cookie, wp-settings-*) are needed to provide a service the user asked for. Commenter cookies are set only when the commenter opts in with the checkbox.
- Is the WP Consent API enough on its own?
- No. Its own description says it does not handle consent and requires a cookie banner plugin. It only passes the visitor's choice between plugins that support it.
- Do I need consent for Jetpack Stats?
- Jetpack lists no visitor cookie for Stats, but it processes IP addresses and other visit data, which is personal data under GDPR. From Jetpack 16.4 it can wait for statistics consent through the WP Consent API.
Sources
- WordPress: Cookies
- WordPress 4.9.6 Privacy and Maintenance Release
- WP Consent API plugin
- Site Kit by Google: Consent mode
- Jetpack: Cookies
- LG München I, judgment of 20 January 2022, 3 O 17493/20
Reviewed 20 November 2026 against WordPress's own documentation. Platforms change their cookies and consent features; follow the links for the current state. General information about EU cookie rules, not legal advice.
Other platformsAnd guides by industry
Check your WordPress siteSee what loads before consent
Free scan · every cookie before consent, after Reject and after Accept