GTM Diagnosis Company Formation Service

Rankings Held, Traffic Fell — and the Real Culprit Wasn't On the Page

A company-formation service was losing organic traffic while its rankings looked stable. AOS ran a diagnosis on fresh telemetry and returned a causal chain rather than a hygiene list — an authority deficit, triggered by the March 2026 core update, with a competitor absorbing the released demand — naming the root cause instead of the symptoms.

88% confidence

01 Ground

A company-formation service faced the most disorienting kind of SEO problem: the rankings still looked roughly where they had always been, but the traffic was draining away. When position and traffic decouple like that, the usual on-page checklist is the wrong tool — the cause isn't a missing H1 or a slow page, it's something happening in the result itself or in the competitive field around it.

The team needed to know which of the plausible villains was real. Was this an AI Overview eating the clicks above the organic results? A YMYL trust problem on a regulated, money-adjacent service? A core update reshuffling who deserves to rank? Each of those implies a completely different remediation, and guessing wrong means spending months fixing the wrong thing while the bleed continues.

  • Rankings broadly held while organic traffic fell — the decoupling that rules out a simple position-loss explanation Search Console 88% confident
  • A structural authority deficit identified as the root cause, not on-page hygiene Semrush 85% confident
  • The March 2026 core update identified as the trigger event aligning with the traffic break GA4 85% confident
  • A competitor identified as absorbing the released demand — the consequence stage of the causal chain Semrush 85% confident

02 Decide

AOS refused to hand back a hygiene list. It built a causal chain on fresh telemetry: the site carried a structural authority deficit, the March 2026 core update was the trigger that turned that latent weakness into a live loss, and a stronger competitor was the consequence — absorbing the demand the client could no longer hold. Root cause, trigger, consequence, in that order.

That framing matters because each link points to a different action. A core-update trigger plus an authority root cause says the fix is trust and authority work, not another round of meta-description polishing. By distinguishing the rankings-held-traffic-fell pattern from a plain ranking loss, the diagnosis steered the team away from the cheap, satisfying, useless fixes and toward the expensive, correct one.

What this might get wrongThe single biggest honest caveat is cost: this was an expensive diagnostic at roughly $6.61 for one run. That's the price of a deep causal diagnosis rather than a dashboard glance — defensible when the decision it informs is 'where do we spend the next quarter,' less so as a routine weekly check. The causal attribution is well-supported by corroborating telemetry but remains an inference about why, not a controlled experiment.

03 Deploy

A causal-chain diagnosis built on fresh telemetry: the rankings-held-traffic-fell pattern established first, then the authority deficit named as root cause, the March 2026 core update as trigger, and the demand-absorbing competitor as consequence.

The output is an explanation with a direction of fix attached — authority and trust work for a regulated, money-adjacent service — rather than a catalogue of on-page nits that would have left the real problem untouched.

04 Result