Add Planning Pool Provenance for the next Campaign Expansion

Planning-Pool-Provenance-for-the-next-Campaign-Expansion.md

@@ -0,0 +1,18 @@
+Planning Pool Provenance before the next Campaign Expansion
+<br>Automated link building rewards the operator who defines the unit of work before the project runs, rather than afterwards. Platform-Mix Review gives solo campaign operators a defined way to judge pool provenance while the campaign is at the campaign expansion. The platform-mix review is the point at which platform diversity either earns its place in the workflow or is dropped. Anchors that repeat word for word across an entire target set appear arranged instead of earned, so variation is a practical habit. The route between layers should be written down before the first submission, since it decides what each project may target. If the log shows plenty of submissions but hardly any confirmations, the bottleneck most often sits in the target list and not the project settings.<br>
+<br>Nothing here depends on opening [GSA Serverified Lists](https://lanjut.in/javierhacker30), though the extended notes there set out verification ratios and indexing checks in more detail. Consistent formatting across runs matters, since two exports with different column names cannot be compared without manual cleanup first. Pull the target list as it stands, deduplicate the domains, and drop every entry that failed verification more than once in the last run. During the campaign expansion, the question is whether pool provenance still supports knowing where a target list came from and how old it is.<br>
+Document Stale Entries Without Mixing Evidence
+<br>Verification confirms that a link exists at the expected location, which is different from the page will keep it. A batch of roughly 64 destinations is large enough to expose a pattern in pool provenance without becoming unreadable. For solo campaign operators running a Tier 2 project, knowing where a target list came from and how old it is matters more than the raw number of attempts recorded against platform diversity. Two exports of the same list taken a month apart are worth comparing line by line, because the change in live links measures list decay directly. Where a count moves without any matching change in the live links, record the discrepancy and leave the reading open until a second check lines up. Never treat a low success count on one platform as a judgment on the whole campaign, since sample size and timing both shape that number.<br>
+Document the Destination Layer Without Mixing Evidence
+<br>When a new engine is added mid-campaign, it starts in the lowest tier first so its behaviour can be studied before it reaches the upper layers. In practice, platform diversity should be assessed against unique-domain coverage before any decision about faster fault isolation. Read unique-domain coverage alongside the platform-mix review results before concluding anything about pool provenance. Watch the share of targets that never leave registration, since a high figure points to a form change rather than a proxy problem. Whatever the settings, a submission that lands on a page nobody links to will contribute very little, and volume alone will not change that. Re-run the same batch against a copy of the previous project to see whether the difference came from the parameters or from the list itself.<br>
+
+Protect the Tier Boundary at the Verification Window
+<br>A supporting layer that imports the identical target pool as the layer above it doubles work and rarely adds anything the structure did not already have. The platform-mix review is the point at which pool provenance either earns its place in the workflow or is dropped. Where platform diversity is concerned, faster fault isolation is the outcome worth paying for, and it is rarely visible immediately. The matcher compares the detected platform against the engine definition, so a wrong identification sends the submission toward the wrong form. A subset of verified addresses checked by hand confirms that the link text and target really show up where the engine recorded them at submission time. Duplicate content pushed to many targets with identical anchors can dilute relevance and waste the indexing attention the campaign was meant to earn.<br>
+Pace the Accepted Sample Before Volume
+<br>Drop the engine that produced the lowest verified count, rerun the same batch without it, and compare the two figures before restoring it. For solo campaign operators running a Tier 2 project, knowing where a target list came from and how old it is matters more than the raw number of attempts recorded against platform diversity. Platform-Mix Review gives solo campaign operators a defined way to judge pool provenance while the campaign is at the campaign expansion. Drain the queue completely before changing the configuration, otherwise the old and new settings run side by side and the result is hard to read at the engine level. Record the outbound link count seen on each target at submission time, so later competition on that page can be measured against it. The next review should be able to answer what changed since the last one.<br>
+<br>A recorded walkthrough covering the same ground: [tutorial](https://www.youtube.com/watch?v=quOII_Z265E)<br>
+Measure Imported Targets Before Volume Against a Baseline
+<br>The resource cost of a run is set by the slowest step, so a project that waits on captcha solving barely gains from a higher thread count. Read unique-domain coverage alongside the platform-mix review results before concluding anything about pool provenance. During the campaign expansion, the question is whether platform diversity still supports knowing where a target list came from and how old it is. A link counts as usable evidence once the page loads cleanly, the link appears in the raw markup, and the anchor matches the text that was submitted. A run that ran cleanly is not the same as a run that produced links, and the two outcomes get conflated whenever reports are skimmed quickly. Ongoing upkeep rather than a single setup is what keeps a target list usable, so the habit deserves a fixed place in the weekly routine.<br>
+Confirm the Mechanism Against a Primary Source
+<br>When an option, engine or macro behaves differently after an update, the behaviour is worth confirming against a primary reference. Tier 2-level decisions about pool provenance during the platform-mix review are documented in the same place. [the GSA SER advanced-setup manual](https://docu.gsa-online.de/search_engine_ranker/advanced_setup) is the appropriate reference here. It is included as a neutral reference rather than as a commercial destination, and it is no substitute for the operator's own evidence.<br>
+<br>What matters after a campaign run is the record of which engines produced verified links and which settings allowed it. Read unique-domain coverage alongside the platform-mix review results before concluding anything about platform diversity. Retaining the accepted destinations, rejected hosts, engine selection, content version and verification window keeps pool provenance and platform diversity inside one evidence set, so the next run can change a single variable against the route from native Tier 2 to the verified Tier 1 placements. List maintenance is an continuing routine, so retesting targets on a regular schedule matters more than a single thorough cleanup. Record the thread limits, the proxy rotation settings, and the captcha configuration used for each run of submissions. Plan the following batch around the tiers that still produce links, and treat the rest as candidates for a future refresh.<br>