For SEO agencies

Triage every SEO client after a Google update in one agent conversation

When Google confirms a core update, your account managers want a call list by mid-morning. This is the runbook for screening every client's Search Console data with your AI agent, ranking who to call, and writing what to say.

Continue with Google

Free for 2 sites · No credit card

Or have your agent set it up

Set up DuckDive for my website. Follow https://analytics.duckdive.ai/agents.md

Updated 17 min read

The short answer

Link each client's Search Console and GA4 to DuckDive before the next update. When Google marks a rollout complete, ask your agent to screen every client for worse position with steady impressions, score the hits by loss, organic reliance and renewal date, drill into the top ones, and draft each account manager's note. Label it provisional.

  • Get the update's dates from Google's Search Status Dashboard first. DuckDive does not know them.
  • Call the clients who score highest, not the ones who email first.
  • Penalties live in Search Console's Manual actions report. Check it before anyone says the word.

The update-morning runbook for a client roster

A confirmed core update turns a head of SEO into a dispatcher: thirty-odd clients, one inbox, and account managers asking who to ring. This runbook assumes your team works through an AI agent and each client's Search Console and GA4 are linked in DuckDive.

DuckDive is the data behind the agent. It imports each client's Google history once and stores it, so a roster question never waits on a fresh pull from Google. The agent still reads clients one at a time, so you ask about every client in plain English. Paid and local clients are covered in the overview for agencies.

  1. Confirm the update and write down its dates

    Name, start day, and whether Google has marked it complete.

  2. Check that every client's data is current

    A failing import looks like a flat line.

  3. Screen for lost position with impressions held

    Pages that sank for searches people still ran.

  4. Score the flagged clients and sort the call list

    Call today, watch, or no action.

  5. Drill into the top two or three

    Pages and searches, before anyone picks up the phone.

  6. Send the notes and book the re-check

    The second look goes in the diary for one week after the rollout ends.

Confirm the update dates before you blame it

Google lists confirmed ranking updates on the Google Search Status Dashboard, with a start date and, once finished, how long each ran. As of November 16, 2026, it shows the November 2026 core update as active, starting November 10.

Rollouts take time. In the dashboard's ranking incident history, the five core updates from March 2025 to May 2026 each took roughly 12 to 18 days, so a client who dropped on day two may move again on day ten. Google's page on core updates and your website also sets the timetable for any verdict: "We recommend waiting at least a full week after a core update completes before analyzing your site in Search Console."

Two more facts shape the client email. That Google page says smaller core updates go unannounced, because they aren't widely noticeable. And on the dashboard, spam updates appear as separate incidents, so check which kind it is before "core" goes in writing.

Give the agent the dates

DuckDive holds your clients' data, not Google's update calendar. Paste the dates into the chat, or let an agent with web access read the dashboard.

Which clients to call before lunch

The first cut: average position worse, impressions about the same. People still searched and Google still showed the client, just lower down. If impressions fell as hard as clicks, that is usually demand, and the guide to diagnosing a traffic drop across many sites covers telling the two apart.

Ask your agent
Using the rollout dates I gave you, compare each client's last 14 days with the 14 before, and keep only clients whose average position slipped by at least one place while impressions moved less than 10%.

Tools it calls list_websites get_search_console_summary

The summary tool returns weekly points, each starting on a Monday, so "the last 14 days against the 14 before" really means the latest two weeks against the two weeks prior. That is close enough for a screen, and the one-place and 10% thresholds keep minor wobbles off the call list.

Watch out

Average position can worsen while a client does better. When a site starts showing up for new long-tail searches far down the page, impressions rise and the site's average sinks, though no existing ranking moved. Check clicks before you flag anyone.

A long list of losers is not a call list. Score each flagged client from 0 to 2 on three factors and add them up.

Who gets a call today: score each flagged client, then total the points
Factor0 points1 point2 points
Size of loss (search clicks, window vs window)Down less than 10%Down 10% to 25%Down more than 25%
Reliance on organic (share of GA4 conversions)Under a thirdA third to two thirdsOver two thirds
Renewal or review dateMore than 90 days away31 to 90 days away30 days or less, or already unhappy
What the total means0 to 2: no action, mention it at the next report3 to 4: watch, re-check after the rollout settles5 to 6: call today

