seo-sxo
SEO técnicoagricidaniel/claude-seoskills.sh ↗
Instalaciones
4010
sin duplicados, en la última sincronización
Desde que contamos
+2.8%
35 lecturas, unas 2 horas de diferencia. No es una curva en vivo.
Nuestra categoría
SEO técnico
nuestro
Última lectura
3 sept 2026
del directorio
Nuestro resumen
nuestroEsta habilidad realiza un análisis exhaustivo de Optimización de la Experiencia de Búsqueda (SXO), determinando si una página objetivo es el tipo correcto para su palabra clave prevista basándose en las páginas de resultados del motor de búsqueda (SERPs) actuales. Analiza las señales de SERP para derivar historias de usuario y puntúa la página desde múltiples perspectivas de personalidad, identificando brechas entre el contenido existente y lo que Google recompensa.
- Informe completo de análisis SXO
- Historias de usuario
- Puntuación de análisis de brechas (0-100)
- Tarjetas de puntuación de personalidad
- URL
- Palabra clave (opcional)
obligatorio
La evidencia indica que la habilidad requiere pago para taxonomía de tipo de página, precios, marco de historias de usuario y plantillas de wireframe.
no detectado
La evidencia no contiene información sobre si se requiere registro para usar esta habilidad.
No puede determinar la salud SEO técnica (como rastreabilidad o velocidad) independientemente de la puntuación de brechas SXO. También depende de obtener la URL objetivo y analizar los resultados de SERP, lo que puede fallar si la URL es inaccesible o si Google devuelve datos insuficientes.
Evidenciastatic 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
Leídos 6 de 6 archivos de texto de la skill.
Instalacióndel directorio
npx skills add https://github.com/agricidaniel/claude-seoLa instalación ocurre allí, no aquí. Somos un índice con una opinión, no un espejo.
Qué hay dentrodel directorio
5 archivos — solo nombres. El directorio no informa los tamaños.
Qué encontraron los auditoresdel directorio
Una skill son instrucciones que tu agente seguirá y scripts que puede ejecutar, así que quién la revisó importa tanto como cuánta gente la instaló.
Instalaciones, lectura a lecturanuestro
El eje empieza en 3.9k, no en cero — el rango va de 3.9k a 4k.
Preguntado en voz altahablado, no escrito
La misma habilidad en las palabras que la gente usa al hablar con un asistente, no al escribir en una caja. Cada pregunta lleva la situación de la que salió, y cada respuesta dice solo lo que respaldan los propios archivos de la habilidad.
Sí, la evidencia sugiere que se requiere pago para varios componentes centrales de la habilidad, como la taxonomía de tipo de página y la información de precios. Debe verificar los requisitos específicos antes de continuar.
Puede realizar un análisis SXO completo utilizando una palabra clave detectada automáticamente a partir de la URL o proporcionando una palabra clave específica al invocar la habilidad. La habilidad está diseñada para detectar desajustes de intención.