The short answer
Give each roofing branch its own DuckDive website with Search Console, Local Services Ads and Google Ads linked. When a storm hits, your AI agent reads every branch against that branch's pre-storm pace, so you see where storm searches jumped, what a charged lead now costs at each branch, and which branch you cut too far to pay for the surge.
- A hurricane gives you days to freeze baselines. Hail gives you the next morning.
- Refresh a hit branch with one all-sources call, then read it.
- Check the branch the storm missed on day 7, and Google Ads conversions after day 8.
Before landfall, or the morning after hail
Most roofing marketing analytics runs on a monthly cycle: a report in the first week that tells you how the season went. A storm will not wait for it. Within a week of hail crossing two service areas, you decide which branches get more Local Services Ads and Google Ads money and which can spare some. That takes a daily read of each branch against its own normal, on the clock below.
DuckDive keeps each branch website's Search Console, Local Services Ads, Google Ads and Google Analytics history and hands it to the AI agent you already use: Claude, ChatGPT, Cursor or another agent that supports remote MCP. One question covers all your branches, and the agent does the arithmetic. It cannot move a budget or read a radar, but it replaces the round of logins on the morning after.
Hurricanes: three days out to landfall
The National Hurricane Center's track forecast cone plots the expected path out to 120 hours. Its glossary says a hurricane watch is issued 48 hours before tropical-storm-force winds are expected, and a hurricane warning 36 hours before; it puts the Atlantic season at June 1 to November 30 (as of November 2026). Hail never gives that notice. Spend it on four jobs:
- Freeze each coastal branch's baseline while its last 14 and 90 days are storm-free.
- Write down budgets: each branch's LSA weekly budget and Google Ads daily budgets. DuckDive does not see budgets, and day 14 needs a number to return to.
- Load the wind and water words: "shingles blown off", "roof tarp", "roof leak", "tree on roof".
- Plan the refreshes: who runs them during the storm, and which branch goes first.
Ask your agentA hurricane watch covers the coast near two of our branches. Before landfall, list each branch's search clicks, LSA leads, charged leads and spend, plus Google Ads spend and conversions, for the last 14 and 90 days, as a table I can paste into our storm log.
Tools it calls list_websites get_search_console_summary get_lsa_summary get_google_ads_summary
Hail: day 0 is the next morning
For hail, the first public record is the Storm Prediction Center's Today's Storm Reports: the day's hail, wind and tornado reports, each downloadable as a CSV, all marked preliminary. The National Weather Service calls a thunderstorm severe at hail one inch across or larger, or winds of 58 mph or more. Mark which branches' service areas sit under the reports, then freeze a baseline before anyone touches a budget.
Ask your agentHail hit last night. Before we move a dollar, give me each branch's daily pace over the last 90 days for search clicks, LSA charged leads and Google Ads conversions, one line per branch.
Tools it calls list_websites get_search_console_summary get_lsa_summary get_google_ads_summary
What you still do outside DuckDive in storm week
Hail swaths come from the weather service or a hail-mapping tool; DuckDive has no weather data or alerts. Budgets change inside LSA and Google Ads. The LSA inbox keeps each caller's details, your job software keeps inspections and claims, and Google Ads arrives as one total per linked account.
Days 1 and 2: reading storm demand in Search Console
Search Console shows which branch sites are drawing storm searches, in which words, and how far above normal. It is not the first signal; phones react the same evening, while Google's newest search day is still settling. Its value is scale and wording, branch by branch.
Your agent reads get_search_console_keywords (a branch's top 100 queries by clicks) for the last 7 and 30 days and keeps those containing your storm words. The 30 include the 7, so it subtracts, divides the rest by 23 for the earlier daily pace, and compares that with the 7-day count over 7.
Ask your agentRefresh the last 3 days of Search Console and LSA data for our Plainsview branch, then compare clicks for queries containing 'hail' or 'storm damage' in the last 7 days with the last 30.
Tools it calls refresh_website_data get_sync_status get_search_console_keywords
A refresh takes one source or all, and a site accepts one call every 15 minutes, so the agent should run a single all-sources refresh for Plainsview rather than two calls.
Refresh rules that shape the first 48 hours
refresh_website_data re-imports the last 1 to 30 days (default 7) for one branch site. Only an Agency Admin or Client Admin, connected with "Also allow actions" kept on, can run it. Three days covers a fresh storm; thirty suits the end of a surge, once delayed Google Ads conversions have posted (see the conversion-delay source). Before quoting a number to the owner, have the agent call get_sync_status to see whether each source is ready, still importing or failing.
The newest day moves
Google's Search Console performance report help says the newest data can be preliminary and might change over the next few hours. Treat the first morning as a direction and read it again after an afternoon refresh.
Reuse one saved word list per hazard every storm, so this week compares cleanly with last spring: "hail damage roof", "dents" and "roof inspection" for hail, plus the wind and water list above.
Hail went through last Tuesday night. Which of our four branches are getting storm searches, and how big is it against their normal?
list_websitesfinds the four Gablestone branch websitesrefresh_website_dataqueues an all-sources re-import of the last 3 days on Plainsview, then on Cedar Bluffget_sync_statusconfirms both re-imports finishedget_search_console_keywordseach branch, last 7 and last 30 days, keeping queries with hail, storm, leak or inspectionget_search_console_summaryeach branch's total clicks for the same windows
Plainsview and Cedar Bluff took the storm. Storm-query clicks per day there run about 15 and 12 times their pace from the 23 days before. Mesquite Flats sits on the edge. Harlow Junction did not see it.
| Branch | Before | Last 7d | Multiple |
|---|---|---|---|
| Plainsview | 10.0 | 148.0 | 14.9x |
| Cedar Bluff | 7.0 | 82.0 | 11.7x |
| Mesquite Flats | 6.0 | 14.0 | 2.3x |
| Harlow Junction | 6.0 | 5.9 | 1.0x |
Working for Plainsview: 1,265 storm-query clicks in 30 days, 1,036 of them in the last 7. That leaves 229 over the earlier 23 days, or 10.0 a day, against 148.0 a day now.
Mesquite Flats more than doubled, but from a small base: 8 extra storm clicks a day, mostly "roof inspection". That supports a modest raise, not a Plainsview-sized one.
A multiple shows where demand moved, not whether crews can meet it, so check the production schedule first.
Read the trust searches on day 2 too. The FTC's advice on avoiding scams after weather emergencies warns that unlicensed contractors and scammers often show up in recovery zones, and tells homeowners to check a contractor's license and insurance. Ask your agent which branches' top queries carry licensed, insured or reviews.
Size your next storm by branch, not by gut feel
Link one branch site free, then ask which storm searches jumped this week and how far above its own normal they sit.
Free for 2 sites · No credit card
Days 2 to 4: moving LSA and Google Ads money
If your branches run Local Services Ads, storm calls often show up there. get_lsa_summary gives three figures per branch account (leads, charged leads, spend), defined on our Local Services Ads data page. Here is what a surge changes.
- The monthly max burns early. Google's How leads work page sets the LSA monthly max at your average weekly budget times the average weeks in a month, and says that once you reach it your ad won't appear for the rest of the month unless you adjust the budget. A hit branch can vanish from the storm towns just as inspections peak.
- The lead mix shifts. Google adds there that lead prices may vary with location, job type, type of lead and bidding mode. Storm week tilts hit branches toward inspection and repair jobs, so prices move with no change on your side.
- Google Ads stretches a daily budget. A campaign might spend up to twice its average daily budget on a busy day, within 30.4 times that figure for the month.
- A new state means screening. Google's US screening requirements list roofing with general liability insurance and state-level business and owner licenses where local law requires them, for select users. Check before sending LSA into a market with no branch.
You make the changes in Google. A day or two later, the agent reads what each one did to that branch's charged leads and Ads conversions.
Days 5 to 7: pricing charged leads, and the branch the storm missed
By day 5 each hit branch has enough charged leads to price.
Ask your agentCompare LSA leads, charged leads and spend for all four branches over the last 14 days against their 90-day pace, and tell me where cost per charged lead rose.
Tools it calls list_websites get_lsa_summary
The 90 days already contain the storm, so the agent takes the 76 days before the last 14 and scales them to a 14-day pace.
| Branch | Cost before | Cost now | Change |
|---|---|---|---|
| Plainsview | $63.43 | $78.40 | +24% |
| Cedar Bluff | $49.91 | $64.70 | +30% |
| Mesquite Flats | $52.93 | $57.10 | +8% |
| Harlow Junction | $50.59 | $52.00 | +3% |
Earlier 14-day pace, in table order: 12.9, 9.8, 10.3 and 10.7 charged leads. Cedar Bluff's cost rose most, by 30%, but those calls are storm inspections, the work you want. The same rise at an untouched branch would need a closer look.
Day 7: the branch outside the storm path
The branch the storm missed still has leaking skylights and replacement quotes. Cut it to fund the hit markets, and a month later its pipeline is thin and nobody remembers why.
We pulled money out of Harlow Junction last week to feed Plainsview. Is Harlow just having a slow spell, or did we starve it?
searchfinds the Harlow Junction website and its idget_search_console_summaryclicks for the last 14 and last 90 daysget_ga4_overviewsessions and conversions for the same windowsget_lsa_summaryleads, charged leads and spend, last 14 and last 90 daysget_google_ads_summaryspend and conversions, last 7 and last 30 days, since the cut was a week ago
Demand at Harlow Junction is normal. Its paid lead flow fell because its budgets fell.
| Signal | Before | Now |
|---|---|---|
| Search clicks/day, 14d | 82.9 | 82.0 |
| Conversions/day, 14d | 2.17 | 2.21 |
| LSA charged, 14d | 10.7 | 8 |
| LSA spend, 14d | $540 | $416 |
| Ads spend, 7d | $557 | $310 |
| Ads conversions, 7d | 7.0 | 4 |
Search clicks and site conversions held. Cost per charged lead went from $50.59 to $52.00, so the LSA account is healthy, just funded less.
The deepest cut was Google Ads. If Harlow's crews have open days, restore that budget first, and expect the 4 conversions to rise a little as delayed ones post.
The pattern to fear is the reverse: search clicks at the quiet branch falling while its budgets stay put. That points to a ranking, site or tracking problem the surge is hiding. Our guide to finding which locations lost calls walks through ruling those out.
Days 8 to 14: settling Ads results and stepping budgets down
Google's page on conversion delay estimates says conversions are reported by impression date and that the lag can make cost per action look higher than it really is. So wait until storm week has filled in, refresh Google Ads for the last 14 days, then ask:
Ask your agentWhich branch's Google Ads conversions grew least during the storm week even though its spend went up?
Tools it calls list_websites get_google_ads_summary
The usual answer is an edge branch where spend rose on a hunch and the damage was light. It splits by branch only when each branch has its own Ads account. For Ads cost beside LSA charged leads, see building an ad spend versus leads ledger.
From day 11, step money back: when a hit branch's storm-query clicks sit within about a fifth of its day-0 pace on two refreshes in a row, return its budgets to the figures you wrote down.
Ask your agentFor each branch we raised after the hail, compare the last 7 days of storm-query clicks with the pace we logged on day 0. Which are back within 20%?
Tools it calls list_websites get_search_console_keywords
Close the storm with a log entry: hazard, branches hit, peak multiple, peak cost per charged lead, budgets moved. NOAA's Storm Events Database, the official record of National Weather Service storm data, holds January 1950 to July 2026 as of November 2026. It lags by months: good for next season's plan, not this week's.
Before hail season
A multiple is only as honest as the normal beneath it, and a roofer has two: the off-season floor from the calmest weeks, and the pre-storm pace, which in spring already includes the season.
Storm calendars differ by state. The Insurance Information Institute's hail facts page, citing the Storm Prediction Center, counts 5,432 hail events in 2025, and its table of major hail events (hailstones one inch or larger) puts Texas at 902 that year, Kansas at 375 and Oklahoma at 369. So each branch needs its own floor.
Ask your agentUsing the weekly Search Console points for the last 12 months, find each branch's 12 slowest weeks and give me its average clicks per day across them. That's our off-season floor.
Tools it calls list_websites get_search_console_summary
DuckDive imports up to 2 years of history and stores it, but the agent's longest window is the last 12 months, so each floor comes from one year. Save the answer in your storm log.
| Branch | Floor | Pre-storm | Hail week |
|---|---|---|---|
| Plainsview | 54 | 92 | 236 |
| Cedar Bluff | 41 | 70 | 139 |
| Mesquite Flats | 47 | 64 | 71 |
| Harlow Junction | 63 | 83 | 81 |
Mesquite Flats' total clicks sit about 50% above its off-season floor but only 11% above its pre-storm pace, so most of its lift is the season. Its storm queries did more than double (the day 2 table), yet they are a small slice of the total: a reason for a modest raise, not a big one.
- Storm-query clicks
- Search Console clicks on a branch's top queries that contain your saved storm words. Limited to the top 100 queries per window.
- Pre-storm pace
- The longer window minus the shorter one, divided by the days left. Without that subtraction, the storm leaks into its own baseline.
- Off-season floor
- A branch's average clicks per day across its slowest weeks in the last year.
Connect in a calm month; each linked source starts a history import that usually takes a few minutes.
Ready for the first spring storm
- A website per branch. DuckDive organises data by website, so each branch you compare is its own site, ideally with its own LSA and Ads accounts. One domain with branch folders is one website.
- Sources attached. After Google sign-in, attach each branch site's GA4 property and Search Console site, and its Ads and LSA accounts where that branch advertises.
- Agent connected. Add
https://api.duckdive.ai/mcpto your agent as a remote MCP server; no API key. ChatGPT needs Business or Enterprise. - A storm admin named. The person who will refresh in storm week holds an admin role with actions allowed.
- Floors and budgets recorded. Each branch's off-season floor, LSA weekly budget and monthly max, saved in the storm log.
- Word lists saved. Hail, wind and water, and insurance-claim wording.
- Trust details visible. License and insurance in plain view on every branch site.
- LSA history exported. Google's transition page names roofing in the US first phase of the move from LSA to Performance Max pay-per-lead campaigns, starting August 2026, and says LSA performance reports won't transition. See saving Local Services Ads history.
Your agent can do the connecting itself from the line below; click Continue with Google once when asked. See also our Claude connection page, and the multi-location overview for brands organised by location rather than storm market.
Paste this into your agentSet up DuckDive for my website. Follow https://analytics.duckdive.ai/agents.md
Hurricane, hail and crew-capacity questions
A hurricane gives us days of warning and hail gives us none. Should the runbook differ?
Only at the start. For a hurricane, use the forecast lead time to freeze each coastal branch's baseline, note its budgets and agree who runs refreshes before landfall. For hail, all of that happens the next morning, from the Storm Prediction Center's reports. From day 1 both follow the same clock, with wind and water words in place of hail words.
We want to chase a storm into a state where we have no branch. What should we check first?
Two things. Google's US screening rules for roofing in Local Services Ads call for general liability insurance and, where local law requires them, state-level licenses, so expect paperwork before ads run. And a site launched that week has no pre-storm history in DuckDive, so compare it with your nearest branch instead.
Our crews are booked weeks out. Should we cap ads at the hit branch?
That is a crew decision first. The data adds two things: whether the branch's cost per charged lead has climbed above its pre-storm pace, and how close its LSA spend sits to the monthly max you recorded. Leads you cannot inspect for weeks still cost money. You change caps inside LSA and Google Ads; your agent shows what each change did over the following days.
Homeowners search with insurance words like claim and adjuster. Do those count as storm demand?
Keep them on their own list. A query such as "hail damage insurance claim roof" comes from a homeowner already talking to an insurer, and it behaves differently from a plain damage search. Ask your agent to report the two lists side by side for each branch, so a jump in claim wording neither inflates nor hides the damage multiple you use for budgets.
We run one Google Ads account with a campaign per branch. Does that work?
For storm week, only as one total. get_google_ads_summary reads a whole linked account, so it cannot tell one branch's campaign from another's inside it. If you want the day-8 spend and conversion question answered per branch, each branch needs its own Ads account linked to its own website. Otherwise read campaign results in Google Ads.
Sources
- Definition of the NHC Track Forecast Cone, NOAA National Hurricane Center, last checked November 16, 2026.
- Glossary of NHC Terms (hurricane watch, hurricane warning, hurricane season), NOAA National Hurricane Center, last checked November 16, 2026.
- Today's Storm Reports, NOAA/NWS Storm Prediction Center, last checked November 16, 2026.
- What Constitutes a Severe Thunderstorm?, National Weather Service Birmingham, last checked November 16, 2026.
- Performance report (Search results): Overview and basic setup, Search Console Help, last checked November 16, 2026.
- How To Avoid Scams After Weather Emergencies and Natural Disasters, Federal Trade Commission, last checked November 16, 2026.
- How leads work, Local Services Help, last checked November 16, 2026.
- About overdelivery and your average daily budget, Google Ads Help, last checked November 16, 2026.
- Business screening and verification requirements, United States, Local Services Help, last checked November 16, 2026.
- About conversion delay estimates, Google Ads Help, last checked November 16, 2026.
- Storm Events Database, NOAA National Centers for Environmental Information, last checked November 16, 2026.
- Facts + Statistics: Hail, Insurance Information Institute, last checked November 16, 2026.
- Local Services Ads transition to Performance Max campaigns with pay-per-lead goals, Google Ads Help, last checked November 16, 2026.
Last reviewed . Numbers in EXAMPLE DATA blocks are fictional.
