A funder, a donor, and a journalist, at different times, all make the same move: find the organization's name and open its website. One organization has a living account of its work, with results and a clear team. Another has a "website under construction" page that's been up for eleven months.
The first gets taken seriously before the first conversation even happens. The second might as well not exist, however wonderful its real work is. A website isn't a showcase or decoration, it's the point where strangers decide whether you're real or not.
A nonprofit's website does specific work: it confirms you exist, explains what you do and for whom, and unlocks infrastructure that doesn't function without it. This isn't a creative project about looking nice, it's trust infrastructure with a verifiable minimum.
The website's first job is confirming reality. Someone who's heard about you goes to check, and the site answers the silent question "are you even real." A living, filled-in site says yes, a placeholder or emptiness says "unclear," and unclear in this context almost always reads as no.
The second job is explaining the substance: what you do, for whom, why it matters, who's behind it. The third, often underrated, is a technical prerequisite for everything else. The verifiers from the unlock chain and TechSoup and Goodstack verification look at your website. Google Ad Grants, covered in the next lesson, requires a working site as a condition. Even domain email, without which verification stalls, lives alongside the site.
A young organization's website doesn't need expensive design. It needs a filled-in required minimum that all three types of readers look for: funder, donor, journalist.
That minimum looks like this. A clear name and mission on the first screen, no scrolling, no guessing. A description of programs: what you specifically do and for whom. Who's behind the organization: the team and board, real people with names, since an anonymous organization breeds distrust. A way to get in touch, and if you accept donations, a clear way to do it. Signs of legitimacy: EIN, status, a link to your Candid profile from your Candid profile. And working HTTPS, that padlock in the address bar, without which a site looks unsafe and technically fails part of the checks.
Between a beautiful empty site and a simple filled-in one, always choose filled-in. An empty page with gorgeous design is worse than a plain page that actually says who you are and what you do. A reader is looking for substance, not aesthetics, and no design can hide an absence of content.
Separately, about the "website under construction" placeholder: it's worse than having no site at all, because it actively communicates "we haven't gotten our act together yet." One honest, filled-in page beats a promising placeholder that's been up for months. A site can and should be improved gradually, but it needs to start filled in at the minimum level, not as a promise of future content.
Below is a website readiness checklist: the required minimum that outside readers check, and the technical prerequisites for the rest of your infrastructure.
Your website readiness checklist, marked with what's already in place and what needs finishing first. Keep it next to the infrastructure checklist from the unlock chain: your site is the link the launch of almost the entire rest of the chain depends on, and it's worth checking its readiness before applying to verifiers and to Ad Grants.
Does the website need to be professional and expensive from the start?
No. It needs a filled-in minimum that honestly tells people who you are. Beauty and complexity can be added later, content matters more than design from day one.
Can a social media page substitute for a website?
Temporarily, sometimes yes, but a website on your own domain is more reliable: it doesn't depend on someone else's platform, and it's exactly what verifiers and Google expect for many programs.
What's most important to do first if time is tight?
The first screen with name and mission, program descriptions, a team with names, and working HTTPS. This minimum is enough for the site to start building trust and unlocking infrastructure.
Do I have to display the EIN and status on the site?
Not legally required, but it's a cheap, strong signal of legitimacy. It's easier for anyone checking to trust an organization that openly shows its status and a link to Candid.
Your site is ready and confirms you're real. But it doesn't bring people to you on its own, it only greets those who've already arrived. Next you need a way to bring the right people there, and nonprofits have a tool for that businesses don't. The next lesson is about Google Ad Grants, and how to get up to $10,000 a month in advertising without losing it to a rule violation.