Claude Prompt for Website Copy: A Voice Brief

A good Claude prompt for website copy gives the model more than a topic. It gives it your audience, offer, verified facts, brand voice and the shape of the page the words must fit. Build that brief once, then use it section by section to get copy that sounds like your business and works in your layout.

Copy is part of the interface. A headline changes what visitors notice first; a subheading affects how quickly they understand the offer; a button label sets an expectation about what happens next. If your positioning or voice is still unclear, start with the foundations of brand strategy and identity, then use the DesignFIT resources to prepare your content and page structure.

This guide shows you what to gather, how to set up a reusable brief in Claude, and how to prompt for specific website sections. You will also get a copy-ready template, checks for accuracy and layout, and advice on where AI can help and where a person needs to make the call.

Why a Claude prompt for website copy needs a design brief

If you ask Claude to “write my homepage”, it has to guess what your business does, which customers matter, what makes your offer different and how much copy the design can hold. Those gaps often produce polished but interchangeable marketing language. More prompting cannot reliably repair missing business facts or an undefined position.

The prompt also needs to describe the page as a visual system. A hero with a headline, short explanation and two buttons needs different copy from a long-form service page. A three-card row needs parallel descriptions. A mobile layout may need a shorter heading so it does not crowd the main action.

These are not universal character limits. They are design constraints to test against your actual wireframe, typography and responsive layouts. The right headline length depends on the font, width, size and line height. The useful move is to tell Claude what component it is writing for, then check the draft in the real design.

Web visitors commonly scan rather than read every word. Nielsen Norman Group reports that 79% of test users scanned a new page, while 16% read word by word in its research on web reading. Treat that as a useful usability finding, not a promise about every visitor. It is a reason to make headings informative, front-load important details and use short sections. See Nielsen Norman Group’s findings on how people read on the web.

A layout-aware brief helps Claude produce copy with a clear hierarchy. The design can then make the offer, proof and next step easier to find. For a deeper look at how copy, structure and visual decisions work together, see our website design service.

What you need before you prompt Claude

Do not start by collecting adjectives for your tone of voice. Start with the facts and decisions that should shape the words. Gather these items in one document, even if some answers are rough.

1. Your audience and their situation

Describe the people you want to reach in concrete terms. Include their role, business type, location if relevant, and the moment they are looking for help. “Small businesses” is broad. “Owners of independent allied health clinics who need a clearer way to explain their services and accept enquiries” gives Claude more to work with.

Add what the audience already knows, what they are worried about and what might stop them taking action. Use customer questions, sales calls and support messages where you have them. Do not paste private or identifying customer information unless you have permission and a good reason.

2. Your offer, in plain language

Write down what you sell, what is included, who delivers it, how it works and what happens after someone enquires. If you have a service process, describe the stages. If you have product options, name them and explain the differences.

Avoid vague claims such as “a complete solution” unless you explain what is actually included. If you do not know a detail, mark it as unknown. Claude should not fill the gap by guessing.

3. Proof you are allowed to use

Collect approved facts: qualifications, years of operation, locations served, product specifications, published reviews, named methods or measurable results that you can substantiate. Include the source or the person who approved each claim if that will help your team verify it later.

Keep proof separate from aspiration. “We aim to reply within one business day” is not the same as “We reply within one business day”. Do not ask Claude to invent client numbers, guarantees, awards, testimonials or performance statistics. If you have no proof for a claim yet, ask it to flag the gap instead of writing around it.

4. Voice examples, not just voice labels

Words such as “friendly”, “premium” and “confident” can mean different things to different people. Choose a few examples of your existing writing that sound right, and explain what works about them. Add one example that sounds wrong and say why.

For instance: “This email sounds like us because it is direct, explains the next step and does not oversell. This draft does not sound like us because it uses vague superlatives and several exclamation marks.” Examples make your preferences more concrete than a list of tone adjectives.

5. The page structure and its job

