# Deep Dive Listicle Platform: All platforms | Type: Sequential Deep-Dive Explainer > **Where this format overrides General Guidelines:** This is a single-topic article cut into sequential segments for immersive top-to-bottom reading—**not** a question-and-answer format and **not** a set of order-independent standalone entries. It introduces requirements with no brand-level equivalent: **segment headers written as declarative statements** (question-form headers are prohibited, the mirror-opposite of the FAQ format §3.11); segments that **build on one another in order**; **parallel depth** across segments; a **personal opening frame** addressed to the curious optimizer; and a required **synthesis closing**. The default permission for occasional question-format headlines (§1.2) is overridden to *avoid* for this format. Text in **red** throughout this page marks anything that overrides or goes beyond the General Guidelines. --- ### Purpose A Deep Dive Listicle takes one topic and cuts it into a sequence of segments that build on one another, so a motivated reader can move top to bottom and come away with a complete, actionable understanding. It reads as one immersive article—each segment a phase, factor, step, or angle of the same subject—rather than a list of interchangeable entries. The format is built for the curious optimizer (§4.2): a reader motivated to improve, understand, or get ahead, who wants a subject explained well enough to act on it. It rewards a full read while staying scannable, and it earns trust by walking the reader through the whole arc instead of answering one isolated question. Do **not** confuse with the FAQ / Service Journalism format (§3.11), which is a question-and-answer structure with one question per H2; the Deep Dive Listicle prohibits question structure entirely. Do not confuse with a conventional listicle of standalone ranked entries—Deep Dive Listicle segments are sequenced and interdependent, not order-independent. --- ### Opening Frame **(REQUIRED, format-specific)** General Guidelines have no equivalent element. The following is mandatory for this format. Every Deep Dive Listicle opens with one to two short paragraphs written for the curious optimizer. Open on a personal, reader-facing note; lead with what the topic means for *them*, not with analysis or framing. Keep it warm and direct rather than detached or explanatory—a personal open outperforms an analytical one. Then signal what the segments ahead will cover. Do not phrase the opening as a question. **Personal (use this):** > If you've ever felt like you're doing everything right and still not getting the results, this is the part no one walks you through. **Analytical (avoid):** > There are several factors that influence outcomes in this area, which this article will examine in sequence. --- ### Segment Rules **(REQUIRED, format-specific)** 1. Cut the topic into segments that **build on one another**—a later segment may assume the reader has read earlier ones. 2. Give each segment a **descriptive header written as a declarative statement**, never a question. Front-load the specific noun or hook so the header is meaningful when skimmed. 3. Keep segments **parallel in depth and length** so the article reads evenly—no one long segment with thin others. 4. Make each segment **self-contained enough to scan** but sequenced to reward a full read. 5. Keep the article on **a single topic**—do not split it into unrelated standalone entries. --- ### Header Formatting **(REQUIRED, format-specific)** Segment headers (H2) must be declarative phrases with the specific noun or hook front-loaded. **Qualifying examples:** > How the timeline actually works > The cost most people miss > What changes after the first year **Disqualifying (question form is prohibited):** > How does the timeline work? --- ### Headline (H1) **(REQUIRED)** - A single declarative H1 that front-loads the specific hook; not phrased as a question - Character count: 80–100 characters - Build from the focus keyphrase outward, per General Guidelines §1.2 - Casing varies by publishing destination—adjust per site style guide before publishing --- ### SEO Title, Meta Description, Focus Keyphrase, SEO Keywords **(REQUIRED)** This format does not lock a format-specific SEO formula—follow General Guidelines §1.2: - **SEO Title:** 50–70 characters; contains the focus keyphrase; front-loaded keywords; contains a verb - **Meta Description:** 100–155 characters; focus keyphrase required; does not repeat the H1 verbatim; entices rather than summarizes - **Focus Keyphrase:** the main search query for the topic; appears in H1, SEO title, dek (CMS field), and meta description - **SEO Keywords:** 1–5 keywords; single words acceptable; lowercase, comma-separated --- ### Tone **(REQUIRED)** Personal, warm, and direct—written to a motivated reader who wants to act on the topic. Speak to the reader, lead with relevance to them, and commit to a clear through-line across the segments. Explanatory without being detached; the opening in particular favors the personal register over the analytical one. --- ### Word Count **(REQUIRED)** No fixed range is locked for this format; length is governed by segment count times parallel per-segment depth. The controlling constraint is parallelism—every segment carries comparable depth—not a total-word target. As a working guide, aim for enough segments to cover the topic's arc with each developed evenly. --- ### Article Structure **(REQUIRED)** The following order is mandatory. The piece is one article on one topic, read top to bottom—not a Q&A and not a set of standalone entries. ``` [AI DISCLAIMER—CUE sites only] "This article was created by content specialists using various tools, including AI." # [HEADLINE—declarative H1, front-loading the specific hook] [OPENING FRAME—1–2 short paragraphs, no header] (REQUIRED, format-specific) - Personal, reader-facing open for the curious optimizer; lead with what the topic means for them - Warm and direct, not detached or explanatory; personal register over analytical - Then signal what the segments will cover - Do NOT phrase as a question [H2 SEGMENT 1—declarative-statement header, specific noun front-loaded] - One coherent part of the topic—a phase, factor, step, or angle - Self-contained enough to scan, sequenced to reward a full read [H2 SEGMENT 2—declarative-statement header] - Builds on Segment 1 [H2 SEGMENT n—declarative-statement headers throughout] - Parallel in depth and length to the others [CLOSING—synthesis paragraph or a "where this goes next" beat] (REQUIRED, format-specific) - Do NOT end abruptly after the final segment [INTERNAL LINKS—3–5, embedded throughout body copy] ``` --- ### Closing **(REQUIRED, format-specific)** General Guidelines have no equivalent element. Every Deep Dive Listicle ends with a synthesis paragraph or a "where this goes next" beat—never an abrupt stop after the last segment. The closing ties the segments back to the reader's goal from the opening frame. --- ### Formatting Rules **(REQUIRED)** - Every segment header is a declarative statement—question-form headers are prohibited - Segments build in order; do not write order-independent standalone entries - Keep segments parallel in depth—if one segment runs long and others thin, rebalance - Keep paragraphs short (2–4 sentences max)—the format leans long; short paragraphs keep it scannable on mobile - Bullet points permitted within a segment—not as a substitute for prose, and never as a way to turn a segment into a mini-list of standalone entries --- ### Internal Links **(REQUIRED)** 3–5 contextual internal links per article, placed naturally within copy. Anchor to explainers on the underlying topic, earlier related coverage, and supporting pieces referenced in a segment. Do not stack as a Related Links block. See General Guidelines §1.4 for anchor-text rules. --- ### Hero Image **(REQUIRED)** Follow the standard format image spec: 1200px+ wide (1600px+ preferred), 16:9, 300K+ resolution; no logos, no text overlays, no generic stock. --- ### URL Structure **(REQUIRED)** 4+ front-loaded keywords, stop words stripped, short and descriptive; built from the focus keyphrase. No format-specific suffix pattern. --- ### Tags **(REQUIRED)** - `TH-CSA` - `The Commons` - *(Tags subject to change—check for updates)* --- ### Prohibited | Prohibited | Reason | |---|---| | Question-and-answer structure of any kind | Format requirement—the Deep Dive Listicle is immersive sequential reading; Q&A belongs to the FAQ format (§3.11) | | Question-phrased segment headers | Format requirement—headers must be declarative statements with the noun front-loaded | | Standalone, order-independent entries that don't build on each other | Format requirement—segments are sequenced and interdependent; order-independent entries make it a conventional listicle, not this format | | Uneven segments (one long, others thin) | Format requirement—segments must be parallel in depth so the article reads evenly | | Ending on the last segment with no closing | Format requirement—every piece closes with a synthesis or "where this goes next" beat | | An analytical, detached opening instead of a personal one | Format requirement—the opening frame addresses the curious optimizer personally; the personal register outperforms the analytical | | 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 or images with text overlays | Format image spec—visually specific imagery required | | 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 | --- ### Acceptance Check Before finalizing, confirm the output satisfies all of the following: - Single topic, cut into sequential segments - Every segment header is a declarative statement (zero question-form headers) - Segments build in order and are parallel in depth - Opening frame is personal and reader-facing—not analytical, not a question - Opening frames the whole piece; closing synthesizes—no abrupt stop - No Q&A structure anywhere --- ### 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 - All facts verified; all links point to reputable sources - Focus keyphrase in H1, SEO title, dek (CMS), and meta description - H1: 80–100 characters, declarative, front-loads the hook, not a question - SEO title: 50–70 characters, matches H1 intent, front-loaded keywords, contains a verb - Meta description: 100–155 characters, no repeated hed language - **Opening frame** present—1–2 short paragraphs, personal register, addresses the curious optimizer, not a question - **Every segment header is a declarative statement**—no question-form headers - Segments build in order and are parallel in depth—no long-then-thin drop-off - **Closing** present—synthesis or "where this goes next," not an abrupt stop - 3–5 internal links placed naturally in copy; not stacked as Related Links - Tone is personal and direct, addressed to a motivated reader - Hero image: 1200px+ wide, 16:9, 300K+ res, no logos/text/stock - URL: short, keyword-forward, 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