# Blog Post to Audio Script Template

Use this template when converting written blog posts to audio-ready scripts for ElevenLabs.

---

## Pre-Conversion Checklist

- [ ] Remove all markdown formatting (links, bold, italic)
- [ ] Spell out abbreviations on first use
- [ ] Convert numbers and currencies to spoken form
- [ ] Remove code blocks (or replace with "[code example in the article]")
- [ ] Add audio tags for emotional beats
- [ ] Break long paragraphs into shorter chunks
- [ ] Add natural pauses at section transitions

---

## Script Structure

### Opening (Hook + Introduction)

```
[conversational] Today I want to talk about [TOPIC].

[matter-of-fact] Here's the thing most people get wrong about this...
```

**Tips:**
- Skip "In this article" or "Welcome to my blog"
- Start with a hook or direct statement
- Set the tone immediately

### Main Content Sections

```
[thoughtful] Let's start with the basics.

[CONTENT]

[short pause]

Moving on to the next point...
```

**Tips:**
- Add `[short pause]` between major sections
- Use `[thoughtful]` for explanations
- Use `[excited]` for wins/discoveries
- Use `[matter-of-fact]` for technical details

### Lists and Bullet Points

**Written version:**
```
Here's what you need:
- A VPS with root access
- At least 1GB RAM
- 20 minutes of time
```

**Audio version:**
```
Here's what you need. First, a V P S with root access. Second, at least one gigabyte of RAM. And third, about twenty minutes of your time.
```

**Tips:**
- Convert bullets to "First... Second... Third..." or "One... Two... Three..."
- Or use "The first thing is... Next... Finally..."
- Don't say "bullet point" or "dash"

### Code Examples

**Written version:**
```
Run this command:
`sudo apt update`
```

**Audio version:**
```
Run sudo apt update. That's S U D O space A P T space update.
```

**Tips:**
- For short commands, spell out if pronunciation is tricky
- For long code blocks: "There's a code example in the article. I'll summarize what it does."
- Never try to read entire code blocks aloud

### Technical Terms

**Written version:**
```
Your TTFB should be under 200ms.
```

**Audio version:**
```
Your time to first byte, or T T F B, should be under two hundred milliseconds.
```

**Tips:**
- Spell out acronym on first use
- Use the spelled version after that
- Convert "ms" to "milliseconds", "KB" to "kilobytes", etc.

### Opinions and Personal Experience

```
[honest] I've tested this on twelve sites over eight months. Here's what I found.

[sighs] The documentation is sparse. If you need hand-holding, look elsewhere.

[satisfied] But the speed improvements are worth the learning curve.
```

**Tips:**
- Add emotion tags for personal takes
- `[honest]` for real talk
- `[sighs]` for frustrations
- `[satisfied]` or `[happy]` for wins

### Section Transitions

```
[short pause]

Now let's talk about [NEXT TOPIC].

[pause]

Here's where it gets interesting...
```

**Tips:**
- Always pause between major sections
- Use transitional phrases: "Now...", "Moving on...", "Here's the thing..."
- Don't say "In the next section" or reference the written format

### Closing

```
[thoughtful] So here's what I want you to take away from this.

[MAIN TAKEAWAY]

[conversational] If you have questions, drop them in the comments. I read every one.

[warm] Thanks for listening.
```

**Tips:**
- Summarize the key point
- Include a soft call-to-action
- Keep it brief
- Don't say "subscribe" or platform-specific CTAs unless intended

---

## Find and Replace Patterns

Run these replacements before generating audio:

| Find | Replace With |
|------|--------------|
| `**text**` | `text` |
| `*text*` | `text` |
| `` `code` `` | `code` |
| `[text](url)` | `text` |
| `###` | (remove) |
| `##` | (remove) |
| `#` | (remove) |
| `---` | `[pause]` |
| `$100` | `one hundred dollars` |
| `1,000` | `one thousand` |
| `%` | ` percent` |
| `e.g.` | `for example` |
| `i.e.` | `that is` |
| `etc.` | `and so on` |
| `&` | `and` |
| `w/` | `with` |
| `w/o` | `without` |

---

## Example Conversion

### Original Blog Post

```markdown
# Why I Stopped Using Managed WordPress Hosting

I spent $3,240 on managed WordPress hosting last year. Across client sites and my own projects, that was the total for **WP Engine** and **Kinsta** combined.

This year? $540. For *better* performance.

## The Breaking Point

Here's what I was getting for $270/month:

- Automatic backups
- Automatic updates  
- Security hardening
- Speed optimization
- Support

Sounds great. Until you realize what you're *actually* paying for.
```

### Converted Audio Script

```
[conversational] Why I stopped using managed WordPress hosting.

[matter-of-fact] I spent three thousand two hundred forty dollars on managed WordPress hosting last year. Across client sites and my own projects, that was the total for W P Engine and Kinsta combined.

[surprised] This year? Five hundred forty dollars. For better performance.

[short pause]

[thoughtful] The breaking point.

Here's what I was getting for two hundred seventy dollars per month. First, automatic backups. Second, automatic updates. Third, security hardening. Fourth, speed optimization. And fifth, support.

[skeptical] Sounds great. Until you realize what you're actually paying for.
```

---

## Voice Settings for Blog Content

| Content Type | Voice Character | Stability | Speed |
|--------------|-----------------|-----------|-------|
| Tutorial | Clear, patient | 0.6 | 1.0 |
| Opinion piece | Warm, opinionated | 0.5 | 1.0 |
| Review | Thoughtful, honest | 0.5 | 1.0 |
| News/Update | Professional, energetic | 0.5 | 1.05 |
| Story/Case study | Engaging, varied | 0.4 | 0.95 |

---

## Quality Checklist (Post-Conversion)

- [ ] No markdown symbols remain
- [ ] All numbers spelled out appropriately
- [ ] Acronyms spelled out on first use
- [ ] Audio tags placed at emotional beats
- [ ] Pauses added between sections
- [ ] Code blocks handled (summarized or noted)
- [ ] Sounds natural when read aloud
- [ ] Approximate length under 15 minutes per segment
