Leap the Nonprofit Discoverability Gap

A nonprofit homepage is expected to perform an impossible job.

It must welcome someone who needs help, explain the mission to a potential donor, reassure a funder, recruit volunteers, promote an upcoming event, recognize sponsors, collect email addresses, publish important news, and prove that the organization is active and credible.

It must do all of this quickly, clearly, and without making anyone scroll too far. The result is often a homepage that tries to say everything while communicating very little.

A visitor sees a mission statement, a large photograph, a row of program names, an event announcement, a donation button, and perhaps a declaration that the organization has been serving the community since 1978.

None of this is necessarily wrong. It is simply too much responsibility for one page.

Home Page Design for Nonprofits

Think of the homepage as the building’s lobby.

A good lobby tells visitors where they are. It creates a sense of confidence. It helps people orient themselves and points them toward the right destination.

The work of the organization does not happen in the lobby.

A hospital lobby does not provide surgery, diagnostic testing, physical therapy, billing assistance, or pediatric care. It helps people reach those services.

A library lobby does not contain every book. A university lobby does not teach every course. A government building does not attempt to conduct every public service at the reception desk.

Yet nonprofits routinely ask their homepages to represent the full depth of their missions.

This usually happens for understandable reasons. Creating one homepage feels manageable. Maintaining dozens or hundreds of pages does not. Programs compete for space. Board members want their initiatives represented. Staff members worry that visitors will miss something important. Eventually, every priority is compressed into a few panels on the same page.

The nonprofit homepage becomes less like a lobby and more like a storage room.

Everything is technically there.

Nothing is particularly easy to find.

A general page cannot answer a specific need

Imagine that a parent is looking for a summer art program for a ten-year-old.

The local arts organization offers one. Its homepage features an “Education and Outreach” section that explains that the organization provides creative experiences for people of all ages.

That sentence may be accurate, but it does not answer the parent’s questions:

• Is there a program for ten-year-olds?
• When does it begin?
• How much does it cost?
• Where is it held?
• Does the child need experience?
• Are supplies included?
• Is financial assistance available?
• How does the parent register?

The parent does not need a summary of the organization’s commitment to arts education. The parent needs a page about the summer art program.

The same distinction applies throughout the nonprofit world.

A business owner does not need to hear that an economic-development organization “supports entrepreneurship and regional growth.” The owner needs to know whether financing is available for a new restaurant.

A purchasing manager does not need a general statement about supplier diversity. The manager needs to find a certified electrical contractor who is licensed to work in Ohio.

A family facing eviction does not need a broad description of a social-service agency’s commitment to community stability. It needs eligibility requirements, hours, documentation instructions, and a phone number.

Broad language can describe the mission.

Only specific information can make the mission usable.

The curse of the program card

Many nonprofit websites address this problem by using a row of program cards.

Each card contains an icon, a program name, a sentence of description, and perhaps a “Learn More” button. It is a reasonable design pattern, but it often conceals how little information exists beneath it.

Sometimes the button leads to a dedicated page. More often, it leads to another general page containing several programs. In the worst cases, there is no button at all.

The card appears to be an information system without actually being one.

Consider a nonprofit with twelve business-assistance programs. Its homepage presents three categories:

• Business Development
• Workforce Solutions
• Community Resources

These labels may make perfect sense inside the organization. They may correspond to departments, funding sources, or internal reporting structures.

To a visitor, they are abstractions.

Where does restaurant financing belong? What about helping hire an apprentice? Is a façade improvement grant a business-development service or a community resource? Would a person who needs export assistance consider looking under “Business Development”?

The website reflects how the organization is managed rather than how the public experiences a need.

That is one of the most common sources of the Discoverability Gap.

Build for the search, not the org chart

Organizations naturally describe themselves in terms of their internal structure.

People outside the organization do not care about that structure unless it helps them get somewhere.

They do not need to understand which department administers a program, which committee oversees an event, or which grant funds a service. They need to recognize their situation and find an appropriate next step.

This requires a subtle but important shift.

Instead of asking: Where does this information belong in our organization?

Ask: What would someone call this if they did not work here?

The difference can be substantial.

• “Community Capital Access Initiative” may be the official program name. A business owner may search for “small-business loans in Rock County.”
• “Emerging Creatives Community Engagement Series” may satisfy a grant proposal. A parent may search for “free art classes for teens.”
• “Certified Enterprise Development Resource Network” may be understood by industry insiders. A buyer may search for “minority-owned suppliers near Chicago.”

Official language still has a place on the page. But it should not be the only language available. A discoverable website translates the organization’s internal vocabulary into the public’s vocabulary.

One audience at a time

Homepages struggle because nonprofits serve many audiences.

An arts organization may need to speak to artists, visitors, donors, volunteers, teachers, sponsors, vendors, and the media. An economic-development group may serve entrepreneurs, established companies, investors, site selectors, municipalities, job seekers, and community partners.

Trying to speak to all of them simultaneously produces vague language:

We bring people together to create opportunities and strengthen our community. Nearly every nonprofit could make that claim.

It does not tell any particular visitor what can be found, what can be done, or where to go next.

Specific pages allow the organization to speak clearly because each page can serve a more focused purpose.

• A page for participating artists can explain application requirements.
• A page for visitors can explain dates, parking, accessibility, and activities.
• A page for sponsors can describe audience reach and partnership opportunities.
• A page for teachers can provide classroom resources.

These pages do not fragment the mission. They make the mission intelligible to the people who experience it differently.

The nonprofit remains one organization.

It simply stops forcing every audience through the same doorway.

Your homepage is not your website

