What Makes a Good Nonprofit Website? 10 Elements, Proven by Real Builds

Key takeaways

• A nonprofit website is part of a marketing system, not a standalone thing. It only fundraises when the brand, the messaging, the technology and the monthly marketing rhythm are designed together.
• The ten essential features: single primary CTA per page, a one-sentence mission, donor-facing transparency, WCAG 2.1 AA accessibility, real-people storytelling, mobile-first structure, donation treated as a product, a named integration stack, AEO-aware content, and a documented maintenance plan with SEO-preserving migration.
• Three things most nonprofit web content misses: donation as a product rather than a form, building for the AI era (AEO-aware content plus machine-readable structure), and weighting migration and SEO preservation as the highest-risk moment in a website's life.
• Real proof: San Diego Foundation (41% conversion lift, 248% planned-giving growth), Curebound (75% net-new donors), Susan Wojcicki Foundation, UNEP World Environment Day across 150+ countries.
• The bonus 11th element is the ongoing strategy process: quarterly reviews, AEO updates, and a migration playbook ready before the next platform shift.

Download the 10-element scorecard and score your own site against these.

Most nonprofit websites don't fail because they're ugly. They fail because they're built as if they're going to do the work alone.

A website is one tool in a larger system. The brand sets up the conversation. The messaging carries it. The technology decides what's possible. The monthly marketing work decides whether anyone shows up at all. Most lists like this one skip past that and go straight to design checkboxes: mission above the fold, donate button in the nav, mobile-friendly, fast, accessible. All true. None of it explains why so many nonprofit websites still don't fundraise.

I've watched this play out across more than 200 builds at Fifty and Fifty. These are the ten elements that actually predict whether a website works, each paired with a real build and the outcome it produced.

A note on framing: this work sits inside Engagement OS, Fifty and Fifty's growth-systems methodology, guided by three diagnostics called Strategic Altitude, Supporter Resonance and Operational Readiness. The elements below are what those diagnostics surface, build after build.

1. Audience research and strategy come before design

A nonprofit website that works almost always started with someone willing to do the unglamorous part first. The audit. The donor profiles. The audience map. The content inventory. The parts nobody wants to pay for.

When I start a new engagement, the first conversation isn't about design. It's about who actually gives, who the organization thinks gives, and the gap between those two pictures. Most organizations assume they know their audience. Most are more wrong than they realize, and that gap is where redesigns succeed or fail, long before the first wireframe.

This is the Engagement OS Diagnose phase. Strategic Altitude surfaces what leadership thinks the audience needs. Supporter Resonance surfaces what the audience actually responds to. Operational Readiness assesses whether the organization can pull off the strategy once it's defined.

In practice: define your audiences specifically. Map the donor journey from acquisition source through conversion. Find where the data shows people drop off today. The site you build for "people who care about our mission" will be worse than the site you build for "people who gave once and didn't renew." The second has a real decision behind it.

2. Build the website inside a marketing system, not a silo

A website sits inside a brand, a messaging system, a marketing stack and the monthly rhythm of how you talk to supporters. The most common reason nonprofit websites underperform is that they were built alone and bolted onto everything else afterward.

When the system is connected, the gains compound. Susan Wojcicki Foundation launched as a complete build rather than a website project: refreshed brand, refreshed messaging, the site itself, a coordinated launch sequence, and a PR partnership so the story landed across channels at once. A new foundation launching into a difficult subject doesn't get a second first impression. Every piece was designed to support every other piece.

The opposite is set-and-forget marketing, agencies that turn on SEO or email and walk away. That stops working inside 12 months, every time.

In practice: before you scope a redesign, audit every channel that touches a supporter. Email, paid, organic, events, donor stewardship, board outreach. Decide what the website has to change so those channels stop competing with each other.

3. Lead the homepage with the problem, not the mission

Most nonprofit homepages talk about the organization. Great ones talk about the problem the organization exists to solve, then earn the right to talk about themselves.

Foundations are especially prone to skipping this. Because they don't need to raise from individuals as urgently, they tend to lead with grant cycles, history and portfolio, and the problem that justifies the work gets buried. International NGOs hit the same wall from the other side: powerful field stories they struggle to turn into a problem statement that lands with someone scrolling on a phone.

Susan Wojcicki Foundation handles this well. Susan Wojcicki, a founder of YouTube, died of lung cancer at 56, and her family launched the foundation in her memory to fund research and prevention. The site distils its mission to one line: building a future where lung cancer is detected earlier, prevented more often, and lives are saved. The homepage opens on the problem. Lung cancer is the deadliest cancer in the United States, and a significant share of those diagnosed never smoked (American Cancer Society, American Lung Association).

Note what they did there. They cited the sources by name, the way a research paper would. That's donor-facing transparency: credibility built through traceability rather than through adjectives.