Loss comes from the screen, organic reliance from GA4 channels, and renewal dates from you: DuckDive holds no contract data, so paste them in. Tune the thresholds to your roster.

Ask your agent
For each flagged client, get the share of GA4 conversions from organic search over the last 90 days, then score and sort them with the renewal dates I'm pasting below.

Tools it calls get_ga4_channels

Organic share measures exposure, not quality; for that, benchmark conversion rates across your clients on a calmer day.

Worked example: a 31-client roster the day after a core update

A fictional agency runs the screen the morning after Google marked an update complete. The latest 14 days cover the rollout; the 14 before are the baseline.

EXAMPLE DATAFictional business: a 31-client SEO roster

The rollout took the last two weeks and Google marked it complete yesterday. Run the update screen across the whole roster, then score whoever it catches using the renewal dates pasted below.

  1. list_websitesfinds all 31 client sites
  2. get_search_console_summaryeach site's weekly points for the last 90 days; the two rollout weeks against the two before (31 calls)
  3. get_ga4_channelsorganic share of conversions over the last 90 days, for the 7 flagged sites

7 of your 31 clients lost position while impressions held. Two more lost clicks with impressions down just as hard, so they fail the screen. The other 22 moved less than one position and less than 10% on clicks.

ClientAvg positionImpressionsClicksVerdict (score)
Alderpoint Legal4.2 → 7.9-2%-38%Call today (6)
Granite Ridge Chiropractic3.6 → 5.8+1%-27%Call today (5)
Corvane Dental Studio5.1 → 7.0-4%-22%Watch (4)
Mossbank Auto Glass6.3 → 7.6-6%-12%Watch (3)
Ironwhistle Brewing2.9 → 3.9-1%-11%Watch (3)
Sablecrest Realty8.8 → 10.1+3%-9%No action (2)
Ottermere Tutoring11.4 → 12.6+8%-4%No action (1)
Quillfeather Bakery3.3 → 3.4-17%-18%Off screen: demand
Tidewell Pools5.0 → 5.2-41%-44%Off screen: seasonal
22 other clientswithin 1.0within 10%within 10%No action

Alderpoint Legal scores 6: clicks down 38% (2 points), 71% of conversions from organic (2), renewal in three weeks (2). Granite Ridge Chiropractic scores 5: down 27% (2), 68% organic (2), renewal in two months (1). Ironwhistle Brewing gets only 22% of conversions from organic but renews in 12 days, so it lands on watch. Quillfeather Bakery and Tidewell Pools held position; they need a short note, not a rescue plan.

Search Console GA4

Have your own call list ready when the next rollout ends

Link your clients' Search Console and GA4 now, and the same screen runs on your real roster the morning Google marks the update complete.

Continue with Google

Free for 2 sites · No credit card

Drilling from a client to the pages and queries that moved

Before the call, the account manager needs two specifics: which pages lost traffic, and on which searches.

Ask your agent
For Alderpoint Legal, which of its top 100 pages lost the most Search Console clicks in the last 7 days?

Tools it calls get_search_console_pages get_search_console_keywords

The pages tool returns up to 100 pages by clicks for a fixed window, so the agent reads the last 14 days and subtracts the last 7. One gap: the page list and the query list arrive unjoined, so nothing says which search fed which URL. The agent pairs them by topic, which usually works on a law firm's practice pages and can fail on a blog with overlapping posts. Before anyone quotes a pair, filter Search Console's Performance report by the page and open the Queries tab.

EXAMPLE DATAFictional business: Alderpoint Legal

Which of Alderpoint Legal's top 100 pages lost the most clicks in the last 7 days, and which of its searches fell furthest?

  1. searchfinds Alderpoint Legal's website
  2. get_search_console_pagestop pages for the last 7 days, then the last 14, to work out the 7 days before
  3. get_search_console_keywordstop queries for the last 7 days and the last 30, to compare positions

