Recap (pending)

Platform: All platforms Type: Episode / Movie Recap

⬇ Download this section

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 red 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.

Headline (H1)

(REQUIRED)

Primary formula: [Show/Movie Name] Recap: [Number] Biggest Moments From [Episode Title]
Alternate formula (UsW only): [Show/Movie Name] Ending Explained

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.

SEO Title

(REQUIRED)

Dek

(REQUIRED)

Meta Description

(REQUIRED)

Focus Keyphrase

(REQUIRED)

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

</span>

Tone

(REQUIRED)

Entertaining and opinionated, but still informative. 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.

Word Count

(REQUIRED)

Target: 400–800 words. 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.

Article Structure

(REQUIRED)

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.

[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

Formatting Rules

(REQUIRED)

(REQUIRED)

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

Link to:

Hero Image

(REQUIRED)

General Guidelines do not specify image requirements. The following specs are mandatory for this format.

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>

URL Structure

(REQUIRED)

General Guidelines do not prescribe URL patterns. The following is mandatory for this format.

Tags

(REQUIRED)

General Guidelines do not specify tags. The following are mandatory for this format.

What to Avoid

Prohibited Reason
Pure plot summary with no analysis or commentary Format requirement—recaps must include opinion, analysis, and forward-looking commentary
No link to the previous episode’s recap Format-specific internal linking requirement—always link one episode back
Show or movie name not front-loaded in the headline Format requirement—the show/movie name must open the headline
Using the “Ending Explained” formula outside of UsW Alternate formula is UsW-specific—confirm before using on other outlets
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

Pre-Publish Checklist