SXO Specialist: Role, Skill Dispatch, and Page-Experience Checks
Human-Edited & Verified • Deterministic AI-assisted research. Editorial standards.
AI Edited
Last updated: 31 August 2026
An SXO specialist maps the searcher's job to the first screen after the click, then checks the page-experience signals Google documents. This URL is the role. The product skill stays on SXO user intent.
TLDR
- First-party GSC (31 Jul–28 Aug 2026) showed 7 impressions at position 14.9 for this query on
/subagents/seo-sxo, not on the skill pillar. - Google does not name SXO as a ranking factor. Page experience is a bundle of signals, not one score.
- Core Web Vitals (LCP, INP, CLS) are used by ranking systems. HTTPS, mobile layout, and interstitial policy still sit on the checklist.
- The skill pillar answers “what is SXO user intent.” This subagent answers “who runs the checks and which CLI to dispatch.”
- Run
npx @seoskillsai/cli run seo-sxo --target "https://example.com"after the intent table exists.
Contents
- What the role actually owns
- How this URL differs from the skill pillar
- Page-experience checks the role runs
- Dispatch the subagent
- FAQ
- Related reading
- Sources
What the role actually owns
The role starts at the SERP and ends when the landing page is usable for that query class. Ranking work lives in other skills. Conversion experiments after a correct landing page are CRO, not this job.
Owned work:
- Label the SERP format (snippet, video, pack, discussion).
- Assign one intent class (know, go, compare, do).
- Check H1 and the first 40–60 words against that class.
- Check CWV, HTTPS, mobile layout, ads vs main content, interstitial risk.
- Dispatch
seo-sxointo the agent runtime.
The SXO user intent pillar is the method. This page is the operator.
How this URL differs from the skill pillar
| URL | Query Google already assigned | Job |
|---|---|---|
/skills/seo-sxo |
sxo user intent (23 impressions, pos 59.7) |
After-the-click method |
/subagents/seo-sxo |
this role query (7 impressions, pos 14.9) | Who runs the checks |
/subagents |
directory | All 18 specialists |
Do not merge the two pages. Do not open a careers slug. The subagents directory lists every specialist file under agents/{slug}.md.
Agency listicles treat the title as a hire. This site ships a local subagent spec plus the seo-sxo skill. That is the unique gap versus the 2026 SERP.
Page-experience checks the role runs
AI Edited
From Search Central (page experience):
- Good Core Web Vitals
- HTTPS
- Mobile-usable layout
- Ads that do not bury main content
- No intrusive interstitials
- Main content distinguishable from chrome
Thresholds the role quotes, not invents (Core Web Vitals): LCP within 2.5s, INP under 200ms, CLS under 0.1. Pair instrumentation with technical SEO.
Dispatch the subagent
npx @seoskillsai/cli add seo-sxo
npx @seoskillsai/cli run seo-sxo --target "https://example.com"
The skill config is the method pack. This subagent is the dispatch file (agents/seo-sxo.md). Full catalog: skills directory.
Open the SXO user-intent skill
FAQ
What does an SXO specialist do?
Maps SERP format to page type, then audits CWV, HTTPS, mobile layout, and interstitial risk. On this site the role URL is /subagents/seo-sxo.
Is SXO a Google ranking factor?
Google does not name SXO. Core Web Vitals are used in ranking systems. Overall page experience uses multiple signals, not one score.
How is this different from an SEO specialist?
SEO owns crawl, relevance, and rankings. This role owns the post-click match and the experience checklist. They share URLs; they do not share the first sentence of the brief.
Should the role live on the skill pillar?
No. GSC already assigned the role query here. Keep “user intent” on /skills/seo-sxo. Cross-link both.
How is this different from CRO?
CRO optimizes conversions for traffic you already have. This role starts from the query and the SERP.
Related reading
Sources
Make SEO Skills AI a Preferred Source
Keep SEO skill docs highlighted in Google Search and AI Overviews.