Preferences

Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. More information (Cookie Policy)

How to Write a Case Study: A Step-by-Step Guide With Examples

Learn how to write a case study step by step: choose the customer, collect the facts, structure the story, write the results and publish it safely.

Published on
19/11/2026
Updated on
19/11/2026
Reading time
25 min
How to Write a Case Study: A Step-by-Step Guide With Examples

Tools

On this page

In short

A case study tells one customer's story in a fixed order: who the customer is, the problem they had, what you did together, and the result, with the method used to measure it. To write one, pick a typical customer with a result you can explain, collect the facts and a baseline before you draft, and get written approval before you publish. Keep every claim exact, because the FTC's rule on testimonials and Google's review guidelines both set limits on what you can publish and how you mark it up.

Want to go further? Ask

Quick quiz

How should you run your blog?

Question 1 of 425%
Why do you want a blog?

What a case study is, and what it is not

A case study is a long-form story about one customer. It names the customer, describes the situation before the work, shows what changed and how, and ends with a result the reader can check. It is written for someone close to buying: a founder, a marketing lead, or an SEO who has to justify a budget to a manager.

It is not a testimonial. A testimonial is one or two sentences of praise. A case study does the job a testimonial cannot: it shows the reader the path from problem to result, so they can judge whether the same path fits their company.

Testimonial or case study?

Testimonial
  • One quote, no context
  • No method shown
  • No measured result
Case study
  • A named customer and their starting point
  • The method, step by step
  • A result with its baseline and source

Why buyers read them

Buyers read case studies because they are looking for a company like theirs. A good case study answers three questions for them: is this company like mine, did they start where I am, and what did they do that I could copy? Write for those questions, in that order. If the reader cannot answer the first one in the opening lines, they will leave before they reach your method.

What makes a case study worth the time

Two things: a specific customer and a result that is hard to fake. A story about a famous brand with no numbers is an advertisement. A story about a small company with a clear baseline and a stated method is evidence. Most of the work is in the second part: finding the baseline and explaining the method in plain words. For the storytelling side of the job, see brand storytelling, which covers how to make the story itself memorable.

Pick the customer, then collect the facts

Choose a typical customer, not only the biggest

The biggest logo is tempting. It is also the least useful for most readers, because their company is smaller, has fewer people and a different setup. Pick the customer whose situation is most common among the people you want to reach. If that customer is a ten-person agency, a ten-person agency is the right case study, even if it looks less impressive on a slide.

Choose a customer who is willing to talk, too. A customer with a good result and no time for an interview will give you a weak story, because you will have to guess the details, and readers can tell when a story is guessed.

Choose a result you can explain

A result is usable when you can answer four questions: what was the starting point, what changed, over what period, and how did you measure it? If you cannot answer the fourth one, do not put the result in the headline. Look for a smaller result you can measure, or for a different customer.

CriterionGood signWarning sign
FitSame size, sector or problem as your target readerOnly fits a company with a large budget
BaselineFigures from before the project, with dates"We were struggling", with nothing to compare
MeasurementA named source, such as a Search Console export or an analytics reportNumbers with no source
WillingnessAgrees to an interview and a review of the textAgrees by email, then never answers
PermissionWritten approval for the name, the logo and the figuresA verbal "fine by me"

Get written permission before you spend time on it

Ask early, in writing, for the right to tell the story, use the name and logo, and publish each figure. Approval at the start is not enough, because the customer will read the final text and may reject a phrase or a number. Keep the approval next to the draft, so you can show it later. The legal side of testimonials is covered in the section on the FTC rule below.

Collect the facts before you write a word

Most weak case studies come from a writer who starts drafting before the facts are complete. Build a fact sheet first. Then run one interview, record it, and only then write. This order saves time, and it keeps the quotes accurate.

The fact sheet

Fill in these fields before the interview: the customer's name and sector, their size, what they sell, the service you provided, the start and end dates, the baseline figures and their source, the results and their source, and the main objection the customer had before they bought. Share the sheet with the customer so they can correct it. A wrong detail about their own company costs you more trust than a missing one.

