Google Ad Grant requirements — eligibility checklist for small nonprofits (2026)
By Glenda Hood · Lead Researcher
Published June 5, 2026
Who qualifies — and who does not
Google Ad Grants are not open to every good cause. The program targets registered charitable nonprofits with a functional web presence and clear mission delivery. Before your communications chair spends an afternoon on forms, run this gate:
Eligible (generally)
- U.S. 501(c)(3) organizations in good standing with the IRS
- Registered charities in other countries where Google for Nonprofits operates (rules vary by region)
- Religious congregations operating community services (food pantry, shelter, counseling) with proper documentation
- PTAs and booster clubs only when they are standalone 501(c)(3) entities — school district accounts do not qualify as the PTA itself
Typically ineligible
- Government agencies and municipalities
- Hospitals and large health systems (separate Google health programs may apply)
- Universities and K–12 schools (foundations tied to schools may qualify separately)
- Political organizations, PACs, and advocacy groups without charitable designation
- Commerce-focused entities whose primary activity is selling products for profit
If your org runs a phone-case fundraiser or merchandise table, that revenue stream does not disqualify you — but your primary mission must be charitable, and your website must not look like an e-commerce store with a donation sidebar.
Document checklist before you click Apply
Gather these before starting the Google for Nonprofits flow:
| Document | Why Google asks |
|---|---|
| IRS Determination Letter (501(c)(3)) | Proves federal tax-exempt status |
| EIN confirmation | Matches legal entity name |
| Board roster with officers | Confirms governance (some regions) |
| Annual report or Form 990 summary | Shows active operations |
| Website URL with HTTPS | Live site reviewers will click every footer link |
Name consistency matters. If your IRS letter says “Friends of Riverside Park Inc.” but your website says “Riverside Park Alliance,” TechSoup reviewers pause the application. Align legal name, DBA, and homepage title tag before submitting.
TechSoup validation — the step boards underestimate
For most U.S. applicants, Google routes nonprofit verification through TechSoup. You create a TechSoup account, register your organization, and wait for validation — often 3–10 business days, longer near quarter-end.
Tips that reduce TechSoup delays:
- Use the exact legal name from your determination letter
- Upload a clear PDF of the IRS letter (not a phone photo with glare)
- Register with an org-domain email (
treasurer@yourorg.org) when possible - If rejected, read the reason code — “entity not found” usually means EIN typo, not fraud
Once TechSoup approves, link that validation to Google for Nonprofits. Skipping TechSoup when it is required is the number-one stall point Missionpath sees in board surveys.
Website requirements Google actually checks
Your site does not need a $20,000 redesign, but it must pass a live reviewer click-through. Minimum bar:
Must have (non-negotiable)
- HTTPS on every page — no mixed-content warnings
- Substantial mission content — not a single splash page with a phone number
- Clear description of what the org does — visible without logging in
- Privacy policy linked in footer
- Contact information — physical address or recognized service area for local orgs
- No excessive commercial content — affiliate-heavy product blogs fail this test for grant applicants
Strongly recommended before apply
- Dedicated Donate or Get involved page with working form
- About page naming leadership structure
- Mobile-responsive layout — reviewers use phones
- Google Analytics 4 installed with at least one conversion event defined
Automatic red flags
- “Under construction” homepage
- Broken donate links pointing to expired PayPal buttons
- Domain parking pages or GoDaddy placeholders
- Sites whose primary navigation is a product catalog
Missionpath’s centerpiece Ad Grant guide assumes your site passes this bar. Fix the website before application, not in parallel.
Google for Nonprofits account structure
Create accounts in this order:
- Organization Google account — Use
admin@yourorg.orgor a role-based account, not a volunteer’s personal Gmail that graduates every May. - Google for Nonprofits enrollment — Apply at google.com/nonprofits with TechSoup validation ready.
- Google Ad Grants application — Inside the nonprofit console after enrollment approves.
- Google Ads account — Link when prompted; use USD currency and correct time zone.
Grant admins should enable two-factor authentication on every admin login. Nonprofit accounts without 2FA are common takeover targets.
Policy requirements that survive approval
Eligibility does not end at approval. Ongoing requirements include:
- Active account management — Log in regularly; see our maintenance guide
- 5% click-through rate (CTR) floor on grant campaigns (Google measures account-level performance over rolling windows)
- No single-word keywords (except approved branded terms)
- No quality score 1–2 keywords left running indefinitely
- Geotargeting must reflect where you actually serve — national targeting for a single-county pantry wastes credit and draws policy scrutiny
- No linking to prohibited content — gambling, weapons, hate speech, misleading health claims
Special cases Missionpath boards ask about
Fiscal sponsors — If you operate under a fiscal sponsor’s 501(c)(3), the sponsor’s tax status usually must anchor the application, with clear disclosure of your program on the website.
Faith-based orgs — Eligible when providing community services. Sites that only list service times without community program detail often struggle at review.
All-volunteer orgs with no staff email domain — Use a durable role account (board@) on Google Workspace nonprofit tier once approved; until then, document why a gmail.com admin is temporary in your internal runbook.
Recently incorporated — Brand-new 501(c)(3)s with determination letters under 90 days old sometimes face extra TechSoup scrutiny; allow longer lead time.
Application timeline (realistic)
| Phase | Duration |
|---|---|
| Internal doc gather | 1–2 weeks (board schedules) |
| Website fixes | 1–3 weeks (volunteer or contractor) |
| TechSoup validation | 3–10 business days |
| Google for Nonprofits review | 2–14 days |
| Ad Grants activation | 3–7 days after Ads account linkage |
Total: 6–10 weeks for well-prepared orgs; 3+ months if the website needs rebuilding.
Pre-submit board vote (recommended)
Because the grant ties to your public web presence and Google account custody, Missionpath recommends a one-page board consent covering:
- Named account administrators (primary + backup)
- Acknowledgment of monthly maintenance duty
- Agreement that ads promote mission pages, not personal projects
- Plan for credential transfer when officers rotate
This prevents the “treasurer left, nobody knows the password” failure mode that kills more grant accounts than policy violations.
After approval
Return to the centerpiece campaign guide for structure, then schedule the monthly maintenance checklist before your first campaign goes live.
Requirements change — Google updated grant policies in 2023–2025 around account-level CTR and conversion goals. Missionpath revises this checklist when official documentation shifts; your board should re-read Google’s nonprofit help center annually.
