The short answer
To prove local SEO results, show each client the whole chain: map rank from Local Falcon, listing searches and actions from Yext, then organic sessions and conversions from GA4. Connect all three per client in DuckDive, ask your AI agent to screen the book for rank gains that never reached the website, and say plainly where the numbers disagree.
- A client pays for enquiries, so a top-three grid on its own does not renew a retainer.
- Strong rank with falling visits from the profile link points at the listing, not the rankings.
- DuckDive reads the latest Local Falcon scan, so keep last month's figures for the comparison.
Walkthrough: one client's slide from grid to phone
Start with the call every local agency gets. The owner of a lock and key shop says the phone went quiet a month ago. Your monthly Local Falcon report shows the shop in the top three across most of its service area. Both are true. The owner will trust the grid again only when you show where the path from rank to phone call broke.
Follow the customer's path one link at a time: search, listing, tap, booking. Each step lives in a different tool, and the example below runs the path in one agent conversation.
Brasswick's owner says the phone has been quiet for a month, but the grid looks great. Walk me from map rank to website enquiries and tell me which link broke.
searchfinds the Brasswick Lock & Key website in the accountget_local_rankingsaverage rank and top-3 share for each tracked keyword, from the latest scanget_yext_summarylisting searches and actions over the last 90 daysget_ga4_channelsorganic sessions and conversions for the last 30 and last 90 days, by channel and again by traffic sourceget_search_console_summaryclicks from regular search results over the same windows
Rank and visibility held. The break is between the listing and the visit: fewer people acted on the listing, and the tagged profile link sent about half its usual traffic. The baseline is a clean monthly average for the two months before this one: the last-90-days total minus the last 30 days, halved, so the month under review is not diluting its own comparison.
| Link in the chain | Monthly baseline | Change |
|---|---|---|
| "locksmith near me": avg rank 2.4, top-3 share 68% | latest scan | n/a |
| Yext listing searches | 6,750 | -2% |
| Yext listing actions | 370 | -20% |
| Organic sessions, source "gbp" (tagged profile link) | 330 | -52% |
| Organic sessions, source "google" | 850 | -4% |
| Organic sessions, other search engines | 170 | -3% |
| Organic total (all sources) | 1,350 | -16% |
| Organic conversions | 52 | -27% |
Search Console clicks are nearly flat, so regular results are fine, and 170 of the 210 organic sessions lost came through the profile link. People still find and see the listing; fewer act on it. Open the Business Profile next: hours, primary category, public edits, new reviews. DuckDive does not hold profile data, so that check is manual.
The answer never reads the grid point by point; that lives on the Local Falcon data source page. Nor does it explain why the map pack and the blue links parted; the map-versus-organic ranking guide owns that question. The job here is narrower: find where the client's money leaks out.
The proof chain from rank to enquiry
Google's ranking help sorts local ranking into three factors, relevance, distance and prominence, and adds that there is no way to request or pay for a better local ranking (Google Business Profile Help, checked November 2026). Distance is out of your hands, so a grid point far from the shop says more about geography than about your work. Rank alone proves little.
So report four links, in the order a customer moves through them, with the tool that reads each.
| Link | What it proves | Tool | If it breaks here |
|---|---|---|---|
| Map rank | The listing shows up near customers | get_local_rankings | Relevance or prominence work: categories, reviews, links |
| Listing activity | People see the listing and act on it | get_yext_summary | Listing content, hours, status on each publisher |
| Site sessions | Some of them visit the website | get_ga4_channels | Link tagging, landing page, tracking |
| Conversions | Visits turn into calls and forms | get_ga4_overview | Page, offer or broken key event |
Ranking factors: Tips to improve your local ranking on Google, checked November 2026.
Most clients break at one link, not four. Name it in the review before the client names a different one, usually "the SEO stopped working."
Ask your agentBefore Thursday's renewal call with Halcyon Window Cleaning, lay out its chain: average rank and top-3 share for each tracked keyword, Yext searches and actions over the last 90 days, and GA4 organic sessions and conversions. Tell me the first link where the numbers stop agreeing.
Tools it calls get_local_rankings get_yext_summary get_ga4_channels
Where Local Falcon, Yext and GA4 disagree, and why
When a strong grid sits next to falling visits, the client assumes one number is wrong. Usually neither is. They measure different things, at different moments, in different places.
- Average rank
- One average rank per tracked keyword from
get_local_rankings; the Local Falcon page - Top-3 share
- How much of the scan puts the client in the top three; Local Falcon's nearest named metric is SoLV
- Listing searches, views and actions
- What
get_yext_summary - Organic sessions
- GA4 sessions in the Organic Search channel, from
get_ga4_channels. Profile-link visits belong here as well; tagged the way the fourth reason below describes, they stay in the channel and can still be counted on their own. - Conversions
- The tool's word for GA4 key events: calls, forms or bookings the client's property counts.
Five reasons the numbers part ways
- A scan is a moment; the rest are totals. A scan records rank on the day it ran; Yext and GA4 count a whole month.
- The grid is even; demand is not. Grid points are spaced evenly, but a florist's orders may bunch up around offices and hospitals. Local Falcon's scan-report guide adds that its two rank averages converge as the scanned area shrinks, so the radius you picked moves the figures as much as your work does.
- Many actions never reach the site. Google counts a call as a click on the profile's call button, and that customer may never open the website. A client can gain calls and lose sessions in the same month; the Yext data source page works through that split in detail.
- Profile visits hide inside organic. An untagged profile link reports as google / organic, the same as a blue-link click. Tag it with source "gbp" and medium "organic" using Google's campaign URL parameters. GA4's default channel group puts any session whose medium exactly matches "organic" in Organic Search, so the client's organic total stays whole and the agent can split out "gbp" by source. Tag every client the same way, or the forty-client screen compares different things.
- Old listing metrics are not today's. Yext's April 2024 release notes say Google retired Customer Actions, Map Views, Search Views, Phone Calls and Search Queries, with Yext decommissioning them from May 15, 2024. If a long-standing client's old deck uses those names, do not set them beside current figures.
Ask your agentFor Brasswick Lock & Key, split the last 90 days of GA4 sessions and conversions by traffic source, and show me how many came in on the gbp source we tagged on the Business Profile link.
Tools it calls get_ga4_channels
Multi-location clients
Google's newer link between Business Profile and GA4 does not report by location for multi-location brands, according to DAC Group's July 2026 write-up. For a client with several branches, tag each branch's profile link with its own campaign value, or give each location its own website in DuckDive. The multi-location overview covers how brands lay that out.
Worked example: which of forty clients gained rank but not visits
One client at a time suits a renewal call, not the first Monday of the month with forty clients. For that, screen for every client whose map rank looks strong while website traffic slips. Those retainers are at risk: your report says "winning" while the owner feels the opposite.
"Pace" needs a definition before you trust the screen. A plain 90-day average includes the month you are judging, so a bad month drags its own baseline down and hides part of the drop. DuckDive's ranges are fixed, but they subtract cleanly: last 90 days minus last 30 days leaves the two months before, and half of that is a monthly baseline with no overlap. Tell the agent to use it.
Ask your agentFor every client with Local Falcon connected, list tracked keywords where top-3 share is above 50% while GA4 organic sessions in the last 30 days ran below their 90-day pace.
Tools it calls list_websites get_local_rankings get_ga4_channels get_search_console_summary
Run the rank-without-visits screen across the book. For pace, use (last 90 days minus last 30 days) divided by 2. On anything you flag, compare Search Console impressions with the same weeks a year ago so I know which drops are seasonal.
list_websitesall 40 client sites and their connected sources; 31 have Local Falconget_local_rankingstracked keywords for those 31, one call per siteget_ga4_channelsorganic sessions, last 30 and last 90 days, for the 17 sites with a keyword above 50%get_search_console_summarylast 90 days of weekly impressions and clicks for the flagged sitesget_search_console_summarylast 12 months for the same sites; its first weekly points are the same part of November a year ago
17 of your 31 Local Falcon clients have at least one keyword above 50% top-three share. Six of those ran below their organic baseline, and three by more than 10%.
| Client | Change | Read |
|---|---|---|
| Pembrook Pediatric Dentistry | -25% | Search clicks fell, impressions held |
| Brasswick Lock & Key | -16% | Organic "gbp" sessions halved |
| Halcyon Window Cleaning | -13% | Impressions down 21%, level with last November: seasonal |
| 3 other clients | within 6% | Watch |
Halcyon is demand, not delivery. Its impressions fell 21% against the recent baseline, but the latest weeks sit within 3% of the opening weeks of its 12-month series, the same part of November last year. Year on year it is flat, so the shortfall is the season, not lost ground. Brasswick is the listing problem you already traced. Pembrook needs a look today: its map rank is strong and its impressions are steady, yet clicks from regular results fell about a quarter.
The agent makes one call per client per source, against data DuckDive already imported and stored, so a forty-client pass fits in one conversation. Pembrook's pattern, map strong and blue links weak, is exactly the case the map pack versus organic guide walks through.
Find your own Pembrook before its owner does
Connect GA4 and Search Console with one Google sign-in, add Local Falcon for the clients who use it, and run the same screen on your real book.
Free for 2 sites · No credit card
The three-line note that admits disagreement
Business owners read the email preview, not a twelve-page report. Three lines fit there: map, listing, website. The third line keeps the retainer: if the website does not match the first two, say so before the owner notices.
Ask your agentWrite a three-line note for Pembrook Pediatric Dentistry's owner that connects this month's map rank, listing actions and website visits, and says plainly where they disagree.
Tools it calls get_local_rankings get_yext_summary get_ga4_overview get_ga4_channels
Draft Pembrook's three-line note for this month. Keep it plain and admit the gap.
get_local_rankingsaverage rank and top-3 share for "pediatric dentist", latest scanget_yext_summarylisting actions over the last 90 daysget_ga4_overviewsessions and conversions, last 30 days against the prior-60-day monthly baseline
| Measure | vs monthly baseline |
|---|---|
| Map: avg rank 2.1, top-3 share 71% | n/a |
| Yext listing actions | +6% |
| Website sessions | -14% |
| Appointment requests | -8% |
"1. On the map you show in Google's top three for 'pediatric dentist' across about 71% of the area we track."
"2. People acted on your listings 6% more than your recent average."
"3. Your website does not match: visits fell 14% and appointment requests 8%. More parents may be calling straight from the listing, but fewer are clicking through from regular Google results, and that is what we are fixing this week."
Line three admits the miss and gives the owner a reason to stay: you saw it first and have a plan. Check one figure by hand in the client's GA4 before sending.
Catching listing problems before rankings move
Rank is a slow signal. A listing that drops off a publisher or picks up wrong hours can cost calls for weeks before a scan shows it. Listing figures react sooner.
Ask your agentHas Yext listing status changed for Sorrel Street Florist, and did its listing searches, views and actions move over the last 30 days?
Tools it calls get_yext_summary
For a florist, actions falling while pre-holiday searches climb is a warning, not noise.
Patterns to watch, most urgent first:
- A publisher no longer shows the listing as live. Fix it before anything else; that is reach you have lost outright.
- Searches steady, actions down. People find the listing and walk away. Suspect hours, phone number, photos or a fresh bad review.
- Views down, grid unchanged. The listing may still rank but show less often, such as for fewer search terms.
- Review count stalled. Prominence includes reviews, per Google's ranking help, so a client who stopped asking will feel it later.
Ask your agentGive me Sorrel Street Florist's review count and average rating on each publisher, and tell me if one publisher has a much bigger share of one- and two-star reviews than the others.
Tools it calls get_yext_reviews
That tool returns counts and averages by publisher and star rating, with no date range and no review text. It tells you where to read, not what people wrote. The Yext data source page lists exactly what DuckDive pulls from listings and reviews.
Two scan rules that keep a forty-client screen honest
The screen sets one client's top-three share beside another's, so any difference in how they were scanned reads as a difference in your work. Choosing service keywords, spelling them consistently and holding a radius steady are covered on the Local Falcon data source page. Running a screen across many clients adds two rules of its own.
Agency rules for the cross-client screen
- Brand terms stay out of the screen. A business nearly always tops the grid for its own name. A client tracking "Halcyon window cleaning" clears 50% without any help from you, lands on the "strong rank" side, and hides a weak position on the terms that bring new customers. Track brand searches if the owner likes seeing them; just tell the agent to skip them.
- Every client is scanned on one fixed day before the report. DuckDive holds only the latest scan, so a client scanned three weeks ago and one scanned yesterday sit in the same table as if they were taken together. Schedule the scans in Local Falcon for the same weekday, a few days ahead of reporting. If one ran late, an admin can have the agent queue a fresh Local Falcon import for that client with
refresh_website_data.
Ask your agentRerun the rank-without-visits screen, but ignore any tracked keyword that contains the client's own business name. Which clients only made the "strong rank" list because of a brand keyword? Treat those as ranking problems, not listing problems.
Tools it calls list_websites get_local_rankings get_ga4_channels
Connecting a book of local clients
DuckDive imports each client's Google, Yext and Local Falcon history once and stores it per website, so the agent you already use can ask about one client or all forty. It reads what your tools collect; it does not run scans or edit listings.
-
Sign in with Google
Use the agency Google login that already has access to your clients' Analytics and Search Console. Signing in opens the account and shares whatever properties that login can reach, so there is no per-client invite step for Google data.
-
Add clients, then their websites
An agency account holds clients, and each client's website sits under it. Give a locksmith with one shop one website; give a two-branch florist with separate sites two. Then attach the matching GA4 property and Search Console site, with Ads and Local Services Ads only where that client buys them. Importing usually finishes within minutes.
-
Add Yext and Local Falcon where a client pays for them
-
Connect your agent
In your assistant, add DuckDive as a custom connector at
https://api.duckdive.ai/mcpand approve it with the same Google login. If you want the agent to add the remaining 39 client sites itself, leave the actions box ticked when you approve the connection; the box does nothing unless you sign in as an Agency Admin or Client Admin. Each assistant puts this in a different menu (Connectors, Apps or MCP) and renames it from time to time; the Claude walkthrough shows one app click by click.
Paste this into your agentSet up DuckDive for my website. Follow https://analytics.duckdive.ai/
agents.md -
Check what arrived before the first screen
A source that is still importing looks like a drop. Ask before you trust a screen.
Ask your agentWhich of my clients have both Local Falcon and Yext connected, which have only one, and is any of their sources still importing or failing?
Tools it calls
list_websitesget_sync_status
For roster-wide work beyond local, such as paid search clients, the agency overview shows the broader setup.
What the connected data leaves out
Know these limits before you build a client review on DuckDive.
- No Google Business Profile source. Listing figures arrive only through Yext; posts, photos and Q&A stay in the profile.
- No review text. Review counts and averages only, by publisher and star.
- Latest Local Falcon scan only.
get_local_rankingstakes no time range, so month-over-month grid trends stay in Local Falcon's own reports. - Preset windows only. The agent chooses among set periods, 7 days at the shortest and 12 months at the longest, so a "since the March site launch" question has to be rounded to the nearest one.
- No call tracking, CRM or booked revenue. Conversions are whatever the client's GA4 counts as key events.
If you need a branded PDF in every client's inbox on the first of the month, a white-label reporting tool fits better; the AgencyAnalytics comparison shows where each wins. DuckDive fits when you need answers across the book that no fixed report gives.
Grids, listings and proof: common objections
Does DuckDive replace Local Falcon or Yext?
No. DuckDive runs no scans and edits no listings; it reads results from the Local Falcon and Yext accounts your clients already have. Both vendors also offer their own MCP server for work inside their product: Local Falcon's connector in Claude's directory can run geo-grid scans, and Yext's June 2026 release notes announce one for Knowledge Graph, Reviews and Scout (both checked November 2026). DuckDive's role is putting their figures beside each client's GA4, Search Console, Google Ads and Local Services Ads data, so one question can cover the whole book.
Can my agent show how a client's grid changed since last month?
Not from DuckDive alone. The Local Falcon tool returns the latest scan for each tracked keyword, with no history. For the trend, use Local Falcon's own reports, or its connector, whose directory listing includes tracking visibility trends over time. To bring last month into a DuckDive answer, paste that month's average rank and top-three share into the chat and the agent will set them against the latest scan.
What do I show a client who is not on Yext?
A two-link chain: map rank, then website sessions and conversions. Keep the listing line in the note and mark it "not measured" rather than dropping it, so the owner can see the gap. If they want listing numbers, the profile's own performance screen counts call-button and website-link clicks, per Google's insights help; copy those in by hand.
What if two clients compete for the same keyword in the same town?
Each client's Local Falcon scan, Yext figures and Google data stay under its own website in DuckDive, and your agent puts them side by side only when you name both. The screen judges each on its own numbers, so one client's gain in a shared grid can be the other's loss in the same month. Read the pair together before you write either note.
Should I connect all forty clients at once?
Sources
- Tips to improve your local ranking on Google, Google Business Profile Help, checked November 16, 2026.
- How To Read a Scan Report, Local Falcon Knowledge Base, checked November 16, 2026.
- What Is SoLV? How To Interpret and Use the Metric, Local Falcon Knowledge Base, checked November 16, 2026.
- Understand your Business Profile performance & insights (how calls and directions are counted), Google Business Profile Help, checked November 16, 2026.
- URL builders: Collect campaign data with custom URLs, Google Analytics Help, checked November 16, 2026.
- Default channel group (Organic Search includes medium exactly matching "organic"), Google Analytics Help, checked November 16, 2026.
- April '24 Release Notes, Yext, checked November 16, 2026.
- June '26 Release Notes (Yext MCP server), Yext, checked November 16, 2026.
- Local Falcon connector, Claude connector directory, checked November 16, 2026.
- How the New Google Business Profile and GA4 Integration Improves Local Marketing Measurement, DAC Group, July 22, 2026, checked November 16, 2026.
Last reviewed . Every business and figure inside an EXAMPLE DATA block is invented.