Facts to collect before the interview

  • Customer name, sector and size
  • Starting situation, with a date
  • Baseline figure and where it came from
  • Result figure, period and measurement method
  • The objection the customer had before buying
  • Your scope of work, in plain terms
  • Permission to publish, in writing

Ask for the baseline and the measurement method

For a search case study, the baseline is usually organic clicks or sessions from Google Search Console or your analytics tool, for a fixed period before the work started. Compare it with the same measure for a fixed period after. Write down the date ranges, the site or property, and any filters. If the customer used a different report, record which one. A result that nobody can reproduce from the report is not a result you should publish.

In Search Console, open the Performance report, set the date range, then add a page filter and choose Custom to write a regular expression. Google announced that filter in its April 2021 note on data filtering, and the same note says the comparison mode supports it too. A pattern like the one below isolates the URLs of one service area, so the baseline and the result cover the same pages. Search Console keeps 16 months of data, so export the baseline months now, before they drop out of the window.

/(services|pricing|case-studies)/

Watch out for seasonality. A tourism site looks weaker in winter whatever you did, and a shop looks stronger in November. Compare the same months one year apart where you can. If you cannot, say clearly in the text that the period was seasonal.

The interview: questions that get real answers

Record the call with permission, and keep the recording. Ask open questions, then follow up on every number. These questions work well:

  • What did your team try before us, and why did it not work?
  • What had to be true for this to be worth the money?
  • What did the first month look like, and what did you change?
  • Which result surprised you, and which one did you expect?
  • Who else in the company was involved, and what did they say?
  • What would you tell a company that is in your position today?

Keep the quotes in the customer's own words. Tidy the grammar, but not so much that the voice disappears, and never put a sentence in their mouth that they did not say.

Isometric illustration of a story document with a rising blue chart, a quote bubble and check marks
A case study is a story with a starting point, a method and a result you can check.

Write the case study, step by step

This is the practical part. Follow the steps in order. Each one produces something the next step needs, so skipping one usually means rewriting later.

Six steps from brief to published story

  1. Write the summary sentenceCustomer, method and change, in one line.
  2. Draft the challengeUse the customer's own words for the problem.
  3. Describe the methodList each action in order, with the reason for it.
  4. Show the resultOne figure, with its baseline, period and source.
  5. Get approvalThe customer confirms the full text and each figure.
  6. Publish and linkA stable URL, a visible date, links to the pages you name.

Step 1: Write the summary sentence first

Before the first paragraph, write one sentence that contains the customer, the method and the change. For example, with a made-up case: "A regional dental clinic rebuilt its service pages around the questions patients ask, and its organic calls rose over six months." If you cannot write that sentence, you do not have a case study yet. You have a project. The same sentence becomes your meta description and the first line of your social post, so it is worth getting right.

Step 2: Draft the challenge in the customer's words

The challenge is where most writers lose the reader. Describe the situation the way the customer would have seen it, with the symptoms they noticed: fewer leads, pages that did not appear in search, a sales team that kept asking for better content. Name the cost of doing nothing, if the customer gave you one. Keep it to one or two paragraphs. A reader who sees their own problem in the first lines keeps reading.

Step 3: Describe the method, not only the tool

Readers copy methods. They rarely copy tools. For each action, write what you did, why you chose it, and what the customer had to do. For a search project, that might be an audit of the pages that already got impressions, a rewrite of the titles that sat just outside the first page, and a review of the internal links between the service pages. Each action needs its reason in the same sentence.

Mention the trade-offs too. If you chose not to do something, say so and say why. Expert readers trust that part more than any list of wins.

Step 4: Show the result and how you measured it

Lead with one headline figure, then give the baseline, the period, the source and the scope. "Clicks went up" with no period is a claim. A result with a baseline, a period and a named report is evidence. Put the source in the text, not only in a chart, so a reader who skips the chart still sees it.