Give Claude a wireframe, outline or simple component list. Name each section and its purpose: hero, service overview, proof, process, frequently asked questions and final call to action. Say which action the page should support, such as booking a consultation or comparing service options.

If you already have a design, note the actual containers: number of cards, button locations, mobile order, approximate text space and whether a heading must sit on one or two lines. If you do not have a design yet, ask Claude for clearly labelled content options, not final text that assumes a layout you have not chosen.

Step 1: Create a source-of-truth document

Make a short document with the five inputs above. Separate confirmed facts from ideas that still need approval. A simple table makes this distinction visible:

Information	What to record	Status
Offer	Deliverables, process, price details if public	Confirmed or needs checking
Audience	Role, problem, buying situation	Current best definition
Proof	Approved facts and their source	Approved, dated or not for use
Voice	Good and bad writing examples	Approved examples
Page	Sections, components and desired action	Draft or approved

This is the document you will maintain when your offer changes. Avoid treating the latest generated answer as the source of truth. Claude can help organise the information, but you are responsible for confirming what is accurate.

Keep sensitive information out unless you have checked your organisation’s policies and the service settings that apply to your account. Anthropic explains how Claude Projects work. Check the current Claude plans and pricing before choosing a plan, because availability and pricing can change.

Step 2: Set up a Claude Project for the work

A Project can keep a set of instructions and reference material associated with related chats. That is useful when you are developing several pages for the same brand: you can reuse the same core facts and voice guidance instead of rebuilding the context in every conversation. Check Anthropic’s Projects help page for current feature details and account requirements.

Give the Project a clear name, such as “Website copy: [business name]”. Add the source-of-truth document and any relevant approved examples. Use plain, clearly labelled files. Separate your business facts, voice examples and page-specific content rather than combining everything into one long, hard-to-update file.

Projects are not a replacement for good instructions. A file full of old brochures, sales scripts and draft claims can make the context less clear, not more. Remove outdated content. Label material that is for reference only. Tell Claude which document takes precedence if two files conflict.

Do not assume Claude will remember every detail in every output. Ask it to use the Project material, identify missing information and flag uncertainty. If your plan or Project setup changes, check the feature details in Anthropic’s documentation rather than relying on old online advice.

Step 3: Write instructions for voice, facts and limits

Anthropic’s prompt engineering documentation describes ways to structure instructions and provide context. XML-style tags can help distinguish sections in a longer prompt, such as role, audience and constraints. They are organisational labels, not magic commands; the quality and clarity of the instructions still matter. See Anthropic’s prompt engineering overview.

Use a voice description plus examples. Add a short list of words or habits you want to avoid, but do not rely on a banned-word list alone. A model can avoid a word and still write in the same generic style. Explain the replacement behaviour: use specific nouns, state what the business does and support claims with supplied facts.

Here is a reusable starting point. Replace the square-bracket notes before using it. Keep only the constraints that are useful for your brand and page.

