seo-sxo
Technical SEOagricidaniel/claude-seoskills.sh ↗
Installs
4,010
deduplicated, at the last sync
Since we started
+2.8%
35 readings, about 2 hours apart. Not a live curve.
Our category
Technical SEO
ours
Last read
Sep 3, 2026
from the directory
Our brief
oursThis skill performs a comprehensive Search Experience Optimization (SXO) analysis, determining if a target page is the correct type for its intended keyword based on current search engine results pages (SERPs). It analyzes SERP signals to derive user stories and scores the page from multiple persona perspectives, identifying gaps between the existing content and what Google rewards.
- Full SXO Analysis report
- User stories
- Gap analysis score (0-100)
- Persona scoring cards
- URL
- Keyword (optional)
required
The evidence indicates that the skill requires payment for pricing, page type taxonomy, user story framework, and wireframe templates.
not detected
The evidence does not contain information about whether registration is required to use this skill.
It cannot determine technical SEO health (like crawlability or speed) independently of the SXO gap score. It also relies on fetching the target URL and analyzing SERP results, which may fail if the URL is inaccessible or if Google returns insufficient data.
Evidencestatic findingsskills/seo-sxo/references/page-type-taxonomy.md:1-67skills/seo-sxo/references/persona-scoring.md:1-68skills/seo-sxo/references/user-story-framework.md:1-73+2
[{"code":"payment","match":"pricing","path":"SKILL.md"},{"code":"payment","match":"pricing","path":"references/page-type-taxonomy.md"},{"code":"payment","match":"Pricing","path":"references/page-type-taxonomy.md"},{"code":"payment","match":"pricing","path":"references/user-story-framework.md"},{"code":"payment","match":"pricing","path":"references/wireframe-templates.md"}]# Page Type Taxonomy for SERP Classification Classify every page -- both the target URL and each SERP result -- into exactly one of these 8 types. When signals overlap, choose the type with the strongest primary signal match. --- ## 1. Landing Page **Primary signals:** hero section with single value proposition, prominent CTA (sign up / get started / book demo), pricing section or pricing link, testimonials or social proof badges, minimal navigation (reduced header links). **SERP indicators (top 10):** branded queries, high ad density at top, sitelinks pointing to /pricing or /features, title tags with "| Product Name". **Content structure:** Hero > Social proof > Features (3-5) > How it works > Pricing > CTA repeat > FAQ. **Required elements:** Primary CTA above fold, trust badges, at least one testimonial, WebSite or SoftwareApplication schema. **Common mismatches:** - Blog Post targeting landing-page keywords (severity: CRITICAL) - Service Page missing CTA focus (severity: HIGH) --- ## 2. Blog Post **Primary signals:** author byline, publish date, article body > 800 words, comment section or social share buttons, breadcrumb with /blog/ segment, related posts section.
# Persona-Based Scoring Methodology Score the target page from the perspective of each derived persona. This reveals which audience segments the page serves well and which it fails. --- ## Persona Derivation Derive 4-7 personas from SERP intent signals. Do not invent personas without evidence -- every persona must trace back to a signal cluster. ### Sources for Persona Derivation | Source | What It Reveals | Example Persona | |--------|----------------|-----------------| | PAA question cluster | Knowledge gaps by audience | Beginner, Technical Evaluator | | Ad copy segments | Commercial audience targets | Budget Buyer, Enterprise Buyer | | Related search themes | Journey stage groups | Researcher, Comparison Shopper | | SERP result types | Content consumption preferences | Visual Learner, Data-Driven Analyst | | Featured snippet format | Expected answer style | Quick-Answer Seeker | ### Persona Card Format For each persona, document: ``` **[Persona Name]** -- [one-line description] - Role: [job title or situation] - Goal: [what they want to accomplish] - Emotional state: [from user-story-framework.md] - Journey stage: Awareness | Consideration | Decision - Key questions: [
# User Story Framework: SERP Signals to User Intent
Derive user stories from observable SERP signals. Every story must cite the
specific signal that generated it -- no guessing.
---
## Signal Sources
### 1. People Also Ask (PAA)
PAA questions reveal **knowledge gaps and concerns** the searcher has.
- Cluster PAA by theme: definitional ("what is"), procedural ("how to"),
evaluative ("is X worth it"), comparative ("X vs Y"), risk ("is X safe")
- Each cluster maps to a distinct persona or journey stage
- Definitional PAA = awareness stage, evaluative PAA = consideration,
comparative PAA = decision stage
### 2. Ad Copy
Ads reveal **commercial triggers and objection handling** that convert.
- Extract recurring themes across all visible ads (top + bottom)
- Common patterns: free trial emphasis (barrier: commitment), trusted-by counts
(barrier: trust), price anchoring (barrier: cost), speed claims (barrier: time)
- If no ads appear, the keyword is likely informational -- commercial intent is low
### 3. Related Searches
Related searches reveal the **search journey** -- what comes before and after.
- Searches with added qualifiers (+ "for beginners", + "pricing") = narrowi# Wireframe Templates: IST/SOLL Patterns Generate before (IST) and after (SOLL) wireframes showing what the page currently looks like vs what it should look like based on SERP expectations. ## Core Principles 1. **Ultra-concrete placeholders**: Not "add CTA" but "add pricing CTA with annual savings badge below hero, linking to /pricing#enterprise" 2. **Mobile-first**: Assume 375px viewport first; above-the-fold (~600px) must contain the most critical element for the page type 3. **Semantic HTML**: Output as section outline with HTML5 elements ## IST Generation Parse the current page and map to this structure: ``` IST: [URL] ├── ABOVE FOLD │ ├── [element]: "[actual content]" │ └── [element]: "[actual content]" ├── MAIN CONTENT │ ├── [section]: "[summary]" (~XXX words) │ └── [section]: "[summary]" (~XXX words) ├── SUPPORTING │ └── [element]: "[description]" └── FOOTER — [elements present] Missing from SERP expectations: - [element]: [why it matters] ``` ## SOLL Templates by Page Type ### 1. Landing Page ``` <header> Nav: logo + 3-4 links max + primary CTA button </header> <section class="hero"> H1: [value proposition matching target keyword] Subhead: [su
--- name: seo-sxo description: > Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe". user-invocable: true argument-hint: "<url> [keyword]" license: MIT metadata: author: AgriciDaniel original_author: "Florian Schmitz (Pro Hub Challenge)" version: "2.2.5" category: seo --- # Search Experience Optimization (SXO) SXO bridges the gap between SEO (what Google rewards) and UX (what users need). Traditional SEO audits check technical health. SXO asks: "Does this page deserve to rank for this keyword based on what Google is actually rewarding in the SERP?" ## Core Insight A page can score 95/100 on technical SEO and still fail to rank because it is the **wrong page type** for the keyword. If Google shows 8 product pages and 2 comparison pages for y
Read 6 of 6 text files in the skill.
Installfrom the directory
npx skills add https://github.com/agricidaniel/claude-seoInstalling happens there, not here. We are an index with an opinion, not a mirror.
What is inside itfrom the directory
5 files — names only. The directory does not report sizes.
What the auditors foundfrom the directory
A skill is instructions your agent will follow and scripts it may run, so who checked it matters as much as how many people installed it.
Installs, reading by readingours
Axis starts at 3.9k, not zero — the range is 3.9k to 4k.
Asked out loudspoken, not typed
The same skill in the words people use speaking to an assistant rather than typing into a box. Each one carries the situation it came from, and each answer says only what the skill's own files support.
Yes, the evidence suggests that payment is required for several core components of the skill, such as the page type taxonomy and pricing information. You should check the specific requirements before proceeding.
You can run a full SXO analysis using either an auto-detected keyword from the URL or by providing a specific keyword when invoking the skill. The skill is designed to detect intent mismatches.