How to write a case study page that ranks and convinces

Use one shape every time. It makes writing fast and helps buyers compare. It also gives search engines clear sections to understand.

• Who the customer is in two lines: name, size or type, what they do
• The problem in their words: one short paragraph or three bullets, a direct quote if you can
• What was done: steps you took and the product’s role, clear and plain, no fluff
• The result with a figure the customer gave and approved, never inferred or modelled
• A quote with a real name and company, permission in writing
• What your product did, named plainly, not claims about the market

This shape ranks on the customer’s brand plus your category and on X for Y searches, like “CRM for interior designers”. Keep each section scannable. One idea per paragraph.

Choose a customer your next buyer will recognise as close to them. Sector, size, and job-to-be-done matter more than famous names. You want clear alignment, not reach.

• Segment by outcome: faster onboarding, fewer support tickets, cleaner data, more qualified demos
• Segment by context: migration from spreadsheets, switching from a known rival, first tool in the stack
• Name the category the buyer uses: “email validation for SaaS”, not your internal term

Aim each case study at one buyer query. Examples: “<Customer> + <your category>”, “<Rival> to <YourProduct>”, “<Category> for <Industry>”. Do not chase broad inspiration keywords on a case study. Save those for a guide or a gallery page.

Ask for permission before you draft. Explain why it helps them: they get a link, accurate messaging, and fewer off target enquiries to their team. Send a one page brief with the sections you will write and what you need from them.

1. 1

   Secure the yes

   Email a short request. State the sections, the review point, and that you will only publish with sign off. Offer to draft quotes for them to edit.

2. 2

   Book a 20 minute call

   Record with consent. Ask: what was hard before, what changed, what surprised them, how they measure success. Ask for a figure they can share.

3. 3

   Agree the figure

   The result must be their number, in their words. You never infer or model it. If they cannot share a metric, use a concrete outcome they accept.

4. 4

   Get written approval

   Share the draft as a Google Doc. Mark the quote, the figure, the logo and the screenshots. Ask them to confirm each in a comment.

Offer options when numbers are sensitive. A range, a ratio, or a relative change can be fine if they suggest it. If they cannot share a result, publish the story without one and be upfront about it. Do not pad with industry averages. As of 2026, published averages vary and do not apply to your product or definition.

Make the page discoverable and useful the moment it loads. Write for the searcher who typed the query and for the buyer who scans on mobile.

• Title tag, about 60 characters: include “case study” and the category, for example “Case study: interior design CRM that saves time”
• H1: match the case outcome or the use case, not the company slogan
• Meta description, 120 to 155 characters: state who, the use case, and the outcome in their words
• URL: /case-studies/<customer>-<use-case>
• Intro: two sentences that say who the customer is and what changed
• Pull-quote near the fold, with a name and company
• Result box: one line with the figure and the timeframe, placed where the “what was done” ends
• Images: real product screenshots and one customer photo if allowed, with alt text that names the screen
• Internal links: to your category page and to one guide that answers the same job-to-be-done
• CTA: one per page, placed after the answer section, phrased as the next step, for example “start your import”, “see pricing”, or “check your site”

On small sites, trust signals decide whether the visitor books a demo or bounces. Add signals you can show honestly: real names on your About page, a postal address, a company registration, a security page that explains encryption and data location, a status page, a changelog with dates, screenshots of the real product, customer logos only with permission, quotes with a name, a visible support address, clear terms and privacy, and links to third-party reviews.

Mark the page up as an Article in JSON-LD. It helps search engines see the headline, author, datePublished and the mainEntityOfPage. Use the Rich Results Test to check it parses. Do not fake reviews or ratings on a case study page.

• Required fields: headline, image, datePublished, author, mainEntityOfPage
• Optional but useful: about, keywords, articleSection matching your shape
• Breadcrumbs: add site wide, they aid sitelinks and help the user go back to /case-studies

Keep Core Web Vitals in the green. Images should be compressed, sized and lazy-loaded. Aim for Largest Contentful Paint at or under 2.5 seconds, Cumulative Layout Shift under 0.1, and Interaction to Next Paint under 200 ms. Do not block content with a modal. Interstitials that cover content on mobile are penalised. Serve the visitor who came for the query before you sell them anything.

A case study will not rank for broad gallery terms. It should rank for specific buyer searches that match the story on the page. Pick one primary query and two supporting queries and write to them directly.

• Branded plus category: “<Customer> <your category>”
• X for Y: “<category> for <industry>” that matches the featured customer
• Switching intent: “migrate from <rival> to <your product>”
• Problem phrased in their words: “clean up duplicate contacts in <tool>”

