"Link in bio, colon, h-t-t-p-s." That is what a text-to-speech engine says when a newsletter essay goes in with its footer still attached. Pasting the whole document is easier than trimming it, so the footer rides along, and the engine does the only job it has: it reads the characters.

A clean script is text you would speak to one person. Everything else is furniture. Text-to-speech does not know which lines are furniture unless you remove them or mark a pause on purpose. These edits are pretty dull. They save more regenerations than a new voice does.

Read it aloud before you generate it

Sit with the script and read one section out loud, at the pace you want the piece to have. Anywhere you stumble, the model will invent a recovery. Anywhere you run out of air, the model will rush or flatten. Change the sentence until you can say it in one breath or in two breaths with a period between them.

Cut filler you would not say. "In this article we will explore" is a heading pretending to be a sentence. Start with the point. If you need a roadmap, say it in one line: "Three edits, then a listening pass."

A common worry is that your prose style is the product and simplifying it will make the piece dull. Clarity is not the same as a smaller vocabulary. Keep the unusual word if you would say it. Lose the clause that exists only to look finished on a page.

Hide the notes

Anything in brackets, parentheses, or all caps is a risk. A parenthetical aside sometimes reads well. A parenthetical production note never does. Delete "(smile)" and "(cut to demo)." If you want a softer delivery, use a tag the studio actually keeps, such as [soft], and know that the tag itself should not be a sentence the listener hears as words. Supported expression tags stay in the text that goes to synthesis. An unclosed bracket is worse: Narration QA, on the Pro plan, flags an unclosed square bracket because the engine may read it aloud.

All caps is emphasis the engine may overdo. A line of capitals longer than a short label is a shout. Rewrite it in normal case. If you truly want stress on one word, use [emphasis] beside that word rather than capitalizing a whole sentence. Narration QA notes all-caps lines that may be over-emphasized. The note is a review aid, not a promise that the audio is fine.

Headings are optional speech. If the heading is a real title the listener should hear, write it as a sentence or leave it as a short title on its own line and accept that it will be announced. If the heading is only for you, remove it from the spoken file.

Abbreviations, symbols, and lists

Decide the spoken form of anything that is not a plain word. "Dr." can be "doctor" or the letters D-R, and the wrong choice is obvious in a medical interview. "St." can be "street" or "saint." Write the words you want, or store a pronunciation rule if the short form has to stay on the page for readers. The pronunciation list is the place for rules you will reuse. For a one-off script, spelling the word out is simpler.

Symbols need words. An ampersand in a title is often "and." A slash can be "and," "or," or "per," and you have to pick. A percent sign should usually be the word "percent" next to a number you have already decided how to say.

Lists need a lead-in. A naked stack of product names sounds like a receipt. Write "The kit includes three things." Then the three things as separate sentences. The listener gets a count and a pause. A bulleted list of sentence fragments often becomes one breathless line.

One idea per sentence

Long sentences are where pace collapses. A sentence that runs past a few hundred characters may be flagged in Narration QA as a pacing risk, with a suggestion to split it or add a short pause. You do not need the report to use the rule. If a sentence has more than one "which" or "that," split it.

Keep contrast in separate sentences when the contrast is the point. "Use the WAV for the edit and the MP3 for the upload" is clearer as two sentences if the listener has to act on both.

Ellipses are pauses, and a page full of them sounds hesitant. Use a period or a real pause tag when you want air. A handful of ellipses in dialogue is fine. A dozen in one short script is a wobble. The Pro narration report notes dense ellipses for that reason.

A before-and-after

Say a creator's draft contains this sentence: "OK so what you wanna do (see fig. 2) is click the EXPORT btn & wait 10s before you upload @ your site/blog." A clean read is: "Click Export. Wait ten seconds. Then upload the file to your site." The figure note moves to the shot list. "EXPORT" loses the shout. The abbreviation and the at-sign become words. Nothing clever was added. The listener can now do the step.

Run this pass on the spoken file only. Leave your outline alone so you still have a map. When the spoken file is clean, generate a single section and listen for leftovers: a heading you meant to cut, a "dot" "com" you meant to hide, a list that still sounds like a dump. Fix the text, not the voice, and generate that section again.

More of the number-and-date decisions live in the numbers guide. The studio's preflight scan can flag numbers, abbreviations, names, punctuation, currency, and dates before you generate. It suggests a spoken replacement. You still choose the reading. It does not rewrite your judgment, and it does not approve the file for a platform.

Frequently Asked Questions

Q: Should I leave markdown in the script? A: Only if you want the punctuation around it to influence the read. Asterisks, hashes, and link syntax are not speech. Paste plain sentences into the chapter or the spoken script.

Q: Will a speech engine skip my headings? A: Do not count on it. If the heading is in the text, assume it will be spoken. Remove headings you do not want announced.

Q: Are parentheses always bad? A: No. A short spoken aside can live in parentheses or between commas. A stage direction cannot. If you would not say the words to a listener, delete them.

Q: How do I emphasize one word without shouting the line? A: Rewrite the sentence so the word lands at the end, or place an [emphasis] tag at that word. Do not capitalize the whole line.

A bad take nearly always traces back to specific characters in the file. Find them before you blame the voice. It is usually a five-minute fix.