# Recap (pending)

Platform: All platforms | Type: Episode / Movie Recap


> **Where this format overrides General Guidelines:** The headline formula is locked to `[Show/Movie Name] Recap: [Number] Biggest Moments From [Episode Title]`, with a UsW-specific alternate formula (`[Show/Movie Name] Ending Explained`). The focus keyphrase structure departs from General Guidelines' `[Person/Topic] [Does/Is] [Thing]` format. The tone is more specific than the universal General Guidelines guidance. This format introduces requirements with no brand-level equivalent: a word count range (400–800 words), a required plot-plus-analysis structure, and a specific internal linking requirement to the previous episode's recap. Text in <span style="color: #dc2626;">**red**</span> throughout this page marks anything that overrides or goes beyond the General Guidelines.

---

### Purpose

A Recap summarizes and analyzes the key moments of an episode, film, podcast, or book for fans who want to relive or understand what happened. Its purpose is to engage readers who are already invested in the subject and to rank for timely, episodic search queries. Recaps must go beyond plot summary—analysis, commentary, and implications for what comes next are required elements.

---

<!-- AGENT-AUDIENCE: headline -->
### Headline (H1)
**(REQUIRED)**

<span style="color: #dc2626;">**Primary formula:** `[Show/Movie Name] Recap: [Number] Biggest Moments From [Episode Title]`</span><br>
<span style="color: #dc2626;">**Alternate formula (UsW only):** `[Show/Movie Name] Ending Explained`</span>

- <span style="color: #dc2626;">The show or movie name must be front-loaded</span>
- Character count: 80–100 characters
- Casing varies by publishing destination—adjust per site style guide before publishing

> **Optimize before publishing.** Recap articles are time-sensitive—they must go live quickly after an episode airs or a film releases. Get the H1 and SEO title right before hitting publish; re-indexing after a correction delays traffic at peak demand.

---

<!-- AGENT-AUDIENCE: seo -->
### SEO Title
**(REQUIRED)**

- Character count: 50–70 characters—titles under 60 risk missing keywords and clarity; titles over 70 are truncated in search results
- Must contain the focus keyphrase
- Must front-load keywords—the first 8 words carry the most weight
- Must match the H1 in intent—similar but not identical
- Must contain a verb

---

<!-- AGENT-AUDIENCE: seo -->
### Dek
**(REQUIRED)**

- Entered as a separate CMS field—do not place inside the article body
- Must contain the focus keyphrase
- Should tease the most surprising or impactful moment from the episode or film

---

<!-- AGENT-AUDIENCE: seo -->
### Meta Description
**(REQUIRED)**

- 100–155 characters (approximately 2 sentences)
- Must contain the focus keyphrase and relevant proper nouns (show name, episode title, key characters)
- Must not repeat the H1 or SEO title verbatim
- Functions as a dek—entices clicks, does not merely summarize

---

<!-- AGENT-AUDIENCE: seo -->
### Focus Keyphrase
**(REQUIRED)**

<span style="color: #dc2626;">

| Type | Format |
|---|---|
| Primary | `"[Show/Movie Name] recap"` |
| Secondary (if applicable) | `"[Show Name] season [X] episode [Y] recap"` |

</span>

- Must appear in: H1, SEO title, dek (CMS field), meta description
- Should reflect how a viewer would search immediately after watching
- Use Google Trends data to validate keyword choices—search volume for recap queries spikes within hours of airing

---

<!-- AGENT-AUDIENCE: general-style -->
### Tone
**(REQUIRED)**

<span style="color: #dc2626;">Entertaining and opinionated, but still informative.</span> The reader watched the episode—they want a writer who has a point of view, not a neutral plot summary. Conversational and specific—avoid vague generalities. Let the writer's voice come through.

---

<!-- AGENT-AUDIENCE: general-style -->
### Word Count
**(REQUIRED)**

<span style="color: #dc2626;">Target: 400–800 words.</span> Recaps are intentionally focused—readers want the key moments and analysis quickly. Do not pad. If the episode is unusually dense or a season finale warrants more depth, it is acceptable to go longer provided every word earns its place.

---

<!-- AGENT-AUDIENCE: general-style -->
### Article Structure
**(REQUIRED)**

<span style="color: #dc2626;">The following structure is mandatory for this format. General Guidelines do not prescribe article structure. Choose chronological or thematic order—both are permitted depending on the episode's structure.</span>

```
[AI DISCLAIMER—CUE sites only]
"This article was created by content specialists using various tools, including AI."

[LEDE / INTRO]
- Open with the biggest moment, most shocking reveal, or most important development
- Do not open with a definition or a neutral scene-by-scene rundown
- No throat-clearing openers

[BODY—chronological or thematic]
- Summarize and analyze the key events
- Include commentary and opinions—do not just describe what happened
- Highlight the most interesting, surprising, or consequential moments
- Discuss implications for future episodes or sequels

[IMPLICATIONS / WHAT'S NEXT—optional but encouraged]
- Where does this leave the characters or storyline?
- What questions remain unanswered?
- What are you anticipating or dreading next?

[INTERNAL LINKS—embedded throughout body copy]
- 3–5 contextual internal links
- Not to be confused with Related Links, which break up inline copy
```

---

<!-- AGENT-AUDIENCE: general-style -->
### Formatting Rules
**(REQUIRED)**