Keep one measure per result. If you show clicks, impressions and revenue together, the reader will ask which one moved the business, and they will be right to ask.

Step 5: Get approval on the final text

Send the full text, not a summary, and ask for a yes or no on each figure. Note the date and the version of the approval. If the customer asks you to remove a figure, remove it, even if you think it is the best number in the story. A story without that figure is still a true story.

Publish on a stable URL, with a visible publication date and an updated date each time you change a figure. Link to the service the customer used, to the pages that explain the method, and to related articles. A case study without links is a dead end, and a few relevant links keep the reader on your site. Sorank's public case studies show one way to lay out a set of stories, so you can compare your draft with a published page.

The structure, section by section

A good structure is plain on purpose. Readers scan case studies. They want to find the customer, the problem, the method and the result in a few seconds, then decide whether to read on. Use the same order every time, so a reader who has read one case study knows where to find things in the next.

The headline

Name the customer or the sector, the change and the time frame. Keep it factual. The headline is a claim you must defend in the first paragraph, so do not write anything you cannot support. Avoid words like "incredible" or "explosive". They are promises, and the reader will check them.

The snapshot: three to five points

Right under the headline, add three to five bullet points: the starting point, the headline result with its figure, the period, the main methods, and the customer's own one-line verdict. A reader who only reads this block should still know what happened.

Customer introduction and challenge

Use two short paragraphs. Introduce the customer in one sentence: what they sell and to whom. Then describe the challenge with the detail from your interview. Do not describe your company here. The reader is not interested in you yet, only in whether the customer looks like them.

The solution and the parts that changed the result

Describe what you did in the order it happened, then stop at the decisions that changed the result. A long list of features makes a case study read like a product page. A short list of decisions, each with its reason, reads like a method, and a method is what the reader came for.

Results, quote and next step

Show the results with their baseline and method. Add one quote from the customer, ideally about a change they saw, not about how pleasant your team was. End with one clear next step for the reader: a page to visit, a question to ask, or a free tool to try. Keep it to one call to action, so the reader does not have to choose.

Sorank's public case studies follow a similar order, from the headline to a question-and-answer block at the end. The Althévia page is one example, so you can compare its layout with your draft.

Public Sorank case study page with headline, key points, challenge, actions, results and questions and answers
A public Sorank case study page, from the headline to the questions and answers.

Three storytelling frames, compared

The same facts can be arranged in three frames. Each one serves a different reader and carries a different risk. Choose the frame before you draft, because the frame decides where the result goes and how long the piece will be.

Challenge, solution, result

Principle: three blocks, each answering one question: what was the problem, what did we do, and what changed.

When to use it: landing pages, sales decks and short summaries, where a buyer needs the logic in a few seconds.

Advantages: it is fast to scan, easy to template across customers, and consistent to read.

Limits: it hides the decision, the doubts and the timeline, so the story can sound generic. A reader who has seen five of these stops after the second block.

Example: "Challenge: reviews of search performance were manual and late. Solution: a weekly report with the three changes that mattered. Result: the review moved from several days to one meeting."

Chronological narrative

Principle: tell the story in time order, from the first conversation to the most recent check-in.

When to use it: multi-phase projects such as migrations, rebuilds and programmes that run over several quarters.

Advantages: it shows the work and how long it took, which is exactly what a buyer planning a similar project needs to know.

Limits: the result arrives late. Put the headline result in the snapshot, or readers who stop early will miss it.

Example: "In the first week, the team listed every report it produced. In week three, the first automated version went live. By the end of the quarter, the review was one meeting."

Quote-led

Principle: open with a sentence from the customer, then prove it with the rest of the story.

When to use it: when the customer is a strong speaker, and for video, audio and social cut-downs.

Advantages: it sounds human, and readers share it.

Limits: a striking quote can cover a vague result, and readers notice when the proof is thin. Always follow the quote with a measure.

