A food bank in St. Catharines can own a domain, pay for hosting, and still lose Saturday volunteers because Google shows last year’s hours and the homepage never names the next shift.
This guide is for Ontario charities and community groups that need a public site people can actually use. Clinics can apply the same checks to booking. It sits beside our notes on nonprofit website design Ontario and Google Business Profile for Niagara nonprofits.
Who this is for
You run programs, not a software company. You need donors, volunteers, and neighbours in Niagara Falls, Welland, or St. Catharines to find you without a scavenger hunt.
Use this list when:
- The website and the Google listing disagree on hours or the phone number
- The homepage talks about “community” and never names the town or the next date
- Staff cannot change a snow-day closure without calling a developer
- The board wants a Canadian partner, not an offshore login they cannot audit
If your site already matches Maps, takes a gift on a phone, and lets two staff publish, skip to the accessibility checks.
Start with one honest first screen
Google’s SEO starter guide is enough for most boards: unique, accurate page titles; headings that outline the page; content that answers the query.
On a phone, the first screen should show:
- Who you help and where (St. Catharines, not “the region”)
- One primary action: Donate or Volunteer, not four buttons at the same volume
- Hours and a tap-to-call number that match Google Business Profile
- The next program date, not a slogan that could live in any city
A visitor who searched “food bank St. Catharines hours” should not have to open a PDF. If the title tag says “Home” and the H1 says “Welcome,” Google has nothing useful to show.
Make the website and Maps tell the same story
A Google Business Profile is not extra marketing. It is how neighbours find you on Maps.
Keep these identical, character for character:
- Legal or public name
- Street address, including unit
- Phone
- Website URL (the real homepage, not a Facebook page)
- Hours, including holiday exceptions
When the listing says open and the site says closed, people stop trusting both. Update both on the same day. If you close for a storm, change Maps first, then the homepage banner.
Categories matter. Pick the type that matches what people search (food bank, shelter, community centre), not a vague “nonprofit organization” if a tighter category exists.
Let staff publish without an Administrator login
WordPress roles exist so a coordinator can post Friday’s food drive without the keys to plugins and users.
Give two people the Editor role. Keep Administrator for the person who handles updates and backups. When someone leaves, disable the user. Do not share one password in a group chat.
If the agency is the only one who can add a closure, you hired a bottleneck. That is why we wrote WordPress for Canadian nonprofits around staff updates, not around the agency dashboard.
Train on a phone for thirty minutes: how to edit hours, how to add a program page, how to write alt text for a photo of the team.
Accessibility is part of the build, not a plugin
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 target is WCAG 2.1 Level AA.
Ontario even lists questions to ask a developer:
- Are you familiar with WCAG 2.0 Level A and AA?
- Have you shipped an accessible site, with links you can check?
- Do you test with automated tools, manual checks, and assistive technology such as a screen reader?
Add your own:
- Can I tab through Donate and Volunteer without getting stuck?
- Do buttons say “Donate $25,” not “Submit”?
- Is contrast on the Give button strong enough, or only pretty?
An overlay plugin is not a plan. Labels and headings live in the theme and the copy. Our AODA and WCAG guide walks through the same checks.
Forms, receipts, and what you collect
Donors bounce when a form asks for a life story. Volunteers bounce when the only path is “email us.”
Keep required fields to what you need to process a gift or a shift. Put error messages next to the field, in plain words. Say who issues tax receipts, and make that tool look like your organization.
The Office of the Privacy Commissioner of Canada’s guidelines for processing personal data across borders note that PIPEDA does not ban transfers to another country, but you remain responsible for the information. If the board wants Canadian hosting, say so in the brief. If you send newsletters, read Canada’s anti-spam rules before anyone promises a weekly blast.
What “done” looks like for Niagara
A cheap homepage with no training is not cheap. Get in writing:
- Pages in scope, and what a new program page costs later
- Who writes copy, who supplies photos, who writes alt text
- Timeline with real dates
- Support after launch: hours, response time, what is included
- Who owns the domain, hosting, and WordPress administrator account
A serious website design company in Canada leaves the organization as owner. After launch you should be able to change partners without rebuilding from scratch. Pair that with how to choose a web agency in Canada if the board is still comparing quotes.
A Tuesday checklist
Do this once a month:
- Open the homepage on a phone. Can you Donate or Volunteer without scrolling past a wall of text?
- Search your organization name in Google. Do hours and the phone match the site?
- Tab through the header. Can you reach Give without a mouse?
- Ask a staff member who is not the web lead to change the next volunteer date. Time how long it takes.
- Check that program pages name the town and the next date.
If any of those fail, fix that before you buy ads.
Book a free consultation
NativaWeb is in St. Catharines. We build WordPress sites for Ontario nonprofits so staff can publish, donors can give on a phone, and the listing on Maps matches the homepage.
Book a free consultation or visit nativaweb.com. Bring the current URL, who owns the domain, and one example of a visitor who could not finish a gift or a volunteer form. We will look at the first screen together.
