A food bank in St. Catharines can raise money all week and still lose Saturday volunteers because the homepage lists last month’s hours. Website updates for charities are how neighbours, donors, and board members decide whether you are open, trustworthy, and ready for the next shift.
This guide is for Ontario and Canadian charities that already have a site (often WordPress) and need a clear split: what staff change themselves, what a charity WordPress developer should own, and what “done” looks like after a storm day or a new program. It sits beside our notes on WordPress for Canadian nonprofits and nonprofit website design Ontario.
Who this is for
You run programs, not a software company. You need the public site to stay true when hours change, a drive moves, or a staff member leaves.
Use this checklist when:
- Only one person knows the password, and they are on vacation
- A volunteer built the site years ago and plugins flash red warnings
- The board wants Canadian support, not a ticket queue overseas
- You searched “website updates for charities” because the homepage is wrong again
If two Editors already publish closures and a named partner handles core updates, skip to the monthly list.
Two kinds of website updates for charities
Charities mix two jobs and then wonder why nothing moves.
Content updates are the words and dates the public needs: hours, program pages, volunteer shifts, donation appeals, snow-day banners, staff bios. A trained coordinator should do these without an Administrator login.
Platform updates are the engine: WordPress core, themes, plugins, backups, security patches. WordPress’s own update documentation is clear: always update to the latest version, back up first, and treat major releases with care. Minor and security releases often run in the background when the host is set up correctly; major feature releases still need a deliberate click or a partner who watches the site.
Confusing the two is expensive. Calling a developer to change Friday’s food-drive time wastes money. Leaving core and plugins unpatched because “nobody has time” risks donor data and a broken Donate button.
What staff should own every week
Give two people the Editor role. Keep Administrator for the person (or agency) who handles plugins and users. WordPress roles and capabilities exist so a coordinator can publish without the keys to the whole house.
Staff checklist (phone-friendly, under thirty minutes when the site is built for it):
- Hours and holiday exceptions match the Google listing character for character
- Next volunteer date or program date appears on the homepage, not only in a PDF
- Donate and Volunteer buttons still work on a phone
- Snow-day or crisis banner: who posts it, who removes it
- New photos get short alt text that describes the scene, not “IMG_4521”
- When someone leaves, disable their user the same day
If your theme hides hours three menus deep, that is a design problem, not a training problem. Fix the theme once so weekly updates stay simple.
What a charity WordPress developer should own
A serious charity WordPress developer (or maintenance partner) does not rewrite every blog post. They keep the platform healthy so staff can write.
Expect them to:
- Apply WordPress core, theme, and plugin updates on a schedule, with a backup before each batch
- Test Donate, Volunteer, and contact forms after updates
- Watch for abandoned plugins and replace them before they become a security hole
- Document who owns the domain, hosting, and Administrator account (you should own all three)
- Train two staff on Editor tasks and leave a one-page cheat sheet
WordPress.org recommends a backup before you start, and notes that automatic background updates cover many minor and security releases when the server allows them. Major releases still need a plan. If your partner cannot explain that split in plain language, keep looking.
Content that goes stale fast
These pages lose trust when they lag:
- Homepage hours and tap-to-call number
- Program list that still shows last year’s schedule
- “How to give” page that points to an old payment tool
- Board or staff page with people who left years ago
- Impact numbers with no year attached
Donors bounce when a form asks for a life story. Keep required fields to what you need to process a gift or a shift. Put error messages next to the field, in plain words.
For Niagara groups, pair the site with a clean Google Business Profile. When Maps says open and the site says closed, people stop trusting both.
Accessibility is part of every update
Ontario’s page on how to make websites accessible is clear. As of January 1, 2021, designated public sector organizations and businesses or non-profits with 50 or more employees must make public websites and content posted after January 1, 2012 meet WCAG 2.0 Level AA, with two media exceptions (live captions and pre-recorded audio descriptions). The organization that controls the site, directly or through a contractor, must meet the rules.
Smaller charities still have donors who cannot use a mouse. A practical build and update target is WCAG 2.1 Level AA.
When staff publish:
- Headings follow the page outline (do not fake a heading with bold alone)
- Buttons say “Donate $25,” not “Click here”
- New images have real alt text
- Keyboard users can reach Donate and Volunteer without getting stuck
An overlay plugin is not a maintenance plan. Labels and structure live in the theme and the copy. Our AODA and WCAG guide walks through the same checks.
A simple monthly rhythm
Weekly (staff): hours, next date, one program or news item if something changed.
Monthly (developer or tech-savvy Admin): plugin and core review, backup restore test, form smoke test on mobile, broken-link scan on Donate and Volunteer.
Quarterly (board-facing): who has Admin access, where backups live, and whether the homepage still matches the mission in the first screen.
Write the rhythm into the support agreement. “Call us when something breaks” is not a plan. “We patch on the second Tuesday; you own content” is a plan.
Red flags that updates are failing
- The only Admin password sits in a volunteer’s personal email
- Plugins have not been touched in a year
- The Donate button opens a PDF
- The agency keeps Admin “so nothing breaks” and you cannot leave without a rebuild
Ownership comes first. After any refresh, you should be able to change partners without buying the site a second time. That is the same standard we use when boards compare a website design company in Canada.
What “good enough” looks like in 2026
A charity site that stays current does three things well:
- Staff can publish a closure or a new shift without waiting for a ticket
- Core, theme, and plugins stay on supported versions with backups that someone has actually restored once
- The first screen on a phone names who you help, where you are, and the next real action
Pretty mockups do not replace that. Niagara nonprofits and Ontario charities that get this right spend less time in panic mode and more time on the mission.
Book a free consult
If your site needs a clear split between staff content and platform care, or you want a charity WordPress developer who leaves ownership with the organization, book a free consultation with NativaWeb. We work with Ontario nonprofits from St. Catharines and across Canada. Start at nativaweb.com.
