mcpbeat Sign in

SEO Sxo Skill for Claude

Assess whether a page satisfies searcher intent and supports the next useful task. Use for SXO, page-type mismatch or search journey reviews.

705 tokens
context cost
SKILL.md, read when the skill is used
2
files
plus reference files
0
copies elsewhere
how many repositories repackaged it
834
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/AgriciDaniel/chatgpt-seo --skill seo-sxo

What comes with it

192 bytes besides the instruction
agents/openai.yaml

The instruction itself

7 sections, as written by the author

Search experience

Input

A query/audience and page, plus observed search examples or funnel evidence if available.

Evidence and runtime

If a skill-resource reader fails to open a linked supporting file, try the

available file or execution tool using the installed plugin root returned by

the host or resolved from this skill's location. Do not hardcode a home folder,

version, or working directory. Distinguish a failed reader call from an absent

file, and files actually attempted from files not attempted. Report a resource

as unavailable only after the supported access paths have failed. If no file

or execution access is available, continue within the evidence you can read

and state that limit.

Read the operating contract when this

workflow is selected. Use runtime and data paths

when choosing a tool or handling missing data. Recheck relevant

search facts and primary sources

before date-sensitive claims. For a quantitative diagnostic, read

scoring; unavailable categories stay unknown.

Supporting resources

Read only the resources needed for the selected part of this task:

  • taxonomy, persona and task fit.
  • conversion review templates.
  • search experience worksheet.

Workflow

  • Classify the page's actual task and observed result types. Keep search sampling, locale and date explicit.
  • Write concrete user stories from evidence: what a searcher needs to learn, compare, evaluate or do. Label inferred personas as hypotheses.
  • Assess the first-screen promise, answer finding, navigation, decision information, trust evidence and task completion path.
  • Use rendered and keyboard observations for interaction claims. A screenshot can reveal layout but not prove a form, checkout or accessibility works.
  • Connect each friction point to an observed step and give a specific copy/layout/content improvement.
  • Define a measurement or usability check with a success criterion. Keep any SXO rubric distinct from the SEO health score.

Deliverable

A search-to-task diagnosis, observed frictions, user-story improvements and an experiment/retest plan.

Boundary

Do not invent conversion rates, persona research, behavioral tests or a quantitative uplift.

Adapted from the public Claude SEO seo-sxo workflow.

How to use it

Copy the folder

Take agricidaniel/seo-sxo from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.