mcpbeat

Sxo

nowork-studio/sxo

> Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits 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 dwell time / engagement, reduce bounce/pogo-sticking, or align a page's experience with search intent. 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.

923 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3311
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/nowork-studio/NotFair --skill sxo

The instruction itself

7 sections, as written by the author

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

visitor is in the right place for their query? Mismatch = instant back-button.

  • Core Web Vitals as experience — LCP/INP/CLS; a slow or shifting page bleeds

users regardless of content. (Cross-ref /seo-analysis for raw metrics.)

  • Scannability — headings, short paragraphs, bullets, the answer near the top

(don't bury it under 800 words of preamble).

  • Mobile usability — tap targets, font size, no intrusive interstitials.

Phase 3 — Conversion path

  • Clear primary CTA, visible without hunting, repeated appropriately.
  • Friction in the goal (long forms, unclear next step, trust gaps).
  • Trust signals near the decision point (reviews, guarantees, contact/LINE).

Phase 4 — Report

Produce: an SXO score split into SERP-click and post-click halves, the

specific fixes ordered by impact (usually: rewrite the title for CTR, fix the

above-the-fold intent match, fix the LCP element, sharpen the CTA), and the

expected signal each fix moves (CTR, dwell, conversion). Write in the user's

language.

How to use it

Copy the folder

Take nowork-studio/sxo from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.