Check Google Ad Grants eligibility in stages: the organisation’s country and registration, Google for Nonprofits verification, the availability of the specific product and the website’s readiness. Keep those decisions separate. For a Zambian organisation, obtain country-specific and Ad Grants product confirmation before treating the programme as an available advertising route.
A country name in a selector is not an eligibility decision for a particular organisation. Build the application record around the exact registered entity and the programme’s current response. Meanwhile, prepare the website evidence and assign responsibilities so the organisation can make a useful decision without confusing general nonprofit status with acceptance into a product.
What must the organisation establish first?
Google for Nonprofits requires charitable registration in a listed country or region. Google for Nonprofits requires verification by Goodstack. The eligibility guidelines make registration and validation distinct requirements. Keep the registered name, registration evidence and authorised representative consistent throughout the application record.
An applicant must meet the requirements for its own country or region. An applicant must agree to the Google for Nonprofits Additional Terms of Service. Ask the organisation’s responsible officer to identify the applicable registration category and review the terms. A related organisation’s acceptance in another country does not answer either question for this entity.
Not every Google for Nonprofits product is available in every country. Google directs applicants to check product availability inside their Google for Nonprofits account. Keep that product check separate from the country-selected registration guidance.
Governmental entities are excluded from Google for Nonprofits. The same guidelines also describe exclusions and exceptions for healthcare and educational organisations. If the applicant operates in one of those areas, record its exact legal and organisational relationship and seek the programme’s determination. Do not relabel an institution as a charitable arm simply to make a form appear suitable.
Keep the country/product row open until the responsible person has obtained the applicable evidence. Record what was checked, when it was checked and the programme response. An empty row is more useful than a confident assumption that leads staff to promise an advertising plan the organisation cannot yet use.
Which website responsibilities remain with the nonprofit?
Ad Grants requires the nonprofit to own the domains its ads point to. The website policy defines ownership as administrative control over content, structure and technical settings. These requirements in the Ad Grants website policy make the domain and access arrangements part of application preparation, rather than merely a designer’s technical detail.
The submitted domain must directly host the organisation’s website. Map the intended advertising destination and inspect where it actually takes a visitor. A domain that forwards people elsewhere needs attention before it is presented as the organisation’s qualifying website. Keep the domain owner and the content owner visible in the preparation record.
Ad Grants does not require an .org domain. Avoid changing a familiar, controlled domain merely because another organisation uses that ending. The useful questions are whether the applicant controls the domain and whether the website meets the actual policy requirements. A new domain name cannot compensate for missing mission information or an unusable enquiry route.
The Ad Grants website policy requires the entire website to use HTTPS. Include the normal pages, embedded resources and the intended donation or contact journey in the technical review. Assign correction work to the person who controls the affected part of the site; a successful homepage visit alone does not complete the review.
| Evidence area | Record to prepare | Responsible reviewer |
|---|---|---|
| Country and product | Applicable country detail and product confirmation | Authorised organisation representative |
| Registered entity | Exact name and registration evidence | Organisation’s responsible officer |
| Validation | Programme verification response | Applicant contact |
| Domain control | Administrative ownership and access route | Domain administrator |
| Mission content | Approved description of purpose and activities | Programme or communications owner |
| Website journey | Tested information, contact and donation routes | Website owner |
| Account operation | Named access and review responsibilities | Account administrator |
What content makes the website useful to applicants and visitors?
Review the site as a person discovering the organisation for the first time. Can that person understand the mission, who the organisation serves and what its programmes do? Replace empty sections with approved factual information. Keep the detail on the website itself, with supporting documents where useful, rather than making a visitor download several files to understand the basic purpose.
Follow every important navigation link. Check that contact details lead to a monitored route and that donation links reach the intended secure process. Write the expected next step beside each link in the review record. This distinguishes a button that merely opens something from a journey that actually serves the visitor.
Review images and claims with the programme owner. A photograph should be honestly described, and a claim about activities or impact should have an owner who can substantiate it. Improving the site for an application should also improve its accuracy for the people who rely on it.
Original eligibility-to-website evidence register
Use this hypothetical example for a community learning organisation considering Ad Grants. The original register has two linked decisions: may this entity proceed with this product? and is its proposed website ready for review? Neither decision is allowed to borrow an answer from the other.
Row one: country and entity. Enter the registered organisation’s exact name and country. Attach the applicable country-specific programme detail and record the official verification route. If the evidence is only a generic selector or another organisation’s experience, mark the row awaiting confirmation. Do not write “eligible” until the relevant determination supports it.
Row two: product availability. Record whether Ad Grants is available through the organisation’s actual Google for Nonprofits route. Keep this separate from the existence of a Google account or the ability to use ordinary paid advertising. The owner of this row must be able to explain which product has been confirmed and for which entity.
Row three: domain and access. Identify the submitted domain and the people responsible for domain administration, website content and technical changes. Ask each owner to confirm the relevant control. Store credentials elsewhere. The register needs a durable responsibility map, not copied passwords that create another access problem.
Row four: mission journey. Select a proposed destination page about one programme. Have a reviewer read it, find supporting information and reach the contact or donation action. Record any broken link, confusing instruction or unapproved claim as a specific correction with an owner. Repeat the review after corrections instead of marking the entire site complete from a checklist tick.
Row five: account stewardship. Name who will administer access, review policy communications and maintain the website after activation. Use manager-account responsibilities where an external manager is proposed. Assign the organisation’s own oversight role as clearly as the operator’s role.
How should the organisation make its decision?
Proceed in the order the evidence supports. Complete registration and country/product confirmation first, then assemble the website review and the account operating responsibilities. If the programme route is unavailable for the entity, keep the website improvements as useful work and consider other distribution routes through a separate decision.
For measurement planning, see Google Ads conversion tracking. For wider campaign context, use Google Ads. To prepare a focused brief, get started with the evidence register and the eligibility or website rows that still need resolution.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.