Skip to content

Works with your stack

Cookie consent for Polylang

follows each page

← Cookie Rocks for your stack

Polylang serves each page in one language. The banner, its details and your cookie policy should follow that language, and link to the right translation of your policies.

By WP SYNTEX · polylang.pro · WordPress.org

Is this your product? Tell us if anything here is out of date. Write to us

Polylang

WordPress plugin

Tested
Tested version
3.9.1
How
Tested automatically around each Cookie Rocks version
Last test
7 November 2026
Latest version
3.9.1 tested
Active installs
900,000+

What Polylang adds to your visitors’ browser

No trackers In our test of Polylang 3.9.1 on 7 November 2026, the plugin itself added no tracker and no cookie. What you place in your pages with it, such as a video or a map, still counts.

What Polylang puts on your pages

Language switcher
Links to the other languages. It loads nothing from outside.
Language cookie
Remembers the visitor’s language so the next page opens in it. It serves the site itself.
Translated pages and policies
Each page linked to its translations, privacy policy and cookie policy included.

What matters for consent with Polylang

One language per page

Polylang links each page to its translations. The banner on a Spanish page should be in Spanish.

Translated policies

Your privacy policy and cookie policy have one translation per language. Each can fall behind the original.

The language cookie

Polylang can remember the visitor’s language in the pll_language cookie. It serves the site itself and needs no consent.

One domain per language

Polylang can put each language in a folder, a subdomain or a domain of its own. Cookies belong to one domain: with a domain per language, the visitor chooses again on each one.

Cookie Rocks with Polylang

  • Lets you edit the banner texts language by language, from its list of languages.
  • Points the banner’s policy link to the translation in the language of the page.

All the features

What our tests found on Polylang

  • Good to know · Cookie RocksCookie Rocks announces India's language rule with its date

    Under Good to know: from May 13, 2027, India lets visitors read the banner and the policy in their choice of 23 languages.

    Seen in our tests, 24 October 2026, Cookie Rocks.

    Full detail

    When the site targets India, the Cookie Rocks 2.8.2 dashboard shows under Good to know that from May 13, 2027 visitors may read the cookie banner and the cookie policy in the language of their choice among 23 languages, English included. It is information, not a task.

  • Good to know · Cookie RocksCookie Rocks accepts one of several required languages

    For Cyprus, the dashboard asks for Greek or Turkish. A site in Greek only gets no language warning.

    Seen in our tests, 24 October 2026, Cookie Rocks.

    Full detail

    When a target country accepts one of several languages, Cookie Rocks 2.8.2 says so. For Cyprus, the dashboard warns that the law asks businesses to inform consumers in Greek or Turkish, in the cookie banner and the cookie policy, only when the site has neither language. A site in Greek only gets no language warning for Cyprus.

  • Depends on a settingCookie Rocks dashboard flags a missing Romanian version

    When the profile targets Romania, Good to know says the law asks businesses to inform consumers in Romanian on the whole site and in the cookie banner.

    Seen in our tests, 18 October 2026.

    Full detail

    When the site profile targets Romania and the site has no Romanian version, the Cookie Rocks dashboard shows, under Good to know, that the law asks businesses to inform consumers in Romanian on the whole site and in the cookie banner. In the code, the notice depends on the site languages and on the banner texts in Romanian.

  • Depends on a setting · PolylangPolylang browser detection redirects the home page and skips its cache

    setting “Detect the browser language (browser)” · by default: off

    Off by default. When on, it redirects the home page by browser language and keeps the default-language home page out of the page cache, except with WP Rocket 3.0.5 or later.

    Read in its code, 16 October 2026, Polylang 3.8.11.

    Full detail

    Polylang's browser language detection is off by default. When on, it redirects the home page with a 302 and Vary: Accept-Language, and keeps the default-language home page out of the page cache (DONOTCACHEPAGE), except with WP Rocket 3.0.5 or later.

See the 3 other findings
  • Good to know · PolylangWith Polylang, the banner and cookie policy follow the page language

    This works whether the language is in the address, set from the content or detected from the browser. Banner texts edited for one language show on that language's pages only.

    Seen in our tests, 15 October 2026, Polylang 3.8.11.

    Full detail

    With Polylang, the Cookie Rocks banner and cookie policy follow the language of the page (French and English tested), whether the language is in the URL directory, set from the content, or detected from the browser on the home page. Banner texts edited for one language show on that language's pages only, and the banner's privacy link leads to the translation in the page's language.

  • Set before the choice · PolylangPolylang sets its pll_language cookie on the first page, before any choice

    by default: on

    It lasts one year, even when the language is in the address. Only code turns it off: define('PLL_COOKIE', false). In our test this left no cookie and /fr/ stayed in French.

    Seen in our tests, 15 October 2026, Polylang 3.8.11.

    Full detail

    Polylang sets its pll_language cookie on the first page a visitor opens, before any choice: one year, path /, SameSite=Lax, not HttpOnly. It is set by default, even when the language already comes from the address (/fr/...), and can only be turned off in code with define('PLL_COOKIE', false). In our test with the language in the address, that constant left no cookie after four page views and /fr/ stayed in French. When a cache plugin is active, Polylang writes the cookie with a small script on each page instead of from the server.

How we test it

Around each version, with its latest release

Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.

  • Polylang 3.9.1, tested on 7 November 2026.
  • The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
  • Settings of the test: Default settings after activation.
  • Last run: Polylang 3.9.1 on 7 November 2026, with WordPress 7.1.3.

Questions

What if my site uses a language Cookie Rocks does not ship?

The banner shows English until you write its texts in that language, on the Appearance page.

Does a cached page show the right language?

Yes. Each language has its own banner file, so every cached page carries the right one.

Is the choice kept when the visitor switches language?

Yes when your languages are folders of one domain, since the choice is a cookie of that domain. With a separate domain per language, the visitor chooses again on each domain.

Can the banner speak the visitor's language when my site does not have it?

Yes, with the Pro. On the Appearance page, turn on « Show the banner in the visitor’s browser language » (off by default). The banner then uses the browser language among the 54 shipped, even without a version of the site in that language. The cookie and privacy policies still follow the page.

What happens after the 30-day trial?

The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.

For Polylang sites

One banner, every language.

follows each page

Every feature of the complete plugin on your multilingual site for 30 days, no card.

  • During the trial: everything, including the full settings and the scans
  • After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
  • What waits for a key: most settings, updates and support

How the trial works, in detail

Get your trial key

Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.

One trial per domain. Local and staging sites never use up your key.

We keep your e-mail address to send your key and help you with it, as explained in our privacy policy. No newsletter, nothing else.