Google gives qualifying nonprofits ten thousand dollars a month of Search advertising, and takes it back from accounts that drift out of policy. The drift is rarely dramatic — a click-through rate sagging below the floor, a batch of forgettable keywords with weak quality scores — and it happens precisely because nobody at a volunteer-run nonprofit is paid to watch. A monthly AI compliance sweep is the cheapest insurance the grant can have.
The Ad Grants deal and its real constraints
The deal: free Search ads for your mission, inside rules that paid advertisers never face. Grants ads serve on Google Search only, below paid ads. Bidding is constrained — the classic two-dollar manual bid cap lifts only when you use conversion-based Smart Bidding, which in turn requires meaningful conversion tracking. And the account must stay actively managed and mission-relevant. None of this is hidden; it is published in Google's Ad Grants policy compliance guide. The trouble is that the rules are enforced monthly against an account nobody reads monthly.
The rules that actually suspend accounts
Four rules cause most deactivations, all published and dated to the January 2018 policy update. The account must hold a 5% click-through rate every month — two consecutive months below risks temporary deactivation. Keywords must keep a quality score above 2; the ones at 1 or 2 must be paused or removed. Single-word keywords are banned, with narrow exceptions such as your own brand name. So are overly generic keywords — the "free videos" and "today's news" class that matches everything and means nothing. Add the structural requirements — mission-based campaigns, geo-targeting relevant to where you operate, at least two ad groups per campaign and two sitelink assets — and compliance becomes a checklist. Checklists are what agents are for.
The monthly compliance sweep, prompt by prompt
One conversation a month, thirty minutes of a volunteer's time. What is the account-level click-through rate this month, and which keywords drag it down — draft the pauses. Which keywords sit at quality score 1 or 2 — draft the pauses. Any single-word or generic keywords that slipped in? Is every campaign geo-targeted to where we actually operate? Are conversions recording — and if we use Smart Bidding, is the tracking it depends on alive? Each answer is a live read of the account; each fix arrives as an exact proposed change that a volunteer approves with one click. The sweep leaves a written trail, which matters when the person running it changes every spring.
Beyond compliance: mission-aligned queries that do real work
A compliant account can still be a wasted grant. The upside sweep looks for the queries where the mission and the searcher genuinely meet: people seeking the services you provide, researching the problem you solve, looking to volunteer or give. The agent reads the search terms the account actually matched, drafts negative keywords for the drive-by traffic that erodes CTR, and proposes tighter ad groups where one message can honestly answer one intent — which is also how quality scores rise. Compliance and effectiveness turn out to be the same discipline: precision.
Grants account, paid account, or both
The grant is a floor, not a strategy. When mission queries are covered and the constraints bind — competitive fundraising terms you cannot win under Grants bidding, audiences you cannot remarket to — a small paid account alongside is the standard graduation. The agent treats both as one estate: the same conversation reads the Grants account for compliance and the paid account for waste, and keeps their keywords from bidding against each other.
Where the approval line sits for a volunteer team
Approve everything — the same posture as any small-budget local account, for better reasons. Volunteers rotate; judgement must live in the process, not the person. Reads never prompt for approval. Every write — pauses, negatives, keyword changes, budget-shaped settings — stops and states exactly what it will change before anyone clicks. The audit trail records each action with tool, account, outcome and timestamp, so the next coordinator inherits a history instead of a mystery. And nothing can be deleted, by architecture: the remove tools are never exposed, and a REMOVED mutation is refused server-side. For an account whose whole value is its continued existence, that floor matters.
What still runs through Google's own processes
It does not apply for the grant, verify your nonprofit status, or argue a reinstatement with Google — those run through Google's own processes. It does not edit your website; it reports when conversion tracking is missing and why the two-dollar cap will bind until it exists, and — on a site that loads Tag Manager, as of v2.16.0 — proposes the conversion action and stages its tag for you to publish. It reads Google Ads, with Analytics, Search Console and Tag Manager when connected — not your donor CRM or email platform. And it does not replace Google's published policy as the source of truth — it enforces the checklist; the policy page remains the authority when rules change.
Setup notes for a volunteer-run team
Connect with the Google sign-in that has admin access to the Grants account — there is nothing to install, and the connector cannot delete anything, which makes it safe to hand a rotating volunteer. Run the full account audit first and let the findings set the agenda; run the compliance sweep on the first Monday of every month after. The trial is 7 days on the full Pro plan for a new workspace, no card — one week is enough to know whether the grant has been quietly at risk, and it drops to the Free plan afterward rather than cutting off. Start free and put the first sweep on the calendar.