What should a foundation website explain before asking for support?

Start with understanding, not urgency

Visitors who arrive on a foundation website may know almost nothing about the organisation. They may have followed a shared link, heard about a project, or be comparing causes before deciding whether to help. A large donation button can be visible, but it should not be the only answer the homepage provides. People need enough context to understand what their support would mean.

Introduce the foundation in plain language. State the issue, the people or environment affected and the change the organisation is trying to make. Avoid beginning with internal programme names or a long institutional history. A visitor should be able to explain the basic purpose to someone else after reading the opening section.

Use a direct invitation to learn more. Link to the mission, approach, current work and ways to help. The website should support people who are ready to donate as well as those who need time, evidence or a personal conversation before making a decision.

Explain the problem with care

Describe the problem without reducing people to statistics or portraying communities only through crisis. Explain what is happening, why it matters and what contributes to it. When the issue is complex, acknowledge that complexity. A foundation can be clear without pretending that one intervention solves everything.

Use data with a source, date and relevant context. A large number without a time period or comparison may create emotion but not understanding. Link to research where appropriate and explain what the foundation knows, estimates or is still learning. This honesty supports credibility.

Show whose perspective shapes the work. Explain how affected people, local partners, researchers or practitioners contribute to decisions. Avoid implying that the foundation alone arrives to save a community. Respectful language makes the work more accurate and signals that participation matters.

Make the approach tangible

The mission describes why the foundation exists; the approach explains what it does. Show programmes, partnerships, activities and decisions in language a visitor can follow. Explain what happens after a grant, campaign, research project or community activity begins. A simple journey can be more useful than a list of abstract values.

Be clear about the foundation’s role. It may fund partners, run services, support research, convene organisations, advocate for change or combine several roles. Explain what it does directly and what others deliver. This prevents visitors from assuming that every outcome is produced by one team.

Describe limits and choices. Not every eligible project can be funded, and not every positive result is immediate. Explain priorities, geographic scope, application criteria or reasons for focusing on certain groups. Transparency helps potential partners and supporters decide whether their expectations align.

Combine evidence with human stories

Evidence helps visitors understand scale, progress and limitations. Stories help them understand experience and meaning. Use both deliberately. A project page might show the need, activity, number of participants, progress indicator and a short story from someone involved. Do not let one emotional story stand in for an entire programme.

Protect dignity and consent. Ask whether people understand where their story, name or image will appear and for how long. Be especially careful with children, sensitive health information, migration status and communities exposed to harm. Give people a way to withdraw consent where practical.

Report what did not work or remains uncertain. A limitation does not automatically weaken a foundation’s case; hiding one can. Explain how the organisation learns, adapts and decides what to do next. This makes an impact story more credible than a collection of perfect outcomes.

Show stewardship and support paths

Before asking for money, explain how the foundation is governed and how it uses resources. Publish board or leadership information, registration details where relevant, annual reports, financial context and policies in language ordinary visitors can understand. A list of documents is less useful than a short explanation of what they show.

Offer more than one way to help. Visitors may donate, volunteer, share information, apply as a partner, attend an event, contribute expertise or advocate for change. Explain what each action involves and what happens after someone responds. If a donation is the best next step, make the page focused without making other support invisible.

Keep the donation path clear and respectful. State whether gifts are one-off or recurring, what information is collected, how receipts work and how questions are handled. Avoid manipulative countdowns or guilt-based language. Trust is more valuable than a short-term conversion.

Build a site people can verify

Create a practical update routine. Assign ownership for projects, reports, leadership, contact details and donation information. Add dates to major updates and archive old campaigns so visitors can distinguish current work from historical activity. A foundation website becomes trustworthy through repeated accuracy.

Make contact possible before and after a donation. Provide a general route and specific routes for partnerships, media, privacy and safeguarding when relevant. Explain expected response times. Publish a privacy notice that matches the forms, analytics and donation tools actually used.

Test the site with people who do not know the organisation. Ask them to explain the issue, the approach, the evidence and the next step. If they can find the donation button but cannot explain what the foundation does, the page asks for support too soon. ChatBuild can help foundations turn mission, method, evidence and support paths into a website that earns understanding before asking for action.

Sources

• Helpful content · Google Search Central

Frequently asked

Should a foundation put a donation button on the homepage?

Yes, but it should sit alongside a clear explanation of the issue, mission, approach and current work. Visitors need context before a support request can be meaningful.

What evidence should a foundation publish?

Use relevant data, sources, dates, programme results, limitations and learning. Combine evidence with carefully consented stories rather than relying on either alone.

How can a foundation protect people featured on its website?

Use informed consent, minimise sensitive details, explain publication clearly and review whether a story or image could create risk. Extra care is needed for children and vulnerable groups.

What support options should a foundation offer?

Depending on its work, options may include donations, volunteering, partnership, expertise, events, applications and advocacy. Explain each action and what happens next.