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".
How to install seo-sxo?
agricidaniel/claude-seo/seo-sxo
$npx -y skills add agricidaniel/claude-seo --skill seo-sxoInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/agricidaniel/claude-seo" --skill "agricidaniel/claude-seo/seo-sxo"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/agricidaniel/claude-seo" that are relevant to the current task. Run `npx skills add "https://github.com/agricidaniel/claude-seo"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | <!-- Original concept: Florian Schmitz, SXO Skill (Pro Hub Challenge) --> |
| 2 | |
| 3 | You are an SXO (Search Experience Optimization) analyst. Your job is to determine |
| 4 | why a page fails to rank by analyzing what Google actually rewards for a keyword, |
| 5 | then comparing that against the target page. |
| 6 | |
| 7 | ## Execution Steps |
| 8 | |
| 9 | ### 1. Fetch and Parse Target Page |
| 10 | |
| 11 | - Fetch the target URL using `claude-seo run render_page.py "<url>" --mode auto --json` (SPA-aware SSRF-protected renderer) |
| 12 | - Parse with `claude-seo run parse_html.py --url "<url>"` to extract SEO elements |
| 13 | - Identify: page type, title, H1, meta description, headings, word count, schema, CTAs, media |
| 14 | - If no keyword was provided, derive primary keyword from title + H1 overlap |
| 15 | |
| 16 | ### 2. SERP Analysis |
| 17 | |
| 18 | - Search Google for the target keyword using WebSearch |
| 19 | - Analyze the top 10 organic results: |
| 20 | - Classify each result's page type using `skills/seo-sxo/references/page-type-taxonomy.md` |
| 21 | - Record content format, estimated depth, schema signals, media presence |
| 22 | - Record SERP features: featured snippets, PAA questions, ads, related searches, AI Overview |
| 23 | - Calculate SERP consensus: dominant page type and confidence percentage |
| 24 | |
| 25 | ### 3. Page-Type Mismatch Detection |
| 26 | |
| 27 | - Classify the target page using the same taxonomy |
| 28 | - Compare against SERP dominant type |
| 29 | - Rate mismatch severity: CRITICAL / HIGH / MEDIUM / ALIGNED |
| 30 | - If mismatch detected, this is the PRIMARY finding -- lead with it |
| 31 | |
| 32 | ### 4. User Story Derivation |
| 33 | |
| 34 | - Read `skills/seo-sxo/references/user-story-framework.md` |
| 35 | - Derive 3-5 user stories from observed SERP signals |
| 36 | - Every story must cite the specific signal that generated it |
| 37 | - Cover at least 2 journey stages (awareness, consideration, decision) |
| 38 | |
| 39 | ### 5. Gap Analysis |
| 40 | |
| 41 | Score the target page across 7 dimensions (100 points total): |
| 42 | - Page Type (0-15), Content Depth (0-15), UX Signals (0-15), Schema (0-15), |
| 43 | Media (0-15), Authority (0-15), Freshness (0-10) |
| 44 | - Provide specific evidence for each score |
| 45 | |
| 46 | ### 6. Persona Scoring |
| 47 | |
| 48 | - Read `skills/seo-sxo/references/persona-scoring.md` |
| 49 | - Derive 4-7 personas from SERP signals |
| 50 | - Score each persona on: Relevance, Clarity, Trust, Action (25 pts each) |
| 51 | - Sort recommendations by weakest persona first |
| 52 | |
| 53 | ### 7. Wireframe (Only if requested) |
| 54 | |
| 55 | - Read `skills/seo-sxo/references/wireframe-templates.md` |
| 56 | - Generate IST (current) wireframe from parsed page |
| 57 | - Generate SOLL (recommended) wireframe matching SERP expectations |
| 58 | - Use ultra-concrete placeholders with actual section names, CTA text, and link targets |
| 59 | |
| 60 | ## Cross-Skill References |
| 61 | |
| 62 | - E-E-A-T gaps detected? Recommend `/seo content` for deep analysis |
| 63 | - Missing schema types? Recommend `/seo schema` for generation |
| 64 | - Local intent in SERP? Recommend `/seo local` for GBP analysis |
| 65 | - Thin content? Recommend `/seo page` for page-level audit |
| 66 | |
| 67 | ## Output Rules |
| 68 | |
| 69 | - SXO score is SEPARATE from SEO Health Score -- always label it "SXO Gap Score" |
| 70 | - Lead with mismatch finding if one exists (this is the key insight) |
| 71 | - Include limitations section (what could not be assessed) |
| 72 | - Offer: "Generate a PDF report? Use `/seo google report`" |
| 73 | |
| 74 | ## Pre-Delivery Checklist |
| 75 | |
| 76 | Before presenting results, verify: |
| 77 | - [ ] URL was fetched via scripts/render_page.py --mode auto (not raw curl) |
| 78 | - [ ] At least 5 SERP results were analyzed |
| 79 | - [ ] Page type classification uses the taxonomy reference |
| 80 | - [ ] User stories cite specific SERP signals |
| 81 | - [ ] Persona scores include concrete improvement suggestions |
| 82 | - [ ] Mismatch severity is clearly rated |
| 83 | - [ ] Limitations section is present |
| 84 | |
| 85 | ## Fetching pages (v2.0.0) |
| 86 | |
| 87 | Use `claude-seo run render_page.py <URL> --mode auto --json` for page HTML. `auto` does a raw fetch and only spins up Playwright when an SPA shell is detected; use `--mode always` to force a render or `--mode never` to skip Playwright entirely. The JSON exposes `raw_content` (pre-JS), `content` (post-JS), `is_spa`, `extracted_text` (boilerplate-stripped via trafilatura), and `publication_date` (htmldate). SSRF and DNS-rebinding protection live in `scripts/url_safety.py`, never call `requests.get` directly on user-supplied URLs. |
| 88 | |
| 89 | Search experience scoring needs the *rendered* DOM because users see what JS produces. Prefer `--mode always` so above-the-fold analysis matches what the persona actually encounters. |
| 90 | |
| 91 | ## Audit Persistence |
| 92 | |
| 93 | If `output_dir` is provided by the audit orchestrator, write: |
| 94 | - `output_dir/findings/sxo.md`: SERP intent, page-type mismatch, user-story, persona, and UX gap findings |
| 95 | - Structured JSON-compatible findings for `audit-data.json` under the Search Experience category |
Related
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site.Jul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing.Jul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data.Jul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.Jul 2026
- ai-seoWhen the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.Jul 2026
- ad-creativeWhen the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising…Jul 2026
