Utilities

How to diagnose when a number looks off

quattr-troubleshooter a saved expert workflow your assistant follows, in Claude, ChatGPT or Cursor

First-line diagnosis when something looks wrong: "no data", "numbers don't match GSC/QWA", auth or entitlement confusion, a feed that seems stale, the tracking-gap vs data-lag vs real-change ladder, ending fixed or with a support-ready summary.

Say any of these

• no data showing
• this number looks wrong
• doesn't match Search Console
• getting an access error
• seems broken
• data is missing
• why is this empty
• I can't see my segment

You never name the skill or a tool, the assistant routes on what you asked. These are the phrasings it recognises for this one.

And when it stays out of the way

What it runs

• describe_data_sources
• get_data_freshness
• resolve_entity
• list_filter_values
• get_query_history
• explain_analysis

6 governed analyses, composed and scoped for you. Named here for transparency, not because you have to ask for them.

The numbers behind it

What it refuses to do

• Never blame the data to avoid saying "real change", and never say "real change" before rungs 1 to 5 are cleared, the ladder runs in order.
• Cross-source level-matching is a known false-alarm generator: reconciliation language is about trends and scoping, not penny-matching [E1 cluster 1].
• When unresolved, the support summary states what was ruled OUT, that is the value handed to support.

What the answer looks like

Claude ChatGPT Cursor acme.example · connected

Why is this empty?

Analysis plan, every step, resolved for you

• Routed to the governed workflowquattr-troubleshooter
• Dates bound explicitlyJul 29 to Aug 1, 2026
• 3 analyses queued in parallelget_data_freshness · describe_data_sources · get_query_history
• Honesty gates armedscope echo · freshness

Not broken, and not a tracking gap, you asked for days GSC hasn't loaded yet.

Diagnosis

data lag tracking-gap vs data-lag vs real-change ladder, rung 2

GSC loaded through

Jul 30 your range ends Aug 1

Fix

end the range at Jul 30 or wait for tonight's load

Jul 29 to Aug 1, 2026

⚠ Observationalas of Aug 1, 2026 (GSC lags 1 to 2 days)IllustrativeOpen in Quattr ↗

Still empty after the load? This becomes a support-ready summary, one click.

A simulated conversation on fictional data. Scope, freshness and the ⚠ Observational marker are attached by the same director that renders every demo here, not written by hand.