In practice: open with a problem statement, not a mission statement. Keep the mission to one sentence. Cite your sources by name. Then introduce the work. Then ask.

4. Use one primary CTA per page

Be clear about what you want a visitor to do. If you want donations, ask for them. If you want volunteers, ask for them.

The cliché is "have a prominent donate button." The real rule is to have one primary action per page. Walk through ten nonprofit homepages and you'll count four to six actions competing above the fold: donate, volunteer, sign up, learn more, attend, follow. When everything is a priority, nothing is.

When we worked with San Diego Foundation, the redesign organized around exactly this. Foundations historically struggle with primary-CTA discipline because their work is largely B2B, advising fund holders and granting to local organizations. San Diego Foundation made the call: every page would drive toward becoming a donor-advised fund holder or a grant partner, and every CTA reinforced one of those two pathways. The result was a 41% conversion lift across the site and 248% growth in planned giving. Not because the new site looked better, but because every page knew its job.

I've seen that pattern repeat at smaller scale across the rest of our 200+ builds. CTA discipline is the cheapest, fastest conversion lever in nonprofit web design, and the one most consistently skipped.

Pro tip: audit your homepage's CTA discipline before scoping a redesign. Open it and count every clickable element above the fold that asks for an action. More than two and you're competing with yourself. The fix is upstream: figure out the primary action, demote everything else, and treat the homepage CTA hierarchy as a strategy decision, not a design decision. Want a structured way to score your site? Download the 10-element scorecard, or talk to us about Fifty and Fifty's Web and Digital Experience service.

5. Differentiate the brand with what only you can credibly say

Most nonprofit homepages sound the same. Same hero phrasing, same mission structure, same stock photography, same About / Our Work / Donate navigation. A donor who scrolls past three foundation websites that sound interchangeable will remember none of them.

Differentiation isn't a design layer. It's a strategy layer. The work is figuring out what only your organization can credibly say, then building the site around that.

Curebound built its identity around one phrase: the city that cured cancer. It tied together facts that would otherwise sit apart. That Curebound operates in San Diego. That the city is home to the Salk Institute and the La Jolla Institute for Immunology. That the foundation funds collaborative research across those institutions. The phrase made the strategy memorable, the site and email program and campaigns all carried it, and 75% of registrants and donors that year were net-new, because the differentiation gave people something to repeat.

In practice: write down what only your organization can say. Test it against what every other nonprofit in your category says. If it could appear on any of their sites, it isn't differentiation. Rewrite until it can't.

6. Focus content, build mobile-first, bury the rest

The two failure modes are mirror images. Some sites try to do everything. Some dump everything onto the page, a section per program and a sub-page per sub-program. Both produce the same visitor: overwhelmed, and unable to act.

The discipline is restraint. Decide what someone needs to see, and when, and put everything else two clicks deep. Mobile traffic is now the majority of nonprofit website visits (roughly 53%, per NPTechforGood), which means the structure has to work on a 5-inch screen first. If a section doesn't earn its space there, it doesn't earn its space at all.

UNEP World Environment Day, the United Nations Environment Programme's annual global campaign, shows this at scale. It runs across 150+ countries with national events, sector partners and content in multiple languages. The site can't put every event on the homepage. It surfaces the year's theme, the way to participate and the global view, and lets everything else live a layer deeper for the visitor hunting a specific country or partner. Done badly this is a dumping ground. Done well, it scales.

In practice: rank-order every section of every page. Build mobile-first. Be willing to cut. A page that does 3 things well beats a page that does 7 things poorly.

7. Use real-people storytelling — no stock photos

Stock photos of multi-ethnic teams pointing at laptops are the visual equivalent of corporate filler. Everyone in the sector uses them. Nobody trusts them. A donor who lands on a stock-photo nonprofit site has been told, on some level, that the organization couldn't be bothered to show its actual work.

Real-people storytelling means named subjects, real photography, named partners, named outcomes. It also means letting the people doing the work tell it: researchers, program staff, beneficiaries with full consent and editorial control, volunteers, the donors who keep coming back. The principle is older than the internet. People give to people.

Curebound does this by naming the institutions and the science. Salk. La Jolla Institute for Immunology. Specific collaborations, specific outcomes. Susan Wojcicki Foundation does it differently: a letter from Susan's family, her story told plainly, and editorial discipline that refuses to turn a public health crisis into decoration. Two approaches, one shared refusal to be generic.

In practice: replace every stock photo with a real one. If you don't have real photos, plan a shoot before launch. It returns more than almost anything else you can spend the same money on, and most nonprofit budgets underfund it. Name your partner institutions. Quote the people doing the work.

8. Treat donation as a product, not a form

Most nonprofit websites treat the donation moment as a form to fill out. The good ones treat it as a product to design, measure and improve.

