Skip to content
Community content. Review instructions before giving them to an AI agent — treat modules like open-source code.

YouTube Script Rules

Rules for writing YouTube video scripts that hold retention: the first 15 seconds, open loops, chapter structure, writing for the ear, retention edits, and CTA placement.

Mby @markdownersPublished August 21, 2026 · ~4 min read

0 downloads · Used by 0 stacks

YouTube's retention graph is the only judge that matters — a script's job is to keep the line flat, not to read well on paper. Every rule below exists to stop a viewer's thumb from moving to the next thumbnail.

The first 15 seconds

  • State the payoff of the video in the first line or two — what the viewer will have, know, or be able to do by the end — before any branded intro, channel greeting, or "in this video I'm going to show you." The viewer already clicked; don't make them re-decide.
  • Cut the branded intro entirely, or move it to after the hook has landed. A 5-second animated logo before any content is a 5-second window for the viewer to leave.
  • Open with the most visually or narratively interesting moment available, even if it's a clip from later in the video, then cut back to set up how you got there — a cold open outperforms a chronological start almost every time.

Open loops and payoff discipline

  • Plant a specific open loop in the first 30 seconds ("by the end of this you'll see why the second method is actually worse") and don't resolve it until the payoff actually lands — the loop is what keeps someone watching through a slower middle section.
  • Every open loop opened must be closed. A script that teases something and never delivers it trains viewers to stop trusting the channel's hooks, which erodes retention on future videos too.
  • Don't stack more than 2-3 open loops at once — a script juggling five unresolved teases reads as manipulative rather than compelling.

Chapter and beat structure

  • Break the script into named beats or chapters before writing prose, each with one job (setup, complication, method, proof, payoff) — a script without a beat map tends to drift and pad.
  • Keep each beat short enough that it earns its place; if a beat doesn't move the argument or story forward, cut it rather than smoothing it into the surrounding text.
  • Place a beat change roughly every 30-90 seconds for anything longer than 5 minutes — the visual and topical shift is itself a retention tool, independent of content quality.

Writing for the ear, not the eye

  • Use short sentences and simple clause structure — a sentence a viewer can follow at listening speed, once, with no re-reading available. If a sentence needs a second read to parse on the page, it will lose a listener the first time.
  • Write in spoken rhythm: contractions, direct address ("you'll notice"), and natural pauses baked into punctuation, not the register of an essay.
  • Read every draft aloud before finalizing. Any line that trips the tongue, runs out of breath, or sounds stilted spoken gets rewritten — the read-aloud test catches what silent proofreading misses.

Retention edits marked in script

  • Mark b-roll and cutaway cues inline in the script ([B-ROLL: product close-up]) at the exact line they support, so editing doesn't have to guess where visual variety is needed.
  • Mark pattern interrupts explicitly — a zoom, a sound effect, a cut to a different angle — at points where the audio alone would run flat for more than ~8-10 seconds. Silence on the visual track is where drop-off spikes.
  • Note any place a graphic, on-screen text, or chart should carry information instead of the voiceover repeating it — offloading data to the visual keeps the spoken pace fast.

CTA placement

  • Place the subscribe/notification CTA mid-roll, right after a payoff moment when viewer goodwill peaks, rather than only at the end when a large share of viewers have already left. Mid-roll asks measurably outperform end-roll asks for subscription actions.
  • Keep any CTA to one sentence and tie it to what just happened ("if that trick saved you time, hitting subscribe means you won't miss the next one") rather than a generic ask disconnected from content.
  • Reserve the end-roll for a single next-action pointer (one specific next video, one specific link) — not a repeat of the mid-roll ask.

Title and thumbnail come first

  • Write the title and thumbnail concept before the script, not after — they set the specific promise the video is being clicked for.
  • Every script must visibly deliver the exact promise in the title and thumbnail, in the opening beat. A title/thumbnail that overpromises relative to the script's actual content produces a click without a payoff, which tanks retention regardless of scripting quality elsewhere.
  • If the script can't honor the title's promise as written, fix the title — don't ship a script that quietly underdelivers.

Outro rules

  • Don't fade out on "thanks for watching, see you next time" — that line is the single most common exit cue and hands the viewer a natural stopping point.
  • End by chaining directly into the next video: name a specific related video, show its thumbnail on screen, and give one sentence on why it's the natural next watch.
  • Keep the outro under 10-15 seconds. A long outro is dead time after the payoff has already been delivered, and dead time is where the remaining audience leaves.
Badge

Link back to this module from your own README.

Get it on Markdowners
[![Get it on Markdowners](https://markdowners.com/mdstack-badge.svg)](https://markdowners.com/m/markdowners/youtube-script-rules)

Comments (0)

Sign in to comment. Sign in

No comments yet. Be the first to add one.

Discussions about this module

No discussions about this module yet.

Start a discussion