Back to the journal

Research

A lab page you can edit the night a preprint goes up

Department sites lag. Postdocs, visitors, and funders still need papers, openings, and a way to email you. Here is a public lab desk you control, and what stays off it.

October 30, 20266 minLinkForge Editorial

A postdoc googles your name on a Sunday because the application portal closes Monday. The department page still says the lab is “recently moved” and lists a paper from three cycles ago. Google Scholar has the citations and none of the practical facts: who is leaving, which project has a funded seat, which email subject line you actually read.

That gap is the lab hub. It is not a second university CMS and it is not a personal blog about your commute. It is a public HTML page you can change the evening a preprint lands, without waiting for a webmaster ticket.

The official faculty profile can stay the HR record. Link it. The hub is the scientific front door: current people, current papers, current openings, and the sentence that tells a stranger how to write to you.

What the page has to answer before anyone applies

Write these as sentences, not as a slogan under a group photo.

  1. Who is the PI, and where is the bench. Name, department, city, and the second affiliation if you have one. Two universities do not need two decaying sites. One hub, two affiliation lines, links to both official profiles.
  2. What the lab actually does this year. One paragraph a non-specialist in the adjacent field can repeat. Methods fashion changes; the paragraph should survive a semester.
  3. Who is in the group. Names, roles, and the year someone is leaving if that affects supervision. A smiling photo from 2019 with no names is how applicants email the wrong person.
  4. How to email. A subject-line pattern (“PhD inquiry — [topic] — [your name]”), what to attach (CV, one-page research note), and what not to attach (a 40-page thesis on the first email). Say whether you read cold emails and in which months you do not.
  5. Open roles, dated. “PhD seat funded from September, applications via the university portal, deadline on the portal.” If nothing is open, write “no funded openings this cycle” and the date you wrote it. Silence reads as “maybe.”
  6. Five papers, then the index. Pin the five a visitor should read first, with HTML titles and links to the publisher, the preprint, or both. Point the rest at ORCID or Google Scholar. A 40 MB PDF list is how a phone gives up.
  7. Code and data. A repository, a data DOI, or an honest “embargoed until [month], then this archive.” “Available upon request” with no mailbox is a closed door.
  8. Visitors. Who you can host, for how long, whether bench space exists, and who pays travel. A one-line “write six months ahead” saves a week of mismatched hope.

Put the email pattern and the openings above the fold on a phone. People applying from a train will not scroll through a mission statement to find the deadline.

Build it in one evening

You do not need a lab GitHub Pages rebuild to ship the first version.

  1. Publish a public page you can edit yourself. On LinkForge that is linkforge.me/u/your-lab (or a name you will not be ashamed to put in a talk slide). Create the page and paste the eight answers above as text, not as a screenshot of the department site.
  2. Add buttons in this order: open roles, email instructions, five papers, code or data, visitor note, official faculty profile. Five links is the free-plan cap; if the lab needs more doors, Pro is 7€/month and also the path to a custom domain such as lab.yourname.org when central IT will not give you a subdomain.
  3. Set the entity type to Organization if the page represents the group, or Person if it is specifically you and the group is described in the text. A lab is not a local shop and it is not a SaaS. The label should match the name in the title.
  4. Write a title a searcher would type: “Rivera Lab — microbial ecology, University of X.” Editable titles are how the page is a document, not a widget. The same idea is covered in SEO for one bio link.
  5. Put the hub URL in your email signature, on the last slide of talks, in the preprint’s author footnote, and on ORCID’s website field. The department page links to the hub; the hub links back. That is the mesh, not a coup.
  6. When a paper posts, you change the five pins the same day. When a student defends, you change the people list the same week. The URL does not change. Old slides keep working.

If you already keep a speaker one-pager for invitations, link it from the lab page. Talks and the group are different jobs. They can share a domain later. They should not share a junk drawer of every podcast you joined.

Human-subjects work, photos, and politics

If the lab runs studies with people, the hub is the public face. It is not the consent form, not the IRB protocol, and not the place to recruit by hiding the study’s purpose. Say how to participate, who to contact about a concern, and how to opt out of photos. Link the ethics board’s public page if one exists.

Group photos need a caption and a year. Ask before you publish a trainee’s face on a page that will be indexed. A trainee who leaves should be able to ask for the photo to come down without a fight.

Personal politics can live on a personal URL. If the lab page is the scientific front door, decide that on purpose. Mixing a campaign with a methods paragraph trains journalists and students to wonder which voice is the group. Split the URLs if both need to exist. The press-room pattern is the sibling for anyone who gets interview requests: bios and a human who answers, separate from the methods page if the volume justifies it.

What to leave in the university’s hands

Payroll, official course catalogues, grant account numbers, and anything under a confidentiality clause stay on systems the university controls. Do not paste award budgets, reviewer comments, or student grades onto a public hub to “be transparent.”

Do not paste a reproduction of a paywalled PDF. Link the legal version. Do not paste patient-level or participant-level data to prove a figure.

A maintenance habit that takes ten minutes

Once a month, open the page on a phone that is not logged into your university account. Check four things: the openings sentence still has a true date, the five papers are still the five you would hand a visitor, every outbound link resolves, and the email subject pattern matches what you told the last applicant. If a link died because a journal redesigned, fix the button. Do not add a sixth “also see” link that you will not check.

Search your own name plus “lab” in a private window after the page has been public for a while. You are looking for whether the hub is one of the results a stranger can open, and whether the title is the lab’s name rather than the name of the tool. Indexing is not a promise with a clock. A page with a real title, real sentences, and a stable URL is the part you control. How a bio page stays readable to Google is the general version of that habit.

Questions people ask before they ship

Will the department object? Some will. Keep their profile as the record they own. Describe the hub as the page you update between CMS refreshes, and link both ways. If a communications office wants a disclaimer, add one line. Do not wait for a redesign cycle to tell applicants the deadline.

Can students share the page in applications? Yes. That is a reason to keep claims checkable. “We pioneered the field” with no papers pinned is how a committee discounts the rest.

What if you are between jobs? Say so. “Moving to University Y in August; inquiries for the new group go to this address.” A hub that pretends the old department is permanent creates confused recommendation letters.

Five papers, one dated opening, one email pattern. Publish that before the next cycle, then keep the URL still while the science moves.

Create my page — Pro is 7€/month (~$7)

Free to start. Pro is 7€/month (~$7 depending on exchange) for a custom domain and full SEO controls.