WordPress cookies2 of 5 need consent
WordPress sets 5 cookies we know of. 2 cookies may only be set after the visitor opts in; 3 are strictly necessary and exempt.
Reviewed · Provider: Automattic / WordPress.org, The website (WordPress)
List of WordPress cookies
wordpress_logged_in_*NecessaryNo consent neededSessionIndicates when you are logged in to WordPress and who you are, for most interface use.
wp-settings-*FunctionalConsent required1 yearStores personalised WordPress admin settings, such as the editor mode or widget order.
comment_author_*FunctionalConsent required1 yearSaves your name and email when you leave a comment so you do not have to re-enter them next time.
wordpress_test_cookieNecessaryNo consent neededSessionChecks that the browser accepts cookies before the WordPress login.
wp_langFunctionalNo consent neededSessionRemembers the language picked on the WordPress login screen.
How to handle WordPress cookies
- 1Load it only after consent
Hold the WordPress script until the visitor accepts functional cookies. Blocking the script is what stops the cookies; hiding them in a banner does not.
- 2Make Reject work
After a visitor rejects, none of the 2 consent-requiring cookies below may be set or kept.
- 3Name every cookie in your policy
List each cookie by name with its purpose, provider (Automattic / WordPress.org, The website (WordPress)) and lifetime.
- 4Check the result, not the settings
Open your site in a private window, reject cookies, and look at what was stored. Or run a scan and compare the three stages.
Tools that help: tracking script blocker · Consent Mode v2 generator
Other vendorsAnd the cookies they set
Does WordPress wait for consent on your site?Scan it in 2 minutes
Free scan · every cookie before consent, after Reject and after Accept