Your Ad Grants rejection says the same thing every time
Five submissions, five identical rejection messages, and not one line about the pages you fixed in between.
The same wording does not mean the same verdict
The message that arrived after your latest submission reads like a verdict on the pages you fixed in between. Read it as a standard reason list instead. Identical wording across submissions tells you the list has not changed. It does not tell you that a reviewer looked at your new certificate, your repaired links or your rebuilt homepage and judged them insufficient.
Google's Ad Grants website policy hands the diagnosis to you. By the end you'll know which checks are written down, which changes to stop making, and whether to resubmit this week or wait a few weeks.
What the rejection message is actually made of
The message lists reasons an application can fail. It names no page and no certificate on your site, and it never says which reason applied. A nonprofit asked the Help Community where to focus after that kind of response, and a volunteer expert answered:
Just a generic list, not necessarily the actual problem.
Diamond Product Expert, a volunteer contributor, Google for Nonprofits Help Community, 6 August 2026
Diamond Product Expert is a Help Community contributor status, not a Google role. Read that line as an experienced volunteer's account of the message rather than a statement from Google about how the review works.
The website policy settles what to do with the message. Treat the list as a checklist, audit the site, and address potential issues before you reapply or request review. Reading the rejection a sixth time won't produce a finding it never contained, and neither will forwarding it to your web developer. Your next submission carries only what your own audit against the published policy puts into it.
Check that the rejection is even about the step you think it is
Before you audit another page, check which decision stalled. Two approvals sit in this process, and separate reviews decide them at different moments.
Google for Nonprofits verification comes first. Your organization has to be registered as a charitable organization in an eligible country, meet the country-specific requirements, and be verified by Google's validation partner Goodstack. Google says most Google for Nonprofits verification requests are reviewed in 2 to 14 business days.
Ad Grants activation is a second step. Each product is activated separately after verification, so approval for Workspace or another Google for Nonprofits product does not necessarily mean Ad Grants is active. With Workspace already running on the same account, you can spend a month rewriting website copy while the stall sits at product activation. Work out which of the two steps your message concerns before you touch the site again.
Three changes that will not move the decision
Three changes get made between resubmissions on the strength of practitioner advice rather than anything Google published. None of them appears as a requirement on the Google pages cited below.
| Change made between submissions | Where it comes from | What the cited Google page says |
|---|---|---|
| Chasing a PageSpeed score of 90+, 100, or all green | Repeated by practitioners | The Ad Grants website policy asks that pages load quickly and recommends PageSpeed Insights with attention to mobile. It publishes no specific score that guarantees approval. |
| Waiting for the domain to reach six months or a year | Repeated by practitioners | The Ad Grants website policy is the page cited as the correction. No published age threshold to point at. |
| Adding a credit card or billing profile to finish activation | Repeated by practitioners | Google's setup error page, Not Eligible for Ad Grants, is the page cited as the correction. |
| Migrating the website to a .org domain | Assumed requirement | Google says a .org domain is not strictly required if the nonprofit owns and controls another top-level domain. |
The left column reports claims repeated by practitioners. They are recorded here as claims, not as Google rules.
Start with the score. Google asks that pages load quickly and recommends testing with PageSpeed Insights, but the Ad Grants website policy publishes no score that guarantees approval. Pushing the number up buys you a faster site and nothing you can point to in the policy.
Domain age is the second. Six months or a year gets quoted as a threshold, and the website policy publishes no age requirement at all. Waiting out the calendar is your decision rather than Google's.
The billing profile. Adding a credit card or billing profile is a practitioner claim rather than a published activation step, and it gets made in the belief that it finishes the job. The page that corrects it is Google's setup error page, Not Eligible for Ad Grants, not anything in the rejection message. If a card already sits on the account, it has not moved your application forward.
The .org assumption belongs in the same group. Google says a .org domain is not strictly required where the nonprofit owns and controls another top-level domain. Migrating off .info or a country domain gains you nothing and hands you a fresh set of redirects and certificates to get wrong before the next submission.
What the policy does ask you to check
The written checks are narrower than the advice circulating around them. Google requires the entire site to be served over HTTPS, and names the failures it warns about: missing SSL certificates, expired certificates, and mixed content.
Entire site is the part that catches people out. A valid certificate on the homepage settles nothing about your donation page, an old campaign microsite on a subdomain, or the pages your CMS serves from a second template. Check the certificate and the mixed-content warnings on every page a campaign would send traffic to.
Speed and links come next. Run PageSpeed Insights, a mobile-friendly test and a broken-link checker across the site, and fix what they return before you reapply or request review. That is the audit the policy asks for, and mobile is where Google says to pay attention.
Each of those checks pairs with a named reason in the list you were sent. That pairing is the only new information your next submission carries, because the message will not supply any.
Resubmit now or wait a few weeks
Your choice this week is between resubmitting with an audit behind it and holding for a few weeks. One piece of evidence supports waiting, and it is worth knowing what it is before you plan around it.
On 19 August 2026, in a Help Community thread about activation rejected five times with identical wording, a Diamond Product Expert wrote that he had "got a bit more information from Google" and that there had been "a recent pattern of too-strict decisions" that Google was fixing. He suggested waiting a few weeks, then resubmitting.
That is a Help Community claim by a volunteer Product Expert, with no Google Help Center notice, policy update or public incident announcement behind it. Take it as a reason to be patient with a careful resubmission rather than a reason to send the same site back unchanged.
This week, pair every reason in the rejection list with one documented change on the site, and hold the submission until each line has something beside it. Any reason you cannot pair with a change is the one to check again rather than skip. The policy asks for that audit before you reapply, and it is the part of this you control.
One documented change per reason, then submit
Identical rejection wording is the same list arriving twice. Everything you learn about your own site comes from the audit you run against the published website policy, so send the next submission once every reason on that list has a change and a date beside it.
The qualification review is free. All we need is your organization's name and website. Start the free quiz
Questions
What are the commonest reasons an application is rejected?
In our experience they are administrative rather than exotic: the verifier cannot confirm the applicant belongs to the organization, the legal name or address does not match the public register, a verification email went unanswered, or the site does not meet Google's website policy. That is precisely why the eligibility and website reviews happen before we apply, not after a refusal.
How we work
Is a rejection permanent?
Not necessarily. Every rejection gets classified first as correctable or final. Correctable covers the ordinary cases (a document the verifier could not accept, a mismatch between your public register entry and your website, a verification request nobody answered), and the case goes back in once that is fixed. It is final when the underlying eligibility problem cannot be resolved or further resubmission stops being reasonable, and then the refund applies.
Our terms
What does activation actually mean after approval?
Approval and activation are two different moments. Google approves the Ad Grants request; then the account has to be switched on and made usable: confirming the correct administrator email, completing the account-access steps Google asks for, and recording the right Customer ID. Google also requires a payments-profile step even though a grant account is never charged through it. Campaign build starts only once the live account is in hand.
How we work
Why are there two applications?
Because Google runs two programs. Google for Nonprofits verifies your organization: you submit that one, with our guidance, because it needs your documents and a legal representative of the organization. Ad Grants is the advertising program that sits on top of it, and we handle that application for you. Approval on the first does not mean approval on the second.
Our terms
Who actually verifies our organization?
Not Google directly. Google currently routes the application to a nonprofit validation partner (Goodstack at the time of writing), which checks two separate things: that the organization is what it says it is, and that you personally are connected to it. It works from public registers, your website, the email addresses involved, and any documents it asks for. Partners and their checks change, so treat the name as current rather than permanent.
How we work
Do we need HTTPS on our website?
Yes. A valid certificate on the domain your ads point to is part of Google's website requirements for Ad Grants, and a site served over plain HTTP will not pass the review. It is usually the cheapest thing on any corrections list: most hosting providers issue a certificate free and switch it on in a few clicks.
Google's rule · Checked AUG 2026
Is there a page speed score our site has to hit?
No. There is no published Ad Grants speed threshold, and AdGranted will not invent one: inventing arbitrary numerical thresholds is exactly what our compliance standard forbids. What gets judged is whether material pages load at a usably quick speed, particularly on a phone. A site slow enough that visitors give up is a genuine problem; an imperfect number from a testing tool, on its own, is not.
Commonly repeated · Not a Google rule
Do a few broken links really matter?
Yes. Google treats broken links, dead pages and poor navigation as a website-policy risk, so a 404 behind a menu item, a donate button that leads nowhere, a redirect loop, or a form that visibly fails to load can each hold up approval. Donation and application paths get particular attention: Google expects them to work, to be secure, and to land somewhere plainly connected to your organization.
Google's rule · Checked AUG 2026
How long does Google take to decide?
No date is promised, and you should be wary of anyone who promises one: the review is Google's process and its timing is outside our control. AdGranted's own work targets roughly seven business days; everything after that is Google's clock. You get a straight answer on where the application stands rather than a guess at when it lands.
Our terms
Sources
- Google Ad Grants Website policy
- Google for Nonprofits eligibility and activation
- Google Ad Grants setup error page: Not Eligible for Ad Grants
- Help Community thread: Rejected for Google Ads Grants, vague response and unsure where to focus (6 August 2026)
- Help Community thread: Ad Grants activation rejected 5x with identical wording despite documented fixes (19 August 2026)