Table of Contents
TL;DR
- Most nonprofit WordPress advice tells you the site costs nothing. The cost is real. The honest range is $0 to $400 per year for a small nonprofit. Domain. Hosting. The Stripe transaction fee on the donate page. The four line items cover most of it.
- The site fails differently from a small-business one. Three audiences (donors, beneficiaries, volunteers) and one volunteer admin most of the year. The volunteer who built it is rarely the volunteer who will fix it.
- Three host signals matter more than price. Daily off-site backups with self-serve restore. Staging included. A nonprofit discount available on application. Pressable, WP Engine, Kinsta, and SiteGround carry it. The public pricing page often does not.
- Five pages do the work. Home with mission and region in the first hundred words. Donate with one form and one impact statement. About with the board and the registration number. Programs in plain language. A reachable phone-and-form page.
- Three habits survive the volunteer handover. A short admin handbook. A scheduled monthly maintenance window with one named volunteer. A boring-is-good rule for plugins. Boring beats flashy when nobody is paid to babysit.
Most nonprofit WordPress advice tells you the site costs nothing. The cost is real. Domain renewal. Hosting.
The Stripe fee on every donation. The hour the volunteer spends fixing the contact form on a Saturday afternoon. The hidden cost of nobody knowing the host login when the original volunteer moves out of state.
The advice that says nothing also tells you the site is easy. The site is not easy. A nonprofit website serves three audiences at once and lives without a paid administrator most of the year.
The same homepage has to talk to a donor, a beneficiary, and a future volunteer. The same admin login has to survive the founder’s retirement and the new volunteer’s first day.
This piece is the calm version. Real costs. Real host choice.
Five pages that do the work. The volunteer handover that keeps the site running across years. The about-page anchor that ties the structured data to the registration the engines can verify.
Why does a nonprofit website fail differently from a small-business one?
A nonprofit site has three audiences at once.
Donors. They want to know where the money goes. The donate page is one job.
The about page with named board and registration number is another. The annual report linked from the about page is the third.
Beneficiaries. The people the nonprofit serves. They want to find a service or a referral.
The programs page in plain language is one job. The contact page with a real phone number is the other.
Volunteers and applicants. They want to find a way in. A "ways to help" page lists what the nonprofit needs.
A volunteer-application form lives next to it. A list of the next three events sits below.
The same homepage has to talk to all three. A small-business site mostly serves customers. The nonprofit site serves three groups with different expectations and a single navigation menu.
The site also lives without a paid administrator most of the year. The volunteer who built it three years ago is rarely the volunteer who will fix it. A plugin update breaks the contact form on a Saturday morning.
The handover is the work. The site that survives the handover is the site that lasts.
What is the actual cost of a nonprofit WordPress site in 2026?
The honest range is $0 to $400 per year for a small nonprofit.
Domain name. Roughly $12 a year for a .org or a .com on Namecheap or Hover. The .org is the conventional nonprofit choice.
The .com works fine. Renewal is the recurring cost. Transfer between registrars is reversible if needed.
Shared hosting. $36-$120 a year on the cheapest tier with daily backups. The under-$4-a-month tiers exist, but not all of them include daily backups or staging. A nonprofit discount on a managed plan (Pressable, WP Engine, Kinsta, SiteGround) lands in the $120-$200 range. The bundle includes backups, staging, and security monitoring.
SSL certificate. Free via Let’s Encrypt. Every modern host installs it automatically. A nonprofit that pays separately for SSL is paying for a service the host should provide.
Theme. Free. A wordpress.org theme that ships clean theme.json and a recent update is the right starting point.
Plugins. Free at the tier most nonprofits need. Rank Math Free for SEO.
WPForms Lite or Fluent Forms Lite for the contact form. UpdraftPlus Free or BackWPup Free for the secondary backup. WooCommerce-and-Stripe-style donation plugins where applicable.
Stock photos. $0-$50 a year. A Canva account or an Unsplash collection covers most needs.
Payment processor. Stripe takes 2.2% + $0.30 per donation on the standard nonprofit rate (which Stripe applies on application). PayPal Giving Fund routes around the standard fee for registered 501(c)(3) nonprofits in the US.
Most small nonprofits do not spend more than that. The figure is the floor, not the wall. Larger nonprofits spend more on event ticketing, on CRM integration, on accessibility audits. The small site does not need any of that on day one.
Which host actually fits a nonprofit budget?
Three signals matter more than the price.
Daily off-site backups with a self-serve restore button. A nonprofit cannot wait for a Monday-morning support ticket when the site goes down on a Friday afternoon. The host’s "we run backups" claim has to come with a button the volunteer can press without calling support.
A staging environment included in the plan. The volunteer who tries a plugin update needs a copy of the site to break safely. The host that bundles staging is the host that protects the volunteer from a Saturday-morning panic.
A nonprofit discount on the order page or available on application. Pressable, WP Engine, Kinsta, and SiteGround all advertise nonprofit pricing or offer it quietly on application. The discount is rarely on the public pricing page — you have to email the host and ask. Send the registration number.
Ask for the nonprofit rate. Wait two business days. The discount is real.
The cheapest shared-hosting tier with no staging and no daily backup is rarely the right answer for a nonprofit. The savings disappear the first time the site goes down on a Saturday morning and the volunteer cannot restore it before the donor calls. The deeper walkthrough on the backup discipline lives in the walkthrough on WordPress backup for beginners.
Which five pages does a nonprofit site actually need?
Five.
A home page that names the mission, the region served, and the year founded in the first hundred words. The hero image is decoration around that sentence, not a replacement for it. "Greater Springfield Food Bank, serving the Pioneer Valley since 2009." Lead with that.
A donate page with one short form, one named impact statement, and one optional recurring-gift toggle. The form has the smallest possible field count. The impact statement is concrete and recent. "$25 buys ten pounds of dry goods this month" beats "your gift makes a difference."
An about page with the named board (or organizing team), a real photo, and the registration number. The structured data on this page reads from the same fields. The named board is the verification anchor.
A programs page that lists what the nonprofit does in plain language. Two or three outcome examples. The agency-style "comprehensive solutions" framing buries what the nonprofit actually does. The programs page is where the beneficiary finds the service.
A contact page with a real phone number, the office address (or a "no public office" note), and the form. The form’s email goes through an SMTP plugin to a real inbox the volunteer checks. The phone number is the local number, not a vanity 1-800.
Five pages do the bulk of the work. A "ways to get involved" page or a blog can land later.
How does Organization (NGO) structured data help a nonprofit get cited?
Organization structured data with the NGO sub-type names the nonprofit as a verifiable entity for AI engines and search engines.
The fields the engines actually use are short. Name. Legal name (often different from the public-facing name). taxID (the registration or 501(c)(3) number for US nonprofits, or the equivalent registration number elsewhere). Address.
Telephone. Email. Founder. sameAs (an array of URLs to outside profiles).
The taxID and the sameAs links are the two most-cited fields. A nonprofit that fills the taxID gives the engines a verifiable identifier. Linking to GuideStar, Charity Navigator, the LinkedIn organization page, and a chamber-of-commerce profile adds four reference points.
Three or four sameAs links is the line between the engines naming this nonprofit and naming a different one with a similar name. The longer-form companion lives at the walkthrough on local-business WordPress essentials.
The dual-layer rule applies. The structured data must match visible content. The registration number on the about page has to match the taxID in the structured data.
The named board on the about page has to match the founder field in the structured data. Hidden structured data with no matching visible content fails both layers.
How do you survive the volunteer handover without burning anyone out?
Three habits save the site.
A short admin handbook. One page in a Google Doc or wherever the nonprofit keeps its other handbooks. The host login URL. The WordPress admin URL.
The plugin update procedure (deactivate non-essential plugins on Friday afternoon, run updates, take a snapshot, leave the site alone over the weekend). The backup-restore procedure. The named person to call when something breaks. Half a page is enough.
A scheduled monthly maintenance window with one named volunteer per month. The volunteer logs in on a chosen Friday afternoon. Runs available updates. Reads the spam-folder check on the contact form.
Confirms the donate page test transaction still works. Logs the date in the handbook. Forty minutes once a month spreads the work across twelve volunteers a year and protects against the bus-factor problem.
A "boring is good" rule for plugins. A nonprofit site that runs ten boring plugins is more reliable than one that runs three flashy plugins. Rank Math over a clever new SEO plugin.
UpdraftPlus over a one-developer backup plugin. WooCommerce over a clever new donation plugin. Boring is the right speed for a site nobody is paid to babysit.
What can AI help with on a nonprofit budget?
AI helps with three things on a tight budget.
Drafting program-page copy. Paste the program description and the audience into an AI chat. Ask for a one-page draft that names the city, the audience, and the outcome in plain English. The chat returns a draft.
Read it. The agency-style "comprehensive solutions" wording will need to come out — the AI tool drifts toward it. Edit the draft into the voice of the program staff.
Translating donate-page text and impact statements into the second or third language a community speaks. The AI tool handles French, Spanish, Portuguese, Mandarin, and Arabic competently for nonprofit-tier copy. A native-speaker volunteer reads the translation before it ships.
The AI tool gets the structure. The volunteer ensures the tone reads right.
Summarizing the last twelve months of program reports into one page of about-the-impact content. Useful for board meetings and grant applications. Paste the source material into an AI chat. Ask for a single page in plain language with two or three numeric outcomes if any are available.
The chat returns a draft. Verify the numbers against the source. The chat tightens the structure. The program staff brings the voice and the verifiable detail.
AI fails on the live render of the site. It cannot read the donor records in the CRM. It cannot make a phone call to a beneficiary.
The honest framing is consistent across nonprofit work. The AI tool accelerates the read. You keep the verdict.
Which page should a nonprofit build first?
The about page.
The about page sets the identity that the donate page, the programs page, and the structured data all verify against. The named board or organizing team. The registration number.
The founding year. A short paragraph in the founder’s voice. A photo from the last twelve months.
Forty minutes once. The home page can be a short placeholder for a week. The donate page can land before the programs page. The about page is the foundation the donors check first and the engines check at the same time.
Both groups read the same four anchors. The name. The number.
The year. The photo. Get those four right, and the rest of the site builds on something the readers can trust.
Other questions worth answering
How do automated tax-deduction receipts work after a Stripe donation lands?
Stripe sends a basic receipt by default. A registered 501(c)(3) in the US must add tax-deduction language and the EIN so the receipt counts on the donor’s filing. Most donation plugins ship a customizable email template that handles this. Test the template with a one-dollar transaction before launch.
What does GDPR require from a charity collecting European donor emails?
GDPR sets the floor at lawful basis, clear consent language, and a working unsubscribe link in every email. A short privacy policy that names what the charity stores and for how long covers most of the visible legal surface. A consent checkbox on the donation form (separate from the donate button) records the lawful basis. Free tools like WPForms Lite or Fluent Forms Lite handle the checkbox cleanly.
Which contact-form plugins keep spam down at zero monthly price?
Three free defenses stop most form spam. Fluent Forms Lite and WPForms Lite ship a honeypot field by default. Cloudflare Turnstile adds a checkbox-free challenge that blocks bot traffic. Akismet handles comment spam separately at no charge for personal-tier use.
When should a charity add an events calendar instead of a plain text list?
Three running events a year is the cutoff. Below that, a plain text list with the date and the RSVP link works fine. Above three concurrent or repeating events, a calendar plugin like The Events Calendar Lite or Sugar Calendar Lite earns its place. The calendar adds schema markup that lets Google and answer engines surface the date directly.
Why does accessibility carry extra weight on a charity homepage compared to a commercial shop?
Because the audience includes the people the mission serves directly, the share who use assistive tech runs higher than at a commercial shop. Screen readers and keyboard navigation matter more on a charity homepage. WordPress.org’s 2024 accessibility-ready theme guidelines name focus indicators, semantic headings, and form labels as the floor. Pick one of those themes and the rest is content work.
Which nonprofit page should you build first?
Running a nonprofit WordPress site that has never been read against its donor flow and Organization structured data? You can contact me here. Tell me the site URL and the rough size of the operation.
I will check the about page, the donate flow, and the Organization structured data, and name the one page worth tightening first. There is no pitch, no upsell, and the conversation is free.