A form is a transaction. A product is an experience connecting the acquisition source, the donor journey and the relationship afterward. Once you treat it that way, you start seeing things invisible from inside the form itself. Which channels bring donors who actually convert. Where people abandon the flow. Whether the recurring-giving prompt is helping or hurting. How a one-time donor becomes a sustaining one.

That's the thinking behind Habitat, a CMS built around fundraising rather than around content. Habitat is a Donately product, and a disclosure: Fifty and Fifty and Donately share a founder, so I'm not impartial about it. Habitat exists because nonprofit teams kept needing a CMS that treated campaigns, events and donation flows as first-class objects rather than retrofits. Susan Wojcicki Foundation runs on it. San Diego Foundation's 248% growth in planned giving was a downstream effect of treating the donor pathway as a product, with every page advancing the journey instead of decorating it.

In practice: stop thinking of the donation page as a form. Measure it like a product. Conversion rate, average gift, recurring uptake, donor lifetime value. Then design the site backward from those.

9. Name your integration stack — CRM, donation, email, forms, automation

Buyers ask agencies about "CRM integration" generically, and that's already the wrong question. The real decision involves named platforms, because each one shapes what the website can and can't do once it ships.

What nonprofits actually use, by category:

• CRMs: Salesforce and specifically the Nonprofit Success Pack; HubSpot; Blackbaud Raiser's Edge
• Donation platforms: Donately, GiveButter, GoFundMe Pro
• Email: MailChimp, HubSpot, Constant Contact
• Forms: Gravity Forms, HubSpot native, or the donation platform's own
• Data and automation: Google Workspace, Zapier, Apollo, and the Model Context Protocol layer starting to connect AI tools to nonprofit data securely
• Project and operations: ClickUp, Monday.com

The principle behind naming all of them: stack decisions drive the CMS decision, not the other way around. I've watched dozens of redesigns get derailed because the CMS was chosen before the integration stack was mapped, and the organization spent the next three years writing custom integrations and losing data in the seams. San Diego Foundation's 41% conversion lift and 248% planned-giving growth don't happen with a misaligned stack, because landing pages, donor-advised fund tools, CRM and planned-giving tracking all have to move data in concert.

Pro tip: do the integration audit before you scope the redesign. List every platform you use. Mark which you're committed to, which are under review, and where the pain is today. Bring that list to your agency on day one. A CMS choice made without that input is guesswork, and you find out 3 months in. For the full walkthrough we use with new clients, talk to us about Fifty and Fifty's Web and Digital Experience service.

10. Build accessibility in from day one — WCAG 2.1 AA is the floor

Most agencies treat WCAG 2.1 AA and ADA compliance as a checkbox. That framing is wrong, and it costs nonprofits real money.

Accessibility is a reach decision. The more people who can use your site, the more screens it renders on, the more assistive technologies can parse it, the more search engines and AI tools can read it, the more fundraising you can do. That's a maths argument sitting on top of the moral one. Excluding people from your site excludes their donations.

It has also expanded past screen readers, colour blindness and learning disabilities, though all of those still matter and WCAG 2.1 AA is the floor rather than the ceiling. The newer audience is machines. AI tools and agents now crawl your site and rebuild its content for people who may never visit it directly. A site those tools can't read is invisible to a growing share of the people who would have found you.

Susan Wojcicki Foundation was built to WCAG and ADA compliance from day one, with content written to be both accessible and understandable on a hard subject. The technical layer includes schema markup, structured data and clean SEO foundations. The result is a site that works regardless of device, network speed or assistive technology, and that machines read as well as people do.

In practice: WCAG 2.1 AA is the floor. Build for screen sizes from televisions down to watches. Write at the reading level your audience actually reads at. Use semantic HTML and schema markup. Run accessibility audits before launch and on every quarterly review, because content drift breaks compliance.

Bonus: Build AEO-aware content and an ongoing maintenance plan

This is the element almost no agency delivers yet, and the one about to separate nonprofit websites that get found in 2026 from those that don't. I think it's the biggest shift in nonprofit web design over the next 24 months, and most organizations don't realize it's happening.

AEO-aware content

Agents and AI tools, ChatGPT, Claude, Gemini, Perplexity and others, already crawl nonprofit sites, parse the content and answer users who never click through. Someone asks about lung cancer foundations to support, and the answer is assembled from content across multiple nonprofit sites. They may never see Susan Wojcicki Foundation's homepage. They see whatever the model could parse.

Building an AEO-aware site (Answer Engine Optimization, the AI counterpart to SEO) means structuring content so machines read it as cleanly as a screen reader does. Schema markup, semantic HTML, structured data, llms.txt files, explicit FAQ blocks, and content written in patterns retrieval systems can lift cleanly. Fifty and Fifty publishes a /llm-info page, a machine-readable description of the agency, as one example. Most nonprofit sites have nothing like it. The ones that adopt it first get cited.