Example: "We finally know which pages matter before we write anything." The next paragraph gives the baseline, the period and the source.

FrameBest forMain riskTypical length
Challenge, solution, resultLanding pages and sales decksGeneric toneShort
Chronological narrativeMulti-phase projectsLate result, lost readersLong
Quote-ledVideo, social and podcastsVague praise without proofShort to medium

In practice, open with the quote, use the timeline for the body, and close with a challenge, solution and result summary. That gives the reader the voice, the work and the logic in one piece.

Prove the results without overclaiming

The results section decides whether the rest of the story is believed. A reader who sees a large figure with no baseline assumes the worst. Four rules keep your claims honest: name the baseline, name the period, name the method, and name the other changes.

Name the baseline and the window

A result is a difference between two states. Write down the starting value, the end value and the window between them. For search, that might be organic clicks per month in the month before the project and in the sixth month after, measured in the same tool on the same set of pages. Name the tool. Search Console and an analytics tool often disagree, so choose one and say which.

Example

Invented figures, for illustration only: a team reports 1200 organic clicks in the month before the project and 4000 in the sixth month, from Search Console, on the same set of pages. A careful reader can check that sentence. "Our traffic exploded" cannot be checked, so it cannot persuade them.

Separate your effect from everything else

Something else changed during the window: a seasonal peak, a new campaign, a product launch, a change in how search engines show results. List those changes in one short paragraph. It does not weaken the story. It makes the claim credible, and a sales team can repeat it without fear. Use "after" rather than "because of" when you cannot isolate your part.

Present the numbers as the source reports them

Round only with the customer's agreement, and never in your favour. If the customer says "about a third", write "about a third" unless the exact figure is in their report. Use the same unit and the same format throughout the text, the table and the bullet points.

Two ways to state the same result

Before
  • "Our visibility skyrocketed"
  • Which tool, which pages, which months: unknown
  • Other changes never mentioned
After
  • Organic clicks per month, from one named report
  • Baseline month and last month of the window stated
  • Other changes in the same window listed

Write headlines and results people remember

The headline and the results figure are what people repeat. Get them right, and your case study is easier to share, easier to quote, and easier for a search engine to match to the question someone typed.

A headline formula that stays honest

Use this pattern: customer or sector, then what changed, then the period. For example, "How a furniture store grew its organic sales in one year" is less exciting than "How a furniture store doubled its search revenue overnight", but you can defend the first one. The second is a promise about the result, and the first one is a description of the work.

Turn a vague result into a precise one

"Our traffic grew a lot" becomes a sentence the reader can check: organic clicks from Google, in one report, rose from the figure in the baseline month to the figure in the last month of the period. Explain the change in terms the reader can verify. If the number is modest, say so. A modest figure that is exact earns more trust than a large figure nobody can trace.

Vague headline or checkable headline

Before
  • Superlatives with no facts
  • No customer named
  • No time period
After
  • Sector and size named
  • The change is specific
  • A fixed period

Check the headline before you publish

Search results cut long titles, and a headline that works on a slide can be unreadable in a results list. Check the length and the wording before the page goes live.

Tip

Run your draft headline through the free Headline Analyzer from Sorank. It scores the title before you publish, so you can fix the length and the wording in one pass.

Five case study formats, compared

A written page is not the only option. Each format fits a different job, and one story can be cut into several. Here are five formats, what each one is for, and where each one falls short.

1. The long web case study

Principle: one full story on one page, with headings, detail and the complete method.

When to use it: for search, for sales teams who send a link, and for AI assistants that read your site.

Advantages: it can rank, it holds the detail, and it lives as a page you can link to from anywhere on your site.

Limits: it takes the most time to write and to keep up to date.

Example: a snapshot at the top, the method in the middle, and a question-and-answer block at the end.

2. The one-page PDF

Principle: the same facts on one downloadable page, for a sales conversation.

When to use it: when the buyer has to forward something to a manager who will not click a link.

