Readability & Plain Language

Plain Language Summaries: Why They Increase Citations (and How to Write One)

08 June 2026 10 min read

Plain language summaries—sometimes called "lay summaries," "plain-speak abstracts," or "impact statements"—are no longer optional. They're increasingly required by funders, embraced by journals, and now essential for discoverability across both human readers and AI engines.

The evidence is striking: papers published with a plain language summary receive 20–30% more citations than comparable papers without one. And crucially, modern language models (GPT, Claude, Gemini) prefer clear, accessible writing when indexing and summarising papers for discovery.

This is the hidden SEO opportunity of 2026: optimising your paper for both human accessibility and AI readability.

The Citation Evidence: De Gruyter and Beyond

In 2023, De Gruyter Publishers analysed citation patterns across 15,000 open-access research papers and found a striking pattern: articles with lay summaries accumulated 23% more citations in the first 12 months post-publication compared to articles without them.

The mechanism isn't mysterious. A well-written lay summary:

Key Takeaway

Papers with plain language summaries get 20–30% more citations in the first 12 months. This effect is strongest in interdisciplinary fields (medicine, public health, environmental science) and weakest in pure mathematics and physics.

Funder and Journal Requirements: The Regulatory Push

Plain language summaries are no longer optional—they're mandated.

UKRI (UK Research and Innovation) now requires a plain language summary for all funded research. The requirement reads: "A concise summary of the research, its context and its potential impact, suitable for non-specialist readers." Failure to provide one can delay grant payment.

NIH (National Institutes of Health) has integrated plain language requirements into grant reporting. NSF (National Science Foundation) similarly expects a "Broader Impacts" statement, which often includes lay summary components.

Journals like eLife, PLOS Medicine, BMC, and The Conversation now automatically publish lay summaries alongside research articles. Many journals ask authors to provide them; some (eLife, Cochrane) write them in-house if you don't.

The shift is clear: funding agencies and publishers treat plain language accessibility as a quality indicator. Papers that can't be explained simply are treated with skepticism.

Adoption rate: 67% of top-tier biomedical journals now accept or require plain language summaries (2025 survey). For clinical and public health journals, this figure is 82%.

Source: Journal policy analysis, Academic SEO research, 2025

How LLMs Prefer Clear Language: The AI Search Factor

Modern language models (LLMs) that power AI search engines—including those used by Google Scholar, semantic search tools, and emerging AI summarisers—perform better on clear, accessible writing than on dense jargon.

Why? LLMs are trained on internet text, which skews toward clarity. When an LLM encounters overly technical or jargon-heavy prose, its confidence in understanding the core claim decreases. This affects:

A plain language summary explicitly written for a high-school education level improves LLM parsing accuracy by approximately 15–20%, according to informal benchmarking. This translates directly to better AI discoverability.

Readability, Flesch Scores, and Citation Correlation

The Flesch Reading Ease (FRE) score measures text readability on a scale of 0–100. A score of 60–70 is "standard" English; 80+ is "easy"; below 30 is "very difficult."

Research papers typically score in the 10–30 range (very difficult). A well-written plain language summary scores 60–75.

The correlation between readability and citations is modest but significant: papers with readable abstracts and lay summaries receive 10–15% more citations than those written at maximum jargon density. This effect is independent of impact factor or novelty—pure readability matters.

Your plain language summary is not your abstract with simpler words. It's a standalone piece of communication that tells a non-specialist why your finding is interesting and what you discovered.

The 5-Step Framework for Writing a Lay Summary

Step 1: Start with the problem (not the methods).

Your opening sentence should answer: "What real-world problem does this paper address?" Not: "We used RNA-seq to profile gene expression patterns." But: "Cancer cells evolve resistance to treatment. We wanted to understand the genetic changes that enable this resistance, so we can develop better therapies."

Step 2: Explain why it matters (context for non-specialists).

Give readers a reason to care. Example: "Each year, 500,000 cancer patients develop drug resistance, cutting their survival time in half. If we could predict which cancers will develop resistance early, we could switch treatments before resistance emerges—potentially saving 50,000 lives annually."

Step 3: Describe what you did (simply).

Avoid methods jargon. Instead of "We performed RNA-seq on 200 patient-derived tumour samples, and conducted differential expression analysis using DESeq2 with a FDR-corrected threshold of 0.05," write: "We studied 200 tumours from patients whose cancer stopped responding to treatment, and identified the genes that turn on in drug-resistant cells."

Step 4: State your key finding (one sentence, clearly).

Example: "We discovered that drug-resistant cancers activate a set of 12 genes involved in drug transport and DNA repair—a signature we can now screen for in patients before treatment begins." This is not a dense results section. It's a single, memorable finding.

Step 5: Explain the implication (what happens next).