The ongoing strategy process

The worst thing you can do with a new website is launch it and stop. The platforms crawling your site update constantly. So do the tools in your stack, and the expectations of your donors. A site that performed in 2024 already needs work for 2026.

Migration is the highest-risk moment in a website's life. A redesign can wipe out years of accumulated SEO and AEO authority overnight if it isn't handled carefully. A defensible methodology includes one-to-one URL mapping with 301 redirects for every legacy URL that ranks or has backlinks, schema preservation, sitemap resubmission to Google Search Console, internal-link auditing, content-parity checks so you don't quietly drop a high-traffic page for looking dated, Core Web Vitals monitoring for 90 days after launch, and llms.txt continuity. Most nonprofit redesigns skip half of it and pay for it in lost traffic the following year.

The fix is a process, not a feature. A quarterly review covering content, security patches, performance, AEO-readiness checks and integration health. An owner, internal or agency, responsible for keeping it current. A migration playbook ready before the next platform shift rather than improvised during it.

Stop doing random acts of marketing. Build the system that makes the website your hardest working employee, then maintain it like one.

Frequently asked questions

What are the essential features of a successful nonprofit website?

The ten elements above are the long answer. The short one: a single primary CTA per page, a one-sentence mission, donor-facing transparency, WCAG 2.1 AA accessibility built in from day one, real-people storytelling, mobile-first structure, donation treated as a product, a named integration stack, AEO-aware content for AI retrieval, and a documented maintenance plan with an SEO-preserving migration methodology.

What accessibility compliance standards should a nonprofit website meet?

WCAG 2.1 AA is the floor. ADA Title III applies to most US-based nonprofits and effectively requires WCAG 2.1 AA as the practical standard. Some sectors add more: Section 508 if you take federal funding, GDPR-aligned accessibility for EU audiences, AODA in Ontario. Build it in from day one rather than auditing at launch. Retrofitting typically costs three to five times what building it in costs. Audit quarterly afterward, because content drift breaks compliance faster than most teams expect.

What's the most important page on a nonprofit website?

It depends on what the website is for. For most nonprofits, the homepage is the conversion hub — it's the single most-viewed page on the site, accounting for over 20% of all pageviews across organizations. For organizations running specific campaigns, the campaign landing page outperforms the homepage in any given quarter. For foundations doing donor-advised fund acquisition, the "become a fund holder" pathway page matters more than the homepage. The question to ask: what's the one action you want a first-time visitor to take? Then build the most important page to surface that action most directly.

Why isn't my nonprofit website converting donors?

The usual reasons, in order. Too many CTAs above the fold competing for attention. The mission buried under organizational language, so a visitor can't tell what problem you solve within 5 seconds. A donation page built as a form rather than backward from conversion metrics. Missing trust signals: no named sources, no real people, no specific outcomes. And a site that doesn't work on mobile, where over half of nonprofit traffic now lives. Work through them in that order. Fixing the first usually shows up within a month.

How do I make my nonprofit website discoverable by ChatGPT, Claude, and Perplexity?

Start with the structure: schema markup, semantic HTML, clear FAQ sections, descriptive titles and headings. Add a canonical /llm-info or /llms.txt file describing your organization in machine-readable form. Make sure the content is parseable, because opaque hero videos and image-based text don't get retrieved. Write in question-and-answer patterns where it fits. Source every factual claim with a working link, because retrieval systems weight content that cites primary sources.

What happens to my SEO during a redesign?

Migration is the highest-risk moment for your organic traffic. A redesign done without a documented SEO methodology can wipe out years of accumulated authority, sometimes 30% or more, sometimes permanently. What protects you: one-to-one URL mapping with 301 redirects for every legacy URL that ranks or has backlinks, schema preservation, sitemap resubmission, internal-link auditing, content-parity checks, and Core Web Vitals monitoring for 90 days after launch. Ask any agency before you sign: what's your migration methodology? If they can't answer concretely, walk away.

How much should a nonprofit invest in a website?

A productized small-org build starts around $5,000. A custom build for a mid-sized nonprofit typically runs $25,000 to $80,000 and up. Larger builds with complex integrations run higher. The more useful question is the system budget, covering strategy, brand, build, integrations, content, accessibility and ongoing maintenance, rather than the build line alone. A $10,000 build paired with $50,000 of supporting investment will outperform a $50,000 build paired with nothing.

Where to go from here

If you're scoping a redesign and want a structured way to score where you stand against these ten elements, download the 10-element scorecard and walk through it with your team.

If you want to talk about what a full engagement could look like, Fifty and Fifty's Engagement OS service is the starting point.

The website is the most important tool in your fundraising stack. Treat it like one.

‍