Google Ad Grants for Bay Area nonprofits: eligibility, limits and what it does not do

What does the Grant actually give you?

A budget you cannot spend anywhere else, on terms Google sets.

From the program FAQ: "you have an ad budget of $10,000 USD per month of in-kind search advertising to use across various campaigns. The funds do not roll over if unused." There is no obligation attached to that number in either direction. Asked whether a grantee must spend it, the FAQ answers plainly: "No, there is no spend requirement."

So it is not cash, it is not a rebate, and an unused month is simply gone. The practical consequence is that the question "how do we spend all of it" is the wrong one to open with. Most nonprofits we look at are nowhere near the ceiling and would not be better off if they were.

Where did the $2 per-click cap go?

This is the claim to stop repeating.

Nearly every third-party guide to Ad Grants still states a $2 maximum cost-per-click. We opened Google's account management policy in a rendering browser and read it end to end on 7 September 2026. There is no per-click cap in it. Not a raised one, not a conditional one. The page does not mention one.

What is there instead is a bidding requirement, quoted in full:

"In order to drive performance for organizations, Ad Grants requires that accounts created on or after April 22, 2019 must use conversion-based Smart bidding for all campaigns, unless using Smart campaigns. Each campaign must use either Maximize conversions, Maximize conversion values, Target CPA, or Target ROAS bidding."

That is a different kind of constraint and it changes the work. A per-click ceiling is something you live under. A bidding requirement is something you have to feed, because Smart bidding needs conversions to bid on. The policy adds that "Campaigns that do not comply with Ad Grants bidding policies are subject to automatic bid strategy changes," so this is enforced by the system rather than by a warning letter.

The $2 figure is the legacy manual-bidding rule. It survives in circulation because nobody re-reads a policy page they summarised three years ago, which is a pattern worth recognising in the claims agencies make that do not survive checking.

What must the account do every month to stay alive?

Four things, and a fifth that catches people who have done everything right.

A 5% click-through rate. Verbatim: "Ad Grants accounts (who are not exclusively using Smart Campaigns) must maintain a 5% click-through rate (CTR) each month (at the account level, not necessarily each keyword). If the CTR requirement isn't met for 2 consecutive months, your account will be temporarily deactivated." The account level qualifier is the useful part, and the policy names its own remedy: pausing low CTR keywords. That is the same discipline as the negative keywords that save you money, applied to survival rather than to budget.

At least one conversion a month. "For accounts created on or after April 22, 2019, at least one of the above conversion types must be set up as described in the Ad Grants activation guide and accrue at least 1 conversion per month."

And here is the clause that quietly disqualifies the easy answer: "Conversion types such as time spent on site or homepage visits may be added to your account, but must be excluded from 'Conversions' and use the category of 'Other.'"

Counting a homepage visit as the monthly conversion is not a workaround, it is a policy breach. The conversion has to be something a nonprofit actually wants: a donation, a volunteer signup, a form, a call. Which means the tracking has to be real before the campaigns are, the argument made in setting up conversion tracking before you spend a dollar and, for the organisations whose real conversion is the phone, in tracking phone calls as conversions.

Two sitelinks and honest geo-targeting. The structure section requires "At least 2 unique sitelink ad assets" and "Proper location settings (specific geo-targeting to show ads in locations where users will find your nonprofit's information and services useful)." Google gives its own example: "If you primarily serve your local community, your ads should be shown only in your town or local area, such as food banks and houses of worship." A food bank in East Palo Alto advertising statewide is out of compliance and also wasting the budget, which is the geographic targeting mistake that wastes half a budget in its purest form.

The program survey. Google periodically sends a survey to all grantees and treats non-response as its own deactivation reason. There is no way to discover this except by reading the policy or by losing the account. Make sure the notification email address is one a human reads.

One sentence closes the page and sets the tone for all of it: "Any account found in violation of program policies is subject to automatic suspension without notification."

Why do most applications fail on the website rather than the paperwork?

Because the website policy is longer and stricter than the eligibility rules, and almost nobody reads it before applying.

Eligibility has three parts, per the FAQ: an eligible nonprofit, "a high-quality website that meets our website policy," and the ability to meet the program policies. The middle one is a full technical standard, and it publishes its own table of the most common rejection reasons: insufficient unique content, unclear mission, poor navigation or broken links, slow load speed, no HTTPS, disallowed commercial activity, poor mobile experience.

