mcpbeat Sign in

SEO Programmatic Skill for Claude

Evaluate or design data-driven page families for useful differentiation, index management and scalable quality. Use for programmatic SEO.

763 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-programmatic

What comes with it

198 bytes besides the instruction
agents/openai.yaml

The instruction itself

7 sections, as written by the author

Programmatic SEO

Input

A dataset, template, representative pages or proposed URL family.

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:

  • scaled-content pilot and utility.
  • architecture choices.
  • template controls.

Workflow

  • Inspect the dataset's grain, keys, duplicates, missingness, freshness and licensing. Match each proposed page to a distinct useful task.
  • Evaluate actual differentiating content, evidence and functionality beyond swapping a city, product or keyword. Sample both rich and sparse rows.
  • Design stable unique URLs, useful hubs, related links, breadcrumbs and explicit handling of empty or low-value records.
  • Review canonical/noindex decisions for true duplicates and faceted or paginated cases. Do not automatically noindex or canonicalize distinct useful pages.
  • Define row-level content acceptance and a representative human review sample. For a small pilot, measure rendering, crawl behavior and indexing evidence before scaling.
  • Check current scaled-content and site-reputation policies. Treat uniqueness percentages, batch sizes and word counts as internal review choices, not Google rules.

Deliverable

A data/template diagnosis, pilot architecture, row-level acceptance criteria, index-management plan and measurable expansion decision.

Boundary

Do not generate fake location presence, product facts or mass pages with no standalone value. A quality plan does not authorize publication.

Adapted from the public Claude SEO seo-programmatic workflow.

How to use it

Copy the folder

Take agricidaniel/seo-programmatic 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.