git:20260903.a6a1fc3 to git:20260905.4909a33

169 added, 74 removed. Audit A to A.

---
name: social-youtube
title: "YouTube Publishing Playbook"
- description: "Ground-truth 2026 playbook for YouTube packaging and structure — titles, thumbnails, hooks, retention editing, Shorts vs long-form. Built on the official mechanics ('the algorithm follows the audience', per-video ranking, satisfaction-weighted watch time), measured retention data (average 23.7%, 55% gone in the first minute, the 10–20s cliff), the packaging-first discipline (top creators spend 30% of time on ideation/packaging vs 5% for small ones), the 20–30x Shorts-vs-long-form RPM gap and what the Mohan parity quote actually said, the December 2024 egregious-clickbait enforcement, and the July 2025 inauthentic-content monetization rules. Activate when crafting anything destined for YouTube."
+ description: "Write YouTube scripts and publishing packages in the author's documented voice. Activate for titles, thumbnails, descriptions, Shorts, channel posts, product launches, demonstrations, customer proof, or revisions using audience feedback. Covers format choice, honest packaging, spoken delivery, and qualified next steps."
license: Apache-2.0
- compatibility: "Octomind content agents. Platform-specific to YouTube (long-form, Shorts, titles, thumbnails, descriptions)."
+ compatibility: "Requires source material and author samples; network and YouTube Studio access for account-specific publishing checks."
domains: content
rules:
- content(youtube)
- match(\byt\s+(video|short|shorts|title|thumbnail|channel)\b)
---
## Overview
- YouTube's own Creator Liaison stated the whole strategy in one line: "The algorithm follows the audience, so please the audience… and then the algorithm will take care of itself." Discovery is pull, not push — recommendations are fetched per viewer, ranked per video (not per channel), and watch time is weighted by satisfaction (surveys, return visits, session continuation), not raw duration. There is no penalty box: a flopped video limits that video, not the channel.
+ Write for a named viewer with a real reason to watch. Follow supplied facts and proof, then the author's documented voice, then platform conventions. Use `content-voice` for general editing; this skill adds spoken delivery and YouTube packaging.
- The measured reality most creators never see: average retention across 10,000+ videos is 23.7%, over 55% of viewers leave within the first minute, and only 16% reach the final ten seconds (Retention Rabbit 2025). Meanwhile the economics are lopsided — long-form median RPM ~$2.50 vs Shorts ~$0.05 (AIR, n=274 channels), a 20–30x per-view gap. This pack exists because packaging (idea, title, thumbnail) decides most of the outcome before a second is filmed: top creators spend ~30% of their time on ideation and packaging; small creators spend ~5% (Paddy Galloway).
+ Produce a publishable package with an identifiable author and an honest next step. Keep source notes separate from spoken copy. Missing evidence makes a factual draft unpublishable; don't fill gaps with invented experience.
- Pair with `content-voice` for scripts. This pack owns the packaging and structure layer; production itself is a downstream concern owned by another domain.
+ ## Mental model
- ## Instructions
+ Work backward from the viewer's task and the evidence you can show. Choose packaging before scripting, then revise it if the footage cannot keep the promise (directional; Galloway). Treat retention graphs as diagnostic evidence for that upload. Don't prescribe universal opening deadlines, re-hook intervals, or a guaranteed format-transfer effect (directional).
- ### Packaging first — the workflow that separates tiers
+ Views, attention, and commercial outcomes answer different questions. Metricool observed rising views alongside falling viewing duration and interaction measures across both formats (measured, Metricool, n=799,718 videos, 2026-07). Keep format and traffic-source comparisons separate; don't infer qualified demand from starts alone (directional).
- Title and thumbnail are decided BEFORE the script is written. If the packaging can't win the click, the video doesn't get made in that form. "The difference between a million views and 28 million views is how you package it" (Galloway); a single thumbnail improvement has measured 40x daily views in a documented case.
+ Open [reference/evidence.md](reference/evidence.md) when choosing cadence, interpreting benchmarks, estimating revenue, or using a case study. Open [reference/delivery.md](reference/delivery.md) when preparing assets, optional formats, disclosures, or monetization-dependent copy. Open [reference/launch.md](reference/launch.md) when planning a launch campaign or creator collaboration.
- - Ideation patterns that repeat: comparison structures ("$10 vs $1,000 …"), "familiar but unexpected" (proven format from an unrelated niche transplanted into yours), stakes escalation.
- - Portfolio rule: 80% of uploads target the proven audience overlap, 20% experiment. When a format works, ride it until it stops working.
- - YouTube's native Test & Compare runs up to three thumbnail/title variants (A/B/C, since 2025) — use it for real stakes uploads; don't call tests early (YouTube labels weak evidence "inconclusive" deliberately). Verify in Studio which metric the test optimizes before trusting a "winner" — historically it favors watch-share, not raw CTR.
+ ## Format and packaging decisions
- ### Titles
+ Use these craft bands as editing choices; they are not platform limits or measured optimum lengths (directional).
- - 50–60 characters as the working band (mobile truncates around there); the keyword and the hook inside the first ~40.
- - The title states the specific promise the video actually keeps — since December 2024 egregious clickbait (title/thumbnail promising what the video never delivers) is removal-eligible, not just demoted, with enforcement expanding globally.
- - Curiosity gap yes, lie no: "I tested every AI coding tool so you don't have to" works; "AI just KILLED programming?!" on a tool review is enforcement bait and satisfaction poison.
- - CTR sensitivity is real at tiny margins — YouTube itself notes a 0.5% CTR difference can be statistically significant at scale. Typical CTR runs 2–10% (directional; search traffic skews higher, browse lower) — judge against your own baseline per traffic source, not a universal number.
+ | Viewer situation | Format and length band | Structure and pacing |
+ |---|---|---|
+ | Casual discovery; result is immediately visible | Short; brief, self-contained demonstration | Show the outcome immediately, then the decisive action; cut setup that doesn't affect understanding |
+ | Buyer solving a named workflow | Long-form; as long as the complete task requires | Show the finished artifact, establish prerequisites, perform the job, retain failure conditions |
+ | Dedicated learner evaluating tradeoffs | Long-form; extended walkthrough | Keep readable screens and thinking time; chapter meaningful stages instead of adding arbitrary cuts |
+ | Comparing products | Long-form; matched demonstrations through a bounded verdict | Hold conditions constant, disclose omissions, show where each option fits |
+ | Audience needs to participate | Live session or Premiere if available; session-length | Schedule around a concrete discussion and staff moderation; prepare the replay package |
+ | Existing viewers need an update | Channel post or poll if available; compact prose | State the change or ask a decision-relevant question; attach useful proof |
- ### Thumbnails
+ For Shorts, finish the promise at the shortest useful length and verify current upload classification in Studio. Don't prescribe a sub-minute sweet spot or an engineered loop advantage (directional). Studio's “How many chose to view” reports viewed versus swiped away (official, YouTube Shorts analytics, 2026-09). Compare it with your own similar Shorts; don't turn it into a universal pass/fail cutoff (directional).
- Honest evidence note: nearly all circulating thumbnail percentages are unsourced aggregator claims — treat them as craft heuristics, not measurements. The defensible rules:
+ The Shorts player update includes Clear Screen, accelerated playback and mute controls; hearts replace thumbs-up, with “Not Interested” and “Don't recommend this channel” replacing dislike (official, YouTube Shorts experience, 2026-06). Make the meaning legible in the footage and captions even with sound muted or interface overlays hidden; test accelerated playback for comprehension (directional).
- - One readable idea at a glance: a face with a real expression, an object with clear stakes, or a bold visual contrast — not all three competing.
- - Three to five words of text maximum, complementing (never repeating) the title; must survive mobile size.
- - High contrast against YouTube's white/dark UI; adjacent evidence from Netflix's artwork testing puts color contrast among the strongest click predictors.
- - Design title + thumbnail as one unit: thumbnail poses the tension, title sharpens it (or vice versa) — together they must promise exactly what the video delivers.
+ ### Match packaging to the entry point
- ### The hook and the retention architecture
+ | Intended entry point | Title | Thumbnail and opening |
+ |---|---|---|
+ | Search | Name the exact task using the buyer's language | Show the output and required context; answer promptly |
+ | Browse/Home | Make the situation understandable without channel history | Show concrete stakes; pay off the visual promise immediately |
+ | Suggested beside a related video | Offer the next useful question in that viewing context | Make the connection clear without copying the adjacent creator |
+ | Existing audience | Name the development they have reason to care about | Supply enough context for a newcomer; avoid unexplained episode lore |
- The measured retention curve dictates structure: the steepest cliff is between seconds 10 and 20, 55%+ are gone by 60 seconds, and a clear value proposition in the first 15 seconds measures +18% retention at the one-minute mark.
+ These packaging choices are craft hypotheses, not traffic-source ranking formulas (directional). Front-load the essential promise and preview truncation on the intended screens. Don't force a fixed character band (directional).
- - 0–5s: pattern interrupt — cold-open on the most interesting frame/claim of the whole video. No branded intros, no "welcome back to the channel" (slow intros cost casual audiences ~60% of viewers in 30 seconds).
- - 5–15s: the specific promise — what the viewer gets and why it's credible ("I ran all seven, three broke, one 10x'd").
- - 15–30s: commitment hook — the roadmap or the stakes that make leaving feel like a loss.
- - Then re-hook every 30–45 seconds: new question, tonal shift, visual change, mini-payoff. Plant one deliberately at 25–35s where the post-hook slump hits. Videos holding >65% past minute one measure 58% higher average view duration for the rest.
- - Match structure to audience mode: casual/entertainment audiences need faster cuts and earlier payoffs than dedicated-learner audiences — a measured 35% of channels use the wrong structure for their audience type.
- - Bridge, don't reset: the classic failure is a strong hook followed by "okay so first, some background" — the energy cliff shows up in every retention graph.
+ Choose a readable thumbnail concept that complements the title. Use the fewest words needed, including none; a relevant natural expression is optional (directional). The breakout-thumbnail sample included text-free images and rarely used exaggerated expressions (measured, vidIQ thumbnails, n=500 thumbnails across 30 niches, 2026-07). Preview at small size and against light and dark interfaces (directional).
- ### Length, chapters, and the session
+ Where available, native A/B testing supports up to three titles, thumbnails, or combinations. Results use watch-time share and the labels “Winner,” “Performed Same,” and “Inconclusive” (official, YouTube A/B testing, 2026-09). Keep variants honest and meaningfully different; don't declare victory from a tiny CTR change or stop a test to manufacture a winner (directional).
- - No universal ideal length: retention peaks at 5–10 minutes in the broadest measured dataset (31.5%), and 8+ minutes unlocks mid-roll ads — a monetization threshold, not an algorithm one. The rumored "4-minute dead zone" has no evidence; a dense 6-minute video at 80% retention beats a padded 20-minute one at 30%.
- - Long videos (10min+) show a secondary exodus around the 55–65% mark — plant your strongest mid-video payoff there.
- - Chapters help navigation, surface in Google results, and matter most on 30min+ content; keyword the chapter names.
- - End screens and playlists feed session-continuation signals — always give the finished viewer a next step from your own catalog (linked series outperform orphan uploads).
- - Descriptions: first two lines carry the search keywords and the reason to click "more"; the transcript is indexed, so say the key terms out loud too.
+ ### Script anatomy and publishing package
- ### Shorts — different game, different economics
+ Cold-open on the promised task or evidence. Explain only the context needed for the next action. Bridge from the hook directly into the demonstration; replace a background reset with context over relevant footage. Change visuals or introduce a new payoff when the subject needs it, then inspect the resulting retention curve (directional).
- - The Shorts feed's first gate is Viewed vs Swiped Away (official Studio metric): the first frame IS the thumbnail. Healthy swipe-away runs 10–30%; over 40% means the packaging or audience match failed (directional benchmarks).
- - Length: sub-60s is the proven zone — measured analyses of 35B views found 13s and 50–60s both perform (bimodal); 3-minute Shorts (allowed since Oct 2024) remain unproven. Loop endings inflate percentage-viewed above 100%, which the feed reads well.
- - Economics honestly: Shorts median RPM ~$0.05 vs long-form ~$2.50 — a million Shorts views ≈ $50. The Mohan "parity" quote (May 2025) was revenue per WATCH-HOUR, not per view; both facts are true. Shorts are a discovery and top-of-funnel tool, not the business.
- - The Shorts→long-form bridge is not automatic: Shorts-acquired subscribers convert to long-form at measurably lower rates — use the persistent related-video link, explicit CTAs, and make Shorts that trailer your long-form pillar.
- - Official: Shorts don't hurt long-form ranking; measured counterpoint: large channels saw long-form view declines after adopting Shorts (n=250, significant for 5M+ subs). Keep formats strategically separate; judge each on its own funnel.
+ Deliver a package containing title options and their distinct promises, thumbnail asset brief, spoken script with separate visual directions, description, caption/subtitle copy, and the intended next step. Include a pinned-comment draft, optional channel-post teaser, chapter labels, end-screen cue, and reply plan where available (directional).
- ### Cadence — the honest three-way evidence
+ Use this description anatomy as a template (directional):
- Official: upload frequency is NOT a ranking factor, no penalty, no magic cadence. Measured correlations: channels posting 12+/month grew views ~4x faster than <1/month (vidIQ, n=10.2M channels — correlation, explicitly not causation), while Metricool (n=800K videos) finds 2–4 long-form/week is where the benefit caps. Synthesis: consistency builds audience habit and portfolio surface; volume that costs quality backfires. Pick the maximum cadence at which every upload clears your packaging bar.
+ | Position | Content |
+ |---|---|
+ | Opening | Exact problem and what the viewer will see; put material limitations near the claim |
+ | Action | Plain-language CTA and verified destination; state affiliation beside the relevant promotion |
+ | Navigation | Timestamps from the final edit with descriptive chapter names |
+ | Evidence | Source links, conditions, corrections, credits and relevant disclosures |
+ | Optional metadata | Relevant hashtags only; preview their rendered placement rather than promising where they appear |
- ### What Dies on YouTube
+ Make the pinned comment useful on its own: clarify a limitation, answer the likely setup question, or explain the next step. Use descriptive tags only where useful; don't keyword-stuff descriptions or promise transcript-indexing gains. Correct captions for names and technical terms. Reserve the final useful beat for the next-video invitation and check the actual end-screen timing allowed by the editor (directional).
- - Egregious clickbait — removal-eligible since Dec 2024 (promise not delivered in the video).
- - Mass-produced/templated content — "inauthentic content" monetization policy (July 2025): near-identical slideshows, generic-template AI output without original insight.
- - AI personas on health/legal/finance/politics — flat monetization ban.
- - Reused content without transformation — clips with no commentary/narrative, pitch-shifted songs, downloads with cosmetic edits.
- - Undisclosed realistic synthetic media — mandatory disclosure since May 2025; YouTube can apply the label itself.
- - AI-slop production values — measured: heavily AI-generated videos show ~70% lower retention; monotonous AI narration loses 35% of viewers within 45 seconds. AI as a tool is fine and monetizable; AI as the product dies on satisfaction.
- - Over-produced intros and channel-branding sequences — the retention data's most consistent killer.
+ ## Launch and proof posts
- ## Pre-publish Checklist
+ Get the audience and buying situation, promise, available proof with source, desired action, destination link, campaign stage, and disclosure obligations before drafting. Include product availability, price conditions when supplied, author role, and who can answer questions. “No CTA” is a valid deliberate choice.
- - [ ] Packaging decided before scripting; title + thumbnail work as one unit and the video keeps the promise
- - [ ] Title ≤60 chars, keyword + hook in the first 40, no undelivered claims
- - [ ] Thumbnail: one idea, ≤5 words, survives mobile size, contrasts with the UI
- - [ ] Cold open in 0–5s; value proposition by 15s; re-hooks every 30–45s; no branded intro
- - [ ] Structure matches audience mode (casual vs learner pacing)
- - [ ] Length is what the content needs — 8min+ only if it stays dense (mid-roll is a bonus, not a target)
- - [ ] Strongest mid-payoff planted at the 55–65% position on 10min+ videos
- - [ ] Description front-loads keywords; chapters named with search terms; end screen links your next video
- - [ ] Shorts: first frame stops the swipe, sub-60s default, loop considered, long-form bridge CTA present
- - [ ] Realistic synthetic content disclosed; nothing template-mass-produced
- - [ ] Test & Compare running on high-stakes packaging; judged on the metric it actually optimizes
+ Use task-complete length bands, not invented minute targets (directional):
+ | Shape | Native anatomy | Length band |
+ |---|---|---|
+ | Launch day | Recognizable problem → working product → who can use it now → limitation → action | Compact demo; extend for necessary setup |
+ | Demo or artifact | Show output → reproduce the decisive steps → inspect the result | Short for an isolated action; walkthrough for a full workflow |
+ | Customer proof | Baseline and conditions → intervention → bounded outcome → what remains unresolved | Enough room for the evidence and exclusions |
+ | Founder decision | Observed constraint → decision → visible artifact → cost of the choice | Brief update or extended explanation when tradeoffs need it |
+ | Objection answer | State the actual objection → show the relevant test → say who should decline | Complete answer without unrelated feature tour |
+ | Recap or lessons | Revisit the original promise → show what happened → correct assumptions → next useful step | Compact synthesis supported by source material |
+
+ Apply the strip-test: with the product name removed, the upload should still teach a useful task or show meaningful evidence (directional). For B2B, start with actual support questions and buyer-intent searches; selected founder cases support testing narrow tutorials, without proving a universal conversion formula (directional; SellOnTube).
+
+ Route long-form CTAs through the description and an available pinned comment; for Shorts, check whether the account offers a related-video or profile route and verify the destination from the viewer's interface. Don't rely on typed URL text being clickable. Use a relevant next-video or series path when further evaluation is needed (directional). Keep source, medium and campaign naming consistent; distinguish placements with `utm_content` (official, Google Analytics URL builder, 2026-09).
+
+ For eligible U.S. creators, Amazon products can be tagged in Shorts, long-form and live streams through Shopping (official, YouTube Amazon affiliate announcement, 2026-08). Disclose the commercial relationship and check account eligibility before writing a native-shopping CTA (directional).
+
+ Seed through relevant creator collaborations and voluntary, clearly affiliated employee participation. Give collaborators the outcome and proof constraints while preserving their voice; don't script fake customer comments or organize engagement exchanges (directional). Repetitive promotional comments and automated minimally changed uploads can trigger spam enforcement; genuine test variations are distinguished from flooding (official, YouTube Spam Policy, 2026-09).
+
+ Use this illustrative launch-week schedule only as a planning example, adjusting to proof readiness and staffing (directional):
+
+ | Relative day, illustrative | YouTube asset | Reply plan | Measure |
+ |---|---|---|---|
+ | T−7 | Channel-post poll or founder constraint update | Collect real objections | Relevant questions and audience fit |
+ | T−3 | Self-contained demo excerpt | Answer prerequisites; verify next-video path | Chose-to-view report and substantive comments |
+ | T0 | Launch walkthrough; Premiere only if staffed | Cover the first hour and following hours; correct broken paths | Watch time, retention at proof, traffic source, buyer questions |
+ | T+1 to T+3 | Objection answer or eligible live demonstration | Resolve unanswered setup questions | Useful follow-up viewing and resolved objections |
+ | T+7 | Bounded proof or recap; use a lessons update if outcomes aren't ready | Add corrections and revisit open questions | Continued viewing, attributable visits and qualified actions |
+
+ The staffing window is a craft choice. Metricool found 83% of interactions in the first ten days (measured, Metricool press release, n=799,718 videos, 2026-08). Keep coverage beyond launch day and preserve evergreen search usefulness (directional). Report destination conversions separately from YouTube-native metrics; don't credit a whole campaign's results to YouTube (directional).
+
+ Use founder delivery for firsthand decisions and brand-channel presentation for durable product instruction. Choose by documented voice and continuity of ownership; no verified founder-versus-brand distribution advantage is established here (directional).
+
+ ## Voice on this platform
+
+ Preserve the author's register, including natural contractions and fragments. Don't manufacture typos, fake edit notes, lowercase camouflage, or dropped articles. Use firsthand claims only when source records support that speaker's experience.
+
+ Write lines the speaker can say while doing the action. Read the script aloud, separate breaths at changes of thought, and replace abstract narration with concrete references to the visible screen or object. Keep useful hesitation only when it occurs naturally; don't write fake thinking pauses or inject filler (directional).
+
+ Remove generic spoken scaffolding such as “In this video we'll,” “without further ado,” and “let's dive in” when it delays the subject. End on the result, limitation, or useful invitation; don't append a recap followed by a subscribe request by habit (directional).
+
+ Apply the AI-tell pass to titles, narration, descriptions, and comments. Remove formulaic contrast frames, padded triads, staccato stacks, empty suspense pivots, needless emphasis words, and tidy moral endings (directional; Aborn, Cox, Gichigi). Also remove rhetorical-question openers, “nobody talks about” framing, miracle-fix stories, engagement-bait closers, hashtag stacks, and emoji bullets (directional). Review em-dash density for readability; retain useful punctuation consistent with the author without enforcing a quota (directional; Cox).
+
+ These are editing judgments, not authorship detectors or measured YouTube penalties. Use a fluent reviewer for localized speech and idioms; conversational-context research motivates this check but does not establish a YouTube engagement gain (directional; MIDI).
+
+ ## Cadence and engagement
+
+ Choose a sustainable publishing pace that leaves time for evidence gathering and replies. Test modest Shorts support for a deeper video before increasing volume; the observed association with long-form views is correlational (measured, Metricool Shorts, n=799,718 videos, 2026-08). Use the evidence reference before quoting frequency benchmarks.
+
+ Assign a responder for launch hours and later coverage, including audience-active evenings or weekends when needed. Answer the actual question in ordinary prose; distinguish a confirmed limitation from a workaround. Remove scam links and abuse while preserving fair criticism (directional). Cross-platform moderation and reply studies motivate staffing, but don't establish a YouTube-specific reply uplift; see the launch reference.
+
+ ## What gets suppressed
+
+ Separate removal, monetization eligibility, and editorial weakness. The egregious-clickbait announcement described undelivered packaging promises and removal initially without strikes, with rollout starting in India (official, Google India, 2024-12). Don't extend that announcement's geographic scope.
+
+ Repetitive or mass-produced content was already ineligible for monetization when “inauthentic content” terminology was clarified; reused-content policy was unchanged (official, YouTube monetization policies, 2025-07). Avoid cosmetic remixes of others' work; add substantive original explanation and secure necessary rights (directional).
+
+ Disclose realistic generated or meaningfully altered media. Routine assistance with scripts, titles or captions alone is exempt; disclosure alone does not limit audience or monetization eligibility (official, YouTube AI disclosure, 2026-09). Use the delivery reference for automatic labels and correction controls. Don't invent an AI-narration retention penalty or a blanket AI-persona monetization ban.
+
## Examples
- ### Example 1: Packaging-first applied
+ These are illustrative drafting examples, not reports of real businesses. Brackets mark missing source material; such drafts are not publishable until filled and checked. The bad versions demonstrate packaging defects, not suggested copy.
- Idea as filmed-first: "My review of the new Claude coding features" → generic, packaging ceiling low. Packaging-first pass: thumbnail = split screen, red "$4,100" over one half, "$12" over the other; title = "I ran the same startup on Claude and on interns for a month". Same underlying content, but now there's a claim to deliver, stakes in the thumbnail, a comparison structure — and the script gets written to pay off that exact promise.
+ ### Developer tool: recorded diagnostic workflow
- ### Example 2: Retention surgery on a real curve
+ Bad title: “This tool fixes every broken build.”
+ Good title: “Find a missing environment variable with [tool].”
+ Opening: “This build fails before the app starts. I'll show the missing variable in the log, then rerun it with [documented configuration]. This recording covers [environment]; other failures need their own diagnosis.”
+ Thumbnail: the relevant log line, with secrets removed.
+ Description: “Reproduce this failure using [fixture link]. Setup requirements: [verified requirements]. I maintain [tool].”
+ Why it works: packaging promises the specific action the footage can show.
+ Why it works: provenance and the environment limitation prevent a miracle-fix claim.
- Analytics show 62% at 0:30 (fine), cliff to 31% by 1:10. Diagnosis: the hook promised the result, then minute one delivered channel branding + background. Fix: cold-open on the result footage, compress background to one sentence over b-roll at 0:20, move the first payoff to 0:45, add a re-hook question at 1:00. The promise-to-payoff gap, not the content, was the leak.
+ ### B2B SaaS: customer proof
+ Bad description: “Teams everywhere save hours with our platform.”
+ Good title: “How [customer] handles duplicate renewal records.”
+ Opening: “[Customer] supplied this export from [period]. The review queue changed from [before] to [after] under [conditions]. These records still needed a person's decision.”
+ Description: “See the matching rules and exclusions in [approved case link]. Try the workflow with [destination]. [Affiliation disclosure].”
+ Pinned comment: “The comparison excludes [excluded work]. The video shows why those records stayed in manual review.”
+ Why it works: the proof shape ties the outcome to its denominator and conditions.
+ Why it works: the CTA offers evaluation without turning the case into a general guarantee.
+
+ ### Consumer creator: product demonstration
+
+ Bad title: “The bag everyone needs.”
+ Good title: “Packing [bag] around a rigid lunchbox.”
+ Opening: “The lunchbox reaches this seam. I'll pack the supplied kit around it and show what doesn't fit. Durability needs a separate test.”
+ Description: “Contents shown: [verified packing list]. [Gifted or sponsored disclosure]. Product details: [destination].”
+ Thumbnail: the actual bag opening and lunchbox, without an exaggerated reaction.
+ Why it works: a visible physical constraint gives the viewer a concrete buying question.
+ Why it works: the test's limitation and commercial disclosure remain beside the claim.
+
+ ### Local service: objection answer
+
+ Bad title: “A perfect garden after a quick visit.”
+ Good title: “What [service] can prune without entering the side passage.”
+ Opening: “This gate blocks access to the back hedge. The site survey shows which branches are reachable from here and which need another access arrangement.”
+ Description: “This example covers [approved site conditions]. Request a site assessment: [booking link]. A quote requires access confirmation.”
+ Follow-up reply: “The video doesn't establish access for your property. Send the site details through the assessment form so the team can check.”
+ Why it works: the objection answer teaches a bounded service decision.
+ Why it works: the booking path preserves the condition instead of promising an unseen outcome.
+
+ ## Checklist
+
+ - [ ] Hook and first line deliver the packaging promise; the upload holds a single central idea.
+ - [ ] Format classification and current asset limits checked; thumbnail and opening previewed on intended surfaces.
+ - [ ] Description, verified CTA/link path, pinned comment and chapter labels prepared where applicable.
+ - [ ] Caption/subtitle copy checked; asset brief includes visual descriptions and alt text where supported; end-screen timing checked in the editor.
+ - [ ] Every specific is supplied or placeholder-marked; unresolved factual placeholders block publication.
+ - [ ] AI-tell pass completed on the whole package; script read aloud and matched to author samples.
+ - [ ] Affiliation, sponsorship/paid-promotion controls and required synthetic-media labels checked.
+ - [ ] Optional channel-post teaser and first-hours reply plan ready; moderation and later follow-up assigned.
+ - [ ] Metric definitions and comparison cohorts recorded; test conclusions use the actual Studio result.
+
## References
- - Official mechanics: YouTube Creator Liaison / Todd Beaupré interviews 2024–2025 ("algorithm follows the audience", per-video ranking, satisfaction weighting, frequency-not-a-factor); Creator Insider (Shorts Viewed vs Swiped Away).
- - Policies: egregious clickbait enforcement (Google blog, Dec 2024), inauthentic-content monetization + AI-persona ban (July 2025), synthetic-content disclosure (mandatory May 2025).
- - Measured: Retention Rabbit 2025 (n=10K+ videos — retention curve figures), vidIQ frequency study 2026 (n=10.2M channels, correlational), Metricool YouTube 2026 (n=800K videos), AIR Media-Tech RPM data (n=274 channels), Nate Black Shorts analysis (35B views), Inflow (n=5,400 Shorts). Thumbnail percentages circulating online are largely unsourced — treated here as heuristics only.
- - Practitioner: Paddy Galloway (Colin & Samir interview) — time-allocation split, packaging quotes.
- - Re-validate periodically: Test & Compare's winning metric, 3-minute Shorts distribution, clickbait enforcement scope, Shorts RPM by region.
- - Companion skills: `content-voice` (scripts that don't sound generated), `trend-youtube` for harvesting what's working now.
+ Dates on undated Help pages denote validation month. Benchmarks and case-study limitations are mapped to actions in the linked references.
+
+ - [YouTube A/B testing](https://support.google.com/youtube/answer/16391400?hl=en), undated; checked 2026-09.
+ - [YouTube Shorts analytics](https://support.google.com/youtube/answer/12942217?co=YOUTUBE._YTVideoType%3Dshorts&hl=en), undated; checked 2026-09.
+ - [Shorts experience update](https://blog.youtube/news-and-events/youtube-shorts-experience-updates-features/), 2026-06-25.
+ - [AI disclosure](https://support.google.com/youtube/answer/14328491?hl=en), undated; checked 2026-09.
+ - [Monetization policies](https://support.google.com/youtube/answer/1311392?hl=en), clarification 2025-07-15.
+ - [Spam Policy](https://support.google.com/youtube/answer/2801973?hl=en), undated; checked 2026-09.
+ - [Clickbait announcement](https://blog.google/intl/en-in/products/platforms/strengthening-enforcement-against-egregious-clickbait-on-youtube/), 2024-12-18.
+ - [Evidence sources](reference/evidence.md#references), [delivery sources](reference/delivery.md#references), [launch and voice sources](reference/launch.md#references), dated individually.
+
+ Re-validate when:
+ - Studio metrics, player controls, test outcomes, or upload limits change.
+ - Policy wording, geographic availability, monetization rules, or disclosure controls change.
+ - New vendor reports revise the sampled period or methodology.
+
+ Validated: 2026-09