Cloaking
Per-domain protection that keeps your content buttons invisible to bots, scrapers, and in-app link scanners — so a real fan sees the funnel and a moderation crawler doesn't.
Cloaking is per-domain protection for your landing pages. It decides, request by request, who is a real visitor and who is automated — bots, scrapers, datacenter traffic, and the link scanners built into social apps — and keeps your content buttons out of the automated view. A fan tapping your link sees the full funnel; a moderation crawler following the same link does not.
You turn it on and tune it per domain in the domain hub, under Домены → домен → «Видимость». There is nothing to add to your links and nothing for visitors to do — the protection travels with the domain.
What this page covers
This is a plain-language overview of what cloaking does and why it matters. It intentionally does not describe how visitors are classified — that's the part that has to stay opaque to stay effective.
Why it matters
When you promote a link — in a bio, in an ad, in a DM — it gets opened by two very different crowds:
- Real fans, who should land on your buttons and convert.
- Automated reviewers — ad-network review bots, platform moderation crawlers, link-preview fetchers, and scrapers — who shouldn't see sensitive content buttons at all.
If an ad reviewer or an in-app scanner sees your content buttons, that's what gets your link flagged, your ad rejected, or your post actioned. Cloaking closes those exposure paths: the automated crowd gets a clean, unremarkable view, so the thing that triggers a rejection is never in front of the thing that rejects it. Your real audience is unaffected.
Ad review
Keep the buttons a paid-ads reviewer would flag out of the reviewer's view.
In-app link scanners
Links opened inside social apps are scanned before they render — cloaking answers those scans cleanly.
Scrapers & bots
Automated crawlers and datacenter traffic don't get a copy of your funnel to index or report.
The controls
Cloaking is a small set of per-domain switches. Every one ships at a sensible default, so a brand-new domain is already protected — you only touch these to make a domain more or less conservative.
Bot-filter level
A single dial for how strict the automated-traffic filter is on this domain:
| Level | What it means |
|---|---|
| Off | No bot filtering on this domain — everyone gets the same view. Use only when you have a reason to. |
| Basic | The default. Filters the common automated and non-human traffic. |
| Strict | Turns the filter up for domains under heavier scrutiny (e.g. an actively-reviewed ad campaign). |
Reliable open (per network)
A per-network set of toggles that improves how reliably your link opens for visitors arriving from each social app — so a tap from your bio lands on your page cleanly instead of a dead-end. Enable it for the apps you actually get traffic from and leave the rest alone.
Traffic-split control
A master switch for the domain's audience routing. On (the default), visitors flow through your geo-segments and per-button conditions as normal. Off, the domain serves its default segment to everyone — a simple, single-view page — bypassing the routing entirely.
Per-domain toggle
All of the above lives on the domain, not your account, so each domain can be tuned for its own traffic. A quiet organic domain and a domain running paid ads can sit at different levels side by side.
Safe defaults
You don't have to configure anything to be protected. Every domain starts with cloaking on at the balanced default — the controls above are there for when you want to dial a specific domain up or down.
Cloaking and the 18+ gate
Cloaking and the 18+ content gate solve related but different problems, and they compose:
- Cloaking targets automated viewers. It's what keeps content buttons out of bot, scraper, and in-app-scanner views — the paths that actually cause ad rejections and takedowns.
- The 18+ gate targets human viewers. It's an optional confirmation step a real person sees before the page.
Because cloaking already prevents the common automated-exposure paths, most creators don't need the gate — it's extra conservatism for human traffic from especially strict sources, not a substitute for cloaking. Turn it on when a specific audience calls for a confirmation step; leave it off otherwise.
FAQ
Next steps
Landing pages
Build a per-domain link-in-bio funnel — geo-segments, button stacks, a notification banner, and a background — then preview and publish it.
Smart Links
One link — /r/<slug> — that holds both your paid subscription and your free trial and decides per visitor which to show: a weighted split with per-country rules. Plus click, subscriber, and revenue performance.