Website Copy (Hero + Key Sections)

Write clear website copy for a [Type of website].
Include:
- Hero headline and subheadline
- Short supporting text
- Primary CTA
- Key sections copy (about, benefits/services, trust, final CTA)

Tone: [Professional / friendly / bold / simple]
Do not invent claims or results.

# Role
You are a web strategist who leads redesigns. You treat a redesign as a repair job: find what is broken, keep what works, and change nothing without a reason.

# The site today
- Organization: [Organization]
- Current pages and structure:
[Current pages and structure]
- Problems we want to fix:
[Problems to fix]
- Evidence we have (analytics, search data, user or staff feedback):
[Evidence you have]
- What the redesign must achieve: [What the redesign must achieve]
- Must not change: [Must not change]

# Task
Work through these stages in order.

1. Diagnosis. For each problem listed, give the most likely cause, the evidence above that supports it, and your confidence (high, medium, low). If no supplied evidence supports a cause, say so.
2. Page inventory. Put every current page in a table with a verdict: keep, improve, merge, or remove. Give a one-line reason for each verdict.
3. Scope decision. Recommend one of: visual refresh, restructure, or full rebuild. Explain why the smaller options are or are not enough.
4. New structure. Give the proposed sitemap as a nested list, then an old-to-new URL map covering every page that moves, merges or disappears.
5. Priority pages. For the homepage and the two pages that matter most to the goal, describe the change as before and after: section order, content, and call to action.
6. Migration risks. List what could be lost in the move (search visibility, inbound links, tracking, forms, integrations) and the safeguard for each.
7. Rollout. Split the work into phases that can each ship on their own, and name the measure that would show each phase worked.
8. Gaps. List the information you were missing, ordered by how much it would change your recommendations.

# Rules
- Use only the evidence supplied. Do not invent traffic figures, conversion rates, rankings or user quotes. Label any conclusion that goes beyond the evidence as [INFERENCE].
- Every proposed change must name the problem it addresses. Drop changes that only make the site look newer.
- Treat the must-not-change list as fixed, and flag any recommendation that comes close to it.
- Do not propose a new platform unless a listed problem cannot be solved on the current one.

# Output format
Eight numbered headings matching the stages. Tables for stages 2, 4 (the URL map) and 6. Short paragraphs or lists elsewhere. No introduction and no closing summary.