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. A strategic approach treats the site as a working system instead, one with specific jobs to do and results you can check. Looking at it that way changes what you decide to build, what you fix first, and how you judge 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? Knowing that answer makes the rest of the project easier, because every page and feature can be weighed against it.

If the honest answer is “all of them equally,” the site will probably end up serving each of them poorly. It works better to pick one primary job, let the others support it, and revisit the choice when your programs change.

Design for everyone

There is a practical case for accessibility and mobile-first design beyond doing the right thing. Most supporters arrive on a phone, and an accessible site reaches more people and tends to convert better for everyone who uses it.

Practically, that means writing WCAG 2.2 AA into the requirements at the start of the build. Retrofitting accessibility after launch costs more, and it tends to turn into a scramble the week before go-live.

Make the key actions effortless

The donation and registration flows deserve more attention than they usually get, because small problems there translate directly into lost gifts and lost sign-ups. Fewer fields, clear trust signals, and accessible forms all reduce drop-off at the point where someone has already decided to act.

Earn trust with content

People trust concrete proof more than they trust adjectives, so lead with real impact numbers, named partners, and clear descriptions of how your programs work. Structure that content with sensible headings and plain language so that both people and AI assistants can read it.

Build to grow

Programs change over time, and the site has to keep up. A strong information architecture lets you add and update content without rebuilding, which protects the investment you made in the original project.

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 comes first, because friction there costs revenue every day it stays broken. After that come the homepage’s first screen and the page that explains what you do, since those decide whether anyone goes further. The pages your programs depend on come next, and the long tail of history pages, archives, and nice-to-haves can wait until everything above them is handled.

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. You lose less by shipping a smaller site that handles its key actions well than by spreading the budget thin across every page.

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? Unlike pageviews, those questions have answers you can actually 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 habit is most of what it takes to run the website as a system you manage rather than an expense you revisit every few years. It’s also how we’ve kept score with the 1,000+ organizations we’ve worked with since 2007: we look at what actually changed in the months after launch.