Answer: "What will researchers or clinicians do with this finding?" Example: "Our discovery suggests that testing for this gene signature could help doctors identify patients at high risk of treatment failure, enabling earlier intervention. We're now working with [partner hospital/company] to develop a clinical test for this signature."

Key Takeaway

A plain language summary is not a dumbed-down abstract. It's a re-framed narrative: Problem → Why it matters → What we did → What we found → What's next. Write for someone with a strong high-school education and genuine interest, but no specialist knowledge.

Common Mistakes and How to Avoid Them

Mistake 1: Oversimplifying to the point of inaccuracy.

You can be simple without being wrong. "We cured cancer" is too simple and false. "We identified a genetic marker that predicts treatment response" is both simple and accurate.

Mistake 2: Using jargon without definition.

If you must use technical terms (sometimes unavoidable), define them once. "RNA" should become "RNA, a molecule that carries genetic instructions." But avoid jargon altogether if a simpler term exists.

Mistake 3: Forgetting the clinical or real-world angle.

Pure curiosity-driven research still has implications. Instead of "We characterised protein binding kinetics in a novel enzyme," write: "We discovered how a protein involved in [disease X] binds to its targets, which could help us design drugs that block this interaction."

Mistake 4: Making it too long.

A lay summary should be 150–250 words. If it's longer than your abstract, it's not accessible—it's just a simplified abstract, and those don't work.

Mistake 5: Passive voice and vague agency.

Avoid: "It was found that resistance develops through genetic mutations." Use: "We found that cancer cells develop resistance by acquiring mutations in these three genes." Active voice is clearer and keeps readers engaged.

Before and After: Real Examples

Before: "Dysregulation of PTEN signalling in oestrogen receptor-positive luminal breast cancers drives endocrine resistance through activation of PI3K/Akt and MAPK/ERK pathways. We performed RNA-seq on 156 hormone-sensitive and 89 hormone-resistant tumours, identifying recurrent alterations in PTEN loss and PIK3CA amplification. Mechanistic studies using CRISPR-mediated PTEN knockout in MCF-7 and T47D cell lines confirmed enhanced proliferation and survival in the presence of tamoxifen. These results suggest PTEN status as a biomarker for endocrine sensitivity and a therapeutic target in combination with CDK4/6 inhibitors."

After: "Breast cancer treatment often fails because cancer cells develop resistance to hormone therapy. We studied 245 breast cancers and found that tumours resistant to hormone therapy often have broken copies of a gene called PTEN. When we recreated this genetic change in lab-grown cancer cells, those cells became resistant to treatment. Our finding suggests that testing for PTEN loss in patients before they start hormone therapy could help doctors choose the right treatment and combination drugs from the start, potentially preventing treatment failure."

The second version is 72 words; the first is 109. The second version is more memorable, actionable, and citable.

Where to Place Your Plain Language Summary

Best practices vary by journal:

If your target journal doesn't require a lay summary, include it anyway. Post it on your institutional website, mention it in your press release, and include it in your Google Scholar profile. It will drive traffic and citations from researchers and the public who stumble upon your work.

The Compound Effect: Why This Matters for Your Career

A single well-written plain language summary doesn't change your career. But across a postdoc or early faculty career, 5–10 papers with lay summaries instead of 0 create a measurable advantage:

For postdocs on the job market, this compounds into a noticeable citation difference—and citations matter for tenure track interviews and fellowships.

Frequently Asked Questions

How long should a plain language summary be?

150–250 words is the sweet spot. Long enough to tell the full story (problem, solution, implication), short enough to stay accessible. If it's longer than your abstract, it's too long and will lose readers.

Should I write the lay summary before or after the paper is finished?

After. You need to know your final findings to write accurately. However, many researchers draft it during revision—it helps clarify what the paper is really about, which often improves the abstract too.

Is a plain language summary the same as a graphical abstract?

No. A graphical abstract is visual (one figure summarising findings). A plain language summary is text. You should have both. They serve different discovery pathways: the graphical abstract works on social media and visual search; the lay summary works for citation discovery and AI parsing.

What if my research has no obvious clinical application?

Every paper has implications. Pure biology research contributes to drug development. Physics findings enable technology. Frame it: "This work helps us understand [fundamental mechanism], which could eventually enable [future application]." Honesty is key—avoid overstating clinical relevance you don't have.

Do I need to include citations in a plain language summary?

No. Keep citations out of the lay summary. If you must reference previous work, do so in plain language: "Previous research showed that X; we wanted to test whether Y." Avoid citations and numbers (except key findings).

Ready to optimise your paper before you publish?

We optimise your title, abstract, keywords, readability, and metadata for Google Scholar, PubMed, and AI search engines.

Submit your paper →