Notes on reporting

What we have learned building reports on Search Console and GA4 — the API quirks, the comparisons that mislead, and the dashboards that survive past month two.

Where the reporting week actually goes

Most SEO teams do not lose time to analysis. They lose it to assembly — exports, joins, formatting, and the same commentary written twelve times.

What the Search Console API gives you that the interface does not

The UI is built for browsing. The API is built for reporting. The difference shows up in row limits, date control, and how far back you can go in one request.

MTD vs LMTD, and the comparison most reports get wrong

Comparing a full month to a partial one is the most common error in monthly SEO reporting. Here is how to set the window so the numbers mean something.

Building a Looker Studio report people actually open

Most dashboards are abandoned within two months. The ones that survive answer a specific recurring question rather than displaying everything available.

Google Sheets automation for SEO reporting, without the Apps Script sprawl

Sheets is a good reporting surface and a bad database. Knowing which is which keeps your automation from turning into a maintenance problem.

Splitting brand and non-brand search properly

Without the split, SEO performance is hostage to whatever the brand team did last month. With a sloppy split, it is hostage to your regex.

Why Search Console and GA4 never agree

They count different events at different moments with different rules. Once you know which difference is causing which gap, the numbers stop being alarming.

Clicks fell but impressions did not. What to check.

A CTR-shaped drop has a short list of likely causes, and working through them in order is faster than staring at the graph.