404 Page & Maintenance Page Creative Copy

## ROLE
You are a creative copywriter who specializes in turning frustrating web experiences into memorable brand moments. You have written award-winning 404 pages, maintenance notices, and system status pages for brands ranging from playful startups to serious enterprise platforms. You understand that these pages are often a user's first encounter with your brand's personality, and you treat them as conversion opportunities rather than afterthoughts.

## OBJECTIVE
Create a suite of creative, functional system status pages for [BRAND NAME] that reflect the brand voice ([BRAND VOICE: playful / professional / quirky / minimal / bold / warm]) and turn dead-end moments into brand-building opportunities. The website serves [AUDIENCE] and the industry is [INDUSTRY]. Current bounce rate on error pages is [RATE OR "unknown"] and the goal is to reduce it by [TARGET: 30-50%].

## TASK

### Step 1 — 404 Page Copy (Page Not Found)
Write 5 complete 404 page variations, each with a different creative approach:

**Variation 1: Humor-Forward**
- Headline: A genuinely funny line that acknowledges the error (not "Oops!" which is overused)
- Subtext (2-3 sentences): Light-hearted explanation of what happened
- Visual direction: Describe an illustration, animation, or interactive element concept
- Search bar prompt: "Try searching for what you were looking for"
- Navigation helpers: 3-4 text links to popular pages with benefit-focused labels
- CTA: Return to homepage or most popular section

**Variation 2: Brand Story Integration**
- Headline: Tie the 404 concept to your product's core metaphor or mission
- Subtext: Use the error as a moment to reinforce what you do and why it matters
- Example for a [INDUSTRY] brand: Connect "lost page" to [INDUSTRY-RELEVANT METAPHOR]
- Include a product screenshot or feature highlight to re-engage interest

**Variation 3: Interactive or Gamified**
- Headline: Invite the user to engage with something fun
- Concept: Describe a mini-game, Easter egg, or interactive element
  - Examples: Hidden object game, simple click game, quiz, drawing tool, music player
- Ensure the interactive element reinforces brand identity
- Include clear exit paths so users do not get permanently stuck on the fun page

**Variation 4: Utility-Focused (Minimal Creative)**
- Headline: Clear and direct (max 5 words)
- Subtext: One sentence explaining the page was not found
- Smart suggestions: "Were you looking for..." with 4-6 auto-suggested popular pages
- Sitemap preview: Key sections with brief descriptions
- Support link: Direct path to help if the user believes this is an error

**Variation 5: Social Proof Redirect**
- Headline: Acknowledge the miss and pivot to your best content
- "Since you're here, check out our most popular [CONTENT TYPE]:"
- Display 3 popular items with thumbnails and brief descriptions
- Include a "Report broken link" small text link for site maintenance

For ALL variations, include:
- Proper HTTP 404 status code reminder (not a soft 404)
- Search functionality placement
- Navigation back to main sections
- Analytics event tracking suggestion (track which 404 URLs are most hit)

### Step 2 — Maintenance Page Copy
Write copy for 3 maintenance scenarios:

**Scheduled Maintenance (Planned Downtime)**
- Headline: Honest but positive ("We're making things better" not "Site is down")
- Subtext: What is being improved (give users a reason to be excited about the downtime)
- Timeline: "We expect to be back by [TIME] [TIMEZONE]. Usually we finish early."
- Status page link: "Follow real-time updates at [STATUS PAGE URL]"
- Alternative actions: What users can do in the meantime
  - "Check our blog for the latest [CONTENT]"
  - "Follow us on [SOCIAL] for updates"
  - "Download our mobile app for uninterrupted access" (if applicable)
- Countdown timer suggestion: Visual element showing estimated return
- Email notification option: "Get notified when we're back" with email input field copy

**Emergency Maintenance (Unplanned Outage)**
- Headline: Transparent acknowledgment without causing panic
- Subtext: "We're aware of the issue and our team is actively working to resolve it."
- What we know: "The issue is affecting [SPECIFIC SERVICES]. [OTHER SERVICES] are working normally."
- Timeline: "We'll update this page every [15/30] minutes with progress."
- Last updated timestamp: Prominently displayed, automatically refreshed
- Apology: Genuine, specific, not performative ("We know you rely on [PRODUCT] for [USE CASE], and this disruption is unacceptable to us.")
- Incident communication template for when the outage is resolved:
  - What happened (plain language, not jargon)
  - What we did to fix it
  - What we are doing to prevent it from happening again

**Partial Outage (Some Features Affected)**
- Status board layout: List each major feature with real-time status
- Status labels: "Operational" / "Degraded Performance" / "Partial Outage" / "Major Outage"
- Per-feature message: "You may experience [SPECIFIC SYMPTOM] when using [FEATURE]. Workaround: [ALTERNATIVE]."
- Subscription prompt: "Subscribe to updates for [SPECIFIC FEATURE]"

### Step 3 — Coming Soon / Under Construction Pages
Write copy for pre-launch and feature preview pages:

**Product Launch Coming Soon**
- Headline: Build anticipation without over-promising (max 6 words)
- Value proposition: 2-3 sentences describing what is coming and who it is for
- Email capture: "Be the first to know when we launch"
  - Input field placeholder: "your@email.com"
  - Button text: "Notify me" (not "Submit")
  - Privacy assurance: "One email on launch day. No spam. Unsubscribe anytime."
- Social proof preview: Early user count, waitlist position, or testimonial
- Launch timeline: "[SEASON/MONTH YEAR]" or "In [X] weeks" — be as specific as you can commit to
- Social links: "Follow the journey on [PLATFORMS]"

**Feature Coming Soon (Within Existing Product)**
- Feature name and one-line description
- "What it'll do" section: 3 bullet points of key capabilities
- "When to expect it" section: Honest timeline with caveats
- Waitlist or beta signup: "Want early access? [CTA]"
- Feedback request: "Help us build this right. What's most important to you?" with quick poll or open text field

### Step 4 — Additional System Pages
Write copy for less common but important pages:

**Geographic Restriction Page**
- "[PRODUCT] isn't available in your region yet. We're expanding and [YOUR REGION] is on our list."
- Waitlist option for when it launches in their area
- Alternative product suggestion if available

**Browser Compatibility Page**
- "For the best [PRODUCT] experience, we recommend [BROWSERS]."
- Link to each recommended browser's download page
- Note which features are limited in the current browser

**Account Suspended Page**
- Clear explanation of why the account was suspended
- Steps to resolve the issue
- Appeal process with timeline expectation
- Support contact for questions

### Step 5 — SEO & Technical Requirements
For every system page, include:
- Recommended meta title and description (even for 404 pages — they get indexed)
- Canonical URL strategy: Self-referencing or pointing to homepage
- Schema markup suggestion: WebPage or ErrorPage schema
- Internal linking strategy: Which pages to link to from each status page
- Performance note: Keep these pages lightweight — they must load even when main infrastructure is struggling