For website portfolio operators

A Monday sweep across every website you run, done by your agent

You run dozens of lead-generation sites and nobody else is watching them. Here is a weekly rhythm where your AI agent checks every site, separates stale data from real drops, and hands you the short list.

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 16 min read

The short answer

If you manage analytics for multiple websites on your own, connect each site's Google data to DuckDive once. Every Monday, one prompt has your AI agent check which sites have stale data, compare last week with the week before for every site, and return only the few that fell past your threshold. Midweek you dig into those few. Later, a scheduled email can replace the prompt.

  • Check freshness before performance: a site whose data stopped arriving looks exactly like a site that crashed.
  • Judge lead sites on site conversions plus charged leads when only some of them buy Local Services Ads.
  • Name every site by trade and town, so one word pulls up a whole group.

The Monday sweep, in the order the agent runs it

Forty sites are too many to open one at a time, and most weeks nearly every site is fine while two or three are not. The sweep finds those few, with a reason attached, so your week goes to fixing instead of looking.

DuckDive stores each site's Google Analytics 4, Search Console, Google Ads and Local Services Ads history once you connect it, so your agent reads from that store instead of waiting on Google site after site. There is no portfolio button: the agent asks about each website in turn and sorts the answers, which is your manual routine minus the forty browser tabs.

  1. List the sites. list_websites returns up to 100 websites per call, with the sources linked to each.
  2. Check freshness. get_sync_status runs per site. Anything failing or days behind goes on its own list, out of the comparison.
  3. Pull two weeks per site. get_ga4_overview over the last 14 days returns sessions and conversions by day, and the agent splits that series in half. No fixed range means "the 7 days before last week" on its own, so the 14-day pull does that job.
  4. Sort and cut. Rank by change, drop sites inside your threshold, drop the tiny ones.
  5. Add a reason. One get_search_console_summary call per flagged site shows whether organic clicks and position moved too, turning "down 30%" into "lost rankings" or "traffic fine, leads gone".
Ask your agent
Run my Monday sweep: for every website, compare the last 7 days of sessions and conversions with the 7 days before and list only the ones down more than 20%.

Tools it calls list_websites get_sync_status get_ga4_overview get_search_console_summary

Set a floor

Percentages mislead on small sites: 5 form fills falling to 3 is a 40% drop that means nothing. Tell the agent to skip sites with fewer than about 10 conversions in both weeks.

Why week against week and not against last year? Monday is for breaks (a dead form, a lost ranking, lost access), which show up as a sudden step between adjacent weeks. Seasonal swings in tree work or gutter cleaning belong in a monthly look over the last 90 days or 12 months.

Catching sites whose data stopped arriving

The worst false alarm in a portfolio is a site that looks dead because its numbers stopped coming in. The quieter failure is a broken site nobody notices because its last good week is still in the report. So the sweep checks freshness first.

The freshness check is one call per site to get_sync_status. For every connected source it returns one of three states (ready, importing, failing) plus a date stamp for the newest day on file. Sort the book oldest stamp first and a concrete site whose GA4 went quiet on Thursday lands at the top before any week is compared. A failing source can mean your Google login lost access, a developer rebuilt the site under a new property, or the domain changed and the old Search Console site went with it.

Ask your agent
Which of my websites have a data source that is failing or more than three days behind?

Tools it calls list_websites get_sync_status

Two different kinds of stopped

A failing status means DuckDive cannot read the source, so the repair is access. A ready, recent status beside sessions that collapsed overnight is the opposite case: DuckDive is reading fine and Google has simply received nothing from the site. Fix that on the website itself, because no re-import can recover visits Google never recorded.

Leave room for Google's own delay

Two of the six inputs settle late. Google's GA4 freshness article (checked November 2026) gives processing a window of up to two days and warns that figures can still move inside it, and Search Console flags its most recent days as preliminary. So a tree-care site that seems to lose half of Sunday may get most of it back by midweek, which is exactly why the follow-up waits.

