FYI: Facebook doesn't like content lockers

EDIT: Content lockers from networks using the same old domains (at least I'm assuming), like domain.com/locker.js - Gotta run a few more tests.

Several different domains hosted on seperate servers with different content. All banned same day.

Doesn't affect me though as none were getting much traffic from Facebook. I only noticed because I shared a few on my personal profile (set to only I could see, was testing something at the time) and got a bunch of messages from facebook with "we removed your post because we think it's spam".

The footprint? Content lockers.

Two of the domains were almost brand new and received very little traffic, none from Facebook users and only a few hits from their bots (which I assume are from when I shared). One domain was unbanned after somehow getting reviewed (which seems to be super rare) after clicking the It's not Spam link.

I've seen this in the past but always assumed it was because: Same host, same content (besides different og:image), and how viral gift cards (not using that niche now) became very frowned upon. Didn't think they were actually looking for javascript code / links. I know, it's a huge footprint but we got away with it for a long time.

Anyone else notice this?

So you weren't cloaking?

I was thinking of trying lockers on FB, but I was going to use a pre-lander with a form that lead to the locker. That way the bots could not find the locker. Then I just have to deal with manual review issue.

No cloaking.

That should work. I would just avoid using the default domains networks give for locker code.