Your Nonprofit Website Isn’t a Sitemap. It’s a Journey.

A nonprofit website may need to help someone find services, explain the organization's work, attract donors, recruit volunteers, support advocacy, and give partners useful information. As those responsibilities accumulate, it's easy for the site to reflect the organization's structure more closely than the needs of the people using it.

Programs get pages, initiatives get sections, and resources are arranged around how the team understands its work. That makes sense internally, but a visitor may simply be looking for help, deciding whether to donate, or exploring a partnership.

Those visitors arrive with something they're trying to accomplish. Visitor journey mapping helps us look at what they need to understand and do, rather than beginning with the pages we already have.

Start with the journey, not the pages

Journey mapping can become detailed, but a nonprofit website can start with three stages that are simple enough to discuss together:

Awareness → Learning → Decision

Awareness is about helping someone recognize that they're in the right place. Someone looking for help needs to see that your organization may address their need. A potential donor needs to understand the problem you're working on. A partner needs to recognize where your work overlaps with theirs.

Learning is where a visitor develops enough understanding to make a decision. They may need to know which services are available, who qualifies, how the organization helps, what impact it has, and what will happen if they reach out.

Decision is the next step that fits their purpose, whether that's getting help, using a resource, donating, volunteering, contacting someone, or becoming a partner. Sometimes another website or resource serves that need better. The map should help us understand those choices without forcing every visitor through the same funnel.

Personas help provide context

Someone looking for immediate help has different needs from a donor or community partner. Personas can help identify those differences, but I wouldn't begin by spending a lot of time on detailed profiles.

I'd focus on who the person is, what they're trying to do, what they already know, what they need to learn, and what could prevent the next step. That context helps us understand what the website needs to do for them.

How this came up with WithinReach

I recently worked through this while developing a website strategy for WithinReach, a nonprofit serving families and communities in Washington State.

WithinReach's main website is part of a broader digital ecosystem of programs, resources, partnerships, and related websites. People can arrive looking for help, learning about the organization's work, exploring a partnership, engaging with advocacy, or considering a donation.

We thought about the main website as a front door to that broader ecosystem. It didn't need to contain everything the organization does, but it did need to help people understand where they were, what was relevant, and where to go next.

Sometimes the right destination is another resource or website. The organization may see that as a handoff between digital properties, while the visitor is simply trying to reach the help or information they need. Organizing the experience around that purpose can reveal gaps that an internal sitemap doesn't.

Your first map is still an assumption

A journey that makes sense to the team is still an assumption about visitors. Someone looking for help may enter through an unexpected page, use different language, skip information the team considers important, or get stuck at a step that seemed straightforward.

That's why the map needs pathway validation. Analytics, search behavior, staff conversations, interviews, and usability testing can help us compare the intended journey with what people actually do.

Start with one action

Start with one important action, such as Get Help, and work backward. Consider what a visitor needs to learn before taking it, what brings them to the organization, and how they'll recognize that they're in the right place.

The starting journey is still:

Awareness → Learning → Decision

Then look for evidence that the path works, including where visitors take a different route or need more help.

That gives you a basis for deciding whether navigation, content, or the connection to another resource needs to change before adding pages or rearranging the site.