After the login problem behind a failing source is solved, you do not have to wait for the backfill to catch up by itself. An admin's agent can run refresh_website_data on just that site and just the broken source, pulling back any span from the last day to the last 30. DuckDive throttles it to one run per site per quarter hour, so on a 42-site book re-pull the two or three sites that failed, never the whole list. Rather than guessing when fresh numbers arrive, let the date stamp in next Monday's freshness check prove the site caught up.

Worked example: forty-two sites, three that need you this week

A fictional operator runs 42 home-service lead sites. This is what the Monday prompt above returns when one source is failing and two sites slipped.

EXAMPLE DATAFictional business: Quarry Lane Concrete, Bellhaven Tree Care, Northpass Septic

Run my Monday sweep. Same rules: 20% down, skip the tiny sites.

  1. list_websitesreturns 42 sites and the sources linked to each
  2. get_sync_statuschecks all 42; Northpass Septic's GA4 source is failing
  3. get_ga4_overviewthe other 41 sites, last 14 days, split into two weeks
  4. get_search_console_summarythe two sites that fell, same two weeks

Three of your 42 sites need you. The other 39 are within 20% of the week before on both sessions and conversions.

SiteWhy it is flaggedSessionsConversions
Quarry Lane ConcreteTraffic steady, quote requests fell from 17 to 6-4%-65%
Bellhaven Tree CareOrganic clicks down 33%, average position 4.1 to 6.8-30%-36%
Northpass SepticGA4 failing, newest data 5 days oldn/an/a

Start with Quarry Lane: sessions barely moved (388 to 371) while conversions fell by two thirds, so check the quote form, not demand. Bellhaven lost rankings (sessions 612 to 431, conversions 22 to 14), a slower fix. Northpass needs its Google access checked first.

Two more sites crossed 20% on fewer than 10 conversions a week, so I left them off as noise.

GA4 Search Console

Note what it left out: 39 healthy rows, and a frozen feed that would have ranked as a 100% drop.

Get your own three-line Monday list

Connect your sites once, and the sweep prompt runs on your real sessions, conversions and sync status.

Continue with Google

Free for 2 sites · No credit card

Wednesday follow-up on the sites you flagged

By Wednesday the weekend's data has settled and you have fixed anything obvious. The follow-up touches only the flagged sites and moves from "what fell" to "why".

Ask your agent
Take the sites you flagged on Monday. For each one, tell me which channel lost the most conversions and which landing page dropped hardest, last 7 days against the 7 before. Three lines per site, no more.

Tools it calls search get_ga4_channels get_ga4_landing_pages get_search_console_pages

If one of the agent's earlier-week figures looks off, ask it to show the arithmetic, since the channel and landing page tools hand back range totals rather than days.

Wednesday triage for a lead site

  • Visitors holding, quote requests gone. From your phone, send a test quote request and tap the call button, then ask the agent whether that site's GA4 conversions moved today. A lead site can keep its traffic and quietly lose every enquiry.
  • One service page carrying the loss. Ask for that site's landing pages, last 7 days against the 7 before. On a single-trade site, losing the main service-and-town page is most of the story.
  • LSA site, charged leads down, form fills flat. The site is fine; the change sits inside the Local Services account (budget, business hours, paused ads). DuckDive sees the counts only, so open Google's Local Services tool.
  • Paid channel down. Look in that Google Ads account for a budget cap, billing hold or paused campaign.
  • Many sites slipped together. That is a portfolio-wide cause, not a site fix; follow the multi-site drop guide.
  • Still stale. Confirm which Google login can see that property.

Write one line per site about what you changed. Next Monday, add "and tell me whether last week's flagged sites recovered" to the sweep, and the agent closes the loop for you.

Lead flow when only some sites run ads

Most of a lead-gen book lives on organic search, a few sites run Google Ads, and some trades take Local Services Ads leads. Judge them all on website conversions and the LSA sites look weaker than they are, because a lead can come straight from the ad without anyone loading the site.

