White-Label Local SEO Reporting: What Agencies Send Clients

An agency reselling local SEO under its own brand sends a client a monthly document covering Google Business Profile performance, Google Maps map pack positions, reviews and the work done. What separates a report that holds up from one that does not is whether its numbers can change without the client's rankings changing.

They can, and it has happened recently at scale. In mid-September 2025 Google removed the &num=100 search parameter that rank-tracking tools relied on to read the top 100 results in one request. Agencies reported clients losing hundreds to thousands of tracked keywords from their reports within days, while traffic from those terms was largely unaffected — because the lost keywords had been ranked 11–100 all along.

  SEPTEMBER 2025 — THE REPORT BROKE, NOT THE SITE
  ┌────────────────────────────┬──────────────────┐
  │ keywords in the report     │ hundreds gone    │
  │ traffic from those terms   │ largely unchanged│
  │ what actually changed      │ a URL parameter  │
  └────────────────────────────┴──────────────────┘
  clients saw the first row only

The agency who described it put the client's view exactly: in their eyes, the keywords were gone.

Nothing in that month's work caused it, and no amount of explanation after the fact undoes a chart that fell off a cliff. It is the sharpest example of a problem that is structural rather than occasional — the reason a report should be built on measurements you define, which is the same argument behind the map pack tracking gap.

What a White-Label Buyer Actually Asks For

Reporting is not a deliverable an agency chooses. It is a line item the reseller specifies before signing. One agency owner posted their full requirement list on 8 August 2026, and it is a useful template because it was written to be sent to suppliers rather than to be read as advice.

  WHAT ONE WHITE-LABEL BUYER SPECIFIED
  8 services to fulfil
    ├─ google business profile optimisation
    ├─ local citations · on-page · keyword research
    ├─ google maps and local pack optimisation
    └─ monthly reporting
  7 conditions on the partner
    ├─ proven results and case studies
    ├─ communicates quickly
    ├─ a clear fulfilment process
    ├─ can handle more clients as we grow
    ├─ comfortable working completely white-label
    ├─ competitive agency / reseller pricing
    └─ will not contact my clients directly
  r/localseo · August 2026

Two details in that list shape the report. Monthly is named as the cadence, and the fulfilment partner never speaks to the end client — which means every explanation of a number has to survive being relayed second-hand by someone who did not produce it. A report that needs a phone call to interpret is a report that will be misread.

The supply side reads the same way. A local SEO freelancer advertising for agency work on 9 August 2026 listed reporting among the things they handle behind the scenes, alongside profiles, citations and location pages.

Report What Cannot Be Silently Redefined

The September 2025 event is the cleanest available test of a report's design. Some lines in a monthly report were unaffected by it. Others collapsed.

  WHAT SURVIVES A MEASUREMENT CHANGE
  ┌────────────────────────────┬─────────────┐
  │ "we rank #4 for X"         │ fragile     │
  │ "247 keywords tracked"     │ fragile     │
  │ "grid average 12.1 → 8.4"  │ holds       │
  │ "calls from the profile"   │ holds       │
  └────────────────────────────┴─────────────┘
  anything counted by a tool can be redefined

The pattern is not that some metrics are better. It is that counts of what a tool could see are hostage to what the tool is allowed to see, while measurements of a defined thing at a defined place are not. A grid average is a measurement of your client's visibility across their service area; a keyword count is a measurement of your vendor's access.

Positions from one check have the same weakness for a different reason — covered in why one rank number lies.

What Goes In, and Why

A defensible monthly local SEO report has four sections and each one answers a question the client already has.

1. Where they are visible. A grid across the service area, compared against last month's, not a list of positions. The comparison is the content.
2. What arrived. Calls, direction requests, website clicks from the profile — the numbers that survive tooling changes because Google reports them directly.
3. Reviews. Count, rating and how recently the last few arrived. Recency is what the corpus consistently treats as the live signal.
4. What was done and what is next. The only section the client can act on, and the one most often shortest.

The cadence question resolves against that list. Sections 2 and 3 change meaningfully month to month; section 1 does not change weekly in a way worth reporting, which is the practical argument in daily vs periodic map rank tracking.

The Cost Side of the Cadence

Reporting weekly instead of monthly multiplies scan consumption by roughly 4.3, per client, for the same grid. That is the largest single lever on tooling cost in an agency, and it is set by a reporting decision rather than a tool-purchasing one — the arithmetic is in grid cost per scan.

The corpus shows both cadences in live use. One agency in a July 2026 thread runs client grids weekly and also pulls grids for prospects:

I'm using them to show clients weekly changes over time, and to pull grids for potential clients to show them where they sit vs their competitors

r/localseo, July 2026

That is a sales cost, not a reporting cost, and it is worth budgeting separately.

Our Interest, Stated

We sell a grid rank tracker. A page arguing that client reports should be built on grid measurements rather than on vendor-counted metrics is a page recommending our own product category, and you should read it as one.

The argument stands or falls on the September 2025 event rather than on our saying so: the metrics that survived it were the ones defined by a measurement, and the ones that collapsed were the ones defined by a tool's access. That would have been true whoever sold the tool.

The Line That Protects You

Put a measurement note in the report itself, every month, in the same place.

It states where positions were measured from, how many points, on what dates, and with which tool. It costs four lines. It is the difference between "our rankings dropped" and "the grid was run from the same 49 points on the same schedule, and here is what moved" — and when a vendor changes what it can see, as happened in September 2025, that note is the only thing in the document that lets you explain the change without appearing to make an excuse.

Building that measurement discipline into the audit stage rather than the reporting stage is easier, and the sequence is in how to do a local SEO audit.