A reviewer looks you up before they score you. What do they find?

You spent months on the proposal. At some point during review, a panelist will stop reading it, open a new tab, and type your name into Google or ChatGPT. Whatever comes back sits next to your PDF while they score you. You cannot touch it on the day. You can fix most of it now.

TL;DR: Most grant and fellowship review isn’t anonymous, so the panel forms a second impression of you, outside your proposal, from whatever a quick search returns. That impression is auditable. Run the searches a reviewer would run, and check that your best work surfaces, that your name resolves to you and not a namesake, and that your own pages aren’t blocking the AI tools reviewers now use. Close the gaps before you submit, not after.

Why does what a reviewer Googles matter more than your formatting?

Almost all grant advice optimizes the document. Almost none of it optimizes what a reviewer sees when they look away from the document.

Some journal peer review hides the author’s identity, but grant and fellowship review almost never does. At NIH, NSF, the ERC, and most fellowship panels, the reviewer knows exactly whose name is on the application. Fellowships are worse in this respect, because the scheme is funding a person, not just a project, so the person is the point. Curiosity is cheap and normal. They read your career narrative, they wonder who you’re, and looking you up costs one tab.

What they find becomes a quiet input to the score. Not a line on the form. Just an impression, formed in a minute, that colors how they read the rest. A clean, current, on-topic footprint reads as low risk. A dead LinkedIn from 2016, a Scholar page that blends your work with three strangers, and nothing online about the specific topic of the proposal reads as something else. None of that’s in your PDF, and all of it’s auditable.

What should you check before you submit?

Sit down a few weeks before the deadline and run the check yourself. It takes about twenty minutes and needs nothing but a browser. Do it logged out or in a private window, so you see what a stranger sees and not what Google has personalized for you.

Does your best work surface for the query a reviewer would type?

Don’t search your own name and stop there. Search the way a panelist would: your name plus your topic, then the topic on its own. “Jane Okafor microplastics,” then “microplastics freshwater uptake.” Does your most relevant paper show up on the first screen, in Google and in an AI tool like ChatGPT or Perplexity? If your strongest work is invisible for the exact query your proposal is about, the reviewer’s search quietly contradicts your claim to own the topic.

Does your name resolve to you, not to a namesake?

Now type your name alone. If the first page belongs to a more famous cardiologist who shares it, or to a LinkedIn that’s not yours, the reviewer may never reach you at all. You can’t evict the namesake, but you can outrank them on your own turf: a personal page you control, an institutional profile that’s actually updated, an ORCID that points at your record.

Is your Google Scholar profile disambiguated and current?

Scholar auto-merges papers by matching names, so profiles routinely absorb work from strangers and drop your own. Open yours. Remove the papers that aren’t yours, add the ones it missed, and make your affiliation and listed interests current. A reviewer who lands on a profile crediting you with a physicist’s papers reads carelessness, whether or not that’s fair to you.

Does your page block the AI a reviewer is now asking?

This one is invisible and common. When a reviewer asks ChatGPT or Perplexity about you, those tools can only quote pages their crawlers are allowed to read. Many university sites and personal setups block AI crawlers by default in robots.txt: GPTBot, PerplexityBot, ClaudeBot, Google-Extended. OpenAI is explicit that pages opted out of its OAI-SearchBot will not appear in ChatGPT’s search answers. So your bio and publications list can be perfectly accurate and still be missing from the exact answer the panel is reading. Check your site’s robots.txt (it lives at yoursite.com/robots.txt). If your own pages are walled off, unwall the ones you want cited.

The impression is fixable, which is the whole point

Notice what these four checks have in common. None of them asks you to become a better scientist by the deadline. Each one asks whether the version of you that a stranger assembles in a minute or two matches the version in your proposal. When it doesn’t, the mismatch does the damage, and you can usually close it in an afternoon.

There is a seasonal reason to do it now. The fall grant and fellowship deadlines are a few weeks out, which means the panels that will read those proposals are a few weeks after that. The search a reviewer will run in October is the same one you can run today.

Where Loud Camel fits

This is the check Loud Camel runs for you on a schedule, so you’re not doing it by hand the week a proposal is due. It watches what surfaces for your name, whether AI tools attribute your work to you or to a stranger, and where your footprint contradicts your CV. Then it drafts the fixes and any outreach for you to approve. It drafts. It does not send anything on its own. You stay the one who decides what goes out.

None of this rescues a weak proposal. It stops a strong one from being read next to a stale page or a stranger who happens to share your name.