When a service website isn't working, the problem is rarely badly written copy in the grammatical sense. The problem is vague copy. Sentences like "complete solutions with excellence and commitment" can be perfectly correct and still say nothing to someone trying to decide whether to contact you.
For me, copy is the work of helping someone quickly understand three things: what you do, whether it fits their case and what happens if they get in touch. The rest is finishing.
How I write with the client
In website projects, I write with you: you bring the business knowledge, I organize, edit and make it ready for people and search engines. In practice, that starts with written questions, not a blank page:
- How do your clients describe the problem when they come to you?
- What do they ask before hiring you?
- What don't you do, or prefer not to do?
- Which recent job explains well what you deliver?
The best raw material usually already exists: answers you send on WhatsApp, proposal emails, the explanation you repeat on the phone every week. That material carries your clients' real language and their real questions. My job is to put it in order, cut the repetition and fit each part into the right place on the page. The structure of a service page, block by block, is in a services page that brings in inquiries.
Trade adjectives for facts
The rule I use most when editing is simple: whenever a sentence relies on an adjective to persuade, I look for the fact behind it.
| Instead of | Try something like |
|---|---|
| Personalized service | You talk directly to the person doing the work, on the channel you prefer |
| Fast delivery | A written timeline in the proposal, with the stages and what each one delivers |
| Serving the whole region | In-person service in Monte Alto and nearby towns; remote for other regions |
| Guaranteed quality | An adjustment period included after delivery |
The fact can be a timeline, a process, a region, a type of client, a deliverable. It doesn't have to be a number, and if it is, it has to be a number you can back up. Unsourced percentages and client counts nobody actually made lead readers to distrust everything around them.
Write for people who scan
Few people read a web page from top to bottom. They skim the headings, read the start of paragraphs and stop where something seems to answer their question. Usability research has shown this for decades, and it changes how you write:
- Headings that say something. "How it works" beats "Differentiators"; "Timeline and payment" beats "Learn more".
- The main idea in the first sentence. If someone reads only the start of each paragraph, they should still understand the page.
- One topic per paragraph, and short paragraphs.
- Lists only for parallel items, like deliverables or steps, not to chop up an argument.
The client's words, not the provider's
Service providers tend to use the vocabulary of their trade. Clients use a different one. They don't search for "on-page optimization"; they search for "showing up on Google". They don't ask for a "visual identity"; they ask for "a logo and a site that looks like the company".
It pays to write with the words clients use and to explain the technical term when it's needed. That helps both reading and search, because people search with their own vocabulary. Another useful rule: give each service a name and always use the same one, on every page. Varying it for style only raises the question of whether they're different things.
Copy that machines can quote too
Search engines and AI assistants read a site looking for clear answers. Copy that answers direct questions with direct sentences — how long it takes, whether you work outside the city, whether the domain stays in the client's name — is easier to understand and to quote correctly.
That doesn't call for a robotic style. It calls for consistency: the same timeline, the same region and the same channels on the site, on your Google profile and on social media. I go deeper into that side in AEO for websites.
What I leave out
When editing, I cut what can't be backed up: promises of results that depend on factors nobody controls, artificial urgency like "only a few spots left", testimonials without a name or context, comparisons with competitors. A shorter, true text works better than a long one the reader has to discount.
I also avoid writing to impress other professionals in the field. The reader is the client, and they want to understand, not admire the sentence.
After launch
Website copy ages: services change, timelines change, new questions come up. That's why I leave the content in a simple CMS or in files I show you how to edit. A short review every so often — what changed, what new question appeared, which sentence nobody understood — keeps the site honest. That is, in fact, the last stage of my website creation process: keep evolving after launch.
If you have the knowledge and just need to turn it into copy, tell me what you do and I'll start with the questions.
References
- Nielsen Norman Group: How Users Read on the Web — why users scan and how to write for it.
- Nielsen Norman Group: Trustworthiness in Web Design — transparency and comprehensive content as credibility factors.
- Google Search Central: Creating helpful, reliable, people-first content — criteria for content centered on the reader.