Google Ads Just Blocked Muse — Overnight

November 5, 2026

AI robot locked out of a Google Ads dashboard with a red blocked warning

Shop Talk | November 5, 2026 | Jons Spot, Toronto

We woke up this morning to a new rule in Google Ads, enforced overnight.

Muse — the AI agent we run a lot of this shop with — can no longer open Google Ads in a browser. Not paused. Not warned. Blocked.

I've been building this whole site with Muse

This isn't a one-off experiment for us. I've been building jons.spot with Muse.

The shop you see today — over a thousand products live, the Christmas personalization line, the Grand Theft Christmas city tees, the Package Deals, the Stereos and Delta Sweet merch, the bulk discounts, the new decoration form, the Shop Talk blog and the Daily Picks series — most of that was built with Muse doing the heavy lifting and me approving it.

I give it a one-line idea. It builds the draft. I check it on my phone, say yes or fix this, and it goes live. That's how a one-person Toronto print shop keeps up.

It's not just products, either. Muse rebuilt our Brands menu, set up the bulk order discounts, wired up the Shop app storefront, sorted out Merchant Center, placed AdSense units without making the site look spammy, and writes the blog posts. I still make every final call — nothing publishes without my yes — but I don't have to click through a thousand Shopify screens to get there.

That was the deal: Muse as my extra hands, my extra eyes, my extra brain for the boring parts, so I can stay on the presses and with customers.

And it's not just Muse. We experiment with a bunch of AI tools around here — Ollama running local models, other agents and setups — always testing what can actually help a small shop run better. Muse is the one driving most of the site build, but we're not locked into one tool. If something works, we use it. If it doesn't, we move on.

The Google Ads part was awesome — while it lasted

The best part of that setup was computer use in Google Ads.

I could just say "take a look at the ads — should we be on ROAS right now, or cast a wider net?" and Muse would actually go in, open the dashboard, read the real numbers, and come back with an answer.

It wasn't guessing. On October 25 it moved our only active campaign, PMax-4, from 150% Target ROAS to 300% because that was the call at the time. On October 27 it added five negative keywords. On October 30 it ran a full audit — $13 a day, $94.47 spent Oct 23-29, 3,539 impressions, 50 clicks, $1.89 average CPC, zero conversions — and told me straight that we were bidding blind at 300% with no purchase data to back it up. It even set up the "Phone calls from ads" conversion so we could track calls, then pulled the call asset back out when I said we're not running call ads right now.

That's what made it awesome. I didn't have to learn Google Ads inside-out. I could ask a question in plain English and get a real check, a real change, and a real explanation back.

Until this morning, when that whole workflow just stopped working.

What happened this morning

We went to do a routine check on our ads. Should we stay on Target ROAS, or cast a wider net? We'd already decided to switch PMax-4 to Maximize conversion value with no target — cast wider, gather data, then bring a ROAS target back later. That change is still sitting undone because Muse can't get in to make it.

We signed in as usual, and Google Ads bounced us straight to a refusal page:

/aw/unauthorized_access
"Access by unauthorized AI agents isn't allowed under the Google Ads Terms and Conditions."

That was it. No campaign change, no settings touched, no warning first. The check we went in to do never got done.

And it wasn't just the agent getting blocked. When I took the browser over myself, I got into the Overview for about five seconds — long enough to see our numbers — then got bounced to the same refusal page.

Our Ads account isn't banned or suspended. Our campaigns are still running. It's this browser session that's flagged. On my own phone, in my own browser, Ads still opens. In the shared browser Muse works in, it doesn't.

It was intermittent at first, too. One fresh open at 7:51 a.m. loaded fine. Then the next navigation tripped it again. That's what enforcement rolling out looks like — not a clean switch-off, but a door that starts closing.

The rule was already in the terms. Last night, they started enforcing it.

Google had already written this into its rules. On August 31, 2026, Google published updated Google Ads Developer Policies that ban what it calls "programmatic proxies" — third-party hosted services, wrappers, or MCP servers that sit between an advertiser and Google Ads and re-expose Google's own tools.

The idea is simple from Google's side: every business should connect to Ads through its own Google Cloud project, with its own credentials. No shared middleman routing requests for a bunch of different businesses at once.

Google's own official Ads MCP server is read-only by design. It can look things up and report back. It can't change a bid, pause a keyword, or edit a budget. That's not a bug, that's the policy.

What changed overnight is that the browser route closed too. Signing in as the user and letting an agent click around Ads — the way a lot of small businesses have been doing it — now gets flagged as unauthorized AI-agent access.

So the writing was on the wall since August. This morning was the morning it hit our account.

What this means if you run ads with an AI agent

If you've been letting an agent manage Google Ads by driving the browser for you, that workflow is done, at least for now:

Don't expect to sign in through an agent browser and get in reliably. It may load once, then bounce you.
Don't try to work around it by signing in again and again. Repeated sign-ins were already a likely trigger, and hammering it risks flagging the session — or worse, the account — further.
Your ads themselves are fine. This is an access block, not an account suspension. Check from your own device and browser, not the agent's.

The sanctioned way forward, per Google's own policy, is the Ads API — but done right:

Your own Google Cloud project, under your own account
Your own Ads API access and credentials
A self-hosted tool that connects with those credentials — not a hosted third-party service routing you through their project

That's the route we're taking. We're setting up a self-hosted Ads connection on our own Google Cloud project, with changes gated by approval. No hosted proxy, no shared credentials.

In the meantime, we're back to doing Ads checks the old-fashioned way: human, on our own device, with GA4 for the conversion side when we need a second look.

Why we're writing about this

We're a Toronto print shop, not a tech blog. But we run this shop with Muse — orders, products, posts, and yes, until this morning, checking our own ads.

Muse is still building the site. That part hasn't changed. It's just the Ads browser door that's closed now, and we're figuring out the proper API front door instead.

When a platform changes the rules overnight for every small business using an AI helper, that's not just our problem. It's every shop owner who thought they finally had a way to keep up with the big advertisers without hiring a full-time media buyer.

Google wants AI in ads — its own AI, on its own terms, through its own API, with your own credentials. What it doesn't want is an agent sitting in your browser, clicking as you.

We get the security argument. Ad accounts move real money. But for a small shop, the gap between "use the API properly" and "just open the dashboard" is a real one. Setting up a Cloud project, API access, and a self-hosted server is not a five-minute job. That's work most small advertisers never signed up for.

We'll keep you posted on how the self-hosted setup goes — what works, what doesn't, and whether it's actually usable for a shop our size. If Google's going to make agents go through the front door, someone has to show what that front door looks like.

For now: if you use Muse, or any AI agent, with Google Ads — check your account from your own device today. Don't be surprised when the agent browser bounces you.

And your ads? They're still running. Go check them yourself.