<project_instructions>
  <role>
    You help write clear website copy for [business name].
    Write for the intended page and its design components.
    Make the offer easy to understand and the next step clear.
  </role>

  <audience>
    Primary audience: [who they are and what situation they are in].
    Their main need: [need or problem].
    Their questions or concerns: [real questions from customers].
  </audience>

  <offer_and_facts>
    Offer: [what we sell and what is included].
    Process: [what happens and in what order].
    Confirmed details: [locations, timings, specifications, prices if public].
    Approved proof: [claims we can verify and where they come from].
    Unknown or not approved: [claims and details that must not be stated].
  </offer_and_facts>

  <brand_voice>
    Sound: [plain-language description, such as direct, calm and practical].
    Write like: [describe a real person or approved sample].
    Prefer: [specific verbs, sentence patterns or useful terminology].
    Avoid: [hype, empty claims, clichés, unexplained jargon].
    Use Australian spelling. Keep sentences clear and varied.
  </brand_voice>

  <voice_examples>
    This sounds like us because: [paste short approved example and explain why].
    This does not sound like us because: [paste short example and explain why].
  </voice_examples>

  <page_design>
    Page: [homepage, service page, landing page or other].
    Page goal: [the action the page should help a visitor take].
    Components: [list sections in order].
    Layout notes: [cards, columns, mobile order, text space or wireframe notes].
    Follow the supplied component limits. Treat them as design requirements,
    then report any limit that makes the message unclear.
  </page_design>

  <writing_constraints>
    Use only supplied facts. Do not invent results, prices, testimonials,
    guarantees, credentials or business details.
    If information is missing, ask a question or mark it [NEEDS CONFIRMATION].
    Avoid these words and phrases: [your specific list of clichés].
    Avoid generic openers, empty superlatives and repeated adjective lists.
    Do not add sections that are not in the requested page outline.
  </writing_constraints>

  <output_rules>
    Write only the section requested in the current task.
    Label each component clearly, such as EYEBROW, H1, BODY and CTA.
    Include a character or word count when requested.
    After the draft, list assumptions and claims that need human review.
  </output_rules>
</project_instructions>

This gives Claude a stable starting point. You still need a separate task prompt for each page or section. That is where you specify the audience priority, exact component, action, evidence and layout limits for the piece you want written.

Step 4: Prompt for one page section at a time

Do not ask Claude to write a whole website in one go. Large requests make it harder to review the connection between each section, and the model may repeat the same claim in several places. Work in page order, but approve the message before polishing every sentence.

Start with the page’s job. For example: “This service page is for clinic owners comparing providers. Its job is to explain what the service includes, answer questions about the process and invite a suitable visitor to request an initial call.” Then give the section name and any layout constraint.

Use a task prompt like this:

Use the Project instructions and reference material.

Page: [page name]
Section: [component name]
Audience priority: [which audience matters most here]
Section job: [what the visitor should understand or do]
Required facts: [facts that must be included, with source if useful]
Do not repeat: [points already explained elsewhere]
Layout: [number and type of components, mobile notes]
Length: [word or character range, if the design has one]
CTA: [action and destination]

Return:
1. The copy, labelled by component.
2. A count for each component where requested.
3. Any missing facts, assumptions or claims needing approval.
Do not write surrounding page sections.

Ask for a small set of alternatives only when there is a real decision to make. Three headline options can help you compare different messages. Ten slight variations create more review work without making the positioning clearer. If you want alternatives, specify what should differ: one focused on the problem, one on the offer and one on a concrete outcome that your evidence supports.

Step 5: Shape the hero around the first screen

The hero needs to tell a suitable visitor what the business does, who it helps and what to do next. Do not use a headline just because it sounds memorable. If a visitor cannot understand the offer from the heading and supporting line, the wording may be hiding the point.

Ask Claude for the parts separately: an eyebrow if needed, an H1, a short supporting line and one primary button. A secondary link can be useful when there is a clear second choice, such as viewing work or comparing services. More buttons do not automatically make the choice easier.

Example task:

Write the hero for our [service] page.
The audience is [specific audience]. The service is [confirmed offer].
The first screen must explain [essential message] and lead to [action].
Return an eyebrow of up to 3 words, an H1 under 9 words,
a supporting line under 25 words and one CTA of 2 to 4 words.
Use plain, specific wording. Do not claim an outcome we have not proved.
Give 3 distinct H1 options, then recommend one and explain why in one sentence.

The sample limits are a starting point for a compact hero, not a conversion formula. Read every version in the intended font and container. A nine-word heading can still wrap badly if it includes long words; a longer heading may work in a wide layout. Check the mobile version, where the same text often takes more vertical space and may push proof or a button lower.

A good review question is: “Can a first-time visitor tell what we offer before they scroll?” Also check that the headline does not promise more than the supporting line and proof can substantiate. If the page is for a specific audience, name them where that makes the message clearer.

Step 6: Keep card grids visually balanced without padding the copy