Nonprofit leaders sometimes evaluate their entire digital presence by looking at the homepage.

They debate the headline, hero image, button colors, and order of the panels. These decisions matter, but they can distract from a more important reality: many visitors will never enter through the homepage.

A person may arrive directly on an event page from a calendar listing. Another may find a resource through Google. A prospective volunteer may follow a link from an email. A buyer may enter through a supplier profile shared by a colleague.

For these visitors, the interior page is the front door.

This is healthy.

A useful website has many entrances because people arrive with a variety of needs. The homepage welcomes broad interest; deeper pages meet specific intent.

The objective is not to route every visitor through the same ceremonial entrance. It is to help each visitor reach the right place with as little confusion as possible.

This is particularly important for search.

Search engines do not primarily ask whether a homepage represents the organization beautifully. They try to identify the page most relevant to the person’s question.

A homepage that briefly mentions 20 programs is unlikely to be the best answer for any of them.

Specificity creates relevance.

The fear of too many pages

Nonprofits often resist creating dedicated pages because they worry the website will become too large.

This is a legitimate concern if pages are created carelessly. Thin, duplicative, outdated content can make a website harder to maintain and less trustworthy.

But the opposite problem is more common: organizations compress important services into too few pages because they confuse simplicity with smallness.

A simple website is not necessarily a website with very few pages.

A simple website is one in which people can understand where they are, find what they need, and know what to do next.

A public library may have thousands of resources and still provide a clear experience. An online retailer can carry millions of products while helping someone locate one specific item. The challenge is not the amount of information. It is how that information is structured.

A nonprofit should not create a page for every sentence it has ever written. It should create a page when the subject represents a meaningful public need, resource, opportunity, program, person, event, or decision.

The test is not: Will this make our website bigger?

The test is: Would someone reasonably look for this?

If the answer is yes, the information deserves a findable home.

The limits of navigation

Even a well-designed navigation menu cannot represent an entire mission.

Navigation usually contains five or six major categories because that is what people can reasonably scan. Those categories help visitors explore, but they cannot name every program, service, event, and resource.

This is another reason organizations should not rely solely on the homepage and main menu.

Discoverability happens through several paths:

• Website navigation
• On-site search
• Search engines
• Digital advertising
• Email links
• Partner websites
• Social media
• Maps and directories
• Shared content networks
• Direct referrals

A program does not need to appear in the main navigation to be discoverable. It needs a useful page, clear connections to related content, and a place within the organization’s information structure.

The menu is a map but it does not describe the entire territory.

The homepage should make promises

Once the homepage is relieved of carrying the entire mission, its real purpose becomes clearer.

A strong nonprofit homepage should answer a few basic questions:

• Who are you?
• Who do you help or serve?
• What kinds of value can people find here?
• Why should they trust you?
• Where should they go next?

It should make promises that deeper pages fulfill.

If the homepage says the organization supports local artists, visitors should be able to discover those artists.

If it says the organization helps small businesses grow, visitors should be able to find specific forms of assistance.

If it says the organization connects buyers with diverse suppliers, buyers should be able to search for qualified companies.

If it says the organization provides essential services, the path to those services should be unmistakable.

The homepage introduces the mission.

The rest of the website proves that the mission is real.

A useful test

Open your organization’s homepage and pretend you know nothing about it.

Do not read it as an employee, board member, donor, or long-time supporter – read it as a stranger with a specific need.

• Can you identify the individual programs the organization provides?
• Can you determine who qualifies for them?
• Can you find upcoming opportunities?
• Can you discover the people, businesses, artists, members, or resources the organization exists to support?
• Can you take a meaningful next step?

Then search Google without using the organization’s name. Search for the need, not the provider.

If the organization serves entrepreneurs, identify the kinds of assistance an entrepreneur might request. If it promotes artists, search for an artist by medium and location. If it provides social services, search using the words a family might use during a difficult moment.

Does the organization appear?

Does the search result lead to the right information?

Or does everything lead back to the homepage, where the visitor must begin again?

That distance—from the specific need to a general description of the organization—is part of the Discoverability Gap.

Give the mission room to exist

A nonprofit’s mission is rarely focused on just one thing. The mission unfolds across programs, relationships, resources, events, people, places, and acts of service. Compressing all of that into a homepage may make the website look tidy, but it reduces the public’s ability to encounter the full value of the organization.

The answer is not a busier homepage. It is a deeper website.

Let the homepage welcome people, explain the central promise, and direct them toward the right path. Then give each meaningful part of the mission enough room to be understood and found.

Repeat after me…the homepage does not need to carry the entire mission.

It needs to open the door so the depth of the mission can be discovered.

---

Key Take Aways

• The Homepage as a Lobby: The homepage should act like a building’s lobby—orienting visitors and pointing them toward the correct destination, rather than attempting to provide every service.
• The Problem with Generality: Because homepages try to appeal to every audience (donors, volunteers, program participants), they often become vague and ineffective at answering specific user needs.
• Avoid “Org Chart” Structures: Websites should be built based on how the public searches, not how the organization is managed internally. Official department names often confuse visitors looking for specific help.
• Homepage vs. Website: A homepage is just one entrance; visitors often arrive directly at internal pages via search engines or external links. Organizations should build a portfolio of specific landing pages rather than relying on the homepage for everything.
• Quality over Quantity: While organizations often fear having “too many pages,” the goal should be simplicity—ensuring visitors can find what they need, understand where they are, and know the next step.
• Making Promises: The homepage should clearly communicate who the organization serves, what value it offers, and what the user can expect, leaving the deeper mission delivery to dedicated internal pages.