Read that list again. Six of the seven are ordinary web quality problems, and none of them are about advertising. The policy names specific pitfalls: thin content, pages that are mostly links or embeds, "Under Construction" pages, and "Relying heavily on PDF documents instead of HTML web pages for core information." That last one describes a great many small nonprofit sites, where the annual report, the program descriptions and the board list are all PDFs.

Two more that are easy to fix and commonly missed. HTTPS must cover the whole site, with no mixed content. And the donation button has to work, on mobile, going to a secure page. Broken donation links are named twice in the policy, once as a navigation failure and once as a commercial one.

On domains, the policy is more generous than the folklore: a .org is not required, and "'Own' means you have administrative control over the website's content, structure, and technical settings." An additional domain goes through a request form and is "reviewed within 3-5 business days."

What does a Grant not do?

This is the section most articles skip, and it is the one that decides whether a Grant is worth the work.

It does not put you in the paid auction. The FAQ, on running a Grant account alongside a paid one: "Your accounts will not compete with one another because Ad Grants ads are in a separate auction after paid ads." And on placement: "Your organization's ads will appear either independently or in positions below paid ads." If four advertisers are bidding real money on a query, the Grant ad is not competing with them for the top slot. It is showing beneath them, or showing on the queries they are not buying.

It does not fund advocacy in an election. From the terms: "Google Ad Grants accounts are not eligible to run election ads in regions where verification is required." The same page requires that grantees be "organized and operated exclusively for charitable purposes." An organisation whose main channel is issue campaigning around a ballot measure should plan around this rather than discover it.

It does not accumulate. Unused budget does not roll over, and there is no spend requirement, so the Grant rewards a small account that runs continuously rather than a large one that runs in bursts.

And it is not free of labour. Somebody has to hold the account to the program's 5% CTR requirement, produce a real conversion every month, keep the geo-targeting honest, and answer a survey. That is a standing commitment, and a Grant that gets deactivated after four months has cost the organisation more than it delivered. Volunteer capacity is the constraint that actually decides this, not eligibility.

Does the Grant favour a small Bay Area nonprofit?

Google argues that it does, and the argument is reasonable.

Asked whether a small nonprofit can compete with large organisations, the FAQ answers: "Google Ads rewards relevancy. In fact, small, local Grantees that use location-specific keywords and targeting may show before large, national organizations."

That is the whole local case, stated by the source rather than by us. A San Mateo food bank bidding on the queries people in San Mateo type has a relevance advantage that a national organisation running one broad campaign does not. It also fits the geo-targeting requirement instead of fighting it, which is a rare alignment between a compliance rule and a strategy.

We have run one Ad Grant to compliance for a client whose case study is published on this site: NorCal Shiba Rescue, an all-volunteer animal rescue. We handled the application, built the campaigns and maintained the CTR requirement. The case study on our site carries the client-verified figures, and we are not restating them here, because a single account is not evidence of what a Grant does generally and this article is about the policy rather than about us.

What would we do first?

In this order, and the order is the point.

Audit the website against the website policy before applying. Every rejection reason in Google's table is checkable in an afternoon: run PageSpeed Insights, click the donation button on a phone, confirm HTTPS across every page, and find the pages that are really PDFs. Fixing these after a rejection costs the same work plus a reapplication.

Decide the conversion before the campaigns. Name the one action worth a monthly compliance obligation, then instrument it. If the honest answer is that nothing on the site is measurable yet, that is the project, and the Grant waits.

Start narrow. Two or three campaigns on the queries the organisation genuinely answers, geo-targeted to where it actually serves. The 5% CTR requirement is easy to hold on a small tight account and hard on a large loose one.

Put a name against the monthly check. CTR, conversions, and the notification inbox. Fifteen minutes a month, owned by a person, not by a committee.

Where these numbers come from

Four Google pages, each opened in a rendering browser and read in full on 7 September 2026. Nothing here is taken from a summary of them, which matters on this subject more than most, because the summaries are where the $2 cap lives.

The bidding requirement, the 5% CTR, the monthly conversion rule, the 'Other' category exclusion, the sitelink and geo-targeting requirements and the suspension language are from the account management policy. The budget, the roll-over and spend answers, the separate auction, the placement below paid ads and the relevancy statement are from the Ad Grants FAQ. The rejection reasons, the domain definition and the content requirements are from the website policy. The election-ad exclusion and the charitable-purpose requirement are from the Ad Grants terms and conditions.

We have not published a click-through rate you should expect, a cost per conversion, or a figure for what a Grant is worth to a nonprofit. We could not read a source for any of them, and one client account is not a benchmark.