Advantages: easy to share inside a company, and easy to print.

Limits: search engines index a PDF less reliably than a page, and it goes stale in a folder nobody opens.

Example: one side of an A4 sheet with the challenge, three results and a short quote.

3. The video interview

Principle: the customer tells the story in their own voice, cut to two or three minutes.

When to use it: for brands whose buyers trust people more than text, and for events where the story can be shown live.

Advantages: the voice is hard to fake, and viewers feel the customer's credibility.

Limits: expensive to produce, and invisible to search engines unless you add a full transcript on the same page.

Example: the customer on camera describing the one decision that changed the result, with the transcript below the video.

4. The short social card

Principle: one result, one image, one line, pointing to the full story.

When to use it: for distribution on LinkedIn or X, where most people never click through.

Advantages: cheap to make, and you can publish one every week.

Limits: no method, so the reader cannot judge the result, and it should never stand alone.

Example: a card with the headline result, the period and a link to the long case study.

5. The multi-customer benchmark report

Principle: several customers in the same sector, combined, with the methods they shared.

When to use it: when you want authority in a category, or when no single customer can be named.

Advantages: more weight than one story, and more useful to a reader who is not in the same position as any one customer.

Limits: it needs clean data from several customers, and clear rules on how you combined the figures.

Example: a report showing the methods customers in one sector used, and the range of their results, with the same measurement rules for each.

FormatBest forMain advantageMain limitEffort to produce
Long web case studySearch and sales linksCan rank, holds detailTakes time to keep currentHigh
One-page PDFForwarding to a managerEasy to shareNot indexed like a pageLow
Video interviewTrust and eventsCredible voiceCostly, needs a transcriptHigh
Short social cardDistributionCheap and frequentNo method shownLow
Benchmark reportAuthority in a categoryWeight and usefulnessNeeds several customersHigh

Note

Start with the long web case study, then cut the other formats from it. Going the other way, from a social card to a full story, usually leaves the method missing.

Make it readable to Google and AI assistants

A case study is a page like any other. Search engines have to find it, read it and understand what it is about. Three things help: a clear URL, a page that answers its question on the first screen, and the right structured data.

One story, one page, one clear URL

Give each customer its own page, with a URL that names the customer or the sector. Do not bury the story behind a carousel or a form. Crawlers cannot read a form, and most readers will not fill one in to see a case study.

A listing page helps readers choose. Sorank's public listing filters its case studies by sector, so a reader can jump straight to their own industry.

Sorank case studies listing with sector filters and one card per customer story
The public listing of Sorank case studies, filtered by sector.

If your team publishes case studies at volume, the workflow matters more than the page. Sorank's page for content teams describes how a team plans and publishes at that pace: Sorank for content teams.

Mark up the page as an article, not as a review

Use Article structured data for a case study page. A customer story is not a review of your product, and Google's review snippet guidelines are strict about reviews that a business controls itself. Here is a minimal example. Replace the placeholders in brackets, and check the result with a structured data validator before you publish.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "[Customer and result, as in the headline]",
  "datePublished": "[YYYY-MM-DD]",
  "dateModified": "[YYYY-MM-DD]",
  "author": {
    "@type": "Person",
    "name": "[Author name]"
  }
}
</script>

Warning

Google's guidelines say that when the entity being reviewed controls the reviews about itself, pages that use LocalBusiness or any other Organization structured data are not eligible. Do not add review ratings about your own company or product to your organization page or to a case study page.

Link the story to the pages it talks about

A case study that names a method should link to the page that explains the method. If your story is about content, link to content marketing examples for a wider set of cases. If it is about how proof supports a sales page, link to social proof marketing.

Stay within the rules on testimonials and quotes

A case study uses a customer's words and figures, so the rules on testimonials apply to it. In the United States, the FTC's rule on consumer reviews and testimonials took effect on October 21, 2024. The FTC's questions and answers on the rule, published in November 2024, explain how staff read it. The rule is codified at 16 CFR Part 465.

