# Cast Introduction / Update (pending) Platform: All platforms | Type: Cast Introduction, Cast Update > **Where this format overrides General Guidelines:** This format covers two subtypes—Cast Update and Cast Introduction—with separate headline formulas. The focus keyphrase structure departs from General Guidelines' `[Person/Topic] [Does/Is] [Thing]` format. The tone is more specific than universal General Guidelines guidance. This format introduces requirements with no brand-level equivalent: a word count range (400–500 words—a notably tight target), and a UsW-specific option to present content in gallery format or as H2-structured sections. Text in **red** throughout this page marks anything that overrides or goes beyond the General Guidelines. --- ### Purpose Cast Introduction and Cast Update articles inform fans about who is appearing in a show or film—whether for the first time or following changes. Cast news is consistently high-interest for entertainment audiences. - **Cast Update:** Covers changes to an existing cast—actors joining, leaving, or changing their role—with context for why the changes occurred - **Cast Introduction:** Introduces readers to the full cast of a new or upcoming show or film --- ### Headline (H1) **(REQUIRED)** **Cast Update formula:** `[Show/Movie Name] Cast Update: Who's In and Who's Out`
**Cast Introduction formula (UsW alternate):** `Meet the Cast of [Show/Movie Title]: [Name], [Name] and More` - Show or movie name must be front-loaded - Character count: 80–100 characters - Casing varies by publishing destination—adjust per site style guide before publishing > **Optimize before publishing.** Cast news—especially departures or new additions—spikes in search around announcements and premiere dates. Get the H1 and SEO title right before hitting publish. --- ### 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 show or movie name and "cast" carry the most search weight - Must match the H1 in intent—similar but not identical - Must contain a verb --- ### Dek **(REQUIRED)** - Entered as a separate CMS field—do not place inside the article body - Must contain the focus keyphrase - **Cast Update:** should summarize who is in and who is out, and tease the reason if newsworthy - **Cast Introduction:** should introduce the ensemble and tease notable names --- ### Meta Description **(REQUIRED)** - 100–155 characters (approximately 2 sentences) - Must contain the focus keyphrase and relevant proper nouns (show name, key actor names) - Must not repeat the H1 or SEO title verbatim - Functions as a dek—entices clicks, does not merely summarize --- ### Focus Keyphrase **(REQUIRED)** | Subtype | Primary | Secondary (if applicable) | |---|---|---| | Cast Update | `"[Show/Movie Name] cast"` | `"[Actor Name] leaving [Show/Movie Name]"` | | Cast Introduction | `"[Show/Movie Name] cast"` | `"[Show/Movie Name] season [X] cast"` | - Must appear in: H1, SEO title, dek (CMS field), meta description - Should reflect how a fan would search for this news around a premiere, announcement, or departure - Use Google Trends data to validate keyword choices --- ### Tone **(REQUIRED)** Informative and straightforward. Readers want the facts quickly—who is in, who is out, and why. Conversational and human—never stiff or institutional. Do not editorialize on casting decisions beyond what has been publicly stated. --- ### Word Count **(REQUIRED)** Target: 400–500 words. This is a tight target—stay focused. Cover who, what, and why clearly. Do not pad. --- ### Article Structure **(REQUIRED)** The following structure is mandatory for this format. General Guidelines do not prescribe article structure. **Cast Update:** ``` [AI DISCLAIMER—CUE sites only] "This article was created by content specialists using various tools, including AI." [LEDE / INTRO] - State the most significant cast change upfront - Identify the show/movie and the context (season, upcoming release, etc.) [CAST CHANGES—H2 format or gallery (UsW: either is permitted)] For each change: - Clearly state who is joining or leaving and in what role - Provide context: storyline reasons, actor's decision, official statements - Note any replacement casting if applicable [INTERNAL LINKS—embedded throughout] - 3–5 contextual internal links ``` **Cast Introduction:** ``` [AI DISCLAIMER—CUE sites only] "This article was created by content specialists using various tools, including AI." [LEDE / INTRO] - Introduce the show/movie and the significance of the cast - Tease notable names and what makes this ensemble worth paying attention to [CAST MEMBERS—H2 format or gallery (UsW: either is permitted)] For each cast member: - Name and role they play - Brief background (known for, relevant credits) - Any details about their character or the production [INTERNAL LINKS—embedded throughout] - 3–5 contextual internal links ``` --- ### Formatting Rules **(REQUIRED)** - **UsW:** Content may be formatted as a **gallery** (one cast member or change per gallery slide) or as **H2 sections** (one cast member or change per H2)—both are permitted; choose based on the volume of changes and the platform context - For Cast Updates: clearly label each change as "joining," "leaving," or "role change"—do not make the reader infer - Provide context for cast changes—storyline reasons, actor statements, or production decisions where available - Do not editorialize on casting decisions beyond what has been publicly stated - Keep entries concise—each cast member or change should be covered efficiently - Keep paragraphs short for mobile readability --- ### Internal Links **(REQUIRED)** 3–5 contextual internal links per article. See General Guidelines §1.4 for full anchor text rules. Link to: - The show or movie's tag page on the site - The actors' celebrity tag pages—especially for departing or newly joining cast members - Related news articles about the show, season, or actors involved --- ### 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 promotional or production image from the show/film, or a key cast member(s) | | Logos | NOT permitted | | Text overlays | NOT permitted | | Generic stock | NOT permitted | --- ### URL Structure **(REQUIRED)** General Guidelines do not prescribe URL patterns. The following is mandatory for this format. - 4+ keywords, front-loaded with show or movie name - Strip stop words - Keep short and descriptive - Cast Update pattern: `[show-name]-cast-update-[details]` or `[show-name]-cast-whos-in-whos-out` - Cast Introduction pattern: `[show-name]-cast` or `[show-name]-cast-meet-[details]` - Examples: `big-brother-27-cast-revealed-meet-the-new-houseguests`, `marty-supreme-cast-timothee-chalamet-gwyneth-paltrow-and-more` --- ### Tags **(REQUIRED)** General Guidelines do not specify tags. The following are mandatory for this format. - `TH-CSA` - `The Commons` - *(Tags subject to change—check for updates)* --- ### What to Avoid | Prohibited | Reason | |---|---| | Leaving cast change status ambiguous (joining vs. leaving vs. role change) | Format requirement—each change must be clearly labeled | | Cast changes without context | Format requirement—explain why the change occurred where information is available | | Editorializing on casting decisions beyond what has been publicly stated | Tone requirement—informative and straightforward | | Padding to hit word count in a 400–500 word target | Tight format—cover the facts efficiently | | 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 production or cast image | | 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 - 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—cast member names, roles, and change details confirmed accurate - Focus keyphrase in H1, SEO title, dek (CMS), and meta description - H1: 80–100 characters, correct subtype formula applied, 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 - **Cast Update:** each change clearly labeled as joining, leaving, or role change; context provided - **Cast Introduction:** each cast member's name, role, and relevant background included - **UsW:** gallery or H2 format chosen and applied consistently - 3–5 internal links—show/movie tag page, actor tag pages, related news articles - Total word count is 400–500 words - Hero image: 1200px+ wide, 16:9, 300K+ res, production or cast photo, no logos/text/stock - URL: show/movie name front-loaded, subtype-appropriate pattern, stop words stripped - 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