AAAC/organic investigation

Investigation dossier · AAAC Wildlife Removal · 2026-08-14

The calls stopped.
The traffic charts lied about why.

A franchisee complaint about falling call volume, five investigation rounds, roughly twelve research agents — and a working model that looks very little like the first verdict. This site walks the whole journey, corrections included.

§ 0 — The complaint

What was reported

AAAC Wildlife Removal runs ~39 city-subdomain WordPress sites. The Treasure Coast (FL) franchisee reported call volume down year-over-year; Dallas had complained similarly since ~June. The obvious suspect — the June 2026 Google spam update hitting a mass-published blog corpus — turned out to be only a fraction of the story.

Tooling: GA4 + Search Console APIs (GA4 properties 390349966 TC, 459755935 Dallas), live-site HTML/REST inspection, Google status dashboard + industry reporting.

§ 1 — The single most important finding

TC: organic sessions ~20× higher Jan–May 2026 vs 2025 · organic calls in the same months

≈ 0 incremental calls

TC organic sessions ran 378–562/mo (Jan–May 2025) vs 4.8k–9.4k/mo (2026). Organic calls in those same months: 19/12/21/18/24 → 26/17/21/26/28 — unchanged. The PAA blog bubble produced roughly zero incremental phone calls, so losing it should cost roughly zero calls. The calls live somewhere else entirely.

Source: GA4 property-level pull, TC property 390349966 (Round 3 seasonality audit).

§ 2 — Headline numbers, as corrected

What we first reported vs. what held up

The investigation revised its own numbers as controls improved — the struck values are our earlier claims, not someone else's.

Network clicks/day, spring window → summer window (35 GSC properties)
−22.5%−9.5%
2026-specific decline after seasonal adjustment; 61–74% of the raw drop was normal summer seasonality (2024 baseline).
TC June organic call events, year over year
−80%−28%
The −80% compared against a one-year bubble artifact (Jun 2025 = 63). Against the 2024 matched window: −28%. Total TC call events hit an all-time high (111, Jul 2026) on paid events.
The only discrete 2026 algorithm event
Jun 11–25
Worth ~−15 to −25%, disproportionately blog. Worst 7-day/7-day decline −20.9% (Jun 20). The earlier "May 17–18 step" does not exist — the network peaked May 26.
TC commercial organic sessions, summer 2026 vs summer 2024
−65%
841 → 295 Google-organic commercial sessions. Real, non-seasonal, and masked in every aggregate view. This is the number that rings the phone.
§ 3 — The working model

Four things happened at once

Layer 1 · algorithm

A modest June event, not a catastrophe

One discrete 2026 event, Jun 11–25, worth ~−15 to −25% of clicks, blog-skewed. The Jun 24–26 spam update landed after the drops began. Blog-light sites actually beat 2024 seasonality (+8%); blog-heavy sites sit −24 to −38% below their 2024 norms.

Layer 2 · bubble + season

Mean-reversion of a content bubble, plus normal summer

TC published 141 PAA question posts Jun 23–Sep 11 2025; Dallas published 310 (Apr 24–Sep 26 2025). That bubble made 2025 useless as a baseline. Summer normally runs ~25% below spring (2024 median ratio 0.75); 2026's ratio (0.72) is within 4% of the 2024 norm at the median site.

Layer 3 · commercial weakness

Commercial visibility was always negligible — and got worse

TC commercial organic peaked at ~1.7 clicks/day; Dallas at ~2–5/day, with "wildlife removal dallas" on page 2 since Nov 2025. TC is a region-brand with a Palm Bay pin and a triplicate-NAP Florida cluster; Dallas is a thin Fort-Worth-cloned site sitting on the network's largest commercial demand pool (50.9k unconverted impressions).

Layer 4 · measurement

The instruments were broken too

Dallas's Bing UET snippet rewrites every tel: link to href="#" — GA call tracking dead since Oct 23 2024. Five more sites collect no usable analytics. On TC, untagged Microsoft Ads traffic masqueraded as "yahoo / organic," and paid call events now mask the organic decline.

Transferring or reworking the PAA content is unlikely to restore calls — it never drove them. Calls live on service-area pages (1 call per ~9 sessions) and in the local pack, not the blog (1 per ~1,650).
§ 4 — Read the full findings

Site map

02

The learning journey

Five rounds: initial verdict → hit map & entity audits → the seasonality corrections → call decomposition → Bing misclassification & the Fort Pierce check. What was confirmed, revised, and retracted.

Follow the rounds → 03

The traffic story

The PAA publishing bubble, the network hit map, the seasonality baseline that changed the verdict, and the Jun 11–25 event.

See the data → 04

Calls & conversion economics

TC's flat-looking call aggregate decomposed: a Yahoo artifact, a −65% commercial decline underneath, the Dallas tel-link hijack, and the network's measurement blind spots.

Decompose the calls → 05

Entity & cluster findings

The Treasure Coast region-brand problem, the Florida shared-NAP doorway cluster, the Dallas thin-clone finding — and why Fort Pierce dedup is a fragility fix, not the cause.

Map the entities → 06

Priorities & open questions

The data-ranked action stack, the one contradiction still open, the remaining data gaps — and the methods & caveats behind every number on this site.

What to do next →