Two dates for testimonials in the United States

Oct 21, 2024The FTC rule on consumer reviews and testimonials takes effect.
Nov 2024FTC staff publish their questions and answers on the rule.

Source: FTC, Consumer Reviews and Testimonials Rule: Questions and Answers

What the rule targets

The FTC's page says the rule's misrepresentation section covers what a reviewer or testimonialist says about their experience with a product or service. It does not address merely their opinion of it. For a case study, that means each sentence attributed to the customer must match what they told you and what they can support. Do not tidy a quote until it says something they did not say, even if the meaning is close.

The same page says that people who lie about having used a product or service can be liable, and it notes that fake reviews have polluted the marketplace. Treat every quote as a statement you would have to defend.

Incentives and disclosure

If you gave the customer a discount, a free month or a fee for the interview or the quote, say so next to the quote. Google's review guidance is blunt on this point: "Don't include fake or undisclosed incentivized reviews on your page or in your structured data markup." Never make the approval of a story depend on a positive verdict. A customer who feels pressure to praise you will give you a quote that reads as fake.

Google Search Central page on review snippet structured data guidelines
Google's review snippet guidelines, including the rule on fake and undisclosed incentivized reviews.

Anonymous and composite stories

Sometimes a customer cannot be named, or you want to combine several projects into one story. That is allowed if you label it. Write "a composite of three clinics" or "a logistics company that asked not to be named", and describe the sector and size precisely. Do not present a composite as one real, named client. Our guide to review schema covers which markup fits which page, if you are unsure where a story belongs.

Warning

This section gives general information about US rules and Google's guidelines. It is not legal advice. For your own case, check with a lawyer, especially if you sell in France or the EU, where other rules on advertising and personal data also apply.

Common mistakes, and how to fix each one

These are the mistakes that show up most in weak case studies. For each one, you will find what it is, how to spot it in your draft, and how to fix it.

Mistake 1: A result with no baseline

What it is: a headline that says clicks went up a lot, with no starting point, or with a starting point taken from a different period than the result.

How to spot it: read the headline figure and ask, compared with what? If the answer is not in the text, the figure has no baseline.

How to fix it: put the baseline period, the result period and the data source next to the figure. If the baseline is not available, say so, and choose a different result to publish.

Mistake 2: The story is about your product

What it is: the case study reads like a feature list, and the customer appears only in the quote at the end.

How to spot it: count the sentences where your product is the subject, then count the sentences where the customer decides something. If your product wins by a wide margin, the draft is a product page.

How to fix it: make the customer the subject of the decisions, and mention your product only where it made a specific difference, with the reason.

Mistake 3: Causation claimed without evidence

What it is: the text says your work caused the result, when other changes could explain it: a seasonal peak, a competitor's outage, a price change, a new product launch.

How to spot it: look for "because of", "thanks to" and "led to" with no second source behind them.

How to fix it: write what happened in sequence, list the other changes the customer made in the same period, and say that the link between your work and the result is your reading of the data, not a controlled test.

Mistake 4: A quote that could be about anyone

What it is: "Working with them was a fantastic experience." The sentence is pleasant and empty.

How to spot it: remove the company name and check whether the quote still fits any vendor in your category. If it does, it adds nothing.

How to fix it: in the interview, ask for a sentence about one specific change: what they did differently, what they noticed first, and what they would tell a peer who is in the same position.

Mistake 5: Changing a figure after approval

What it is: the customer approves the text, then you update a number or add a sentence before publishing.

How to spot it: compare the final page with the version the customer approved, line by line. Check the figures first, because they are the most sensitive.

How to fix it: send the exact final version, ask for a yes on each figure, and keep the approval with the page file. If you must change anything, send it again.

Mistake 6: No date and no update rule

What it is: a case study from two years ago describes a tool or a method that no longer exists, and the page shows no date, so the reader cannot tell.

