# Fan Theory / Fan Question (pending) Platform: All platforms | Type: Fan Theory, Fan Question > **Where this format overrides General Guidelines:** This format covers two subtypes—Fan Theory and Fan Question—each with its own locked headline formula. Both depart from the open headline principles in §1.2. The focus keyphrase structures depart 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 (300–500 words—the shortest of any format), a per-theory/question H2 structure for UsW, and Google Trends keyword requirements for H2 subheadings. Text in **red** throughout this page marks anything that overrides or goes beyond the General Guidelines. --- ### Purpose Fan Theory and Fan Question articles engage the fan community around a show, film, or subject by either exploring a compelling theory or directly answering a question that fans are actively asking. Their SEO value lies in capturing long-tail search traffic from viewers who are curious, invested, and searching for answers or speculation. These articles are intentionally short and focused—get to the point fast. --- ### Headline (H1) **(REQUIRED)** **Fan Theory formula:** `This [Show Name] Fan Theory About [Character/Plot Point] Will Blow Your Mind`
**Fan Question formula:** `Biggest Questions About [Show Name] Answered` - Show name must be front-loaded or prominently positioned—it is the primary keyword anchor - Character count: 80–100 characters - Casing varies by publishing destination—adjust per site style guide before publishing > **Optimize before publishing.** Articles are indexed almost immediately after publishing. 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 first 8 words carry the most 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 - **Fan Theory:** should tease the theory and hint at the evidence - **Fan Question:** should signal that the piece answers a specific, burning question --- ### Meta Description **(REQUIRED)** - 100–155 characters (approximately 2 sentences) - Must contain the focus keyphrase and relevant proper nouns (show name, character name) - 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) | |---|---|---| | Fan Theory | `"[Show Name] fan theory"` | `"[Character Name] theory"` | | Fan Question | `"[Show Name] fan question"` | `"What happened in [Show Name]?"` | - Must appear in: H1, SEO title, dek (CMS field), meta description - Should reflect how an engaged fan would search after watching an episode or reading coverage - Use Google Trends data to validate keyword choices and inform H2 subheadings --- ### Tone **(REQUIRED)** Speculative, engaging, and conversational. - **Fan Theory:** lean into the speculation—present the theory with enthusiasm and lay out the evidence clearly. This is a fun, exploratory piece, not a news report. - **Fan Question:** direct and informative—answer the question clearly, then support it with context and detail. The reader came here for an answer; give it to them. --- ### Word Count **(REQUIRED)** Target: 300–500 words. This is the shortest format in the standards. These articles are intentionally focused—readers want a quick, satisfying answer or a well-presented theory. Do not pad. Stay tight. --- ### Article Structure **(REQUIRED)** The following structure is mandatory for this format. General Guidelines do not prescribe article structure. **Fan Theory:** ``` [AI DISCLAIMER—CUE sites only] "This article was created by content specialists using various tools, including AI." [LEDE / INTRO] - Introduce the show and the theory—hook the reader immediately - No throat-clearing openers [H2—Theory name or description (Google Trends keyword)] - Clearly explain the fan theory - Present the evidence that supports it (scenes, dialogue, visual details, etc.) - Acknowledge any counter-evidence if relevant [ADDITIONAL H2 SECTIONS—one per theory if covering multiple] (UsW: each theory gets its own H2 with a Google Trends keyword) [INTERNAL LINKS—embedded throughout] - 3–5 contextual internal links ``` **Fan Question:** ``` [AI DISCLAIMER—CUE sites only] "This article was created by content specialists using various tools, including AI." [LEDE / INTRO] - Introduce the show and the question being answered - No throat-clearing openers [H2—The question as a subheading (Google Trends keyword)] - Directly answer the question - Provide supporting details and context [ADDITIONAL H2 SECTIONS—one per question if covering multiple] (UsW: each question gets its own H2 with a Google Trends keyword) [INTERNAL LINKS—embedded throughout] - 3–5 contextual internal links ``` --- ### Formatting Rules **(REQUIRED)** - **UsW:** Each theory or question must have its own H2 subheading—do not stack multiple theories or questions under a single H2 - **UsW:** H2 subheadings must include keywords found in Google Trends - **Fan Theory:** the theory must be clearly stated and the supporting evidence must be explicitly laid out—do not leave the connection implicit - **Fan Question:** the answer must come first—do not make the reader work to find it - Bullet points permitted for evidence lists or supporting details—not as a substitute for prose - 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's tag page on the site - Character pages relevant to the theory or question - Other relevant articles that provide context for the theory or answer **UsW:** 3 minimum, 5 maximum. Do not confuse with Related Links—Related Links are used to break up inline copy and are counted separately. --- ### 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 show or film being discussed | | 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 name and theory/question topic - Strip stop words - Keep short and descriptive - Fan Theory pattern: `[show-name]-fan-theory-[topic]` or `fan-theory-[show-name]-[topic]` - Fan Question pattern: `[show-name]-fan-questions-answered` or `[show-name]-questions-answered-[topic]` --- ### 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 | |---|---| | Fan Theory: presenting the theory without the supporting evidence | Format requirement—evidence is the core of a fan theory article | | Fan Question: burying the answer or not answering directly | Format requirement—the answer must come first | | UsW: multiple theories or questions under a single H2 | Format structure requirement—each theory/question gets its own H2 | | H2 subheadings without Google Trends keywords (UsW) | Format requirement for UsW | | Padding to hit a word count—these articles are intentionally short | Format is 300–500 words; do not inflate with unnecessary content | | 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 show/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 - 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 and source material verified; speculation clearly framed as such - Focus keyphrase in H1, SEO title, dek (CMS), and meta description - H1: 80–100 characters, correct subtype formula applied, show name prominent - 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 - **Fan Theory:** theory clearly stated; supporting evidence explicitly laid out - **Fan Question:** answer comes first; supporting details and context follow - **UsW:** each theory or question has its own H2; H2s contain Google Trends keywords - 3–5 internal links—show tag page, character pages, related context articles (UsW: 3 min, 5 max); not confused with Related Links - Total word count is 300–500 words - Hero image: 1200px+ wide, 16:9, 300K+ res, show/film still or promo, no logos/text/stock - URL: subtype-appropriate pattern, show name front-loaded, 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