Both scheduled runs since the last brief failed silently. The Saturday job
fired on 15 Aug and 22 Aug (confirmed via Task Scheduler), but both logs stop mid-collection with
no error, and LastTaskResult: 1 on both. Running the collector by hand today finished
cleanly in under 5 minutes, so the collector itself isn't the fault — something about the
unattended 2am context is killing the job before it logs anything. This is the second time this
exact failure has happened. This report compares the 28d window ending 22 Aug against the 18 Aug
snapshot; the windows overlap by 24 days, so 7d figures are soft signal only.
Last week's brief flagged that cta_click had only just started firing on three
landing pages. This week the entrant counts multiplied — /exclusive-access grew
6.5x in one snapshot — and click-through on all three is strong.
| Landing page | Entrants (was) | This week | Cumulative CTR |
|---|---|---|---|
| /exclusive-offer | 28 | 43 (+15) | 9.3% |
| /exclusive-access | 22 | 144 (+122) | 15.3% |
| /vip-access | 24 | 94 (+70) | 17.0% |
This makes the two-week-old robots.txt contradiction urgent, not optional. These pages are still in the disallow block while taking real, converting traffic. Either they're live campaign pages that should be indexed and promoted, or they're test pages that shouldn't be getting this much traffic. Someone needs to decide which, this week, and find where the traffic is coming from.
Total ranked (US) went 21 to 23, which clears the movement threshold on its own.
| Keyword | Position | Change |
|---|---|---|
| forever model trading | 8 | was 28 — 20-place jump into top 10 |
| inverse value gap (new) | 20 | newly visible, vol 40/mo |
| teach v2 | 97 | was 84 — fell further out of reach |
Nothing shipped this week targets /indicators/forever-model, so read the jump as a
normal SERP reshuffle, not a result of any deliverable landing.
Real query, country and page data for Toodegrees for the first time. Two findings that DataForSEO could never show:
| Market | Impressions/28d | Avg position | DataForSEO showed |
|---|---|---|---|
| India | 501 | 19.1 | 0 keywords |
| UK | 360 | 14.6 | 0 keywords |
| Germany | 101 | 6.9 | 0 keywords |
| Vietnam | 226 | 33.3 | 0 keywords |
Confirms landmine 11: rank tools were never blind because the traffic wasn't there — it
was there and invisible. The IFVG page cluster (inverse fair value gap and its
variants) is the other headline: 400+ impressions across dozens of query forms, all sitting at
position 16-40, essentially zero clicks. The page the AI-citation work has flagged repeatedly for
zero citations turns out to have the same problem in classic search.
The twist: every fix this data suggests was already shipped 10 days ago.
Checking git log found commit fac168e (13 Aug), which rewrote all 17
indicator meta descriptions (most were 60-80 characters where Google renders ~160 — a
snippet problem, not a ranking one), fixed a TTFM title/homepage-cannibalization issue this
session independently found today, and shipped a new article leading with "inverse" instead of
"inversion" — targeting the exact IFVG cluster above, since GSC showed searchers say
"inverse" about 9x more often. That article is ~10 days old and plausibly still ramping.
Someone already has independent GSC access and is running this exact playbook. Worth finding
out who and coordinating, rather than this workspace duplicating the work blind.
Cumulative since 31 Jan 2026. Weekly movement is the subtraction against last week's snapshot.
| Funnel | Path now | This week |
|---|---|---|
| Purchase Journey | / 8,405 → /pricing 3,010 → /checkout 570 → /welcome 97 | +142 / +68 / +15 / +3 |
| Indicators to Purchase | /indicators 4,560 → /pricing 1,899 → /checkout 391 → /welcome 76 | +95 / +44 / +10 / +4 |
| Exit Popup Capture | popup 754 → captured 57 | +135 / +10 |
Only 15 new sessions reached checkout this week — below the 30-entrant floor needed to read a rate. The completion count (3 of 15) looks better than last week's, but the sample is too small to call it fixed. Cumulative end-to-end held flat at 1.15%. D1 (diagnose the checkout drop-off) stays open; re-check next week with a larger window.
Referring domains rose 52 to 53, which clears the movement threshold on its own (any change counts). Total backlinks essentially flat, 141 to 142.
| Gained this week | Spam | First seen |
|---|---|---|
| theforbestimes.com | 60 | 2026-08-21 |
Spammy domains (spam score 30+): 12 → 16 → 17 over three straight snapshots. The trigger set two weeks ago has fired. "Watch, and disavow if it keeps rising" is now due. Dofollow share sits at 30.4%. Top domain (TradingView) is 47.9% of all backlinks and mostly nofollow, so headline count still overstates real authority — effective clean dofollow links remain roughly 20.
No partner link landed this week. Both Tier 1 asks are drafted and ready in the 10 Aug deliverables folder. They are the only work that reliably moves dofollow equity, and need no content — just sending.
Tradeify, Apex Trader Funding and Lucid Trading. Toodegrees refers customers to them via
the TOO code and gets nothing back link-wise. Drafted, compliance-checked, unsent
for a second week. Deliverable D7.
Co-built the Fractal Model, TTrades ranks #1 for it, Toodegrees ranks #16 for the co-branded term, no link either way. Same-day job. Deliverable D8.
Solves: dofollow equity plus topical relevance on a term already rankingSecond week unsent, zero content cost. Deliverables D7 and D8.
File is built (17 domains, spam 30+, third straight week climbing) but the GSC account connected this week doesn't have permission to submit it. Needs whoever manages the property directly.
Still the largest conversion gap on the account. This week's sample was too small to close it out. Deliverable D1.
Commit fac168e (13 Aug, by a site contributor) already fixed the
TTFM, snippet-length, and IFVG-vocabulary issues this week's data surfaced. Someone is
already running this playbook faster than this workspace can see — worth coordinating
instead of duplicating.
Checked 23 Aug: handled via a canonical-tag mechanism already live in the codebase, better than the 301 this deliverable asked for. Deliverable D4, closed.
/exclusive-access and /vip-access surge is coming from. The robots.txt question itself is resolved (deliberate, correct) — the source of the surge is not.