BLACKHATMAPAffiliate & infrastructure forum

Drip over 90 days vs firing them all in a week - did anyone ever see a difference

Started 21 May 2024 · 11:07 · 7 replies · 439 views

Page 1 of 18 posts

MetricsOverMagic

Senior Member

21 May 2024 · 11:07#1

I've paid a premium for staggered placement on every batch I've bought since 2021 and I've never once seen data justifying it. So before I pay it again, I want to know whether anyone has.

What I have is four batches, two of each, same site, same anchor mix, roughly comparable link quality:

Batch Links Schedule Weeks to first movement Peak gain
A 12 over 11 weeks 7 +4 positions
B 10 all in 6 days 5 +5 positions
C 14 over 13 weeks 9 +2 positions
D 11 all in 4 days 6 +3 positions

The blast batches moved sooner and no worse. Nothing bad happened to either of them. n=4 on one site is not a study and I know it, which is why I'm asking rather than concluding.

Specifically: has anyone got a case where a blast caused a visible problem that a drip didn't? Because the entire justification for the premium is that risk, and I've never seen it documented anywhere except in the marketing of people selling drip schedules.

—

old_growth_seo

Senior Member

21 May 2024 · 13:44↑ replying to #1#2

You won't find one, and the reason is that drip feeding is a solution to a problem that was retired in 2016.

The logic made sense in the Penguin era. Penguin ran as a periodic refresh - it landed, it looked at your profile as a whole, and if the shape of it screamed purchase, the site went down and stayed down until the next refresh, which might be a year. Under those conditions, velocity mattered enormously, because you were being assessed on a snapshot and a spike was the most visible thing in one.

Penguin 4.0 in September 2016 made it real-time and made it link-level. Once the response is 'this individual link is discounted' rather than 'this site is flagged', the shape of your acquisition curve stops being the unit of judgment. There's nothing for the spike to be a signal to.

Drip feeding survived because it's a good story, because it lets a seller bill monthly instead of once, and because nobody can prove a negative. I stopped paying for it in 2017 and I've never seen a reason to start again.

The one thing I'd still stagger: placements on the same domain. Eight links from one site in a week is a different signal to eight links from eight sites in a week, and that one I do think still matters.

11 thanks

drift14

Newbie

21 May 2024 · 14:02↑ replying to #1#3

you're paying for a calendar entry mate

—

byte_broker

Member

22 May 2024 · 09:31↑ replying to #1#4

I'll defend the premium, but not for the reason it's sold for.

When someone buys 12 links and asks for them over 11 weeks, what actually happens on my end is that I place them as slots come up on sites I'd want to use anyway. A blast means I fill the order from whatever is available this week, and what's available this week is disproportionately the inventory that isn't moving.

So the drip premium isn't buying you safety from a velocity signal. It's buying you the right to wait for better placements, and it works because it changes what the seller can get away with. Depends what you're running, but if you've ever had an order filled unusually fast and been slightly disappointed with the sites, that's the mechanism.

Buy the schedule if you're buying from someone with inventory you can't inspect. Don't buy it if you're picking the sites yourself, because then you're paying for nothing.

6 thanks→ aged domains + hosting, PM for the list

onyxtundra

Newbie

22 May 2024 · 10:18↑ replying to #4#5

That's the first argument for drip I've heard that isn't superstition. Noted.

—

hexforge

Senior Member

23 May 2024 · 15:52↑ replying to #1#6

Two methodological things about your table, neither of which changes your conclusion but both of which affect how much weight to put on it.

Your weeks-to-first-movement column is measuring different things for the two conditions. For a blast, the clock starts when the whole batch is live. For a drip, it starts when the first link is live, which is up to eleven weeks before the batch is complete. Batch A moved at week 7 with maybe half the links placed. If you re-baselined both to the halfway point of placement you would get a smaller gap and possibly none.

Second, batches B and D are also your smaller batches. Fewer links, faster placement, and less time for anything else on the site to change during the measurement window. Shorter windows are cleaner windows.

I would still bet the same way you would. I just would not quote the two-week difference as though it were the finding.

—

Ravenstack

Senior Member

23 May 2024 · 16:21↑ replying to #6#7

Good catch on the baseline. Does that survive if you re-run it, MetricsOverMagic?

—

MetricsOverMagic

Senior Member

04 Jun 2024 · 09:39↑ replying to #7#8

Re-baselined to the midpoint of placement rather than the first link, as hexforge said.

A: 7 weeks becomes 2. C: 9 becomes 3. B and D barely move, 5 and 6 become 4 and 5.

So the drip batches were faster, not slower, once you measure them correctly, and my original table had it backwards. Which makes the case for drip slightly better than I stated and still nowhere near a premium.

What I'm actually taking away is byte_broker's version - I'm going to keep asking for staggered placement with sellers whose inventory I can't see, and stop paying for it where I pick the sites. That's not the answer I came in looking for.

Still nobody with a case where a blast caused a problem. Eight replies in and that's the number I care about.

8 thanks

You must be logged in to reply. Request an account — new registrations are reviewed by a moderator before approval.