For an operator, the gap between LSA leads and charged leads is the line to watch, because charged leads are what each LSA site actually costs you. Google's How leads work page (Local Services Help) bills only valid leads. As of November 2026, valid leads include a call you answer or call back, a missed call during business hours where the caller stays on past 20 seconds, a voicemail, a text or email, and a booking request (bookings in the US and Canada only). A follow-up from the same phone number or email within 15 days of the last interaction is not charged a second time.

So compare within groups. Organic-only sites: GA4 conversions are the whole story. LSA sites: add charged leads. Google Ads sites: careful, because Ads conversions are often the same form fills GA4 already counted. The spend-to-lead ledger guide sorts out which count goes where.

Ask your agent
Sort my websites into three groups: organic only, running Google Ads, and running Local Services Ads. Compare conversions for the last 30 days inside each group, never across groups.

Tools it calls list_websites get_ga4_overview get_google_ads_summary get_lsa_summary

Ask your agent
Find every gutter site in my account. Over the past 30 days, how many LSA leads did each get, how many did Google bill me for, and what did each spend?

Tools it calls search get_lsa_summary

The figures come from get_lsa_summary, which reports leads, charged leads and spend for the LSA account linked to that website, so the count is only as good as the linking.

Watch LSA closely right now: Google says Local Services Ads are moving into Google Ads as Performance Max campaigns with pay-per-lead goals, in phases from August 2026, and that LSA performance reports won't transition. If your LSA sites are in an early wave, read how to save LSA reports before the move.

Worked example: two lookalike sites, one with LSA

Two gutter sites from the same template, in towns of similar size. One takes Local Services Ads leads, the other runs on organic only, and on website numbers alone the organic one wins.

EXAMPLE DATAFictional business: Tri-County Gutter Pros and Kettle Creek Gutters

Tri-County Gutter Pros and Kettle Creek Gutters are basically the same site in two towns. Over the last 30 days, which one actually brought in more customers?

  1. searchfinds both sites by the word "gutter"
  2. get_ga4_overviewsessions and conversions for each, last 30 days
  3. get_lsa_summaryTri-County's leads, charged leads and spend; Kettle Creek has no LSA account linked

Tri-County, once LSA is counted. On the website alone Kettle Creek is ahead by 13 conversions. Add Tri-County's 39 charged leads and it brought in 77 contacts to Kettle Creek's 51.

Last 30 daysTri-CountyKettle Creek
Sessions1,1401,310
Site conversions3851
LSA leads46none
Charged leads39none
LSA spend$1,365none
Cost per charged lead$35none
Conversions plus charged leads7751

Seven of Tri-County's 46 LSA leads were not charged. Some callers may also have used the form, so treat 77 as an upper bound.

Before switching on LSA for Kettle Creek, check that Google offers it for that trade there, and that someone can answer the extra calls.

GA4 Local Services Ads

The lesson for the Monday sweep: if a site runs LSA, a fall in site conversions can be offset by charged leads, or made worse by them. Add get_lsa_summary to the sweep for those sites only, and the flag list stops punishing the sites that sell by phone.

Naming sites so the agent finds them fast

Your agent finds sites by name or address: search matches either, and list_websites takes a text filter. Name sites after their domains and "the gutter sites" becomes a guess. Start each name with trade and town and one word pulls the whole group.

  • Trade, then town, then brand. Group questions start with the trade.
  • One spelling per trade. Mix "tree" and "arborist" and half the group goes missing.
  • No ad status in names. The agent already sees which sources are linked.
  • Mark idle sites. Add "parked" and tell the sweep to skip them.
EXAMPLE DATASite names that make group questions easy
AddressName in DuckDive
tricountygutterpros.exampleGutter Springfield, Tri-County Gutter Pros
kettlecreekgutters.exampleGutter Brookfield, Kettle Creek Gutters
bellhaventree.exampleTree Bellhaven, Bellhaven Tree Care
quarrylaneconcrete.exampleConcrete Millbrook, Quarry Lane Concrete
northpassseptic.exampleSeptic Northpass, Northpass Septic (parked)

