Build trust, programme and due-diligence content.
On this guide Browse sections
What your NGO website must say
Short answer: An NGO website should publish what a funder or donor checks first: your legal name and registration details, mission and the places you work, the people on your governing body, programmes with real evidence, annual reports and financial summaries, and clear contact and donation details. Date anything that can go out of date, show only registrations you hold, and review the content every quarter. Design comes later; credible content is what earns trust.
Minimum content, in the order a due-diligence reviewer looks
| Page or block | Must show | Proof to link |
|---|---|---|
| About / legal identity | Registered legal name, legal form, registration number and year, address | Registration certificate (redact personal data) |
| Governance | Governing body names and roles, last updated date | Latest filed list or resolution |
| Registrations | FCRA, CSR-1, the DARPAN ID and 12A/80G – only those you hold, with validity | Order or certificate references |
| Programmes | What, where, for whom, since when, with one measurable result each | Project reports or photos with consent |
| Reports and finances | Last two or three annual reports and audited summaries | PDFs, dated |
| Contact and donate | Phone, email, office address; how donations are receipted | Sample receipt layout, privacy note |
The quiet failures are dates. A programme page last touched three years ago tells a funder the organisation may have stopped that work. Put “Updated: month year” on every evidence page and keep a simple register of who updates what.
For the layout that holds this content, see the NGO website template and structure; the overview is on building an NGO website. Ready text blocks come from your NGO profile and annual report; both have editable report and profile files. No DARPAN ID yet? Get help with DARPAN.
By Vekho P. Ringa, Editor. Last verified 22 Oct 2026. Sources: practice guidance drawn from common funder due-diligence requests; show only registrations and figures you can document. General information only, not legal advice.
A website becomes valuable when it helps a stranger verify the NGO’s identity, understand its work and find credible evidence without making unnecessary claims.
This checklist focuses on content readiness.
Which website page is for you? This page is the content checklist: what information, evidence and documents your website should actually publish so that a funder or partner doing due diligence can verify you. If you are still deciding which pages and menus the site should have, start with the NGO website template and structure guide, then come back here to fill each page. The NGO website hub links both.
1. Identity information
The website should make the following easy to find:
- legal organisation name;
- public/brand name if different;
- legal form;
- registered office;
- operational geography;
- official email;
- official phone;
- website/domain ownership contact internally.
Do not hide the organisation’s legal identity behind a campaign brand.
2. About content
A useful About page answers:
- when and why the organisation began;
- mission;
- major programme areas;
- geography;
- communities served;
- organisation model.
Avoid long ceremonial histories that never explain current work.
3. Governance content
Publish a proportionate amount of governance information:
- governing structure;
- current governing body / board / trustees;
- leadership roles;
- accountability statement;
- annual-report links;
- major policy categories where useful.
Review this content whenever office bearers change.
4. Registration / compliance content
Possible disclosures:
- registration/incorporation;
- NGO Darpan;
- tax approval;
- CSR-1;
- FCRA;
- other sector-specific registrations.
For every displayed registration, check:
- exact legal name;
- number;
- status;
- validity where applicable;
- whether it should be public.
Do not say “all Government approved” or imply endorsement.
5. Programme content
For each active programme:
- programme name;
- need/problem;
- location;
- target group;
- activity;
- current status;
- evidence/results;
- relevant report.
Archive completed programmes instead of leaving them looking active forever.
6. Project pages
A funded project page may show:
- project title;
- period;
- geography;
- partner/funder where disclosure is permitted;
- activities;
- outputs;
- evidence;
- report.
Do not disclose agreement amounts or partner branding unless appropriate.
7. Evidence and results
Use definitions.
Good:
Weak:
Evidence can include:
- monitoring summaries;
- reports;
- evaluation;
- annual report;
- dashboards;
- case stories;
- external assessment.
8. Annual reports
Maintain a clear archive by year.
Every report link should be tested.
Use titles such as:
- Annual Report 2025–26
- Audited Financial Statements 2025–26
- Project Report — [Project] — 2026
9. Financial accountability
Depending on the NGO’s disclosure policy:
- annual audited accounts;
- summary financials;
- audit statement;
- major funding categories.
The public figure should reconcile with approved/audited records.
10. Funder and partner information
Separate:
- current funding partner;
- implementation partner;
- Government department supporting a project;
- historical funder;
- network/member organisation.
Do not make every relationship look like an endorsement.
11. Beneficiary / participant stories
Before publishing:
- confirm permission where appropriate;
- protect vulnerable identity;
- avoid unnecessary medical/financial details;
- explain context;
- do not exaggerate change.
A story is illustration, not population-level evidence.
12. Photographs
For each image, consider:
- source;
- permission;
- date;
- location;
- programme;
- caption;
- vulnerable-person risk;
- whether identity needs to be visible.
Avoid generic stock images that imply they depict actual beneficiaries.
13. Donate content
If donations are accepted:
- recipient legal name;
- purpose;
- payment route;
- receipt process;
- contact;
- applicable tax statement;
- privacy/security.
Do not claim “100% tax deduction” or a universal deduction.
14. Volunteer content
Explain:
- actual role;
- location;
- time;
- eligibility;
- safeguarding/background requirements where relevant;
- expenses/support;
- contact.
Avoid collecting unnecessary personal data before a role is defined.
15. Contact content
Use an institutional route.
Recommended:
- official email;
- phone;
- office address;
- contact form;
- WhatsApp only if organisation-managed;
- map where useful.
Test the form.
16. Privacy content
Explain, at minimum:
- what website information is collected;
- forms;
- analytics/cookies where used;
- contact data;
- donation/payment data where applicable;
- third-party services;
- contact for questions.
Do not copy a privacy policy for tools the NGO does not use.
17. Terms / disclaimer
Where appropriate, clarify:
- website information;
- external links;
- donation terms;
- application/volunteer information;
- professional/non-Government status if relevant.
18. News and updates
Only add a news section if it will be maintained.
A website showing the latest “news” from three years ago can weaken trust.
Alternative:
- Recent Updates
- Reports
- Current Projects
19. Search and internal links
Visitors should be able to move naturally:
Home → Programme → Evidence/Report → Contact/Support
Funders:
About/Governance → Programme → Reports → Due-diligence information → Contact
20. Content maintenance register
Create:
| Page | Owner | Last reviewed | Next review | Trigger |
|---|
High-change pages:
- leadership;
- registrations;
- contact;
- current project;
- funding opportunity;
- annual reports.
21. Quarterly website review
Check:
- broken links;
- old leadership;
- expired registrations;
- old funding calls;
- missing reports;
- forms;
- mobile;
- contact;
- website backup/update;
- analytics/search errors where used.
22. Content credibility checklist
Before publishing a claim, ask:
- Is it true?
- Is the number defined?
- Is there evidence?
- Is the period clear?
- Is it current?
- Is it safe to publish?
- Does it imply endorsement?
- Does another page contradict it?
23. Minimum viable NGO website content pack
Before launch prepare:
- legal identity sheet;
- About;
- governance;
- 2–5 programme summaries;
- contact;
- annual report or activity report where available;
- 10–20 approved photographs;
- basic disclosures;
- privacy page;
- primary action/CTA.
This is better than launching many empty pages.
24. NGO due-diligence readiness
A funder reviewing the website should find consistency with submitted documents.
Check:
- legal name;
- address;
- governance;
- programme geography;
- years;
- current registrations;
- annual reports;
- beneficiary claims;
- partner/funder claims.
Website inconsistencies can create unnecessary due-diligence questions.
25. Common content failures
- Another NGO’s copied text remains.
- Old office bearers.
- Unverified “awards”.
- Registration certificate images expose personal data unnecessarily.
- Programme numbers conflict between pages.
- Funder logos imply current partnership.
- Broken report links.
- Contact information differs across footer/about/contact.
- Blog exists only for SEO.
- Website claims activities the NGO has not actually delivered.
26. Related NGOGrant guides
- NGO Website Template & Structure
- NGO Profile Format
- Annual Report Format
- Governance Guide
- Due Diligence Checklist
- Beneficiary Records & Data
Website content: common doubts
Should we publish our registration certificate on the website?
Publishing the number and date is usually enough; if you upload the certificate, remove personal details such as signatures, home addresses or ID numbers of individuals.
Is it wise to put audited accounts online?
Many funders look for them. If you would rather not publish full statements, publish a dated summary and say the full accounts are available on request.
Can we show our 80G status before approval comes?
No. Say nothing about donor-deduction approval until you hold the order, and then show its number and validity exactly as issued. General information only, not legal advice.
How often should the site’s content be reviewed?
Every quarter for programmes, team and contact details; immediately when a registration, governing body member or bank detail changes.
Do we need a privacy note?
Yes, if the site collects names, emails or donations. Say what you collect, why, who sees it and how to ask for removal.
What should never go on the site?
Beneficiary details that identify vulnerable people, unconsented photos of children, and claims you cannot back with records.
NGOGrant boundary
NGOGrant can help organise, write and implement website content. The NGO remains responsible for factual accuracy, permissions, current governance/registration information and approval to publish.