Why Most Nonprofit Websites Are Under-Monitored

A nonprofit's programme delivery is measured. Fundraising campaigns are evaluated. Staff performance is reviewed. The website — which may be the first point of contact for beneficiaries, funders, and donors — is often managed by instinct, updated by feel, and assessed only when someone notices something is wrong.

This guide covers how to set up meaningful website monitoring for a nonprofit: what to track, how often to review it, and how to turn analytics data into decisions rather than just numbers.

The Problem With "We Have Google Analytics"

Most nonprofit websites have Google Analytics installed. Far fewer have it configured to measure anything meaningful. Having GA4 tracking pageviews isn't monitoring — it's having the potential for monitoring without using it.

Meaningful website monitoring requires three things: the right data being collected, regular review of that data, and a process for acting on what you find. Most organisations have the first at some level, skip the second, and never get to the third.

What to Track: The Metrics That Matter

Not all analytics data is equally useful. For nonprofits, the metrics that matter most are those connected to your actual goals.

Conversion Events

A conversion is any action on your website that represents a meaningful outcome. For nonprofits, typical conversions include:

• Donation completions (or clicks through to a hosted donation platform)
• Contact form submissions
• Newsletter or mailing list sign-ups
• Volunteer application submissions
• Resource downloads (if relevant to your mission)
• Event registrations

These should be configured as conversion events in GA4. Until you've done this, your analytics setup is measuring activity (visits, pageviews) but not outcomes.

For how to configure conversion events, see my guide on Google Tag Manager setup for nonprofit Webflow sites.

Organic Search Performance

Google Search Console shows you how your site performs in search: which queries you appear for, your average position, how many people click through, and which pages generate the most search traffic.

This is separate from GA4 and requires its own setup. Connect your Search Console property to GA4 for integrated reporting.

Traffic Sources

Where is your website traffic coming from? The primary channels to monitor:

• Organic search: People finding you via Google and other search engines
• Direct: People who type your URL directly or arrive without a tracked referrer
• Referral: People arriving from links on other websites
• Social: Traffic from social media platforms
• Email: Traffic from email campaigns (requires UTM parameter setup)
• Paid: Traffic from any paid advertising

Channel mix matters because different sources have different conversion rates and different implications for your communications strategy.

Engagement Metrics

GA4's engagement metrics — engagement rate, average engagement time, pages per session — give a sense of whether people are finding what they're looking for or bouncing immediately. Look at these by page and by traffic source.

Top Pages

Which pages receive the most traffic? Which pages lead most frequently to conversions? These aren't always the same pages, and the gap is instructive. A highly-trafficked page that generates no conversions warrants investigation — is it serving its purpose, or is something broken?

How Often to Review: The Monitoring Cadence

Monthly: Core Performance Review

A monthly review should cover:

• Total sessions and unique users (compared to previous month and year-on-year)
• Conversion counts by type
• Top traffic sources
• Organic search performance from Search Console
• Any significant changes — traffic drops, new referrers, page errors in Search Console

This review should take 30–45 minutes with a properly configured dashboard and should produce at least one action item: a page to investigate, a content gap to address, an error to fix.

Quarterly: Deeper Analysis

Quarterly reviews look at trends rather than snapshots:

• Are conversions increasing, decreasing, or flat over the past quarter?
• Which content is driving the most meaningful traffic?
• Are there pages consistently failing to perform that need attention?
• How does performance compare to the same quarter last year?

Annual: Strategic Review

The annual review connects website performance to organisational strategy:

• Did the website support this year's communications goals?
• Which audiences are we reaching, and which are we missing?
• Are our key pages still serving their purpose, or have strategic priorities shifted?
• What investment does the website need in the coming year?

The annual review feeds directly into the content audit process.

Making Monitoring a Governance Function

Website monitoring is often treated as a technical task — something the digital person checks occasionally. For nonprofits, it's more accurately a governance function: the mechanism by which the organisation knows whether its website is fulfilling its institutional purpose.

This reframing has practical implications:

• Reporting: Website performance data should be reported to senior leadership, not just discussed within a communications team. The Communications Director should be able to report website performance to the CEO the same way programme outcomes are reported.
• Accountability: Someone specific should own the monitoring function — not as a casual responsibility, but as a named accountability with time allocated for it.
• Documentation: Monitoring findings should be documented, not just noted. A log of monthly reviews creates institutional memory and makes it easier to identify trends over time.

For integrating monitoring into your broader website governance framework, see my guide on website governance policies for nonprofits.

Setting Up a Monitoring Dashboard

Manually navigating GA4 every month is time-consuming and inconsistent. A custom dashboard — in Looker Studio (free, formerly Data Studio) connected to your GA4 property — lets you see your key metrics at a glance without navigating multiple reports.

A basic nonprofit monitoring dashboard should show:

• Session and user trends (month-on-month comparison)
• Conversion counts by event type
• Top pages by sessions
• Traffic source breakdown
• Search Console data (if connected)

Building this takes a few hours initially but saves significant time in each subsequent monthly review.

When Something Goes Wrong: Alert-Based Monitoring

Scheduled reviews catch trends. They don't catch sudden problems. For issues that need immediate attention — a page going offline, a form stopping working, a traffic drop that suggests a technical problem — you need alert-based monitoring.

GA4 allows you to set up custom alerts for significant changes in metrics. Google Search Console sends email alerts for significant indexing issues. Uptime monitoring tools (UptimeRobot has a free tier) can notify you immediately if your site goes offline.

For nonprofits, the minimum alert setup is: Search Console email alerts enabled, and an uptime monitor checking your site and your most important forms every few minutes.

Connecting Monitoring to Action

The purpose of monitoring isn't to produce reports. It's to inform decisions. The test of a good monitoring process is whether findings lead to changes — to content, to site structure, to budget, to priorities.

If your monthly review produces data but no actions, either the data isn't actionable or the governance structure to act on it isn't in place. Both are fixable, but they require different interventions.

For technical foundations including analytics setup, see my GTM setup guide. For the content side of what monitoring should feed into, see the content audit guide and the pre-launch checklist for how monitoring should be established before a site goes live.

If you'd like help establishing a monitoring framework as part of a broader site governance review, the Blueprint Audit includes assessment of your current analytics configuration and recommendations for a sustainable monitoring approach.