Set the name when the agent adds each site: add_website takes a name along with the address.

Ask your agent
Find every site with septic or concrete in its name, and tell me which of them still have no Search Console linked.

Tools it calls list_websites get_website

Connecting a few dozen sites in one sitting

The agent does most of the setup. Your part: one Google login that sees every site, and one click.

  1. Put every site within reach of one Google login

    As of November 2026, Google's Analytics hierarchy page allows up to 100 Analytics accounts and up to 2,000 properties in each, so neither ceiling bites at 60 sites. The limit that does bite is your own patience: keep one property per site inside one account, or a handful grouped by trade, and a single login reaches every site DuckDive needs to read. For sites someone else built, have them add your login as a user; the access guide covers who grants what.

  2. Connect your agent and sign in

    Copy the one-line prompt near the start of this page into whichever assistant you already use for the business: Claude, Cursor, Claude Code, ChatGPT on a Business or Enterprise plan, or any client that accepts remote MCP servers with an OAuth login. On the Google screen, choose the login that owns your properties, and leave "Also allow actions" on, because adding 40 sites is an action and only an admin account may take it. Can't spot where servers get added? Each app files it differently, often under a connector, plugin or app setting, and those labels move between releases. The agent self-setup page shows what the agent does next.

  3. Hand the agent your site list

    Paste your addresses and the names you want in one message. The agent adds each with add_website, links the clear matches from list_available_sources, and asks only about unclear ones. The bulk onboarding run sheet covers the snags.

  4. Link ad accounts only where they exist

    On a lead-site book, analytics plus search data is the pair every domain needs; paid accounts are the exception. If only your gutter and tree sites buy clicks or carry an LSA profile, attach ad accounts to those few and let the organic-only sites show no ad data, which is a normal shape, not a missing link. Yext listings and Local Falcon grid scans are extra connections you add per domain, and only where you already pay for those tools.

  5. Wait for the imports, then sweep

    Every new link kicks off a backfill. DuckDive puts a typical backfill at a few minutes, with properties holding years of data running longer, so use the gap to check the display names against the naming scheme above. When each row of the freshness check reads ready, run the sweep prompt that same day, even a Thursday.

A scheduled email instead of a Monday prompt

After a month of Monday prompts you know which numbers you actually read. Then a scheduled DuckDive email can carry the routine, and the agent keeps the judgement calls. The agent sets it up with create_scheduled_report:

  • How often: daily, weekly or monthly.
  • Range: the last 7 days, last 10 days, last 30 days, or all time.
  • Sources: all of them, or one of GA4, Search Console, Google Ads, Local Services Ads, Yext, or Local Falcon (the tool calls it "heatmaps").
  • Websites: up to 50 per report.
  • Recipient: always your own account email.
  • Who: an admin whose connection allowed actions.
Ask your agent
Schedule a weekly DuckDive email with the last 7 days of GA4 and Search Console for my first 50 websites, and a second one for the rest.

Tools it calls list_websites create_scheduled_report

The sources setting takes one value, so "GA4 and Search Console" comes back as all sources or one report per source; let the agent say which it chose. Over 50 sites, split by trade rather than by the order you added them, so each email reads as a comparable group. Read the first one before you retire the prompt.

Keep the Monday prompt, switch to the email, or run both?
QuestionScheduled emailMonday prompt
Arrives if you forgetYes, on its scheduleNo, you have to ask
Lists only sites past your thresholdNo, there is no threshold settingYes, you set the cut
Answers a follow-up questionNo, it is a fixed reportYes, ask in the same chat
Covers 60 sitesPartly, as two reports of up to 50Yes, one call per site
Goes to a partner or assistantNo, only your account emailNo, it stays in your chat
Needs admin rightsYes, admin with actions allowedNo, read access is enough

