How to write case studies that convince humans and get cited by AI

March 24, 2026
0 minute read

For decades, case studies and customer success stories were human-focused BOFU (Bottom of the Funnel) or sales artifacts. They hid in downloadable PDFs and static website pages, designed mostly to build trust with prospects before they signed a contract. In 2026, case studies have transformed into multimedia stories that inform another important audience: AI answer engines.


Key Points
  • Case studies now drive AI answers, not just human trust, so structure them for both
  • Lead with clear, specific results so that AI can extract and cite them
  • Use concrete data, named entities, and direct quotes to anchor credibility
  • Write headers and sections as answers to real questions, not generic labels
  • Treat every case study as structured, citable ground truth and your most defensible content asset


It’s common knowledge in the digital marketing industry that online discoverability is moving away from traditional methods and into the era of zero-click content engagement. Up until recently, SEO professionals aimed for customer success stories to be indexable by the Googlebot in a way that wins visibility in search engine results for relevant search queries. Today, your case studies aren’t just indexed by search engine bots or used as collateral by sales teams. They hold the potential to serve as reliable, high-fidelity training data for AI answer engines.


Fortunately, the underlying elements that make case studies compelling to humans and discoverable by search indexing bots are the same ones that make them citable by AI models. In this guide, we’ll walk through the subtle differences and changes you can make to existing case study production and publication workflows to make your success stories (and those of your clients) satisfy the human need for narrative and the AI need for structured facts.


Interviews and numbers: Mining the ground truth


Customer success stories are typically based on interviews rather than short testimonials. This means that whoever is producing the case study needs to take on the role of a journalist—including background research, the art of interviews, and sometimes even the technical aspects of recording, filming, and editing the interview.


Simply asking a client if they’re happy and steering them toward a quote about how helpful your team has been will not yield a particularly original or helpful answer. To get an answer worthy of human and bot attention, you need to extract and communicate the “unguessable” truths and sentiment—the kind that AI cannot predict or hallucinate based on its training data.


Radically specific and unguessable details


When interviewing clients for case studies, your primary goal is to extract metrics that are unique and memorable. An AI can guesstimate (infer through probabilistic next-token generation) that an SEO agency “improved traffic” for a client. It cannot hallucinate “increased organic traffic by 4,162%” or “added 600 clients in 30 days.” These very specific metrics and numbers serve as ground truth anchors that verifiably tie your agency to the results.


Tip: In the questions sent to the interviewee in advance, gently push for numbers, percentages, and “before and after” KPIs.


Trust signals and sentiment


AI engines love numbers, but they also look for reasons to trust or distrust content according to their preset parameters. AI crawler bot algorithms are trained to detect sentiment and attribution, so a direct and attributed quote from a valid entity (like a C-level executive) serves as a valuable trust signal for the AI to validate the data points surrounding it.


Tip: Make sure that every case study features at least one champion quote that explicitly defines the problem and the solution in the client’s own words and voice.


The structure: Optimizing for extraction


The raw data from your interview needs to be organized before it can be consumed. Typically, the advice is to save the conclusion for the summary and “the best for last” since humans prefer a linear logical journey. Bots, on the other hand, just want facts fast. You can deliver both by balancing storytelling and the listing of data.


BLUF with a cheat sheet


Retrieval-Augmented Generation (RAG) systems often prioritize information found early in the document. If your key results are buried somewhere in the middle or toward the end of the page, the AI might miss them. This is where the “Executive Summary” becomes your secret weapon. By placing a structured table of facts at the very top of the page, you reduce the cognitive load for human prospects scanning for results, while serving up a clean, structured data platter for AI crawlers.


Tip: Place a cheat sheet of facts at the very top of your case studies, with a bulleted list or table that explicitly labels your data points: Service, Key Result, Industry, Business Name, etc.


The narrative: fluency is authority


Once you have your ground truth data and structural BLUF in place, it’s time to write the actual story. While humans prefer a hero’s journey, AI models are looking for semantic associations and question-answer pairs. Here’s how you can combine both:


Reverse-engineering intent


Generic headers like 'The Challenge' are invisible to an AI looking for answers. To win the citation, you need to reverse-engineer the user's prompt. Treat your H2s as the answers to the questions your prospects are typing into ChatGPT or Google.


Tip: Change generic headers like “Results” to specific questions like “How [Client] improved their ROI” or “How [Your Brand] Helped [Client] Achieve [Impressive Number]”. Instead of simply replacing “Challenge” with “Slow Site”, go into detail like “Decreased Website Performance due to Core Web Vitals failures.”


