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 your keyword, your blog post will never break through -- no matter how
well-optimized it is.
Commands
| Command |
Purpose |
/seo sxo <url> |
Full SXO analysis (auto-detect keyword from page) |
/seo sxo <url> <keyword> |
Full SXO analysis for a specific keyword |
/seo sxo wireframe <url> |
Generate IST/SOLL wireframe with concrete placeholders |
/seo sxo personas <url> |
Persona-only scoring (skip SERP analysis) |
Execution Pipeline
Step 1: Target Acquisition
- Fetch the target URL via
claude-seo run render_page.py <URL> --mode auto (SPA-aware and SSRF-safe)
- Parse with
claude-seo run parse_html.py <URL> to extract: title, H1, meta description,
headings hierarchy, word count, schema markup, CTAs, media elements
- If no keyword provided, extract primary keyword from title tag + H1 overlap
- Validate keyword is non-empty before proceeding
Step 2: SERP Backwards Analysis
Read references/page-type-taxonomy.md for classification rules.
- Search Google for the target keyword (WebSearch)
- For each of the top 10 organic results, record:
- URL and domain authority tier (brand / niche authority / unknown)
- Page type (classify using taxonomy)
- Content format (long-form, listicle, how-to, comparison, tool, video)
- Word count estimate (from snippet length and page structure)
- Schema types present (from currently supported SERP features; exclude FAQ/HowTo)
- Media signals (video carousel, image pack, thumbnail presence)
- Record SERP features present:
- Featured snippet (paragraph / list / table / video)
- People Also Ask (extract all visible questions)
- Ads (top and bottom -- count and analyze ad copy themes)
- Related searches (extract all)
- Knowledge panel / local pack / shopping results
- AI Overview presence and source types
- Calculate SERP consensus:
- Dominant page type (>60% = strong consensus, 40-60% = mixed, <40% = fragmented)
- Content depth expectations (average word count tier)
- Schema expectation (most common structured data types)
- Media expectations (video required? images critical?)
Step 3: Page-Type Mismatch Detection
This is the core SXO insight. Compare target page type against SERP consensus.
Mismatch severity levels:
| Target Type |
SERP Expects |
Severity |
Recommendation |
| Blog Post |
Product Pages |
CRITICAL |
Create dedicated product page |
| Blog Post |
Comparison |
HIGH |
Restructure as comparison with matrix |
| Product |
Informational |
HIGH |
Add educational content layer |
| Landing Page |
Tool/Calculator |
HIGH |
Build interactive tool component |
| Service Page |
Local Results |
MEDIUM |
Add location signals + local schema |
| Any type match |
- |
ALIGNED |
Focus on content depth and UX |
Classification rules:
- Classify target page using
references/page-type-taxonomy.md
- Classify each SERP result using the same taxonomy
- Flag mismatch if target type differs from SERP dominant type
- If SERP is fragmented (no dominant type), note opportunity for differentiation
Step 4: User Story Derivation
Read references/user-story-framework.md for the full framework.
From SERP signals, derive user stories:
- PAA questions reveal knowledge gaps and concerns
- Ad copy themes reveal commercial triggers and value propositions
- Related searches reveal the search journey (what comes before/after)
- Featured snippet format reveals the expected answer structure
- AI Overview reveals what Google considers the definitive answer
For each signal cluster, generate a user story:
As a [persona derived from signal],
I want to [goal derived from query intent],
because [emotional driver from ad copy / PAA tone],
but I'm blocked by [barrier derived from PAA questions / related searches].
Generate 3-5 user stories covering the primary intent angles.
Step 5: Gap Analysis
Compare the target page against SERP expectations across 7 dimensions:
| Dimension |
What to Compare |
Score |
| Page Type |
Target type vs SERP dominant type |
0-15 |
| Content Depth |
Word count, heading depth, topic coverage |
0-15 |
| UX Signals |
CTA clarity, above-fold content, mobile layout |
0-15 |
| Schema Markup |
Present vs expected structured data types |
0-15 |
| Media Richness |
Images, video, interactive elements vs SERP norm |
0-15 |
| Authority Signals |
E-E-A-T markers, social proof, credentials |
0-15 |
| Freshness |
Last updated, date signals, content recency |
0-10 |
Total: 0-100 SXO Gap Score (lower = larger gap, higher = better alignment)
Step 6: Persona-Based Scoring
Read references/persona-scoring.md for methodology.
- Derive 4-7 personas from SERP intent signals:
- Cluster PAA questions by theme
- Segment ad copy by target audience
- Map related searches to journey stages
- For each persona, score the target page on 4 dimensions (25 pts each):
- Relevance: Does the page address this persona's need?
- Clarity: Can this persona find their answer within 10 seconds?
- Trust: Are there adequate trust signals for this persona?
- Action: Is there a clear next step for this persona?
- Output persona cards with scores and specific improvement recommendations
- Sort recommendations by weakest persona first (biggest opportunity)
Step 7: Wireframe Generation (Optional)
Only execute when /seo sxo wireframe is invoked.
Read references/wireframe-templates.md for templates.
- Generate IST (current state) wireframe from parsed page structure
- Generate SOLL (target state) wireframe based on:
- SERP consensus page type
- Gap analysis findings
- Persona scoring weaknesses
- Use ultra-concrete placeholders:
- NOT: "Add a CTA here"
- YES: "Add pricing CTA with annual savings badge below hero, linking to /pricing#enterprise"
- Output as semantic HTML section outline with annotations
DataForSEO Integration
If DataForSEO MCP tools are available:
- Before any API call, run cost estimate and confirm with user
- Use
serp_organic_live_advanced for precise SERP data (positions, features, snippets)
- Use
kw_data_google_ads_search_volume for search volume and competition metrics
- Fall back to WebSearch if DataForSEO unavailable -- note reduced precision in output
SXO Score vs SEO Health Score
The SXO score is separate from the main SEO Health Score.
- SEO Health Score = technical compliance (crawlability, speed, schema, etc.)
- SXO Gap Score = alignment between page and SERP expectations
- A page can score 95 SEO + 30 SXO = technically perfect but strategically misaligned
- Both scores should be reported together when both are available
Cross-Skill References
| Finding |
Hand Off To |
| E-E-A-T gaps in persona scoring |
/seo content for deep E-E-A-T audit |
| Missing schema types |
/seo schema for generation |
| Local intent detected in SERP |
/seo local for GBP analysis |
| Content depth gaps |
/seo page for deep page analysis |
| Technical issues found during fetch |
/seo technical for full audit |
| Image/media gaps |
/seo images for optimization |
Output Format
Full SXO Analysis
## SXO Analysis: [URL]
### Target Keyword: [keyword]
### 1. SERP Landscape
- Dominant page type: [type] ([confidence]% consensus)
- SERP features: [list]
- Content depth norm: [word count range]
- Schema expectation: [types]
### 2. Page-Type Alignment
- Your page type: [type]
- SERP expects: [type]
- Verdict: [ALIGNED | MISMATCH (severity)]
- Impact: [explanation]
### 3. User Stories (derived from SERP signals)
[3-5 user stories with source signals]
### 4. Gap Analysis (SXO Score: XX/100)
[7-dimension breakdown table]
### 5. Persona Scores
[4-7 persona cards with 4-dimension scores]
### 6. Priority Actions
[Ranked list: fix mismatch first, then weakest persona gaps]
### 7. Limitations
[What could not be assessed, data source notes]
Error Handling
| Error |
Action |
| URL fetch fails |
Report error, suggest checking URL accessibility |
| No keyword provided or detected |
Ask user to provide target keyword |
| WebSearch returns <5 results |
Proceed with available data, note limited sample |
| SERP has no organic results (all ads) |
Note highly commercial SERP, analyze ad copy only |
| Target page is JavaScript-rendered |
Note limitation, use available HTML content |
| DataForSEO cost exceeds threshold |
Fall back to WebSearch, notify user |
Quality Checklist
Before delivering results, verify:
1---
2name: seo-sxo
3description: >
4 Search Experience Optimization: reads Google SERPs backwards to detect page-type
5 mismatches, derives user stories from search intent signals, and scores pages
6 from multiple persona perspectives. Identifies why well-optimized pages fail
7 to rank by analyzing what Google rewards for each keyword. Use when user says
8 "SXO", "search experience", "page type mismatch", "SERP analysis", "user story",
9 "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".
10user-invocable: true
11argument-hint: "<url> [keyword]"
12license: MIT
13metadata:
14 source: https://skillmd.com/skills/agricidaniel/seo-sxo
15 author: AgriciDaniel
16 original_author: "Florian Schmitz (Pro Hub Challenge)"
17 version: "2.2.5"
18 category: seo
19---
20
21# Search Experience Optimization (SXO)
22
23SXO bridges the gap between SEO (what Google rewards) and UX (what users need).
24Traditional SEO audits check technical health. SXO asks: "Does this page deserve
25to rank for this keyword based on what Google is actually rewarding in the SERP?"
26
27## Core Insight
28
29A page can score 95/100 on technical SEO and still fail to rank because it is the
30**wrong page type** for the keyword. If Google shows 8 product pages and 2 comparison
31pages for your keyword, your blog post will never break through -- no matter how
32well-optimized it is.
33
34## Commands
35
36| Command | Purpose |
37|---------|---------|
38| `/seo sxo <url>` | Full SXO analysis (auto-detect keyword from page) |
39| `/seo sxo <url> <keyword>` | Full SXO analysis for a specific keyword |
40| `/seo sxo wireframe <url>` | Generate IST/SOLL wireframe with concrete placeholders |
41| `/seo sxo personas <url>` | Persona-only scoring (skip SERP analysis) |
42
43## Execution Pipeline
44
45### Step 1: Target Acquisition
46
471. Fetch the target URL via `claude-seo run render_page.py <URL> --mode auto` (SPA-aware and SSRF-safe)
482. Parse with `claude-seo run parse_html.py <URL>` to extract: title, H1, meta description,
49 headings hierarchy, word count, schema markup, CTAs, media elements
503. If no keyword provided, extract primary keyword from title tag + H1 overlap
514. Validate keyword is non-empty before proceeding
52
53### Step 2: SERP Backwards Analysis
54
55Read `references/page-type-taxonomy.md` for classification rules.
56
571. Search Google for the target keyword (WebSearch)
582. For each of the top 10 organic results, record:
59 - URL and domain authority tier (brand / niche authority / unknown)
60 - Page type (classify using taxonomy)
61 - Content format (long-form, listicle, how-to, comparison, tool, video)
62 - Word count estimate (from snippet length and page structure)
63 - Schema types present (from currently supported SERP features; exclude FAQ/HowTo)
64 - Media signals (video carousel, image pack, thumbnail presence)
653. Record SERP features present:
66 - Featured snippet (paragraph / list / table / video)
67 - People Also Ask (extract all visible questions)
68 - Ads (top and bottom -- count and analyze ad copy themes)
69 - Related searches (extract all)
70 - Knowledge panel / local pack / shopping results
71 - AI Overview presence and source types
724. Calculate SERP consensus:
73 - Dominant page type (>60% = strong consensus, 40-60% = mixed, <40% = fragmented)
74 - Content depth expectations (average word count tier)
75 - Schema expectation (most common structured data types)
76 - Media expectations (video required? images critical?)
77
78### Step 3: Page-Type Mismatch Detection
79
80This is the core SXO insight. Compare target page type against SERP consensus.
81
82**Mismatch severity levels:**
83
84| Target Type | SERP Expects | Severity | Recommendation |
85|-------------|-------------|----------|----------------|
86| Blog Post | Product Pages | CRITICAL | Create dedicated product page |
87| Blog Post | Comparison | HIGH | Restructure as comparison with matrix |
88| Product | Informational | HIGH | Add educational content layer |
89| Landing Page | Tool/Calculator | HIGH | Build interactive tool component |
90| Service Page | Local Results | MEDIUM | Add location signals + local schema |
91| Any type match | - | ALIGNED | Focus on content depth and UX |
92
93**Classification rules:**
94- Classify target page using `references/page-type-taxonomy.md`
95- Classify each SERP result using the same taxonomy
96- Flag mismatch if target type differs from SERP dominant type
97- If SERP is fragmented (no dominant type), note opportunity for differentiation
98
99### Step 4: User Story Derivation
100
101Read `references/user-story-framework.md` for the full framework.
102
103From SERP signals, derive user stories:
104
1051. **PAA questions** reveal knowledge gaps and concerns
1062. **Ad copy themes** reveal commercial triggers and value propositions
1073. **Related searches** reveal the search journey (what comes before/after)
1084. **Featured snippet format** reveals the expected answer structure
1095. **AI Overview** reveals what Google considers the definitive answer
110
111For each signal cluster, generate a user story:
112```
113As a [persona derived from signal],
114I want to [goal derived from query intent],
115because [emotional driver from ad copy / PAA tone],
116but I'm blocked by [barrier derived from PAA questions / related searches].
117```
118
119Generate 3-5 user stories covering the primary intent angles.
120
121### Step 5: Gap Analysis
122
123Compare the target page against SERP expectations across 7 dimensions:
124
125| Dimension | What to Compare | Score |
126|-----------|----------------|-------|
127| Page Type | Target type vs SERP dominant type | 0-15 |
128| Content Depth | Word count, heading depth, topic coverage | 0-15 |
129| UX Signals | CTA clarity, above-fold content, mobile layout | 0-15 |
130| Schema Markup | Present vs expected structured data types | 0-15 |
131| Media Richness | Images, video, interactive elements vs SERP norm | 0-15 |
132| Authority Signals | E-E-A-T markers, social proof, credentials | 0-15 |
133| Freshness | Last updated, date signals, content recency | 0-10 |
134
135**Total: 0-100 SXO Gap Score** (lower = larger gap, higher = better alignment)
136
137### Step 6: Persona-Based Scoring
138
139Read `references/persona-scoring.md` for methodology.
140
1411. Derive 4-7 personas from SERP intent signals:
142 - Cluster PAA questions by theme
143 - Segment ad copy by target audience
144 - Map related searches to journey stages
1452. For each persona, score the target page on 4 dimensions (25 pts each):
146 - **Relevance**: Does the page address this persona's need?
147 - **Clarity**: Can this persona find their answer within 10 seconds?
148 - **Trust**: Are there adequate trust signals for this persona?
149 - **Action**: Is there a clear next step for this persona?
1503. Output persona cards with scores and specific improvement recommendations
1514. Sort recommendations by weakest persona first (biggest opportunity)
152
153### Step 7: Wireframe Generation (Optional)
154
155Only execute when `/seo sxo wireframe` is invoked.
156
157Read `references/wireframe-templates.md` for templates.
158
1591. Generate IST (current state) wireframe from parsed page structure
1602. Generate SOLL (target state) wireframe based on:
161 - SERP consensus page type
162 - Gap analysis findings
163 - Persona scoring weaknesses
1643. Use ultra-concrete placeholders:
165 - NOT: "Add a CTA here"
166 - YES: "Add pricing CTA with annual savings badge below hero, linking to /pricing#enterprise"
1674. Output as semantic HTML section outline with annotations
168
169## DataForSEO Integration
170
171If DataForSEO MCP tools are available:
172
1731. **Before any API call**, run cost estimate and confirm with user
1742. Use `serp_organic_live_advanced` for precise SERP data (positions, features, snippets)
1753. Use `kw_data_google_ads_search_volume` for search volume and competition metrics
1764. Fall back to WebSearch if DataForSEO unavailable -- note reduced precision in output
177
178## SXO Score vs SEO Health Score
179
180The SXO score is **separate** from the main SEO Health Score.
181
182- SEO Health Score = technical compliance (crawlability, speed, schema, etc.)
183- SXO Gap Score = alignment between page and SERP expectations
184- A page can score 95 SEO + 30 SXO = technically perfect but strategically misaligned
185- Both scores should be reported together when both are available
186
187## Cross-Skill References
188
189| Finding | Hand Off To |
190|---------|-------------|
191| E-E-A-T gaps in persona scoring | `/seo content` for deep E-E-A-T audit |
192| Missing schema types | `/seo schema` for generation |
193| Local intent detected in SERP | `/seo local` for GBP analysis |
194| Content depth gaps | `/seo page` for deep page analysis |
195| Technical issues found during fetch | `/seo technical` for full audit |
196| Image/media gaps | `/seo images` for optimization |
197
198## Output Format
199
200### Full SXO Analysis
201
202```
203## SXO Analysis: [URL]
204### Target Keyword: [keyword]
205
206### 1. SERP Landscape
207- Dominant page type: [type] ([confidence]% consensus)
208- SERP features: [list]
209- Content depth norm: [word count range]
210- Schema expectation: [types]
211
212### 2. Page-Type Alignment
213- Your page type: [type]
214- SERP expects: [type]
215- Verdict: [ALIGNED | MISMATCH (severity)]
216- Impact: [explanation]
217
218### 3. User Stories (derived from SERP signals)
219[3-5 user stories with source signals]
220
221### 4. Gap Analysis (SXO Score: XX/100)
222[7-dimension breakdown table]
223
224### 5. Persona Scores
225[4-7 persona cards with 4-dimension scores]
226
227### 6. Priority Actions
228[Ranked list: fix mismatch first, then weakest persona gaps]
229
230### 7. Limitations
231[What could not be assessed, data source notes]
232```
233
234## Error Handling
235
236| Error | Action |
237|-------|--------|
238| URL fetch fails | Report error, suggest checking URL accessibility |
239| No keyword provided or detected | Ask user to provide target keyword |
240| WebSearch returns <5 results | Proceed with available data, note limited sample |
241| SERP has no organic results (all ads) | Note highly commercial SERP, analyze ad copy only |
242| Target page is JavaScript-rendered | Note limitation, use available HTML content |
243| DataForSEO cost exceeds threshold | Fall back to WebSearch, notify user |
244
245## Quality Checklist
246
247Before delivering results, verify:
248- [ ] Target URL was fetched via `claude-seo run render_page.py <URL> --mode auto` (not raw curl/fetch)
249- [ ] Page type classification uses taxonomy from references
250- [ ] At least 5 SERP results were analyzed
251- [ ] User stories cite specific SERP signals as evidence
252- [ ] Persona scores include concrete improvement suggestions
253- [ ] SXO score is clearly labeled as separate from SEO Health Score
254- [ ] Limitations section is present and honest
255- [ ] Cross-skill recommendations are included where relevant