Map the query to intent. If a query is informational, answer first, then offer a next step. If the page answers the query but the next step is missing or below the fold, add a clear CTA where the answer ends. If the visitor is not the buyer, accept that no change will convert them. Use product analytics that join landing pages to signup or demo events to tell these apart.

Copy this into your editor and replace the brackets. Keep each part short. Keep the customer’s voice where quoted. Do not add adjectives you cannot prove.

Title tag: Case study: <category> for <industry> at <Customer>
H1: How <Customer> <plain outcome> with <YourProduct>
URL: /case-studies/<customer>-<use-case>
Meta description: <Customer> used <YourProduct> to <job-to-be-done>. They say <their short quote>. See what changed and how they made it work.

Intro
<Customer> is a <size/type> that <what they do>.
They needed to <job-to-be-done> without <constraint>.

Who they are
Two lines on the company: <what, where, who uses it>.

The problem, in their words
“We needed to <problem in their exact words> because <trigger/event>.”: <Name, Role, Company>

What we did
- Step 1: <what was tried or migrated>
- Step 2: <how you implemented it>
- Step 3: <what the team changed in their process>
Product’s part: <name the features used in plain words>.

The result, with their figure
<Result in one line, using the customer’s approved figure and timeframe>.
Context: <one sentence that explains how they measured it>.

Quote
“<Short proof quote that mentions the outcome or experience>.”: <Name, Role, Company>

Screenshots
- <Screen name>: <what the image shows>
- <Screen name>: <what the image shows>

What they used
- <Feature A> for <job>
- <Feature B> for <job>
- <Integration> with <tool>, if any

Next step CTA
<One sentence that matches the page’s answer, for example “Start your import” or “See pricing”.>

A good finished page looks like this: a clear headline in their terms, a one line result near the fold, a short “what we did” that names the parts used, a quote with a real person, and screenshots that match the story. The CTA sits where the answer ends, not in a modal.

Use one CTA on the page. Phrase it as the next step in the reader’s terms. Place it where the answer ends. Do not interrupt reading with a popup. Interstitials reduce trust and can hurt ranking on mobile as of 2026.

Measure conversion using your own product analytics. A landing page conversion rate is conversions divided by sessions that began on the page. A signup conversion rate is accounts created divided by visitors of the signup path. A trial to paid rate is paying accounts divided by trials started in the same cohort. Ignore industry averages. Only your site’s rates over a period with a few hundred sessions matter.

• Documented friction to remove: extra fields on signup, a card before the product is seen, email verification before the first screen, password rules that reject real passwords, no SSO, and vague error messages
• Match plan names on the page to the app, docs and emails, if you link to pricing
• If you run a free trial, say that it is time-limited and full product. If you run freemium, say that it is free forever with limits. These are different models and set different expectations

Join Search Console data with product analytics. Look at which case study pages bring clicks, which ones start sessions that convert, and which queries lead to them. Then adjust copy and CTAs by intent, not by traffic alone.

• If impressions rise without clicks, improve the title and meta description. Use the customer’s words and the category name
• If clicks rise without conversions, check intent and the next step placement. Add the CTA where the answer ends and show trust signals
• If the visitor is not the buyer, accept it. Students, competitors and agencies will read but not convert. Do not add more banners

Refresh the page when the customer’s situation changes. Update screenshots, quotes and the result if they approve a new figure. Show a datePublished and dateModified in your Article markup. Use a changelog entry if the product part used has improved.

1. 1

   Day 1: shortlist and ask

   Pick three customers by sector and outcome. Send the permission email with your one page brief and proposed angle.

2. 2

   Day 2: record and transcribe

   Run one 20 minute call. Get consent to use their name, logo, quotes and screenshots. Transcribe and pull their exact phrases.

3. 3

   Day 3: draft the shape

   Fill the template. Keep quotes verbatim. Write the title and meta. Add internal links to your category page and one guide.

4. 4

   Day 4: visuals and schema

   Capture screenshots, compress images, write alt text. Add Article JSON-LD and test it. Check Core Web Vitals in PageSpeed Insights.

5. 5

   Day 5: review and ship

   Send for approval in Google Docs. On sign off, publish. Submit the URL in Search Console. Share it with sales and support to use in replies.

After publish, add the case study to your /case-studies index. Link to it from the relevant feature and pricing pages. Add it as a related link in the matching guide article so it earns internal PageRank and buyer clicks.