Recruiting Grad Students: Copy and Content That Works for Research Labs

A principal investigator at a top-twenty cognitive neuroscience program told us last spring that her single biggest bottleneck on the lab's growth was not funding or compute. It was applicant pipeline. The lab was producing strong work, the open positions were posted on the standard channels, and the applications coming in were not the applications she wanted to be receiving. The lab's website, she suspected, was part of the problem.

She was right, and what we have seen across labs since is consistent. The recruitment story most lab sites are telling is incidental rather than intentional. The page that should be doing the most work for the lab's future is buried two clicks deep and reads like the rest of the site. The fix is not technical. It is editorial. Here is what we have learned about content that actually helps research labs recruit the graduate students they want.

The lab website is doing three jobs at once

Most lab sites are simultaneously trying to serve three audiences whose needs are deeply different. Peer researchers want to find the lab's recent papers, see who is in the group, and understand the methods. Study participants want to know whether they are eligible, what the time commitment looks like, and how to enroll. And prospective graduate students want to know whether this lab is the right place to spend the next five to seven years of their professional life.

The structural mistake most lab sites make is trying to serve all three audiences from the same homepage. The result is a page that does each job poorly. The peer researcher cannot find the papers. The participant cannot find the eligibility criteria. The grad student cannot find the lab's intellectual story. Our research industry page discusses the broader architecture pattern we apply to lab sites. The short version is that the homepage routes, and each audience gets a path designed for it.

The recruitment path is the one that deserves the most editorial care, because it is the only path where the visitor is making a major life decision and looking to the website to support it.

The "join the lab" page is the most important page on the site

For a prospective graduate student, the conversion event is reading the "join the lab" page and deciding to email the PI. Most lab sites' versions of this page are a single sentence (often: "Interested students should contact [PI email]"). A small minority include the actual information a student needs to make the decision. The labs that recruit well in 2026 have a real version of this page, and it is not hard to build once the PI understands what it needs to say.

The page should cover six things. What the lab is actually working on right now (not the PI's tenure-track statement from a decade ago). What kinds of projects new students typically take on in their first two years. What technical and intellectual background helps a student succeed in the lab (and what does not matter as much as students often assume). What the lab's funding picture looks like, including the relevant fellowships and assistantships students can pursue. Who the current students are and what they are working on. And what the timeline and process for joining looks like, including the application deadlines for the relevant program.

This is content the PI mostly already has in their head. Writing it down once and putting it on the website saves the PI hundreds of email exchanges with prospective applicants, and it produces dramatically better applicants because the people who write to the lab after reading the page are people who already know whether it is a fit.

Current students should write the page about being a current student

The single most effective recruitment content we have helped labs produce is a page of current-student perspectives in their own voices. A few short paragraphs from each student about what they are working on, what their day-to-day looks like, what they wish they had known before joining, and where they hope the work leads. The page is more honest than anything the PI could write, and prospective students read it like a primary source.

Producing this content is light work. A thirty-minute interview with each student, edited into a short page-section each, with a current photo and a link to their current project. Updated annually as cohorts turn over. The content survives student departures because each section is self-contained and dated, and the historical sections become useful background for future applicants who want to understand the lab's intellectual evolution.

The labs that have done this consistently for several years end up with the strongest recruitment story in their subfield without ever having tried to "do marketing." The story is just there for students to read.

The research page should explain why the work matters

Most research-lab websites treat the research page as a list of publications and project titles. For peer researchers, that is fine. For prospective graduate students, it is insufficient. A first-year graduate-school applicant is trying to decide between five labs that all have strong publications and impressive project titles, and the deciding factor is usually which lab's research story makes them excited to wake up and work on it.

The fix is writing a short, plain-English overview for each major research thread the lab is currently pursuing. What is the big question. Why is it still open. What approach is this lab taking that other labs are not. What would success look like in five years. This is the content a tenure committee already expects to read in the PI's annual review, and it is also exactly the content that helps a prospective student decide whether the lab's intellectual project lines up with what they want to spend a PhD on.

For a lab pursuing several distinct threads, each gets its own page. The student looking specifically at, say, the lab's memory-consolidation work should be able to land on a page about memory-consolidation work without having to read about the lab's other two project lines first.

Methods and tools deserve their own page

A class of prospective student that most labs underserve is the methods-driven student. The student who is choosing labs based on the techniques they want to learn rather than the question they want to ask. For these students, a page that names the specific methods the lab uses (with enough detail to be useful) is the deciding factor.

The page reads more like documentation than marketing. The neuroimaging modalities the lab works with, the analysis tools the students are trained on, the experimental paradigms the lab has developed or adopted, the open-source code the lab maintains. Specific software, specific instrumentation, specific analytic frameworks. A student who lands on this page and recognizes their training goals on it is a student who emails the PI within the week.

This is also content that does double-duty for the peer-researcher audience, who want exactly the same information for collaboration purposes. One well-written methods page can serve both audiences without compromising either.

What this changes about the lab's recruiting pipeline

A lab that gets its website content right does not need to do additional outreach to fill its applicant pool. The right students start finding the lab through search and through their advisors' recommendations, and by the time they email the PI they already know whether the fit is real. The PI's email volume goes down because the misqualified applicants stop writing. The cohort that arrives in the fall is the cohort the PI wanted.

The work to produce all of this is meaningful but not enormous. A few weeks of writing, an annual maintenance cadence, and a willingness to let the lab's actual voice come through on the page. For PIs whose time is the scarcest resource in the lab, the return on this investment is among the highest available.

If your lab's website is starting to feel like it was built for a different audience than the one you are actually trying to reach, we should talk. We work with research groups across multiple institutions and would love to learn what your recruitment pipeline needs.