
# Timeline (pending)

Platform: All platforms | Type: Relationship / Nostalgic Timeline


> **Where this format overrides General Guidelines:** The headline formula is locked to `[Subject]: A Complete Timeline` or `[Subject]: A Complete Breakdown`—neither contains a traditional verb, which is permitted for relationship timelines under the existing General Guidelines §1.2 exception. 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 (500–2,000 words), a chronological article structure, and per-entry photo requirements. Text in <span style="color: #dc2626;">**red**</span> throughout this page marks anything that overrides or goes beyond the General Guidelines.

---

### Purpose

A Timeline is a highly engaging, evergreen article that traces the key moments in a relationship or subject's history in chronological order. Its purpose is to attract both search traffic (people researching a couple or subject's backstory) and social traffic (people who want to relive or discover the arc of a story). These pages function as durable reference pieces and should be updated as new milestones occur.

---

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

<span style="color: #dc2626;">**Required formulas:**
- `[Subject]: A Complete Timeline`
- `[Subject]: A Complete Breakdown`</span>

<span style="color: #dc2626;">Keep the subject front-loaded. Do not move it after "A Complete Timeline" or "A Complete Breakdown."</span>

- Character count: 80–100 characters
- <span style="color: #dc2626;">A verb is **not required**—relationship timelines are an explicit exception in General Guidelines §1.2</span>
- 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.

---

<!-- 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
- Is a concise version of the H1, not a string of keywords
- <span style="color: #dc2626;">A verb is **not required**—relationship timelines are an explicit exception in General Guidelines §1.2</span>

---

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

- Entered as a separate CMS field—do not place inside the article body
- Must contain the focus keyphrase
- Should summarize the arc of the timeline in a way that entices the click

---

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

- 100–155 characters (approximately 2 sentences)
- Must contain the focus keyphrase and relevant proper nouns
- 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 | `"[Subject] timeline"` |
| Secondary (if applicable) | `"[Subject] relationship"` |

</span>

- Must appear in: H1, SEO title, dek (CMS field), meta description
- Should reflect how a real person would search for this subject's history
- Use Google Trends data to validate keyword choices

---

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

<span style="color: #dc2626;">Romantic and nostalgic.</span> The reader should feel the arc of the story—the highs, the lows, and the milestones. Conversational and human—never stiff or institutional. Confident and specific—avoid vague generalities.

---

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

<span style="color: #dc2626;">Target: 500–2,000 words.</span> Word count is a target range, not a hard ceiling. More complex or longer-running relationships may require more depth—provided the article remains well-organized and every entry 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.</span>

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

[LEDE / INTRO]
- Briefly introduce the subject and why this timeline matters
- Set the tone—romantic, nostalgic, engaging
- No throat-clearing openers

[TIMELINE ENTRIES—listed chronologically]
Each entry must include:
  - Date or time period (e.g., "June 2018", "Summer 2021")
  - Photo of the key moment (see Photos section)
  - Description of the moment—what happened and why it matters

[INTERNAL LINKS—embedded throughout entries and intro]
- 3–5 contextual internal links
- Placed naturally within relevant entries
```

---

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

- <span style="color: #dc2626;">Entries must be listed **chronologically**—earliest first, most recent last</span>
- <span style="color: #dc2626;">Every entry must include a date or time period</span>
- <span style="color: #dc2626;">Every key moment must have a corresponding photo (see Photos section below)</span>
- Keep entry descriptions concise and readable—each entry should feel like a moment, not a summary
- Keep paragraphs short for mobile readability

---

### Photos
**(REQUIRED)**

<span style="color: #dc2626;">General Guidelines do not specify per-entry photo requirements. The following is mandatory for this format.</span>

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

- Include a photo for **each key moment** in the timeline
- Photos must clearly depict the subject at or around the time of that moment
- Generic stock images are not permitted for individual entries
- Each photo must meet the standard image specs:

| Spec | Requirement |
|---|---|
| Minimum width | 1200px (1600px+ preferred) |
| Aspect ratio | 16:9 |
| Resolution | 300K+ pixels |
| Logos | NOT permitted |
| Text overlays | NOT permitted |
| Generic stock | NOT permitted |

</span>

---

<!-- 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 celebrities' or subjects' tag pages on the site
- Articles about specific events in the relationship referenced in the timeline
- Previously published articles about milestones mentioned in the piece</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;">Pattern: `[subject]-relationship-timeline` or `[subject]-timeline`</span>
- <span style="color: #dc2626;">Strip stop words</span>
- <span style="color: #dc2626;">Keep short and descriptive</span>
- <span style="color: #dc2626;">Examples: `cheryl-hines-robert-f-kennedy-jr-relationship-timeline`, `stevie-nicks-lindsey-buckingham-relationship-timeline`</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;">Entries listed out of chronological order</span> | <span style="color: #dc2626;">Format requirement—timeline entries must run earliest to most recent</span> |
| <span style="color: #dc2626;">Entries without a date or time period</span> | <span style="color: #dc2626;">Format requirement—every entry must be anchored in time</span> |
| <span style="color: #dc2626;">Key moments without a corresponding photo</span> | <span style="color: #dc2626;">Format requirement—each entry requires a photo</span> |
| <span style="color: #dc2626;">Subject placed after "A Complete Timeline" in the headline</span> | <span style="color: #dc2626;">Format rule: subject must be front-loaded</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 for individual entries | Format photo requirement—images must depict the subject at the time |
| 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; all dates and events verified against reputable sources
- Focus keyphrase in H1, SEO title, dek (CMS), and meta description
- H1: 80–100 characters, `[Subject]: A Complete Timeline` or `[Subject]: A Complete Breakdown` formula, subject front-loaded, no prohibited language
- SEO title: 50–70 characters, matches H1 intent, front-loaded keywords
- Meta description: 100–155 characters, no repeated hed language
- Dek entered as CMS field—not placed inside article body
- Entries listed chronologically—earliest first, most recent last
- Every entry includes a date or time period
- Every key moment has a corresponding photo (1200px+ wide, 16:9, 300K+ res, no logos/text/stock)
- 3–5 internal links—subjects' tag pages and articles about specific events in the timeline
- Total word count is 500–2,000 words
- URL: `[subject]-relationship-timeline` or `[subject]-timeline` 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
