docs(content): 20.09 pipeline-first content plan revision

[pftg]

Re-review of the content plan against our goals, SEO state, and current market. Four researchers ran in parallel (market/trends, on-site SEO, competitors, goal-alignment); every load-bearing claim below I verified myself against the repo or a live source.

Docs only — no content, templates, or CSS changed.

The finding that reorders everything

2607's own rabbit-hole rule (executive-summary.md:51):

Content is not pipeline. Blog posts and SEO support conversations; they do not sign clients by November. The human-path steps (warm outreach, the call, the close) are what count. Never ship a content sprint while the outreach is stalled.

Outreach is stalled (backlog.md:95): "ALL 5 messages HOLD — zero sendable rows." Batch-1 pre-research found 3 of 5 rows unsendable; the other 20 were built the same day by the same method. Card #12 is blocked on #29.

Four Rails deep-dives shipped Jul 22 → Aug 7 anyway. That's the configuration the bet prohibits. P0 is now unblocking the pipeline, not writing.

Biggest win needs no new content

/services/vibe-code-rescue/ carries the full offer — free Rescue Context Call, 48-hour audit scorecard, $2,500 / $7,500 / $10,000 tiers. It is the conversion page for the company's only active bet.

Zero of 608 blog posts link to it. Nav only. These six are pre-qualified rescue traffic and each links to it zero times: fire-dev-shop-guide, dev-shop-red-flags-checklist, hiring-dev-shop-questions, vibe-coding-crisis-ai-code-debt, quality-tax-ai-mvp-cost, 47-startups-failed-same-coding-mistake.

Under an hour of work, no new maintenance debt.

What 20.08 got wrong

Assumption	Reality	How verified
2-3 posts/week sustainable	~6/month; June 2026 published zero	Post dates Apr–Aug
Snippet rewrites → ~435 clicks	Modelled pre-AI-Overviews (~61% CTR loss on informational SERPs)	Seer 2026
Queued rows are new territory	7 rows duplicate existing posts; F2 already shipped	On-disk audit
Rails traffic funnels to rescue clients	Mechanism was removed by the Aug 7 exemption	Repo history

F2 already caused the damage: rails-8-authentication-generator-complete-guide (347 lines, Jul 29) shipped against an existing rails-8-authentication-generator-devise-migration (1,337 lines) plus two older posts. Four posts now compete on one keyword.

News policy — the flexibility question, answered

One test: will someone search this in six months?

Type	Example	Home	Slots
Durable — CVEs, releases, EOLs	CVE-2026-66066	Blog, fast	Swap, never add
Event — incidents, drama, funding	PocketOS DB wipe	LinkedIn only	Zero

The PocketOS post scored 48/50, ran the full 9-persona pipeline, earned 1 click in 3 months. A CVE ID is a permanent search string.

A swap rule rather than a new lane — net posts/week unchanged, deliberately, because throughput is binding. Plus 1 refresh slot/month: the Kamal 1/Traefik post is already factually wrong and still ranking.

Market changes worth acting on

• CVE-2026-66066 (Active Storage → RCE, CVSS 9.5, disclosed Jul 29) — verified via Rapid7 and Akamai. Underserved angle: upgrading Rails is not sufficient — libvips must go to ≥8.13 and secrets must be rotated. Rails ≤7.1 has no patch.
• F7 (Ruby 3.4 YJIT) cut — stale version line; Ruby 4.0 is stable.
• The category is contested. justinmckelvey.com/vibe-code-rescue — cited in our own strategy as proof the model works — now sells "Vibe Code Rescue" at $25K–$50K under that exact name, alongside Future Wonder, Pragmatic Coders and others. 2607's "competitors are only just entering it" (Jul 21) no longer holds.

Left for Paul, not decided here