Explicit entity naming


To help AI models pinpoint relationships between data points, you can feed their knowledge graph with defined “Entities”. Through the lens of an AI algorithm, a brand is an entity, a speaker is another, as is the author and other brands mentioned in the text. The more entities an AI can recognize, the easier it is to weave your truths into its answers to queries.


Tip: Flaunt your tech stack and name the tools and technologies you employ. This will help you associate the brand with industry giants and software ecosystems in the eyes of AI models.


Turning case studies from sales collateral to AI training data


For years, the goal was to keep users reading pages for as long as possible. Today, the goal is to provide an answer that drives action whether directly or indirectly. Winning the mentions in the new answer economy of online discoverability doesn’t mean reinventing the proverbial wheel. It means creating a better experience for busy human readers and AI models alike.


When it comes to case studies in the age of AI answers, a good success story is just the beginning. By writing, structuring, and publishing case studies rich with explicit entities, specific integers, and semantic clarity, you turn them into high-fidelity training data that AI models use to generate answers to user queries.


Did you find this article interesting?


Thanks for the feedback!
By Shawn Davis April 1, 2026
Core Web Vitals aren't new, Google introduced them in 2020 and made them a ranking factor in 2021. But the questions keep coming, because the metrics keep changing and the stakes keep rising. Reddit's SEO communities were still debating their impact as recently as January 2026, and for good reason: most agencies still don't have a clear, repeatable way to measure, diagnose, and fix them for clients. This guide cuts through the noise. Here's what Core Web Vitals actually measure, what good scores look like today, and how to improve them—without needing a dedicated performance engineer on every project. What Core Web Vitals measure Google evaluates three user experience signals to determine whether a page feels fast, stable, and responsive: Largest Contentful Paint (LCP) measures how long it takes for the biggest visible element on a page — usually a hero image or headline — to load. Google considers anything under 2.5 seconds good. Above 4 seconds is poor. Interaction to Next Paint (INP) replaced First Input Delay (FID) in March 2024. Where FID measures the delay before a user's first click is registered, INP tracks the full responsiveness of every interaction across the page session. A good INP score is under 200 milliseconds. Cumulative Layout Shift (CLS) measures visual stability — how much page elements unexpectedly move while content loads. A score below 0.1 is good. Higher scores signal that images, ads, or embeds are pushing content around after load, which frustrates users and tanks conversions. These three metrics are a subset of Google's broader Page Experience signals, which also include HTTPS, safe browsing, and mobile usability. Core Web Vitals are the ones you can most directly control and improve. Why your clients' scores may still be poor Core Web Vitals scores vary dramatically by platform, hosting, and how a site was built. Some of the most common culprits agencies encounter: Heavy above-the-fold content . A homepage with an autoplay video, a full-width image slider, and a chat widget loading simultaneously will fail LCP every time. The browser has to resolve all of those resources before it can paint the largest element. Unstable image dimensions . When an image loads without defined width and height attributes, the browser doesn't reserve space for it. It renders the surrounding text, then jumps it down when the image appears. That jump is CLS. Third-party scripts blocking the main thread . Analytics pixels, ad tags, and live chat tools run on the browser's main thread. When they stack up, every click and tap has to wait in line — driving INP scores up. A single slow third-party script can push an otherwise clean site into "needs improvement" territory. Too many web fonts . Each font family and weight is a separate network request. A page loading four font files before rendering any text will fail LCP, especially on mobile connections. Unoptimized images . JPEGs and PNGs served at full resolution, without compression or modern formats like WebP or AVIF, add unnecessary weight to every page load. How to measure them accurately There are two types of Core Web Vitals data you should be looking at for every client: Lab data comes from tools like Google PageSpeed Insights, Lighthouse, and WebPageTest. It simulates page loads in controlled conditions. Lab data is useful for diagnosing specific issues and testing fixes before you deploy them. Field data (also called Real User Monitoring, or RUM) comes from actual users visiting the site. Google collects this through the Chrome User Experience Report (CrUX) and surfaces it in Search Console and PageSpeed Insights. Field data is what Google actually uses as a ranking signal — and it often looks worse than lab data because it reflects real-world device and connection variability. If your client's site has enough traffic, you'll see field data in Search Console under Core Web Vitals. This is your baseline. Lab data helps you understand why the scores are what they are. For clients with low traffic who don't have enough field data to appear in CrUX, you'll be working primarily with lab scores. Set that expectation early so clients understand that improvements may not immediately show up in Search Console. Practical fixes that move the needle Fix LCP: get the hero image loading first The single most effective LCP improvement is adding fetchpriority="high" to the hero image tag. This tells the browser to prioritize that resource over everything else. If you're using a background CSS image for the hero, switch it to anelement — background images aren't discoverable by the browser's preload scanner. Also check whether your hosting serves images through a CDN with caching. Edge delivery dramatically reduces the time-to-first-byte, which feeds directly into LCP. Fix CLS: define dimensions for every media element Every image, video, and ad slot on the page needs explicit width and height attributes in the HTML. If you're using responsive CSS, you can still define the aspect ratio with aspect-ratio in CSS while leaving the actual size fluid. The key is giving the browser enough information to reserve space before the asset loads. Avoid inserting content above existing content after page load. This is common with cookie banners, sticky headers that change height, and dynamically loaded ad units. If you need to show these, anchor them to fixed positions so they don't push content around. Fix INP: reduce what's competing for the main thread Audit third-party scripts and defer or remove anything that isn't essential. Tools like WebPageTest's waterfall view or Chrome DevTools Performance panel show you exactly which scripts are blocking the main thread and for how long. Load chat widgets, analytics, and ad tags asynchronously and after the page's critical path has resolved. For most clients, moving non-essential scripts to load after the DOMContentLoaded event is a meaningful INP improvement with no visible impact on the user experience. For websites with heavy JavaScript — particularly those built on frameworks with large client-side bundles — consider breaking up long tasks into smaller chunks using the browser's Scheduler API or simply splitting components so the main thread isn't locked for more than 50 milliseconds at a stretch. What platforms handle automatically One of the practical advantages of building on a platform optimized for performance is that many of these fixes are applied by default. Duda, for example, automatically serves WebP images, lazy loads below-the-fold content, minifies CSS, and uses efficient cache policies for static assets. As of May 2025, 82% of sites built on Duda pass all three Core Web Vitals metrics — the highest recorded pass rate among major website platforms. That baseline matters when you're managing dozens or hundreds of client sites. It means you're starting each project close to or at a passing score, rather than diagnosing and patching a broken foundation. How much do Core Web Vitals actually affect rankings? Honestly, they're a tiebreaker — not a primary signal. Google has been clear that content quality and relevance still dominate ranking decisions. A well-optimized site with thin, irrelevant content won't outrank a content-rich competitor just because its CLS is 0.05. What Core Web Vitals do affect is the user experience that supports those rankings. Pages with poor LCP scores have measurably higher bounce rates. Sites with high CLS lose users mid-session. Those behavioral signals — time on page, return visits, conversions — are things search engines can observe and incorporate. The practical argument for fixing Core Web Vitals isn't just "because Google said so." It's that faster, more stable pages convert better. Every second of LCP improvement can reduce bounce rates by 15–20% depending on the industry and device mix. For client sites that monetize through leads or eCommerce, that's a revenue argument, not just an SEO argument. A repeatable process for agencies Audit every new site before launch. Run PageSpeed Insights and record LCP, INP, and CLS scores for both mobile and desktop. Flag anything in the "needs improvement" or "poor" range before the client sees the live site. Check Search Console monthly for existing clients. The Core Web Vitals report surfaces issues as they appear in field data. Catching a regression early — before it compounds — is significantly easier than explaining a traffic drop after the fact. Document what you've improved. Clients rarely see Core Web Vitals scores on their own. A monthly one-page performance summary showing before/after scores builds credibility and makes your technical work visible. Prioritize mobile. Google uses mobile-first indexing, and field data shows that mobile CWV scores are almost always worse than desktop. If you only have time to optimize one version, do mobile first. Core Web Vitals aren't a one-time fix. Platforms change, new scripts get added, campaigns bring in new widgets. Build the audit into your workflow and treat it like any other ongoing deliverable, and you'll stay ahead of the issues before they affect your clients' rankings. Duda's platform is built with Core Web Vitals performance in mind. Explore how it handles image optimization, script management, and site speed automatically — so your team spends less time debugging and more time building.
By Ilana Brudo March 31, 2026
Vertical SaaS must transition from tools to an AI-powered Vertical Operating System (vOS). Learn to leverage context, end tech sprawl, and maximize retention.
By Shawn Davis March 27, 2026
Automate client management, instant site generation, and data synchronization with an API-driven website builder to create a scalable growth engine for your SaaS platform.
Show More

Latest posts