Sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and intent match, page speed / Core Web Vitals as experience, readability and scannability, clear CTAs, mobile usability, and the things that cause pogo- sticking back to Google. Use this skill when the user has decent rankings but poor CTR or poor on-page conversion, wants to improve dw
Install
npx skills add jeremybrasher/grokbot-skills --skill sxogit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/notfair/seo/sxo ~/.claude/skills/sxoPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Search Experience Optimization (SXO) You are an SXO specialist working at the seam of SEO, UX, and CRO. Your job is to optimize the entire path — win the click on the SERP, then satisfy and convert the visitor so they don't bounce back to Google. Rankings get the click; experience keeps it. > Credit: capability inspired by the open-source `claude-seo` project > (MIT, Agrici Daniel). Implementation is original to NotFair. --- ## Step 0 — Scope Collect the **target URL** and the **primary query/intent** it should serve, plus the **page goal** (lead form, purchase, call, read-through). ## Phase 0 — Preflight & data Read and follow `../shared/preamble.md`. If GSC connected, pull the page's **impressions, CTR, and average position** per query — a high-position / low-CTR query is an SXO problem at the SERP; high CTR but you suspect bounce is an SXO problem on the page. ## Phase 1 — SERP click optimization - **Title & meta** — compelling, intent-matching, benefit/number/freshness where apt; not truncated. Compare CTR vs. expected for the position. - **Rich results** — eligible for FAQ/Review/HowTo/sitelinks that increase SERP real estate and CTR? Flag missing schema (hand to `/schema-markup-generator`). - **URL & breadcrumb** display — clean and trustworthy. ## Phase 2 — Post-click experience (anti-pogo-stick) - **Above-the-fold intent match** — does the first screen immediately confirm the
Details
- Skill name
sxo- Repository
- jeremybrasher/grokbot-skills
- Path
collections/notfair/seo/sxo/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Sxo skill do?
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and intent match, page speed / Core Web Vitals as experience, readability and scannability, clear CTAs, mobile usability, and the things that cause pogo- sticking back to Google. Use this skill when the user has decent rankings but poor CTR or poor on-page conversion, wants to improve dw
How do I install the Sxo skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill sxo. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Sxo popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Upgrade
38jeremybrasher/grokbot-skills
Upgrade the NotFair plugin to the latest version. Updates the marketplace repo, installs the new version to the plugin cache, and updates installed_plugins.json. Use when asked to "upgrade notfair", "update notfair", or "get latest version". Also handles inline upgrade prompts when a skill detects UPGRADE_AVAILABLE at startup.
Setup Cms
38jeremybrasher/grokbot-skills
Connect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my CMS", "set up WordPress", "configure Strapi", "add Contentful", "connect Ghost", or "CMS setup". Also trigger if the user asks why no CMS data appears in a seo-analysis report.
Vertical Construction
38jeremybrasher/grokbot-skills
Domain knowledge for the construction vertical (contractors, field crews) so architect and pm don't spec construction products naively. Covers the vocabulary (bid vs estimate, takeoff, retainage, change order, AIA G702/G703, lien waiver, draw schedule), the non-obvious money rules that incumbents like Procore price out of reach for small contractors, what a naive build gets wrong (no assemblies, ignored retainage, ungated sub payments), and the entities that must be modelled. Applied by architect when writing ARCH-{slug}.md and by pm when writing PLAN-{slug}.md for any of the four construction
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.