- <span style="color: #dc2626;">Lead with the most impactful moment—do not open with a neutral scene-by-scene summary</span>
- <span style="color: #dc2626;">Analysis and commentary are required—a purely descriptive plot recap is not sufficient</span>
- <span style="color: #dc2626;">Address implications for future episodes or sequels—forward-looking commentary is a required element</span>
- Bullet points permitted for lists (e.g., "5 Biggest Moments")—not as a substitute for prose analysis
- Keep paragraphs short for mobile readability

---

<!-- AGENT-AUDIENCE: human-only -->
### Internal Links
**(REQUIRED)**

3–5 contextual internal links per article. See General Guidelines §1.4 for full anchor text rules.

<span style="color: #dc2626;">Link to:
- The show or movie's tag page on the site
- The actors' or characters' tag pages
- The **previous episode's recap**—always link back one episode to keep readers in the series
- Previously published articles about key events or storylines mentioned in the recap</span>

---

<!-- AGENT-AUDIENCE: human-only -->
### Hero Image
**(REQUIRED)**

<span style="color: #dc2626;">General Guidelines do not specify image requirements. The following specs are mandatory for this format.</span>

<span style="color: #dc2626;">

| Spec | Requirement |
|---|---|
| Minimum width | 1200px (1600px+ preferred) |
| Aspect ratio | 16:9 |
| Resolution | 300K+ pixels |
| Subject | A still or promo image from the episode or film being recapped |
| Logos | NOT permitted |
| Text overlays | NOT permitted |
| Generic stock | NOT permitted |

</span>

---

<!-- AGENT-AUDIENCE: human-only -->
### URL Structure
**(REQUIRED)**

<span style="color: #dc2626;">General Guidelines do not prescribe URL patterns. The following is mandatory for this format.</span>

- <span style="color: #dc2626;">4+ keywords, front-loaded with show name and episode/season identifiers</span>
- <span style="color: #dc2626;">Strip stop words</span>
- <span style="color: #dc2626;">Keep short and descriptive</span>
- <span style="color: #dc2626;">Pattern: `[show-name]-recap-[episode-keywords]` or `[show-name]-season-[x]-episode-[y]-recap`</span>
- <span style="color: #dc2626;">Examples: `summer-i-turned-pretty-recap-season-3-episode-5`, `1923-s2-e5-recap`, `wednesday-season-2-ending-explained`</span>

---

<!-- AGENT-AUDIENCE: human-only -->
### Tags
**(REQUIRED)**

<span style="color: #dc2626;">General Guidelines do not specify tags. The following are mandatory for this format.</span>

- <span style="color: #dc2626;">`TH-CSA`</span>
- <span style="color: #dc2626;">`The Commons`</span>
- *(Tags subject to change—check for updates)*

---

<!-- AGENT-AUDIENCE: human-only -->
### What to Avoid

| Prohibited | Reason |
|---|---|
| <span style="color: #dc2626;">Pure plot summary with no analysis or commentary</span> | <span style="color: #dc2626;">Format requirement—recaps must include opinion, analysis, and forward-looking commentary</span> |
| <span style="color: #dc2626;">No link to the previous episode's recap</span> | <span style="color: #dc2626;">Format-specific internal linking requirement—always link one episode back</span> |
| <span style="color: #dc2626;">Show or movie name not front-loaded in the headline</span> | <span style="color: #dc2626;">Format requirement—the show/movie name must open the headline</span> |
| <span style="color: #dc2626;">Using the "Ending Explained" formula outside of UsW</span> | <span style="color: #dc2626;">Alternate formula is UsW-specific—confirm before using on other outlets</span> |
| NSFW in any metadata field | Suppresses article in feeds—see General Guidelines §1.3 |
| Clickbait or misleading headlines | Helpful Content algorithm penalty risk—see General Guidelines §1.2 |
| Generic stock images | Format image spec—hero must be a still or promo image from the episode or film |
| Affiliate links (unlabeled) | Google penalty risk—see General Guidelines §1.4 |
| "Click here" or "read more" as anchor text | Poor UX and SEO signal—see General Guidelines §1.4 |
| Publishing without human review | Universal compliance rule—see General Guidelines §1.8 |

---

<!-- AGENT-AUDIENCE: human-only -->
### Pre-Publish Checklist
- AI disclaimer present at top of article (CUE sites only) and "Created With AI" checkbox checked in CUE
- Named human byline—creator/first editor only, no staff byline
- If updated article: byline and dateline handled per General Guidelines §1.5
- All facts verified; character names, episode titles, and plot details confirmed accurate
- Focus keyphrase in H1, SEO title, dek (CMS), and meta description
- H1: 80–100 characters, `[Show/Movie Name] Recap: [Number] Biggest Moments From [Episode Title]` formula (or UsW "Ending Explained" alternate), show/movie name front-loaded
- SEO title: 50–70 characters, matches H1 intent, front-loaded keywords, contains verb
- Meta description: 100–155 characters, no repeated hed language
- Dek entered as CMS field—not placed inside article body; teases biggest moment
- Lede opens with the biggest moment or most impactful development—not a neutral summary
- Analysis and commentary present throughout—not a pure plot summary
- Implications for future episodes or sequels addressed
- 3–5 internal links—show/movie tag page, actor pages, previous episode's recap, related articles
- Total word count is 400–800 words
- Hero image: 1200px+ wide, 16:9, 300K+ res, episode or film still/promo, no logos/text/stock
- URL: `[show-name]-recap-[episode-keywords]` or `[show-name]-season-[x]-episode-[y]-recap` pattern
- Headline casing adjusted for publishing destination
- Tags applied: `TH-CSA` and `The Commons`
- Passes all Google Helpful Content standard questions (General Guidelines §1.7)
- Human review and approval obtained before publishing