How to collect testimonials and case studies for your site

Ask within a week of the moment a client is happiest, which is usually delivery, launch or the first visible result. Ask three specific questions instead of "could you write a testimonial", and get written permission to use their name, company and logo. Most clients will answer, the answers will be usable, and the best of them become case studies.

When should you ask?

At the high point, not at the invoice. The right moments on a typical project:

• The day the work is delivered or the site goes live.
• The first time the client tells you something worked: an enquiry from the new site, a report that took an hour instead of a day.
• The end of a long engagement, when the relationship is at its warmest.

Wait more than a month and the enthusiasm has faded; the client is onto the next thing and your request is a chore. Ask at the invoice and the request reads as a condition of payment, which it must never be.

Build the ask into the project itself. Put "collect testimonial" as the last line of the project plan with a named owner, so it happens in the delivery week rather than being remembered six months later. When we close a website design and development project, the handover call ends with the question, and the written follow-up goes out the same day.

What should you ask so the answer is usable?

"Could you write us a testimonial?" produces "Great team, highly recommended", which proves nothing. Ask questions whose answers contain the specifics a reader needs:

1. What was the problem before we started, in your words?
2. What changed as a result? If there is a number, what is it?
3. What would you say to someone who is considering working with us?

The first answer gives the reader a situation to recognise. The second gives proof. The third gives the quote. Together they are a testimonial, and with a little more detail they are a case study.

Send the questions in an email the client can answer in five minutes, or ask them on a call and write up the answers for approval. The email is short:

Thanks again for the work on the new site. Would you be willing to answer three quick questions? We would use your answers, with your approval, as a testimonial on our site. [The three questions.] A couple of sentences each is plenty. If it is easier, I can write a draft from our calls and send it for you to edit.

Offer the draft option every time. Half the testimonials on any agency's site were drafted by the agency from the client's own words and approved by the client, and there is nothing wrong with that as long as the words are true and the approval is real.

Do you need permission to publish a testimonial?

Yes, in writing, and specific. Permission to "use my feedback" is not permission to put a company logo on your homepage. The email that approves the final text should also cover:

• Name, job title and company as they will appear.
• Logo, if you will show one, and photo, if they will provide one.
• Where it may appear: website, proposals, social media.
• The right to remove it later, which you should grant without being asked. It makes people more willing to say yes.

Keep the approval email in the project folder. If the contact leaves the company and their successor asks you to take the quote down, do it that week.

The law is moving against invented and paid-for endorsements. The US Federal Trade Commission's rule on fake reviews and testimonials, in force since October 2024, bans fabricated testimonials and buying positive reviews. India's Consumer Protection Act 2019 covers misleading advertisements, and the Bureau of Indian Standards published a standard on online consumer reviews (IS 19000:2022) that the government has signalled it may make mandatory. The EU's unfair commercial practices rules treat fake reviews the same way. None of this affects a real quote from a real client. Check with your lawyer if you operate incentive schemes for reviews, since the rules on disclosing incentives vary.

How do you turn a testimonial into a case study?

A case study is a testimonial with a before, an after and a number. It is the most persuasive page on a service company's site and the one most companies never write, because it needs the client's cooperation and an hour of writing. One good case study does more than a page of quotes.

The structure that works, in order:

1. Who the client is and what they do, in two sentences. Anonymised if they prefer ("a logistics company in Sharjah with 40 staff"), but a named client is worth far more.
2. The problem, in their words where possible. What was costing them time, money or customers.
3. What was done, briefly. Readers skim this part; they care about the outcome.
4. The result, with a number: enquiries per month, time per task, page speed, error rate. If there is no number yet, say what changed and come back for the number in three months.
5. A quote, from the testimonial you already collected.

Write it, send it to the client for approval with the same permission list as above, and publish it at a stable URL such as /work/client-name. Our guide to what to put on a portfolio page covers how case studies and project listings fit together.

Where should testimonials go on the site?

Next to the decision they support, not on a page of their own. A "Testimonials" page in the menu is read by almost nobody; a quote next to the enquiry form is read by everyone about to fill it in.

• Homepage: two or three, below the services section, with names and faces.
• Service pages: one or two per page, from clients who bought that service.
• Contact or quote page: one, next to the form, that addresses a hesitation ("they explained everything in plain English").
• Case studies: their own section, linked from the menu as Work or Case studies, each with its own URL.
• Proposals: the two most relevant, every time.

One thing not to do: mark up your own testimonials with Review or AggregateRating structured data in the hope of star ratings in search results. Google's documentation on review snippets says reviews must not be "self-serving", and it gives reviews of a business placed on that business's own site as the example. The markup will not produce stars, and it can earn a manual action. Stars in search come from third-party review platforms, and from Google reviews on your Business Profile.

Should you collect Google reviews instead?

As well as, not instead. A Google review is public, shows in Maps and in the knowledge panel, and carries a stranger's trust that a quote on your own site cannot. A testimonial on your site is placed where you need it and can say more. Collect both from the same moment, with the Google review request first because it is the one most clients will not do unprompted.

The practical setup: get the short review link from your Business Profile, put it in the follow-up email, and for a business with a counter or a reception, turn it into a QR code with the QR code generator and print it. Google's policies prohibit paying for reviews or asking only your happiest customers while discouraging others, so send the same request to everyone. Our guide on Google Business Profile covers the rest of the setup.

What if clients do not reply?

Send one reminder after a week, with the draft option again. After that, let it go. A testimonial extracted by persistence is not worth the goodwill it costs, and some clients have policies that prohibit endorsements altogether, in which case ask for an anonymised case study instead; most companies that cannot endorse a supplier by name can still approve a description of the work with the name removed.

Over a year, this process produces far more usable material than any site needs. Decide at the planning stage which pages will carry which proof, which our guide on how to plan a company website covers, and the testimonials you collect will have a place to go the week they arrive.