Technical
How to audit technical search health in one sweep
technical-health-audit a saved expert workflow your assistant follows, in Claude, ChatGPT or Cursor
One technical sweep: Core Web Vitals, indexability, orphan pages, internal-link equity and crawl-budget waste, issues ranked by the search traffic actually at risk, not by raw counts.
Try it
technical health check
Private beta Part of the quattr-ai-search plugin, rolling out org by org. Request access ↗
Say any of these
technical audittechnical SEO healthsite health checkcore web vitals statusindexation issuesis anything technically brokenfull technical sweep
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
Not for a single metric's drop diagnosis (anomaly-investigator), for AI-crawler-specific readiness (ai-crawler-readiness), or for linking-only worklists (linking-opportunity-review).
Use it instead of anomaly-investigator when the ask is a proactive sweep, not a symptom; use ai-crawler-readiness instead when the subject is AI bots.
What it runs
site_health_cwv_checkindexation_gap_diagnosisorphan_pagesinternal_link_flowcrawl_budget_wastesearch_performancegsc_breakdown
7 governed analyses, composed and scoped for you. Named here for transparency, not because you have to ask for them.
The numbers behind it
Metrics it reads, each defined in the reference
Bot hitsCrawl depthCrawler response timeCumulative Layout ShiftIncoming internal linksIndexability flagsInteraction to Next PaintLargest Contentful PaintLighthouse category scoresOutgoing internal linksOverall page-experience verdictPerformance scoreStatus-code hitsUnique pages crawledVerified versus spoofed GooglebotVital gradeVital grade distributionWeakest vital
What it refuses to do
- Counts don't rank issues; traffic at risk does, that join is this skill's whole point.
- CWV thresholds and grades come from the verb; never invent pass/fail cutoffs beyond what it returns.
- A clean sweep on a partial feed is reported as partial.
What the answer looks like
Is anything technically broken?
Analysis plan, every step, resolved for you
- Routed to the governed workflow
technical-health-audit - Dates bound explicitly
Jul 1 to Jul 31, 2026 - 5 analyses queued in parallel
site_health_cwv_check · indexation_gap_diagnosis · orphan_pages · internal_link_flow · crawl_budget_waste - Honesty gates armed
scope echo · freshness
One real risk: 12 pages that earn clicks are blocked from indexing, issues ranked by traffic at stake, not raw counts.
- Traffic at risk
- ≈9.4K clicks/mo sum of the affected pages' current search traffic, the ranking key
- Indexation blocks
- 12 pages noindex or canonical conflicts on pages that earn clicks
- CWV
- mobile LCP 3.1s needs improvement, desktop passes
- Orphans · crawl waste
- 6 pages · 28% of fetches feeds the linking and crawl-efficiency worklists
Jul 1 to Jul 31, 2026
⚠ Observationalas of Aug 2, 2026IllustrativeOpen in Quattr ↗
Fix order: the 12 blocked pages first, they carry 71% of the traffic at risk.
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.
Want this Skill running on your own accounts? Every Quattr customer works with an AI Search Strategist who sets it up with you.