How to Write Website Copy That Converts in One Week
A one-week copywriting process for writing clear positioning, proof, objections, CTAs, FAQs, and conversion-focused page structure.
Most website copy fails for a boring reason: it's written to sound impressive instead of to answer the questions a buyer is actually asking. You don't need a month and a positioning agency to fix that. You need a week, a clear process, and the discipline to write what your buyer needs rather than what your team likes.
We write conversion copy on the same one-week clock we build sites on. Here's the process that gets us from blank page to launch-ready copy in five working days.
Why a week is enough, and what it isn't enough for
A week is plenty of time to synthesize what you already know about your buyer into sharp, specific copy. It is not enough time for net-new research: surveys, interviews with strangers, a positioning workshop from scratch. The constraint is a feature: it forces you to use real signal you already have rather than inventing it. If you don't know your buyer at all yet, copy isn't your first problem.
Day one: mine, don't brainstorm
Skip the brainstorm. Pull raw material from sources that already contain your buyer's words: recent sales calls, support tickets, lost-deal notes, and demo recordings. These tell you the exact objections, questions, and phrases that matter. Collect buyer questions, objections, the proof that moves them, and their real decision criteria. This is your entire raw material. Copy is synthesis, not invention.
Day two: write the positioning spine
Before any page, write four lines: the audience, the outcome you create for them, the offer, and the reason to believe. Everything else hangs off this spine. If you can't write a concrete reason to believe (a number, a named client, a specific mechanism), you've found the gap that will weaken every page until you fill it.
Day three: turn questions into structure
Outline each page by turning buyer questions into sections. Don't start from a template's sections; start from what the buyer needs answered, in the order they'd ask. The homepage might answer "what is this, who's it for, why believe you, what does it cost, what do I do next." Every section earns its place by handling one question or one objection.
Day four: draft short and direct
Now write. Short sections, not short thinking. A hero plus six to eight scannable blocks beats one 800-word essay nobody finishes. Lead with the outcome. Make CTAs specific ("Book a 20-minute teardown," not "Learn more"). Keep each section doing one job. Drafting is fast when the outline already maps to buyer questions.
Day five: edit for specificity
Editing is where conversion copy is won. Hunt down every vague claim ("powerful," "seamless," "best-in-class") and either prove it or cut it. Add proof exactly where the buyer takes a risk: near pricing, near the signup, near security claims. This pass is non-negotiable, and it's the one AI can't do for you.
Where FAQs actually belong
Put FAQs where objections genuinely appear: pricing, security, and implementation pages, not as a keyword dump at the footer. Mirror the real objections from your sales calls. Done honestly, FAQ content helps buyers and earns FAQ-rich snippets; done as stuffing, it helps nobody.
How long should the homepage be?
| Section | Job |
|---|---|
| Hero | Outcome + primary CTA |
| Proof strip | Logos, metrics, credibility |
| Problem / solution | Make the stakes clear |
| How it works | Reduce perceived risk |
| Objection handling | FAQ or comparison |
| Closing CTA | One clear next step |
Short sections, clear hierarchy, one idea each. Length follows the buyer's questions, not a word target.
Can AI write the first draft?
As raw material, yes. As final copy, no. AI doesn't know your proof hierarchy or which objection actually kills deals in your segment. It defaults to confident vagueness. Use it to get unstuck, then edit hard for specificity. The human pass is what separates copy that converts from copy that fills space.
What to do next
Block five days, gather your sales calls and tickets, and write the positioning spine first. If you'd rather have it done with you, Metamatter writes conversion copy as part of every site sprint, built from your real buyer signal, not generic templates.
Pressure-test the draft before launch
Before copy ships, run it past two cheap tests. First, the "so what" test: read each section aloud and ask whether a busy buyer would care; if the honest answer is no, cut it or sharpen it. Second, the "only us" test: could a competitor paste their logo on this page and have it still read true? If yes, you've written category boilerplate, not positioning. Then hand the page to someone outside the company and watch where they hesitate or re-read. Confusion you can see beats feedback you have to interpret. Five days is enough time to write and to run these tests if you don't waste day one on a brainstorm. The edit pass is where average copy becomes copy that actually moves a deal forward.
FAQ
Where should I get input if I can't run a positioning workshop?
Mine sales calls, support tickets, lost-deal notes, and demo recordings. One week doesn't allow net-new research. It allows synthesis of what you already know buyers ask.
How long should homepage copy be?
Short sections, not short thinking. A hero plus six to eight scannable blocks beats one 800-word essay. Every section should answer one buyer question or handle one objection.
Should FAQs go on every page?
Put FAQs where objections actually appear: pricing, security, implementation pages. Mirror sales objections, not keyword stuffing. FAQ schema helps snippets when the content is genuine.
Can AI draft the first version?
Yes as raw material. No as final copy. AI won't know your proof hierarchy or which objection kills deals in your segment. A human edit for specificity is non-negotiable.