Five pages lost the most, each down 30% to 52%. Their main searches slid from the top five to the bottom of page one or onto page two.

PageClicks, 7 days beforeLast 7 daysChange
/practice-areas/workers-compensation412198-52%
/practice-areas/car-accidents365211-42%
/blog/after-a-rear-end-collision288176-39%
/practice-areas/slip-and-fall190121-36%
/locations/eastbrook-office14098-30%
Query (avg position)30 days7 days
workers comp lawyer eastbrook3.49.1
workers compensation claim denied3.98.7
car accident attorney near me4.810.6
rear end collision what to do3.18.2
slip and fall lawyer4.611.0

Lead with workers' compensation: the biggest page loss and two of the five searches. The 30-day positions include some rollout days, so the true "before" was likely a little better. The page for each query is my match by topic; confirm it in Search Console before quoting it.

Search Console

What Search Console can tell you on day one, and what it cannot yet

Search Console is not same-day data. Google's page About Search Console data says collected data "should be available in 2-3 days", and the Performance report help warns that the newest data "can be preliminary". On the morning a rollout ends, the last couple of days on every chart are missing or provisional.

DuckDive answers from stored imports, so a stale client would sail through the screen looking calm. Rule those out first. If a client's Search Console import is behind, an admin can re-pull up to the last 30 days of it; each site accepts one refresh per quarter hour, so stagger them across the roster rather than firing all 31 at once.

Ask your agent
Before the update screen, tell me which clients have Search Console or GA4 data that stops before the rollout's final day, or an import that has not finished. Those get a footnote, not a verdict.

Tools it calls list_websites get_sync_status

Day one tells you who lost position and on which pages, not whether it will stick. Google's guide to debugging Search traffic drops puts it bluntly: "Small fluctuations in position can happen at any time." It goes further for pages that still do their job: "we recommend avoiding making radical changes if your page is already performing well."

Clicks and impressions
Clicks through from Google Search results, and times the site appeared in them. Impressions stand in, roughly, for demand.
Average position
Site-wide, the average position of the site's topmost result. For a page or query row, the average for that row. Lower is better.
Preliminary data
The newest days, still being collected. Google draws them as a dotted line on its chart.

Core update client communication: the note your account managers send

Clients forgive a ranking drop. They don't forgive spotting it first, or a broken promise of a fix by next week. Good core update client communication goes out before they ask, in four parts:

  • What happened: the update's dated name, linked to Google's dashboard.
  • What we see: two or three before-and-after figures from windows of equal length.
  • What we are doing: the pages under review, and what we are leaving alone.
  • When you hear next: one week after the rollout ends.

Never promise a recovery date. Google's core update guidance says confirming an improvement could take several months, sometimes until the next core update. Clients that held position get a shorter note: searches fell, not rankings.

Ask your agent
Draft a two-paragraph note for the Quillfeather Bakery account manager saying whether last week's click drop looks like rankings or seasonal demand, with the numbers behind it.

Tools it calls get_search_console_summary get_search_console_keywords get_ga4_channels

EXAMPLE DATAFictional business: Quillfeather Bakery

Draft the Quillfeather Bakery note: rankings or seasonal demand, with the numbers.

  1. get_search_console_summarythe last 14 days, plus the weekly 12-month trend to see whether impressions have been sliding since late summer
  2. get_search_console_keywordstop queries for the last 7 and last 30 days
  3. get_ga4_channelsorganic sessions and conversions for the last 30 days
Search ConsolePrior weekLast weekChange
Clicks612484-21%
Impressions18,40014,900-19%
Average position3.33.5+0.2

"Hi, a quick update on last week. Clicks from Google fell 21%, but your rankings held at an average position of about 3.5. Fewer people searched: impressions fell by almost the same share, led by wedding cake searches, which have eased off every week since the August peak in your 12-month trend while your position stayed between 3.2 and 3.6."

"We won't change pages that still rank well over a seasonal dip. We'll watch the cake order page and send fresh numbers on the 4th, once Google's current update settles. Nothing here needs action from you."

