Nonprofit website strategy: what a great site needs

Most nonprofit websites are built like brochures: a stack of pages that describe the organization, refreshed every few years when the design starts to feel dated. Strategy treats the site differently: as a working system with jobs to do, ways to fail, and results you can check. That shift changes what you build, what you fix first, and how you know whether any of it worked.

The five jobs your site has to do

Strip away the page-by-page details and nearly everything a nonprofit website does falls into five jobs:

Weigh your current site against those five jobs and the redesign conversation changes. You stop asking whether the site looks dated and start asking which job it’s failing at — and what that failure is costing you.

Lead with purpose

Every effective nonprofit site can answer, in one sentence, what it’s for. Is it primarily to raise funds, recruit volunteers, deliver programs, or build credibility? Clarity of purpose shapes every other decision.

If the honest answer is “all of them equally,” the site will do none of them well. Pick the primary job, let the others support it, and revisit the choice when your programs change.

Design for everyone

Accessibility and mobile-first design aren’t niceties. Most supporters arrive on a phone, and an accessible site reaches more people and tends to convert better for all of them.

Practically, that means treating WCAG 2.2 AA as a requirement in the build, not a retrofit after launch. It’s cheaper that way, and it keeps accessibility from becoming a scramble the week before go-live.

Make the key actions effortless

Donation and registration flows are where strategy meets revenue. Fewer fields, clear trust signals, and accessible forms reduce drop-off at the moment that matters most.

Earn trust with content

Concrete proof builds more trust than adjectives: real impact numbers, named partners, clear program descriptions. Structure that content so people and AI can both read it.

Build to grow

Programs change. A strong information architecture lets you add and update content without rebuilding, protecting your investment over time.

Where to start when the budget is tight

Few organizations can rebuild everything at once, and few need to. The useful move is to rank the work by how close it sits to money and mission, then fund the top of the list properly instead of spreading a small budget across the whole site.

In practice the order usually looks like this: the donation flow first, because friction there costs revenue every day it stays broken. Then the homepage’s first screen and the page that explains what you do, because they decide whether anyone goes further. Then the pages your programs depend on. And only after that, the long tail of history pages, archives, and nice-to-haves.

The same logic works in reverse when a proposal comes in over budget: protect the pages that do the five jobs and trim everything else. A smaller site that converts beats a sprawling one that doesn’t.

Measure the things the site exists to do

Pageviews and time on site are comfortable numbers, but they don’t tell you whether the site is working. A site can grow traffic for years while donations stay flat.

Tie measurement back to the jobs instead. Are donations being completed, and where do donors drop out along the way? Are people signing up for the newsletter, for events, to volunteer? Are the right people finding you through search, and increasingly through AI assistants? And what do those tools say about you when they do? Those questions have answers you can act on.

Set a small handful of these measures before a redesign starts, record where you stand today, and check again a quarter after launch. That one habit turns the website from a periodic expense into a system you can manage. It’s also how we’ve kept score with the 1,000+ organizations we’ve worked with since 2007: not by how the launch felt, but by what changed afterward.