Timeline (pending)

Platform: All platforms Type: Relationship / Nostalgic Timeline

⬇ Download this section

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

Headline (H1)

(REQUIRED)

Required formulas:

Keep the subject front-loaded. Do not move it after “A Complete Timeline” or “A Complete Breakdown.”

Optimize before publishing. Articles are indexed almost immediately after publishing. Get the H1 and SEO title right before hitting publish.

SEO Title

(REQUIRED)

Dek

(REQUIRED)

Meta Description

(REQUIRED)

Focus Keyphrase

(REQUIRED)

Type Format
Primary "[Subject] timeline"
Secondary (if applicable) "[Subject] relationship"

</span>

Tone

(REQUIRED)

Romantic and nostalgic. 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.

Word Count

(REQUIRED)

Target: 500–2,000 words. 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.

Article Structure

(REQUIRED)

The following structure is mandatory for this format. General Guidelines do not prescribe article structure.

[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

Formatting Rules

(REQUIRED)

Photos

(REQUIRED)

General Guidelines do not specify per-entry photo requirements. The following is mandatory for this format.

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>

(REQUIRED)

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

Link to:

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
Entries listed out of chronological order Format requirement—timeline entries must run earliest to most recent
Entries without a date or time period Format requirement—every entry must be anchored in time
Key moments without a corresponding photo Format requirement—each entry requires a photo
Subject placed after “A Complete Timeline” in the headline Format rule: subject must be front-loaded
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

Pre-Publish Checklist