Why do AI assistants quote some case studies and ignore others?

A design case study becomes quotable when you rebuild it as a structured answer page: a direct result statement in the opening, question based headings, self contained capsules under each heading, one comparison table, and schema markup that labels the work as a CreativeWork. Google AI Overviews, Perplexity and ChatGPT Search extract passages, not pages, so every section must survive on its own. In 2026 the winning format is a case study that reads like a documented answer to the question your client actually typed.

Why do AI assistants quote some case studies and ignore others?

AI assistants quote case studies that state a verifiable result inside the first sentence of each section, because retrieval pipelines score passages for standalone clarity.

Retrieval augmented generation splits your page into chunks, usually one heading plus the paragraphs beneath it. A chunk that opens with "the client wanted a refresh" carries no extractable fact. A chunk that opens with "the checkout redesign cut cart abandonment from 71% to 54% in eight weeks" gives the model a complete, attributable claim it can lift without context.

Three signals decide whether your passage gets cited:

• Self sufficiency: the passage names the project, the metric and the timeframe without relying on earlier paragraphs.

• Specificity: numbers, tools and dates beat adjectives. "Figma prototype tested with 12 users" outranks "user centered approach".

• Structure: headings phrased as real questions match the query patterns people type into assistants.

Google's own guidance on helpful content rewards content written for people first, and passage level clarity is the practical expression of that principle for machine readers.

How do you structure a case study page with the capsule method?

The capsule method places a 120 to 150 character declarative summary directly under every question heading, followed by supporting evidence, so each block can be extracted whole.

Think of the page as a stack of independent answer blocks. Each block has three layers: the question heading, the capsule, and the proof. The capsule does the work of a snippet: one sentence, active voice, no pronouns pointing backward, no links inside it. The proof layer carries the detail, the screenshots, the before and after numbers.

Apply this sequence when you rebuild an existing case study:

1. List the five to seven questions a prospective client would ask about the project.

2. Turn each question into an h2 heading, written the way a person speaks.

3. Write the capsule first, count the characters, cut until it fits the 120 to 150 range.

4. Add 60 to 120 words of evidence under each capsule, with at least one concrete number.

5. Move every comparison into a table and every process into a numbered list.

6. Add FAQ schema and CreativeWork schema before publishing.

1 List the five toseven questions a… 2 Turn each questioninto an h2 heading,… 3 Write the capsulefirst, count the… 4 Add 60 to 120words of evidence under… 5 Move everycomparison into a table and… 6 Add FAQ schema andCreativeWork schema…

This structure also improves traditional SEO. Passage level clarity tends to lift dwell time because scanners find answers faster, and scanners are most of your traffic.

Which data should a quotable case study contain?

A quotable case study contains at least one baseline metric, one post launch metric, the measurement window and the tools used, because those four elements let an assistant verify the claim.

Design work is easy to describe and hard to prove. The fix is to publish the measurement frame alongside the outcome. If you ran a usability test, name the sample size. If you tracked conversion, name the analytics tool and the date range. A designer working as a freelancer in Italy or anywhere else competes on evidence, not on portfolio aesthetics.

When a client forbids publishing numbers, publish the method and the qualitative finding instead. "Five of eight participants abandoned at the shipping cost step" is still a citable fact and it protects the relationship.

How do you write headings that match what people ask AI?

Headings match AI queries when they repeat the natural phrasing of a real question, such as "how long does a UX audit take" instead of "Methodology".

Assistants match your passage against the user's prompt. The closer your heading sits to that prompt, the higher the retrieval score. Pull the headings from your sales calls and your inbox: those are literal questions from buyers.

Useful patterns that work across design portfolios:

• How long does the project take, and what happens in each phase?

• What did the redesign change, measured in numbers?

• Which tools and deliverables does the client receive?

• What would you do differently on the next project?

The last one earns trust and gets quoted often, because honest retrospectives are rare in portfolio writing. Keep each heading under about 60 characters so it survives truncation in search results.

What technical markup makes a case study extractable?

Technical markup makes a case study extractable when the page carries Article or CreativeWork schema, FAQPage schema for the question section, and clean semantic HTML with one h1 and sequential h2 headings.

Structured data does not guarantee a citation, but it removes ambiguity about what the page contains. Google's structured data documentation lists the properties that matter for creative works: name, creator, datePublished, about and description. Fill them with the same facts that appear in the visible text, never with claims the page does not show.

Three practical rules for the markup layer:

• Keep the FAQ answers in schema identical to the visible answers, word for word.

• Use descriptive alt text on before and after screenshots so image results can surface them.

• Avoid client side rendering for the main content, because some crawlers still read the raw HTML first.

Semantic HTML is the foundation. A page built from proper h2, p, ul and table tags is already machine readable before any schema is added.

How do you measure whether AI assistants cite your case study?

Citation tracking works by running a fixed set of prompts monthly across ChatGPT, Perplexity and Google AI Overviews, then logging which URLs appear and how often your case study is named.

Build a small prompt list from your buyer questions, run it on the first of every month, and record the results in a spreadsheet. Track three columns: prompt, assistant, cited URL. Over a quarter you will see which sections get pulled and which never surface.

Pair that with conventional signals: impressions and average position in Search Console for the question style queries, scroll depth on the case study page, and the number of inbound enquiries that mention a specific project. A case study that gets cited but never converts usually has a weak call to action, not a weak structure.

Iterate on the capsules that never get extracted. Rewrite them shorter, add a number, remove the pronoun. Small edits to a single passage often change citation behaviour within weeks.

Frequently Asked Questions

How long should a case study page be for AI citation?

Between 900 and 1,400 words works well, because the page needs enough distinct passages to cover several questions without diluting each one. Length matters less than the independence of every section.

Can I publish a case study without client permission for the numbers?

Publish the method and the qualitative findings instead, and anonymise the client as a sector description. Method details such as sample size and test rounds remain citable without exposing commercial data.

Does a portfolio image alone get quoted by AI assistants?

Rarely. Images support a claim but assistants extract text. Pair every visual with a caption that states the before and after outcome in one sentence.

Do I need a blog post and a case study for the same project?

No. One well structured case study page covers both intents when its headings answer the questions a blog post would raise. Duplicating the content splits authority across two URLs.

How often should a case study page be updated?

Review it every six months and refresh the dates, tools and metrics. A page that names 2026 in its measurement window signals current, verifiable work to both readers and retrieval systems.

Start with one project you already shipped. Rewrite its opening as a result statement, convert its headings into buyer questions, and add a capsule under each one. That single page will outperform a dozen image only portfolio entries in both search and AI answers, and it gives every future client a reason to trust the numbers before the first call.