Blog / Digital growth /

Case studies that rank and convert

“We tripled leads!” Lovely. How? Over what period? Compared with what?

Too many case studies stop at the headline. The page might win a click, but a prospective customer can’t tell whether the work applies to them.

A strong case study tells a specific, approved story: where things started, the decisions made, the work done and what can be verified afterwards. It should leave the reader better informed, not just impressed. Search can bring the right person to the page. Honest evidence helps them decide what to do next.

Get permission before you write

Confirm the client has approved the story and every detail you plan to share. Removing a name doesn’t make a project anonymous. A niche, location, product range or timeline can still give the client away.

Agree what can go public: company description, screenshots, metrics, quotes, process details, names. Keep a record of the approval and the version reviewed. If an NDA covers the work, I don’t publish details without explicit permission from whoever can give it.

If no real case can be shared, do not invent one. You can publish a process article, a clearly labelled hypothetical example or an explanation of how you approach a problem without pretending it happened to a client.

Explain the starting point honestly

Describe the context that matters to the work. What problem did the organisation need to solve? What constraints shaped the plan? What was already in place? Give enough detail for the reader to understand the decisions, while protecting information that should stay private.

Don’t paint the starting point as a disaster just to make the outcome shine. If data was limited or the timeline changed, say so (if approved). An honest account is more believable than a story without trade-offs.

If you’ll discuss results, define the baseline: the metric, the period, the source and what else changed. Seasonality, campaigns and migrations all move search traffic, so don’t credit one intervention without evidence.

Show the work, not just the headline

Explain what the team actually did and why. That might include research, technical fixes, content changes, implementation or coordination. Describe the sequence and the decision points, not every routine task.

A reader should be able to see the connection between the problem and the work. If the case study concerns a collection page, explain how the page was selected, what changed and how the team evaluated it. If the work involved site performance, show the technical issue and the way it was tested.

Use screenshots or diagrams only when they add understanding and the organisation has approved them. Remove customer data and internal identifiers. Add text descriptions where images carry important information so the page remains accessible.

Present results with limits

Use numbers only when the source is reliable and the client has approved publication. Explain what the number represents. A percentage increase needs a baseline; a ranking claim needs the query, location and date context; a revenue figure needs an agreed definition and attribution method.

Distinguish observed change from causal proof. “Organic clicks rose during the period” is different from “the SEO work caused the rise.” If several initiatives ran together, say that the contribution cannot be isolated. If results are mixed, include that rather than hiding it.

Don’t promise the next client the same outcome. A case study shows what happened in one context. Say which conditions may differ and what a new project would need to assess.

Connect the story to the reader’s next question

A case study can rank for a specific problem or service query if the page answers that query clearly. Use a descriptive title, a direct opening and headings that follow the reader’s questions. Keep the company and service names accurate, but do not cram keywords into every heading.

Link to related service pages and practical resources where they help. A case study shouldn’t turn into a sales page in disguise. I’d rather end it with a natural next step: a question, a note on how an assessment works, or a relevant guide.

Use a clear summary for skimmers, but preserve the detail that makes the story credible. A page with only challenge, solution and results headings can feel generic if each section says nothing specific. Writing for skimmers: formatting that keeps people reading can help with the structure without stripping away useful context.

Measure its usefulness over time

Search Console can show the queries and pages that earn search impressions. Analytics may show how people use the page if tracking is configured appropriately. Ask the sales or support team whether the case study helps answer questions, but do not treat a page view as proof that it closed a deal.

Review the page if the service changes, if the result is no longer representative or if the client asks for an update. Add a date to the internal record and keep the public page accurate. If permission expires or the organisation withdraws approval, follow the agreed process.

For content measurement, see Measuring content performance without vanity metrics and How I report SEO results to clients.

Before you publish, check who approved each claim, image and metric. What evidence can you show that lets a reader judge the work without exposing the client?