Plan a useful NGO website information architecture.
On this guide Browse sections
The structure behind a trustworthy NGO site
Short answer: A good NGO website template needs about eight sections: Home, About (with legal identity), Our Work, Where We Work, Impact and Reports, Governance and Transparency, Donate or Get Involved, and Contact. Keep the menu to those, put registrations and reports one click from the home page, make every page readable on a phone, and use a theme you can update yourself. Any free or paid template works if it supports this structure.
A sitemap you can hand to a developer
Home ├─ About → Mission · History · Legal identity ├─ Our Work → one page per programme ├─ Where We Work → districts, map ├─ Impact & Reports → annual reports · project reports ├─ Governance & Transparency → governing body · registrations · policies · finances ├─ Get Involved / Donate → donate · volunteer · partner └─ Contact
Choosing a template: what to check before you install
| Check | Why |
|---|---|
| Edits without code | Staff, not a developer, will update programme pages every few months |
| Fast on a basic phone connection | Many visitors, including funders on the move, read on mobile |
| Readable text and contrast | Accessibility is also credibility |
| Clean headings (one H1 per page) | Helps search engines and screen readers |
| Active updates from the theme maker | An abandoned theme becomes a security risk |
Stock “charity” templates often ship with a donation counter and countdown timers. Remove anything you cannot keep accurate; a counter stuck at last year’s figure does more harm than no counter.
What to write on each page is in the website content checklist; the hub is NGO website guides. Text for About and Impact pages can come straight from your profile and annual report, with templates in the NGO profile and report templates. The governance page draws on the policies checklist.
By Vekho P. Ringa, Editor. Last verified 22 Oct 2026. Sources: practice guidance; no particular theme or vendor is endorsed. General information only, not legal advice.
A useful NGO website should help a visitor answer four questions quickly:
- Who is this organisation?
- What does it actually do?
- Why should I trust the information?
- What can I do next?
The site should support donors, funders, beneficiaries, partners, volunteers, regulators, journalists and community members without forcing them to search through scattered PDFs or vague marketing copy.
Which website page is for you? This page is the structure guide: which pages to build, how to organise the menu and footer, and what each page is for. Once the structure is set, use the NGO website content checklist to check what each page must contain for due diligence: identity, governance, registration, finances and evidence.
1. Recommended NGO website architecture
A practical starting structure:
- Home
- About / Organisation
- Governance
- Programmes
- Geography / Where We Work
- Impact / Evidence
- Annual Reports / Publications
- Funding / Partners where appropriate
- Documents / Disclosures where appropriate
- News / Updates where genuinely maintained
- Contact
- Support / Donate where applicable
Smaller NGOs do not need every item as a separate top-level page. Several can be combined if the content remains clear.
2. Homepage
The homepage should explain the organisation, not simply show a large photograph.
Recommended sections:
Identity
Legal/public name, location, what the NGO does.
Main programme areas
Three to six clear programme cards or sections.
Evidence
Recent programme numbers, reports or outcomes only where supported.
Trust
Link to governance, annual reports, registrations/disclosures where appropriate.
Current activity
Recent update, active project or relevant news.
Primary action
Contact, volunteer, partner, donate, view reports or another genuine next step.
Avoid filling the homepage with every document, project and registration number.
3. About page
Useful fields:
- legal identity;
- history;
- mission;
- geography;
- sectors;
- organisation model;
- current leadership/governance;
- contact;
- key milestones.
Separate founding story from factual organisational information.
4. Governance page
A governance page can include:
- legal form;
- governing body structure;
- current office bearers / trustees / directors;
- board/governing responsibility;
- accountability approach;
- conflict / policy framework;
- annual-report links.
Do not publish unnecessary identity details.
Keep the page updated when leadership changes.
5. Programme pages
Each programme should answer:
- what problem it addresses;
- where;
- for whom;
- what the NGO does;
- current project/activity;
- evidence/results;
- relevant reports;
- contact or next action.
Avoid one generic “Our Activities” page with hundreds of photos and no explanation.
6. Geography / where we work
If geography matters to funders and beneficiaries, make it explicit.
Possible structure:
- State;
- district;
- block;
- village / city;
- programme;
- current status.
Do not claim national reach because one online activity had participants from many States.
7. Impact / evidence
This page should distinguish:
- reach;
- outputs;
- outcomes;
- impact evidence.
Possible items:
- monitoring data;
- outcome indicators;
- evaluation;
- annual-report results;
- case studies;
- external assessment.
Avoid “10,000 lives transformed” unless the organisation can explain exactly what was measured.
8. Annual reports and publications
Create a simple archive:
| Year | Report | Financial statement / audit | Project reports |
|---|
Use actual files and clear dates.
Avoid broken download links and duplicate filenames such as annual-report-final2-new.pdf.
9. Trust and disclosure content
Depending on what is appropriate to publish:
- legal name;
- registration information;
- registered office;
- NGO Darpan;
- tax approval/status;
- CSR-1;
- FCRA where applicable;
- annual reports;
- key policies;
- contact.
Do not display an approval as current if it has expired or changed.
Do not create a “Government approved NGO” badge.
10. Funding / partners page
Show genuine relationships.
Possible categories:
- current institutional partners;
- completed projects;
- Government-supported projects;
- CSR projects;
- philanthropic support;
- community partners.
Do not use partner logos without permission.
A past funder should not be presented as a current endorsement.
11. Donate / support page
If the NGO accepts public donations, clearly explain:
- legal recipient name;
- purpose;
- available payment route;
- donor contact;
- receipt process;
- restrictions;
- tax information only where current and applicable.
Do not publish sensitive banking credentials beyond what the organisation intentionally makes public.
Online payments need their own payment, privacy, receipt and security review.
12. Contact page
Include:
- official email;
- phone;
- office address;
- map/location where useful;
- enquiry route;
- office hours if maintained.
Do not use only a personal WhatsApp number without an institutional contact route.
13. Website navigation
Keep top navigation task-oriented.
A useful NGO hierarchy:
Home | About | Programmes | Impact / Reports | Get Involved / Funding | Contact
For a larger information platform, hubs can replace generic navigation.
The goal is not the maximum number of menu items. It is to help users find the next relevant page.
14. Footer
A strong footer can contain:
- legal/public name;
- registered office;
- official email;
- main navigation;
- privacy policy;
- terms/disclaimer where needed;
- social links;
- copyright.
Do not crowd the footer with every registration certificate.
15. Mobile structure
Many users will first see the NGO on a phone.
Check:
- readable headings;
- tap targets;
- navigation;
- no horizontal overflow;
- image size;
- forms;
- download links;
- contact buttons;
- performance.
A desktop-only layout can make even good content unusable.
16. Accessibility
Basic content accessibility includes:
- meaningful heading hierarchy;
- image alternative text where appropriate;
- good contrast;
- keyboard-accessible navigation;
- labelled forms;
- descriptive links;
- readable font sizes;
- captions/transcripts where necessary.
Do not use text embedded inside images as the only way to convey important information.
17. SEO structure
SEO should follow useful information.
Each important page should have:
- one clear topic;
- descriptive title;
- H1;
- useful body content;
- internal links;
- meaningful URL;
- relevant meta description;
- updated information;
- no duplicate thin pages.
Avoid creating dozens of State/city pages with nearly identical text.
18. WordPress structure
For an NGO that regularly updates reports, projects or news, WordPress can be useful.
Plan:
- roles / access;
- theme;
- pages;
- media library;
- backup;
- updates;
- security;
- forms;
- performance;
- SEO;
- analytics;
- ownership of domain/hosting.
The NGO—not a departing vendor or volunteer—should retain administrative ownership.
19. Website launch checklist
Identity
- legal/public name correct;
- official contact correct;
- office address correct.
Content
- programme pages reviewed;
- current governance;
- reports open;
- registration claims current.
Technical
- mobile tested;
- forms tested;
- HTTPS;
- no broken links;
- backups;
- admin ownership;
- analytics/search setup if used.
Trust
- privacy page;
- disclaimers where needed;
- no fake testimonials;
- no unsupported statistics;
- no Government logos implying endorsement.
20. Example compact NGO site
For a smaller NGO:
- Home
- About & Governance
- Programmes
- Reports & Impact
- Support / Get Involved
- Contact
This may be more effective than twenty thin pages.
21. Common NGO website mistakes
- Homepage says “Welcome to our NGO” but never explains the work.
- Leadership page is years out of date.
- Programme photos have no date/location/context.
- Annual report links are broken.
- “Impact” is actually attendance.
- Expired tax/FCRA/CSR claims remain visible.
- Donor logos used without permission.
- Contact form goes nowhere.
- Website owner/admin credentials belong only to an external developer.
- Every page is written for Google instead of the intended reader.
Templates and themes, answered
Is a free WordPress theme good enough for an NGO?
Often, yes, if it is actively maintained, fast and lets you edit pages easily. Paying for a theme does not by itself make a site more credible.
How many pages does a small NGO website need?
Six to twelve pages is plenty to start: the core sections above, plus one page per programme once you have more than one.
Should the donate button be on every page?
A clear Donate link in the header is enough. Make sure the donation page explains how receipts are issued.
Do we need a separate governance page?
It helps. Funders look for the governing body, registrations, policies and reports together, and one page saves them hunting.
Can we use a one-page website?
For a very new NGO, as a start. Move to separate pages once you have more than one programme or any reports to publish.
22. NGOGrant website-service boundary
NGOGrant can help with information architecture, NGO-focused content, WordPress implementation, trust/disclosure pages, mobile review and SEO-ready structure.
Website work does not itself create NGO registration, tax approval, CSR eligibility, FCRA permission or donor endorsement.