Before this goes out: the same week last year sits at the very edge of the 12-month range I can read, so I can't compare like for like. Open the bakery's Performance report in Search Console, which keeps 16 months, and check last November's impressions before you add a year-on-year line.

Search Console GA4

Before a note leaves the agency

  • The update is named and dated. Link the dashboard entry so the client sees it was not just them.
  • The windows match. Seven days against seven, never a week against a month.
  • No penalty language. Unless the Manual actions report lists one.
  • One figure checked by hand. Confirm it in the client's Search Console before sending.
  • A re-check date, not a recovery date. Promise when they will hear next.

Worked example: the client who asks if they were penalised

Someone will ask, usually the owner, usually by phone. The honest answer separates two things Google handles very differently.

A manual action is applied when, in Google's words, "a human reviewer at Google has determined" that pages break its spam policies. Google notifies you in the Manual actions report and message center, and you request a review after fixing it. A core update is a broad ranking change that Google says does not target specific sites, with nothing to request. Hacked content and malware sit in the Security issues report.

DuckDive reads neither report, so step one happens in Search Console itself. The agent handles step two: do the timing and shape of the loss match the rollout?

Ask your agent
Granite Ridge Chiropractic's owner thinks they were penalised. The core update ran [start date] to [end date]. Show weekly clicks, impressions and average position for 90 days: does the slide start inside the rollout, and is it spread across pages or one page?

Tools it calls get_search_console_summary get_search_console_pages

EXAMPLE DATAFictional business: Granite Ridge Chiropractic

Does Granite Ridge's slide start inside the rollout, and is it one page or many?

  1. searchfinds Granite Ridge Chiropractic's website
  2. get_search_console_summarythe last 90 days, grouped into weeks around the rollout dates you gave
  3. get_search_console_pagestop pages for the last 7 and last 30 days, to see how widely the loss spread

The slide starts in the first week of the rollout. Weekly clicks went from 1,120 to 770 in two weeks while impressions stayed near 22,000, and average position went from 3.6 to 6.2.

WeekClicksImpressionsAvg position
3 weeks before1,15021,9003.5
2 weeks before1,13021,6003.6
1 week before1,12021,7003.6
Rollout week 187021,8005.4
Rollout week 277022,0006.2

The loss is spread: 17 of the top 30 pages lost clicks, none more than a fifth of the drop. The timing fits the update but says nothing about manual actions, so open both Search Console reports before you call.

Search Console

If both reports are clear, the account manager can say: "Google's manual actions report lists nothing against your site. Your drop lines up with a Google update that hit many sites over the same two weeks. We're reviewing the pages that lost most and will show you fresh numbers once it settles." If either report is not clear, the call is about that report.

Setting up your roster before the next update

Update morning is the worst day to discover a client was never linked. Each source brings its history in when you link it and DuckDive keeps it, so whatever you connect this month becomes next update's baseline.

  1. Use the agency Google account your team already reports from

    Whichever login your analysts open client properties with is the one to sign up with. A client whose property it cannot see has to grant that login access in Search Console or GA4 before DuckDive can list it.

  2. Link Search Console first, then GA4, then the rest

    In an agency account, each website sits under its client. Search Console comes first because it drives the whole screen. GA4 comes next, since the organic-share score depends on it. Google Ads and Local Services Ads only matter for clients who run them, and can wait. A freshly linked source usually finishes importing within a few minutes.

  3. Or have an admin's agent work through the list

    Paste the prompt below into an agent signed in as an Agency Admin, approve the one Google screen with "Also allow actions" left on, and name the clients to add. It links whatever matches without doubt and asks you about any property it is unsure of.

    Hand this to your agent
    Set up DuckDive for my website. Follow https://analytics.duckdive.ai/agents.md
  4. Give each account manager the connector

    Account managers add https://api.duckdive.ai/mcp to their own agent and approve it with their DuckDive login; nobody handles a key. On update morning they read and ask, while setup and refreshes stay with admins. Claude users can start from the prefilled connector link; on ChatGPT it takes a Business or Enterprise workspace. Per-app walkthroughs: Claude, ChatGPT, Cursor.

  5. Rehearse the screen on a calm week

    Run the roster screen and the scoring prompt once when nothing is rolling out. You will find the clients with odd baselines, settle the thresholds, and learn how long 31 or 40 clients take, all before a client is waiting on the answer.