1. Fresh GSC export — every CTR conclusion rests on the Jul 19 pull; the AI-Overviews re-baseline can't be done without it.
2. What was June? Zero posts. If content reliably loses to other projects, cadence should be 4/month, not 6.
3. The price question. Our page deliberately undercuts: "a full rescue at $7,500 when traditional agencies quote $25K-$55K for the same work." But our ICP was just burned by cheap development, and we published "Cheap Developers Are Expensive When Nobody Senior Reviews the Code" on Jul 31. Competing on price argues against our own thesis.
4. Category name — keep "Vibe Code Rescue" and fight for it, or differentiate?

Verification notes

• Competitor cadence figures are WebSearch-derived; the egress proxy blocked WebFetch on publisher domains, so titles/URLs/dates are solid but cadence counts are estimates.
• Verbatim founder quotes largely failed to collect (Reddit/HN/IndieHackers blocked). Your call transcripts are a better source.
• The "84% adoption / 29% trust" stat circulating as 2026 data is actually the 2025 Stack Overflow survey — not used.
• This clone is shallow (history starts Aug 1), so the June gap is verifiable from post dates but not attributable to a cause from git history.

Summary by CodeRabbit

• Documentation
  • Updated the active content strategy for August–November 2026.
  • Added an outreach-first publishing gate and clarified capacity at approximately six posts per month.
  • Prioritized pipeline outcomes, discovery calls, and routing existing traffic to the rescue service.
  • Consolidated overlapping Rails topics and added durable-news and content-refresh guidelines.
  • Documented corrected projections, capacity assumptions, missing inbound links, and current market risks.
  • Updated workflow guidance and marked the previous content plan as superseded.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a0a47531-97c9-4b82-a64e-96a835130c2c

📥 Commits

Reviewing files that changed from the base of the PR and between 0a35723 and f7b5cc9.

📒 Files selected for processing (6)

• .okf/content-strategy/content-plan.md
• .okf/log.md
• docs/projects/2510-seo-content-strategy/20-29-strategy/20.08-content-plan-data-driven-q3-2026.md
• docs/projects/2510-seo-content-strategy/20-29-strategy/20.09-content-plan-revision-aug-2026.md
• docs/projects/2510-seo-content-strategy/GOAL-AT-A-GLANCE.md
• docs/workflows/blog-pipeline.md

---

📝 Walkthrough

Walkthrough

The PR introduces the August 2026 pipeline-first content plan, supersedes the prior Q3 allocation, gates publishing on outreach readiness, updates content priorities and metrics, and aligns strategy and blog-pipeline documentation with plan 20.09.

Changes

Content strategy revision

Layer / File(s)	Summary
Plan authority and supersession .okf/content-strategy/content-plan.md, .okf/log.md, docs/projects/2510-seo-content-strategy/20-29-strategy/*	Plan 20.09 becomes the plan of record. Plan 20.08 is marked as superseded, while its GSC analysis remains valid.
Pipeline and content priorities docs/projects/2510-seo-content-strategy/20-29-strategy/20.09-content-plan-revision-aug-2026.md	The plan prioritizes outreach unblocking, limits publishing to six posts per month, links qualified posts to the rescue offer, reduces topic cannibalization, defines news handling, and selects CVE-2026-66066 as the weekly article.
Metrics and stop rules docs/projects/2510-seo-content-strategy/20-29-strategy/20.09-content-plan-revision-aug-2026.md	Metrics now track discovery calls, LinkedIn replies, conversion, enablement use, and outreach stalls. Duplicate topics, event-news blog posts, territory expansion, old forecasts, and stalled publishing are stopped.
Strategy and workflow wiring docs/projects/2510-seo-content-strategy/GOAL-AT-A-GLANCE.md, docs/workflows/blog-pipeline.md	The overview and blog pipeline reference 20.09, enforce the P0 outreach gate, and direct future plan updates to the August revision.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• jetthoughts/jetthoughts.github.io#284: The revised plan reclassifies a Rails topic introduced by this PR.
• jetthoughts/jetthoughts.github.io#387: The revised plan prioritizes the same Vibe Code Rescue acquisition funnel.
• jetthoughts/jetthoughts.github.io#437: This PR updates the same content strategy and blog pipeline areas while superseding the earlier Q3 plan.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/content-calendar-next-post-hztfag

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}