Feature cards work best when each card plays the same role. If one card explains a service, one lists a benefit and one gives a process detail, the visitor has to work harder to compare them. Choose a consistent pattern: for example, each card can name one part of the offer and explain what it means for the customer.

Tell Claude the number of cards, what each one covers and the format each needs. You can ask for similar lengths to help the grid feel balanced, but do not force identical word counts when the ideas differ. If equal heights are essential, the designer can manage the visual treatment with the component design; the words still need to be natural and useful.

Example task:

Write 3 cards for the section “What the service includes”.
Card topics: [topic one], [topic two], [topic three].
For every card, return a heading of 3 to 5 words and a description
of 18 to 24 words. Keep the descriptions similar in length and structure.
Each card must explain a distinct part of the offer.
Use only the confirmed information in the Project. Do not repeat benefits.
Flag any card that lacks enough facts instead of adding filler.

Then check the cards as a set. Do the headings use the same grammatical shape? Do descriptions answer the same kind of question? Are the benefits distinct? Does one card contain an unverified claim? If a card is shorter, improve the information rather than adding a vague sentence just to match the others.

Step 7: Write proof, calls to action and microcopy

A proof section should make evidence legible, not decorate the page with impressive-looking numbers. Ask Claude to use only approved proof and to keep the relationship between a number and its label clear. A number without context can confuse visitors; a claim without a source can create a trust problem.

A call to action should describe the next step in language the visitor understands. “Contact us” may be fine if that is the familiar action. If the action is a booking request, say so. Avoid promising an instant quote, a free assessment or a response time unless the business actually offers it.

Button labels are small, but they affect both visual hierarchy and expectations. Use one main action consistently where the same action appears across the page. Secondary actions should look secondary in the design and stay distinct in the copy. Label form fields and explain required information clearly. For a form error, tell people what to fix rather than displaying a generic failure message.

Prompt for microcopy like this:

Write the primary CTA and the form introduction for this page.
Action: [what really happens after the visitor submits].
Required details: [what the form asks for].
Do not imply [anything the business cannot guarantee].
Return 3 button labels under 4 words and a form introduction under 30 words.
Recommend the clearest option for a first-time visitor.

Review each label against the actual interaction. If a button says “Book a call”, the destination should let the visitor book or clearly explain the booking process. Design and copy should agree about what happens next.

Step 8: Review the draft for accuracy, voice and layout

Treat the first result as a working draft, not finished website copy. Review it in this order so that surface edits do not distract from bigger problems.

1. Check the message. Can the intended visitor tell what the business does, who it is for and what the next step is?
2. Check the facts. Verify every number, credential, guarantee, timeframe, location, price and performance claim against your source document.
3. Check the voice. Compare the draft with your approved examples. Remove phrases that sound like generic business copy, even if they are not on your banned list.
4. Check the page structure. Does every section have one clear job? Remove repetitions and sections that do not support the page goal.
5. Check the component. Read the copy in the actual layout at desktop and mobile sizes. Check heading wraps, card balance, button visibility and the amount of text before each action.
6. Check the interaction. Confirm that button text, form labels, confirmation messages and the real next step match.

Nielsen Norman Group’s guidance on concise, scannable and objective web writing is a useful editing lens: cut unnecessary words, make content easy to scan, and prefer specific information over unsupported promotion. Those are editorial principles, not a guarantee of a particular conversion rate.

Use Claude as a second reviewer with a focused prompt: “Review this copy against the supplied facts and voice examples. Do not rewrite it yet. List unsupported claims, vague phrases, repeated points, unclear terms and layout-limit issues. Quote the exact wording for each issue.” Fix the problems yourself or ask for a revision once you agree with the diagnosis.

Do not accept a rewrite just because it reads smoothly. Smooth language can still be inaccurate, too long or strategically wrong. Keep an approval record for claims and offers that need legal, clinical, technical or leadership review.