How to spot it: check whether the page shows a publication date, and whether every tool and method it names still exists.

How to fix it: show the date, add an updated date each time you change a figure, and take the page down or label it clearly when its result is no longer true.

Before you publish

  • The customer approved the final text in writing
  • Every figure has a baseline, a period and a source
  • The quote is in the customer's words and names a specific change
  • Other changes during the period are listed
  • The page shows a publication date and an update rule
  • The markup is Article, not Review
  • A composite customer presented as a real, named client
  • A year in the headline, unless the result depends on it

Measure whether your case studies work

A case study has a job. It might bring search visitors, help a sales call, or support a claim in an AI answer. Decide the job first, then pick the metric that fits it, so you do not judge a sales story by search traffic or a search page by sales calls alone.

MetricQuestion it answersWhere to read it
Clicks and impressions on the case study pageDoes the story appear for its own searches?Google Search Console, page report
Visits from AI assistantsDo assistants send readers to the story?Referral reports in your analytics tool
Sales calls that mention the storyDoes the story help close a deal?CRM notes or call tags
Shares and forwardsIs it useful enough to pass on?Social and email analytics
Cost per storyIs it worth producing?Your time and budget records

To compare the cost of a story with its return, estimate the value of the traffic it brings and the time it took to produce. Then review the page again at fixed points, for example after 30, 90 and 180 days, and compare each reading with the baseline you wrote down at the start.

Tip

The free Content Marketing ROI Calculator from Sorank helps you turn the traffic and the cost of a story into a return you can compare with other projects.

For a wider view of how to set these measures up, read content marketing metrics and KPIs.

Do this week:

  1. Pick one customer who matches your most common reader, and check that you can name a baseline for them.
  2. Write the summary sentence, then the fact sheet, before you book the interview.
  3. Send the approval request in writing, with the permission to publish each figure.

Frequently asked questions

How long should a case study be?

There is no fixed length. Make the result visible on the first screen, give the method in order, and cut any paragraph that does not help a buyer decide. A long page is fine when every section answers a question the reader has.

Do I need the customer's permission to publish a case study?

Yes. Get written approval for the story, the name, the logo and each figure. Let the customer read the final text, and keep their approval next to the draft.

Will a case study help my search rankings?

Not on its own. A specific case study can rank for its own searches and earn mentions, but its strongest effect is on the reader who compares vendors and needs proof.

Get your content plan for 30 days for free

We analyse your competitors, your website and your AI visibility to create a tailored content plan for free.

Our free SEO tools

See all our free tools

Get your content plan for 30 days for free

We analyse your competitors, your website and your AI visibility to create a tailored content plan for free.

Man with dark hair and beard wearing a light brown shirt speaks in front of a microphone on a podcast or recording setup.Portrait of a man with short dark hair wearing a white shirt and dark jacket, looking directly at the camera with a neutral expression.Man with short dark hair, beard, and clear glasses wearing a black t-shirt with a white circular logo, standing in front of a stone wall.Celio fabianoSmiling young woman with long brown hair wearing a red top and necklace, outdoors in a tree-filled background.Profile photo of Xavier Breull, Sorank customer
Google
Solid yellow five-pointed star icon on transparent background.Solid yellow five-pointed star icon on transparent background.Solid yellow five-pointed star icon on transparent background.Solid yellow five-pointed star icon on transparent background.Solid yellow five-pointed star icon on transparent background.
5/5
+5,000
users

Testimonials from ambitious founders

0 to 10000 visitors in 5 months

Celio Fabianomonrobotlavevitre.frGoogleE-commerce

0 to 5000 visits in 8 months

Thibault BMsorank.comGoogleSoftware

0 to 1104 clicks in 4 months

Dominiqueflight-sensations-idf.comGoogleLeisure and aviation

0 to 163 clicks in 6 months

Coworking Pariscoworking-paris.frGoogleOffice broker

x92 clicks in 7 months

Guide Zanzibarguidezanzibar.comGoogleTravel