Borlabs Cookie, the WordPress default, handled without a plugin of your own
Borlabs Cookie is what a German WordPress site most likely runs. Its box is plain DOM with a refuse link, and the consent autopilot uses exactly that link, so the site records the refusal the way it would for a visitor.
Recogniser facts
| Detected by | #BorlabsCookieBox or .borlabs-cookie-box |
|---|---|
| Reject path | The refuse link (a.borlabs-cookie-refuse) or a [data-cookie-refuse] control |
| Accept path | The accept-all link or the data-cookie-accept controls, only with consent: accept |
| API | None used; Borlabs exposes its choice through the DOM, and the DOM is enough |
| Considered done when | The detected box is gone from the page |
| Fallback | A renamed class means the recogniser stays silent and the heuristic runs |
As of 2026-09-04
Reject the banner as part of observe
import { Browserberg } from '@browserberg/sdk';
const bb = new Browserberg({
apiKey: process.env.BROWSERBERG_API_KEY,
baseUrl: 'https://browserberg.com',
});
const session = await bb.sessions.create();
// A WordPress site running Borlabs Cookie.
await session.act({ steps: [{ action: 'navigate', value: 'https://www.handwerk-mueller.example/' }] });
const page = await session.observe({ consent: 'reject' });
// The banner was answered before candidates were collected.
console.log(page.url, page.candidates.length);
What this looks like on a Mittelstand site
Most of the German web is WordPress, and most of that is Borlabs. This is the banner your agent meets on supplier, association and service pages.
Content-blocked embeds stay blocked
Borlabs replaces maps and videos with placeholders until consent is given. After a refusal they remain placeholders; if your task needs the embedded content, pass consent: accept knowingly.
Forms work without consent
Contact and order forms on Borlabs sites do not depend on the marketing category. A refusal leaves them usable, which is what an agent filling a form needs.
Every fresh session is a first visit
The refusal is stored in the site’s own cookie. A new session has none, the box returns, and the recogniser answers it again without your code noticing.
Questions engineers ask
Some Borlabs boxes only have "accept all" and "individual settings".
Then the refuse link is absent and the recogniser does not fire. The heuristic tries to find a refuse control by text; if there is none, observe reports the box still present rather than accepting on your behalf.
Is a refusal the same as closing the box?
No. Closing without a choice leaves consent unanswered and some sites re-open the box on the next page. The autopilot uses the refuse action so the site stores a decision.
Does the recogniser touch the Borlabs cookie directly?
No. Writing the cookie by hand would forge a consent record. The recogniser only does what a visitor can do in the box.
Which other CMPs are recognised?
Roughly seventeen, including Usercentrics, Cookiebot, OneTrust and consentmanager, plus a heuristic for the rest. The concept page lists the values.
Point it at a WordPress site
Five browser hours, no card. Open the page, call observe, read the candidates.