Sources: settings as listed in DuckDive's create_scheduled_report tool, checked November 2026.

What this weekly check will not catch

A weekly pull is a rhythm, not an alarm. Know where it stops.

  • Breaks between Mondays. DuckDive sends no alerts. A form that dies Tuesday shows up next Monday, unless a daily email on the last 7 days narrows the gap.
  • Jobs and revenue. Everything DuckDive reads is marketing data: analytics, search, ad accounts, listings and rank scans. Nothing from a call tracker, a CRM or your invoices reaches it, so the sweep stops at the lead and never learns whether the homeowner booked.
  • LSA lead detail. Leads, charged leads and spend only. Recordings, lead types and disputes stay in Google's tools.
  • Campaign-level Ads. Google Ads arrives as an account summary; keyword work stays in Google Ads.
  • Exact date windows. Ranges are fixed (7, 14, 30 or 90 days, 6 or 12 months), so "since the form change on the 9th" is read off the daily series.
  • Google Business Profile. Not a source.

It is also the wrong tool for some readers. Three sites and only GA4? Google's own reports are enough. Renting sites to local businesses and owing each tenant a branded report? A white-label reporting tool fits better. If your sites earn from display ads and affiliate links rather than leads, the content-site portfolio page is the better read, and if you own the companies rather than run the sites yourself, start with DuckDive for portfolios.

Running it solo: practical questions

Should I sweep all 42 sites in one chat, or split the sweep by trade?

Count the calls first. Each site needs a freshness check and a 14-day GA4 pull, and each flagged site adds a Search Console call, so 42 sites come to roughly 85 to 90 tool calls plus the opening site list. If the answer gets long or slow to read, run one prompt per trade name (gutter, tree, concrete, then the rest). A trade group that comes back clean needs no Wednesday follow-up at all.

Is there a cap on how many websites one account can hold?

DuckDive has not published a cap. The agent reads your site list up to 100 at a time, and each scheduled email covers up to 50 websites, so a bigger book just means more calls or reports.

Why split the week into a Monday sweep and a Wednesday follow-up?

Because Sunday is still settling on Monday morning. Google allows GA4 up to two days to process, and Search Console marks its newest days as preliminary. Monday's job is a candidate list; by Wednesday those weekend numbers have firmed up, so the digging happens on figures that will not shift under you.

Can the scheduled email go to my virtual assistant or business partner?

No. The send-to address is locked to the email on your DuckDive account, and the scheduler offers no field for a second recipient. If an assistant triages the list for you, set a mail rule on your side that forwards it to them.

Some of my sites sit under a different Google login. What then?

DuckDive lists the properties and accounts your connected Google login can reach. The simplest fix is to add your main login as a user on those properties, so one sign-in covers every site. Our access guide walks through it for each Google product.

How does the agent know which of my sites run Local Services Ads?

From what is linked. The site list your agent reads shows each website's connected sources, so it can sort sites by whether an LSA account is attached. A site whose LSA account was never linked in DuckDive will look organic-only and get judged on form fills alone, so link every LSA account to its site, even the small ones.

Sources

  1. Data freshness (Google Analytics Help): why Monday's newest GA4 day can still move. Checked November 16, 2026.
  2. Performance report (Search results): Overview and basic setup (Search Console Help): the preliminary-data note. Checked November 16, 2026.
  3. How leads work (Local Services Help): which contacts count as valid, billed leads. Checked November 16, 2026.
  4. Local Services Ads transition to Performance Max campaigns with pay-per-lead goals (Google Ads Help): migration waves and reports. Checked November 16, 2026.
  5. Google Analytics hierarchy (Google Analytics Help): the account and property ceilings. Checked November 16, 2026.

Last reviewed . Numbers in EXAMPLE DATA blocks are fictional.

Hand Monday's site check to your agent

Connect your sites once, and next Monday starts with a short list instead of forty dashboards.

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