Google Ad Grant rejected your church website? Here's how to fix it

You did the paperwork. You got verified, applied through Google for Nonprofits, and waited. Then the email came back: your Google Ad Grant was rejected because of your church website. If that's where you are, take a breath. It happens to a lot of churches, and it is almost always fixable.

I'm Zach, and I run White Oak Media. We've been helping churches get found online since 2019, and I manage Google Ad Grants for churches. One of them is a church in Massachusetts that came to me after Google had turned it down over its website and how its ads were performing. We worked through it together, and Google let it back into the grant. So I want to walk you through what Google is actually looking for, in plain words, and what I'd check first.

Why Google looks at your website at all

The Ad Grant gives your church free Google search ads. Every one of those ads sends someone to your website. Google doesn't want to spend its money sending people to a page that's broken, empty or confusing, so it reviews the site before it turns the grant on, and it can pause accounts later if things slip.

That's actually good news. It means a rejection is rarely about your church. It's about the site, and the site is something you can change this month.

Google publishes its Ad Grants website policy, and it lists the most common reasons it turns sites down: not enough unique content, an unclear mission, poor navigation or broken links, slow loading, a site that isn't secure, commercial activity that isn't allowed, and domain redirect problems. When I look at church sites, a handful of those come up again and again.

The fixes that matter most for churches

Here is the checklist I use, in the order I'd work through it. Each item comes straight from Google's policy; the church examples are what I usually see.

Own your domain, and make it the real site. Google wants your organization to control the domain and for that domain to host your site. If your web address simply forwards to a Facebook page, a giving portal or another company's page, that's a redirect problem. Our post on church website hosting and domains walks through how to check who owns yours.
Say what your church is and does. Google asks that the site clearly state your mission and describe your activities. A church home page that is only a photo, a service time and a Give button often isn't enough. Put a short, plain statement of who you are near the top, and give your ministries real pages.
Write real words, not just embeds. Google calls out thin content and pages that are mostly links or embedded material. A sermons page that is only a YouTube feed, or an events page that is only a calendar widget, reads as thin. Add a few sentences of your own to each key page: home, about, what to expect, ministries and contact.
Show you're a real, local organization. Google suggests listing your physical address, and your EIN or other registration details. For most churches, the street address in the footer and on the contact page does the job.
Fix broken links and dead buttons. Click every item in your menu and footer on your phone. Test the Give button all the way to the giving page. Old links to last year's Easter page or a retired ministry are common.
Make it fast and easy on a phone. Google recommends testing with PageSpeed Insights. Huge photos straight off a camera are a common culprit on church sites.
Serve the whole site over https. Every page, not only the home page. If your address bar shows a warning on some pages, that needs fixing before anything else.

What about the ads side?

The Massachusetts church I mentioned wasn't only a website problem. Google had also flagged how the ads were performing. Once a grant is running, Google expects the account to meet its own rules, like a 5% click through rate across the account and conversion tracking that actually works. I covered those in detail in the complete guide to the Google Ad Grant for churches, so I won't repeat them here.

What I'd say is this: fix the website first. Every ad lands on a page of your site, so a clear, fast, honest website helps your approval and your ad results at the same time.

How to resubmit without getting rejected again

Google's own advice after a rejection is simple: use its list as a checklist, check your site against every requirement, and fix everything before you resubmit your activation request in your Google for Nonprofits account.

The key word there is everything. It's tempting to fix the one thing someone noticed, resubmit the same week, and hope. Go through the whole list instead, ideally with someone who didn't build the site, because fresh eyes catch the broken link you've clicked past for two years.

A few practical tips. Keep notes on what you changed and when. Check the site on a phone, not only a laptop. And make sure two people at the church can log in to the website, the domain and the Google account, so the whole thing doesn't rest on one volunteer.

When it makes sense to get help

Plenty of churches can do this themselves. If you have a staff member or volunteer who is comfortable editing the site, this list and an afternoon will get you most of the way.

It makes sense to get help when you've already been rejected more than once, when nobody at the church is sure who controls the domain, or when the site itself is old enough that fixing it page by page feels endless.

That's the reason I offer Ad Grant approval help. For $295, one time, I review your whole site against Google's Ad Grant website policy, give you a clear fix list, check your changes, and help you resubmit. If Google says no again, one more round is included. I can't promise Google's answer, and I won't pretend to, but I can make sure your site is ready before it goes back in. If you decide to have us manage the grant afterward, that $295 is credited toward your first month when you start within 60 days.

If you'd like to talk it through first, grab a time on my calendar or call me at (860) 854-4983. The grant exists to help people find churches like yours, and I'd be glad to help you get there.