Add Planning Anchor Distribution for the next First Controlled Batch

Planning-Anchor-Distribution-for-the-next-First-Controlled-Batch.md

@@ -0,0 +1,18 @@
+Planning Anchor Distribution ahead of the next First Controlled Batch
+<br>Every campaign requires a data folder that holds targets, submitted URLs, verified URLs, and the logs kept for later review. Post-Update Comparison gives solo campaign operators a defined way to judge anchor distribution while the campaign is at the first controlled batch. The post-update comparison is the point at which content-to-target fit either earns its place in the workflow or is dropped. List quality determines how much of a long run turns into placements, since a weak target set produces plenty of attempts and few confirmations. When a new engine is added mid-campaign, it starts in the lowest tier first so its behaviour can be watched before it reaches the upper layers. A monthly check of verified counts per engine indicates where effort pays, and it takes far less time than rebuilding a list.<br>
+<br>The full write-up at [a maintained GSA SER list reference](https://git.newnaturalphilosophy.org/lilianaboyes09) is optional reading, useful mainly when a campaign needs a written process rather than quick steps. Notes on which engine produced each link add value, since one link count can conceal quite different engine blends. Check the captcha solver balance and the per-engine success report side by side before assuming that target-side filtering alone explains the drop in verified links. During the first controlled batch, the question is whether anchor distribution still supports using readable topical language instead of repeating one commercial phrase.<br>
+Pace One Batch at a Time Across Two Layers
+<br>Captcha costs scale with submission volume, so poorly filtered lists burn budget on targets that were hardly ever going to accept a post. A batch of roughly 64 destinations is large enough to expose a pattern in anchor distribution without becoming unreadable. For solo campaign operators running a Tier 2 project, using readable topical language instead of repeating one commercial phrase matters more than the raw number of attempts recorded against content-to-target fit. The poster populates each form field from the project data, then follows redirects and confirmation links until it reaches a page that reports success. Record the response codes returned during submission, and treat a cluster of identical errors as a sign that a single engine requires attention. A captcha service that runs out of credit mid queue halts submissions quietly, and the interface goes on showing a campaign that is doing nothing at all.<br>
+Record Volume Against Evidence Without Losing the Audit Trail
+<br>Split the project into tiered groups so the easier targets carry the first tier and everything else can be tested separately. For a conservative rollout, content-to-target fit should be assessed against duplicate-host rejection rate before any decision about faster fault isolation. Read duplicate-host rejection rate alongside the post-update comparison results before concluding anything about anchor distribution. Halt the run at the first sign of a repeated error, fix the cause, and restart from the checkpoint rather than continuing. Store the error log for each engine separately, since one combined log hides which platform produced which failure and at what point it started. Record the date of the last list refresh, because understanding when the pool was rebuilt helps the next reviewer assess whether staleness is a factor.<br>
+
+Define the Comparison Baseline Across Two Layers
+<br>Text quality sets a limit on what an engine will take, because some platforms turn down spun text that fails a readability check. The post-update comparison is the point at which anchor distribution either earns its place in the workflow or is dropped. Where content-to-target fit is concerned, faster fault isolation is the outcome worth paying for, and it is rarely visible immediately. A campaign log that records failures alongside successes is more useful than a summary reporting only the closing verified total. A run that ran cleanly is not the same as a run that produced placements, and the two outcomes get confused whenever logs are read quickly. Think of the process as a cycle of submit, verify, prune and repeat, with each pass refining the targets that the following round receives.<br>
+Review the Working Target Pool Without Mixing Evidence
+<br>If the verified rate falls sharply on one engine, pausing that module and logging the failure keeps the rest of the run moving. For solo campaign operators running a Tier 2 project, using readable topical language instead of repeating one commercial phrase matters more than the raw number of attempts recorded against content-to-target fit. Post-Update Comparison gives solo campaign operators a defined way to judge anchor distribution while the campaign is at the first controlled batch. Thread count has a natural ceiling, because too many parallel requests trigger rate limits and waste submissions on rejected targets. When results improve, check whether the improvement came from the list, the engines or the content before repeating it. Do the smallest test batch first and expand the volume afterwards when the error rate and the verification trend look stable.<br>
+Separate One Batch at a Time Before Volume
+<br>Statements about coverage are easy to make and hard to verify, so a figure is only meaningful alongside the method used to derive it. Read duplicate-host rejection rate alongside the post-update comparison results before concluding anything about anchor distribution. During the first controlled batch, the question is whether content-to-target fit still supports using readable topical language instead of repeating one commercial phrase. Two runs that differ only in thread count allow a fair comparison, while runs that change several settings at once explain nothing about which change mattered. Maintain one line per run in a single file, since a flat list of dated runs is easier to scan than a directory of exports. Every campaign leaves two useful artifacts behind, namely the verified list itself and the engine configuration that generated it.<br>
+<br>The mechanism described above is demonstrated here: [video walkthrough](https://www.youtube.com/watch?v=TiB6k2Nn47k)<br>
+Confirm the Mechanism Against a Primary Source
+<br>Where a setting or macro is involved, a primary source settles the question faster than a second-hand account. Tier 2-level decisions about anchor distribution during the post-update comparison are documented in the same place. [the robots exclusion protocol standard](https://www.rfc-editor.org/rfc/rfc9309.html) 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>A campaign becomes manageable once each change can be traced to a result. Read duplicate-host rejection rate alongside the post-update comparison results before concluding anything about content-to-target fit. Retaining the accepted destinations, rejected hosts, engine selection, content version and verification window keeps anchor distribution and content-to-target fit 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. Verification should run on a regular cadence, because pages disappear, change their rules and stop accepting comments at short notice. Store the anchor text distribution as a file, so later runs can be compared against the same pattern rather than a recollection of it. Keep a standing list of engines that stopped producing verified links, so the next build does not waste threads on them again.<br>