Why Pool Provenance changes as the Campaign Expansion proceeds
Why Pool Provenance changes as the Campaign Expansion runs
Deciding how many outbound links a page may hold keeps the profile realistic and stops any one target from looking unusually heavy. Engine-Compatibility Check gives list-maintenance specialists a defined way to judge pool provenance while the campaign is at the campaign expansion. The engine-compatibility check is the point at which platform diversity either earns its place in the workflow or is dropped. Without a regular schedule the posting pattern looks mechanical, and patterns that look that way are simpler for a platform to filter out. Campaign structure is simpler to judge from the verification log than from the settings page, since the log shows what was genuinely placed. When captcha costs rise faster than verified link counts, the usual cause is a set of engines that rarely finish a post.
The fuller account at GSA Serverified Lists is offered as background, useful when a reviewer needs to explain a setting to somebody else. Exporting a small sample of live placements gives a firmer basis for the next decision than any dashboard total. Roll the change out to a single tier only, watch the next two batches, and widen it only if the error rate stays flat. During the campaign expansion, the question is whether pool provenance still supports knowing where a target list came from and how old it is.
Compare Imported Targets Before Volume Without Mixing Evidence
At verification time the engine records whether a link is dofollow or nofollow and stores that attribute alongside the verified address. A batch of roughly 36 destinations is large enough to expose a pattern in pool provenance without becoming unreadable.