We scored
100 out of 100.

The gap between the two columns is the whole story. Their own page has nothing paid on it, so the heaviest check passes for nothing and it scores 77. Three real creator pages with an OnlyFans link on them scored 25, 35 and 25, and on every one the paid address was sitting in the page for anything to read.

Their own page, 77, and for the same reason as Linktree: nothing paid on it to find. We have not yet measured a creator page here, so we are not going to guess at one.

Aimed at exactly our market and ships a file called bouncy-meta-escape.js, while the OnlyFans address sits in the same page as an ordinary link. Their own marketing site scores 45; a page they host for a creator scores 27. The creator number has moved a lot: 45 on 26 August, 5 on 31 August, 27 now, and ten of that came back because we fixed our own check rather than because they changed anything.

Both columns are creator pages here, one without a paid link and one with, which is why they are close. Their pages are rendered on the server with every destination in the source as an ordinary link, and they run Google Analytics, Microsoft Clarity and a Meta pixel flag on the creator page.

Turns up in search, makes a preview box when shared, and tells wherever you land where you came from. We have not measured one of their creator pages.

The lowest company page here by some way, and the one most adult creators already use. No creator page measured yet.

The widest gap between the two columns we have measured. Their own site scores 72. A real creator page built on Carrd, with an OnlyFans link on it, scores 20: the paid address is readable straight off the page, and the page makes a preview box with the creator's name and photo in it when the link is shared. Carrd is a page builder rather than a link-in-bio product, so none of this is a feature they got wrong. It is what you get when a general tool is used for this job.

The only other product in this table that passes the heaviest check. On a creator page with a paid link, the destination is not in the served HTML at all: the links are filled in after the page loads and their robots file disallows the resolver path. What costs it the rest is a full preview card on every creator page, with the creator's name as the title and a profile photo as the image, and Google Analytics through Tag Manager on creator pages but not on hoo.be's own. That is Google, not Meta: there is no Meta pixel here, and the difference matters.

We cannot give beacons a number. Their site checks whether a visitor is a real browser and turns ours away at the door, so we never see the page. Open it in Chrome and it loads fine. That is their protection doing its job, and it may well mean Meta cannot read their pages either, which would count in their favour on these same checks. We could dress our scanner up as something it is not and get in, and we would rather leave this blank than publish a number we did not really measure.