Give Visitors Reasons to Trust Your Organization
Before people contribute money, time, or personal information, they need to understand who runs your organization and how it delivers on its mission. Make that evidence easy to find near donation appeals, program details, and registration forms.
5. Impact Evidence and Respectful Stories
Show what your work achieves with dated, clearly explained results. Distinguish between activities delivered, such as workshops held, and outcomes achieved, such as participants gaining a skill.
For each published figure, identify the reporting period and link to the supporting report where available. Avoid presenting an estimate as a measured result.
Pair nonprofit impact reporting with stories that explain the human context. Obtain permission before publishing names, photographs, or personal experiences, and respect anyone who prefers to remain anonymous.
6. Leadership, Financial Information, and Contact Details
Help visitors understand who is accountable for your work. Include:
- Leadership and governance: Relevant staff and board profiles with clear roles.
- Financial transparency: Current annual reports and financial statements approved for publication.
- Organizational details: Your official name and verified registration information, where applicable.
- Working contact options: A monitored email address, phone number, and accurate office or service hours.
For public-facing locations, publish the full street address, opening hours, and directions to the correct entrance. Include nearby transit stops, parking options, and verified accessibility features, such as step-free access or an accessible washroom. Assign a staff member to keep these details current.
Build an Accessible, Mobile-Friendly Website
People should be able to find support, read your reports, and complete forms across different devices and ways of browsing. Include accessibility and mobile testing in the project scope from the start.
7. Accessibility Across Content, Forms, and Documents
Ask your designer to check that visitors can:
- Navigate menus, links, and forms using a keyboard, with a visible focus indicator.
- Read text with sufficient contrast and enlarge it without losing content.
- Understand meaningful images through appropriate alternative text.
- Identify form fields and understand how to correct errors.
- Access video information through captions and other appropriate alternatives.
These checks reflect W3C’s introductory accessibility guidance, which also makes clear that basic checks alone cannot establish full accessibility.
Include donation tools, embedded forms, and downloadable reports in the review. Ask for a documented testing scope, combining automated checks with manual evaluation. Agree on an accessibility target, such as WCAG 2.2 AA, and verify applicable legal requirements separately.
8. Mobile Usability and Fast, Dependable Pages
Test complete tasks on a phone: open the menu, find a program, register, and follow the donation journey. Check that buttons are easy to select, text stays readable, and forms work when the on-screen keyboard appears.
Review large images, background videos, and third-party embeds when investigating slow pages. Agree on performance goals and test representative pages across devices and connection speeds.
Include the Tools Your Team Needs After Launch
Your nonprofit website needs to work for the people managing it. Before launch, decide who will update pages, respond to enquiries, and keep connected tools running.
9. An Editable CMS and Clear Content Ownership
Choose a content management system (CMS) that lets staff handle routine updates, such as changing program hours, publishing reports, and adding events.
Ask your designer to demonstrate these tasks during training. Include written instructions and give each editor access suited to their responsibilities.
Your organization should also retain control of its domain, hosting, website content, and connected accounts. Record who manages each account and how access transfers when staff changes.
10. Connected Forms, CRM, and Email Tools
Map what happens after someone submits a form. A volunteer application might enter your CRM, notify a coordinator, and send the applicant an acknowledgement.
For each nonprofit CRM integration, confirm:
- Which information transfers and where it goes.
- Who receives notifications and handles follow-up.
- How duplicate records and failed transfers are handled.
- Which subscriptions or additional fees apply.
Test the complete workflow before launch and after major changes. A successful on-screen message should be followed by a check that the submission reached its destination.
Alt text: Nonprofit website form workflow connecting submissions, acknowledgements, staff notifications, and follow-up.
11. Privacy, Security, and Ongoing Maintenance
Document what personal information you collect, why you need it, who can access it, and how long you retain it. Have the relevant privacy requirements reviewed for your organization.
Assign responsibility for software updates, backups, account security, and recovery. Ask how backups are restored and who responds when something breaks. Include ongoing website maintenance costs in your budget.
Make Your Website Discoverable and Measurable
Your website should help people find relevant programs and give your team a clear way to assess whether visitors complete useful actions.
12. SEO Foundations and Meaningful Conversion Tracking
Start nonprofit SEO with clear, useful program pages. Describe the support offered, who qualifies, and the actual service area. Give each page a descriptive title and heading, connect related pages with internal links, and ask your developer to check that public pages can be indexed.
For nonprofit website analytics, track outcomes separately:
- Completed donations.
- Submitted volunteer applications.
- Event registrations.
- Service enquiries.
A donation-button click shows interest; it does not confirm a completed gift. If visitors move to another platform, include that journey in your measurement plan and test it before relying on reports.
Keep names, email addresses, payment details, and sensitive enquiry information out of analytics events and page URLs.