Limits to know before you promise a client anything

  • 100 rows per call. Query and page tools return the top 100 by clicks, so on a large site the drill-down sees the head, not the long tail.
  • Fixed date ranges. Every window ends today, and the longest reaches back 12 months. The agent cannot ask for "the nine days before the rollout began", so it brackets the rollout with whole weeks, and the note should say which weeks.
  • No query-by-page breakdown. No split by country or device either.
  • Performance data only. Manual actions, security issues and indexing stay in Search Console.
  • No alerts and no organic rank tracking. Someone on your team asks, and positions are Search Console averages, not daily checks of a keyword set.

Some agencies should use something else. With a handful of clients, opening each property by hand is quick and free. For branded monthly reports, see the AgencyAnalytics comparison. Map pack clients need the local SEO agencies page; publishers, the content site portfolio page. Tool details are on the Search Console integration page.

What heads of SEO ask before connecting a roster

Can DuckDive tell me if a client has a manual action?

No. Open the Manual actions report in the client's own Search Console before anyone mentions a penalty. The agent's part is the timing check from the Granite Ridge Chiropractic example: it can show whether a slide lines up with the rollout, not whether a reviewer at Google flagged the site.

Does DuckDive know when Google releases an update?

No, and it sends no alerts. Take the dates from the Google Search Status Dashboard and paste them into the conversation, or ask an agent that can browse to read the dashboard first.

How many clients can the agent screen in one conversation?

There is no single call that covers every site. The agent reads each client separately against data DuckDive already stored, so a 40-client screen means 40 rounds of tool calls. If it stops partway, ask it to continue from the last client it finished.

Should we pause content or link work during a rollout?

Google does not ask for a freeze. Its core updates page says to avoid "quick fix" changes and to focus on changes that make sense for users over the long term, and its traffic drops guide recommends avoiding radical changes to a page that already performs well. A workable house rule: scheduled work ships as planned, and any rewrite prompted by the drop waits until a week after Google marks the update complete.

Can the agent compare this update with the previous core update?

Only if the earlier rollout finished inside the last 12 months, the longest range the Search Console tools accept. Paste both sets of dates from the dashboard's ranking history, and the agent lines them up against the weekly points in each client's 12-month trend. For anything older, open the client's Performance report, which Google extended to 16 months of data.

Which clients should we link first if we cannot connect all 40 before the next update?

The ones most likely to score 5 or 6 on the call matrix: clients that get most of their conversions from organic search, and clients whose renewal falls within 90 days. Each linked site starts importing its history straight away, so its baseline is waiting when the update lands. The rest can follow in batches during quieter weeks.

Sources

  1. Google Search Status Dashboard, Google, checked November 16, 2026.
  2. History for Ranking, Google Search Status Dashboard, checked November 16, 2026.
  3. Google Search's core updates and your website, Google Search Central, checked November 16, 2026.
  4. About Search Console data, Search Console Help, checked November 16, 2026.
  5. Performance report (Search results): Overview and basic setup, Search Console Help, checked November 16, 2026.
  6. Debug Google Search traffic drops, Google Search Central, checked November 16, 2026.
  7. Manual actions report, Search Console Help, checked November 16, 2026.
  8. Security issues report, Search Console Help, checked November 16, 2026.
  9. Introducing the new Search Console, Google Search Central Blog, January 2018, checked November 16, 2026.

Last reviewed . Every client, page and figure inside an EXAMPLE DATA block is invented for this runbook.

Have the roster linked before the next rollout

Link every client's Search Console and GA4 once, and your next update morning starts with a scored call list instead of thirty browser tabs.

Free for 2 sites · No credit card · Working in an agent? Let it set DuckDive up