Step 9: Keep the brief current as the business changes

A reusable brief is useful only if it stays current. Review it when your offer, pricing, target customer, service area, process or proof changes. Remove information that is no longer true, and mark draft positioning as draft until it is approved.

When Claude repeats an old claim, check the reference files and instructions before adding another rule. The source document may be outdated, or two documents may disagree. Fix the source of the confusion, then start a fresh section prompt with the corrected information.

Save approved copy by page and date. Keep the final text separate from options you rejected. If you later ask Claude to revise a page, provide the current approved version and say what should change, what must stay and why. This makes the next task clearer than simply asking for “a better version”.

Mistakes to avoid when using Claude for website copy

Asking for a tone instead of demonstrating it

“Make it warm and professional” can produce language that sounds like hundreds of other businesses. Show a short sample, say what makes it right and add a contrasting example. Then check the generated copy against those examples.

Treating a list of banned words as the whole voice guide

A list can help you catch familiar clichés, but it cannot define your position or personality. Claude can replace a banned phrase with a different vague phrase and still miss your voice. Pair exclusions with positive instructions and evidence: what to say, how to say it and what to support.

Letting Claude invent the missing facts

If you have not supplied a price, turnaround time or customer result, Claude cannot know it. Tell it to flag missing details. Do not leave a plausible-sounding claim in place because it reads well.

Asking for the whole site before agreeing on the message

A full-site draft can create many pages of copy before anyone has decided what the business wants to be known for. Settle the audience, offer and main message first. Then draft the homepage and key service page, test the language with real customers or internal stakeholders, and extend the approved direction.

Applying the same word limit to every component

A card, hero and service explanation have different jobs. Use limits that match the wireframe and revise them after testing the copy in the design. If a strict limit makes a sentence unclear, tell Claude to identify the conflict rather than silently cutting essential meaning.

Mistaking more options for better strategy

Claude can produce many alternatives quickly, but it cannot decide which business position you should own without meaningful inputs and human judgement. Ask for a few options that explore distinct messages, then choose based on customer needs, business priorities and evidence.

When should you use a designer or brand strategist?

Claude can organise supplied material, draft options and help you find concise wording. It cannot independently confirm that your business has a distinctive position, that customers understand your offer or that an attractive phrase is true. Those decisions need research, judgement and approval from people who know the business and its market.

Bring in a brand strategist or designer when the same questions keep returning: different people describe the business in different ways; the website attracts the wrong enquiries; your offer is hard to explain; or the copy and visual identity feel like they belong to separate companies. Those are often foundation problems, not prompt problems.

A design-led process connects positioning, voice and visual choices. It asks what should be noticed first, what evidence belongs near a claim, how the page guides a visitor and how the identity stays consistent across touchpoints. If the brand foundation is unclear, AI may make the writing more polished without making it more distinctive. Learn about DesignFIT’s brand work if you need help aligning your position, voice and identity.

A simple checklist before publishing AI-assisted copy

Use this checklist before the copy goes live:

• The audience and page goal are clear.
• The offer and process are described accurately.
• Every claim, number, price and timeframe has been checked.
• The draft uses approved voice examples and avoids generic filler.
• Each heading tells visitors what its section is about.
• The sections and cards are easy to scan and not repetitive.
• Headings, paragraphs and buttons fit the actual desktop and mobile design.
• Button labels match the action and destination.
• Form labels and messages explain what the visitor needs to do.
• A named person has approved the final copy and any regulated claims.

Wrap-up: Make Claude work from a real brief

A reliable Claude prompt for website copy is a compact working brief: audience, offer, verified facts, examples of your voice and constraints from the page design. Keep those foundations in a Project, prompt one component at a time, and review every draft for truth, clarity and how it sits in the layout.

The goal is not to make every sentence sound clever. It is to help the right visitor understand your offer, trust what you say and take the next step. If your brand voice or position is still hard to define, talk with DesignFIT about brand strategy and identity.