Search Experience Optimization (SXO), the bridge between SEO and UX/CRO. Audits the journey from the SERP click to the on-page goal: click-through factors (title, meta, rich results), then post-click signals that keep users and drive conversions: above-the-fold relevance and intent match, page speed / Core Web Vitals, readability, clear CTAs, mobile usability, and what causes pogo-sticking back to Google. Use when the user has decent rankings but poor CTR or poor on-page conversion, wants bet...
Installs into .claude/skills of the current project.
Are you the author of Sxo?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hashgraph-online-sxo)
---
name: sxo
argument-hint: "<page or site URL, e.g. https://example.com/landing>"
description: >
Search Experience Optimization (SXO), the bridge between SEO and UX/CRO. Audits
the journey from the SERP click to the on-page goal: click-through factors (title,
meta, rich results), then post-click signals that keep users and drive
conversions: above-the-fold relevance and intent match, page speed / Core Web
Vitals, readability, clear CTAs, mobile usability, and what causes pogo-sticking
back to Google. Use when the user has decent rankings but poor CTR or poor on-page
conversion, wants better dwell time / engagement, less bounce, or a page
experience aligned with search intent. Trigger on: "SXO", "search experience
optimization", "good rankings but low CTR", "high bounce rate from search",
"pogo-sticking", "improve dwell time", "SEO and conversion", "ranking but not
converting", "engagement signals", "make this page convert search traffic". For
pure landing-page conversion in ads use /google-ads-landing; for content quality
use /seo-page.
---
# Canonical NotFair workflow
Read [`../../seo/sxo/WORKFLOW.md`](../../seo/sxo/WORKFLOW.md) completely, then follow it as the active workflow. Resolve every relative reference from that file against `../../seo/sxo/`.
