# The 20-Minute Weekly Google Ads AI Routine

Five prompts every Monday: week-over-week numbers, search-term sweep, budget pacing, ad health, one improvement — with rules for what to approve.

Tutorials · Published 2026-08-10, updated 2026-10-26.

> A weekly Google Ads routine with an AI agent is five prompts in twenty minutes: the week-over-week summary, the search-term sweep, a budget pacing check, an ad and asset health check, and one evidenced improvement proposal. Approve negatives and fixes on the spot, approve at most one spend change per week, and skip anything the agent cannot back with numbers it just pulled.

The weekly routine is five prompts, run every Monday, in twenty minutes:
numbers, search terms, budgets, ad health, one improvement. The agent
pulls every number and argues every case in seconds; you stay in control —
approving, and skipping. This is the maintenance layer that sits on top of
[everything Google already automates](https://adcopilot.cloud/google-ads-automation), covering
the judgement calls no Smart Bidding model makes.

The routine assumes you have run a
[first audit](https://adcopilot.cloud/tutorials/your-first-ai-google-ads-audit) and cleared the
backlog; a weekly pass maintains a clean account, it does not clean a
messy one. One conversation, all five prompts, in order.

## The routine at a glance

| Slot | Prompt | Minutes | Ends with |
| --- | --- | --- | --- |
| 1 | Week-over-week summary | 4 | Understanding |
| 2 | Search-term sweep | 5 | Approved negatives |
| 3 | Budget pacing check | 4 | At most one budget proposal |
| 4 | Ad and asset health | 3 | Fix list |
| 5 | One improvement | 4 | One approved or parked change |

## Prompt 1 — the week in numbers

```text
In account <account>: last 7 days vs the 7 before — spend, conversions,
cost per conversion, by campaign. Three sentences on what moved and the
most likely cause, checking change history before you speculate.
```

Read it, don't act on it. The summary exists to load the week's context
into your head — and the agent's conversation — before anything is
decided. The "check change history" clause is what separates a cause from
a guess: last Monday's approved budget change should be the first suspect
for this Monday's movement.

**Approve:** nothing here — it is a read. **Skip:** any urge to react to
a single week's cost-per-conversion wobble on low volume.

## Prompt 2 — the search-term sweep

```text
Pull search terms from the last 7 days with cost and no conversions.
Classify them, recommend negatives with match types, show me the list —
then add the ones I confirm to the campaigns where they appeared.
```

The compressed version of
[the full sweep](https://adcopilot.cloud/tutorials/negative-keyword-sweep-with-ai): classify,
judge, one add-negatives call per campaign.

**Approve:** clearly irrelevant terms, on sight — negatives can only stop
spend. **Skip:** "plausibly fine" terms and the competitor-blocking
debate; the first needs time, the second is a quarterly decision, and
neither belongs in a Monday slot.

## Prompt 3 — budget pacing

```text
For each enabled campaign: daily budget, average daily spend last 14
days, lost impression share to budget, cost per conversion. Flag
campaigns that are capped AND converting well, or uncapped AND wasting.
If one budget change is clearly justified, propose it with the evidence.
```

The two flag conditions are the only budget situations that deserve
weekly attention: a winner being throttled, or a loser left running.

**Approve:** at most one budget change per week, and only when the
evidence column convinces you independently. **Skip:** simultaneous
changes to several budgets — batch spend changes destroy your ability to
read next week's Prompt 1, and the one-change cap is the whole reason
this routine stays trustworthy. The reasoning is the same as in
[the approval workflow](https://adcopilot.cloud/tutorials/approval-workflows-for-ai-ads-changes):
set your AI client to ask before AdCopilot's write tools so it stops at each spend change, because they are the only expensive mistakes.

## Prompt 4 — ad and asset health

```text
Any ads disapproved or limited by policy this week? Any ad group left
with zero or one enabled RSA? Any campaign missing sitelinks or
callouts? Short list, worst first.
```

A three-minute smoke test for silent breakage. Disapprovals are the
urgent class — a disapproved ad is blocked distribution wearing an
"enabled" label.

**Approve:** asset fixes on the spot — new sitelinks or callouts drafted,
reviewed, created. **Skip:** rewriting healthy ads because you are bored
of them; creative changes belong in a deliberate session with a
hypothesis, not a health check.

## Prompt 5 — one improvement

```text
Based on everything this session, propose the single highest-value
change to account <account> this week. State the evidence, the exact
change, the risk, and how we'll know in 14 days whether it worked.
Wait for my decision.
```

The open slot is what makes the routine an optimisation practice rather
than pure maintenance. Some weeks it proposes a device bid adjustment
with a table behind it; some weeks a keyword graduation from the search
terms; some weeks it says "nothing clears the bar this week" — which is a
correct answer and worth praising.

**Approve:** the proposal if — and only if — the "how we'll know"
criterion is concrete. **Skip:** proposals whose evidence is a
recommendation rather than a measurement. The agent argues from your
account's data, and the standard to hold it to is the one from
[the audit method](https://adcopilot.cloud/google-ads-audit-ai): findings, not vibes.

## Close the session

```text
Log this session: everything changed, everything proposed and declined,
and the one thing to watch by next Monday.
```

Thirty seconds, and next week's Prompt 1 has a written baseline to
check against. Over months, these logs become the account's management
history in plain language — every change explained at the moment it was
made, which is a record most manually-run accounts never have.

## Start this Monday

Set a recurring twenty-minute slot, paste the five prompts into a note,
and run the routine once — this week's session will be slower than
twenty minutes and that is fine; the second one will not be. If nothing
is connected yet,
[Start free](https://app.adcopilot.cloud/signup) and you can run
the full routine inside the five-day trial — enough to know whether
Monday-by-prompt beats Monday-by-dashboard for you.

## Questions

### Why cap the routine at one spend change per week?

Because attribution needs stillness. Change three budgets and a bid strategy in one session and next Monday's numbers cannot tell you which change did what. One evidenced spend change per week keeps the account legible to its own history — and if something is urgent enough to break the rule, it should be urgent enough to be obvious.

### Does the routine replace monitoring during the week?

It replaces routine fiddling, not awareness. The Monday session is the deliberate, evidence-first pass; between sessions, a quick 'anything unusual in account X yesterday?' costs one read prompt whenever you feel the itch. What the routine removes is the daily temptation to change things — most weekday tinkering is reaction to noise.

### Can I run the same routine across several client accounts?

Yes — the five prompts are account-agnostic, so agencies run them per account, naming the account at the start of each conversation. With per-member connectors, each account manager runs the routine on the accounts their own Google sign-in can reach, and the audit trail records each person's sweep separately. Twenty minutes per account is the honest budget.

---

This is the markdown copy of https://adcopilot.cloud/tutorials/weekly-optimization-routine-with-ai. The index of the site's pages is https://adcopilot.cloud/llms.txt.
