seo-audit
Review crawlability, on-page signals and content issues, then prioritize fixes.
npx skills add coreyhaines31/marketingskills --skill seo-auditAudit technical and content issues, map site structure and plan search-focused pages.
Use an audit for an existing site, architecture for a new hierarchy, and structured data when a page has facts eligible for markup.
Review crawlability, on-page signals and content issues, then prioritize fixes.
npx skills add coreyhaines31/marketingskills --skill seo-auditImprove how clearly pages answer questions and expose sources for AI search.
npx skills add coreyhaines31/marketingskills --skill ai-seoPlan scalable landing pages around unique, useful data and search intent.
npx skills add coreyhaines31/marketingskills --skill programmatic-seoMap category hierarchy, URL patterns and internal linking.
npx skills add coreyhaines31/marketingskills --skill site-architectureAdd or correct JSON-LD to describe facts already visible on a page.
npx skills add coreyhaines31/marketingskills --skill schemaImprove an app store listing’s search visibility and conversion assets.
npx skills add coreyhaines31/marketingskills --skill asoNo skill in this category has a full write-up yet.
These six come from one author and cover one pipeline rather than six competing tools: audit what is there, decide the structure, plan the pages, then describe the facts. Run them in that order and each one gives the next something to work with. Running site-architecture before an audit usually produces a redesign you cannot ship; running schema before the page has its facts settled produces markup that has to be rewritten a week later. The realistic starting point is one section of the site — a category, a hub, a blog folder — because a full-crawl report on a site you have not touched yet is mostly noise. Keep the output of each run. When you re-run the audit in a month, the comparison between two lists is worth more than either list on its own, and it is the only way to tell whether a fix actually changed anything.
Run the audit on your own site first, not a client's. Read the list it returns and cross out anything you cannot see a concrete fix for: an audit that flags twenty issues you will never ship is worse than one that flags four you will. Then pick a single page and do the whole loop — audit, fix, re-crawl, compare — before running it site-wide. For schema, paste the generated JSON-LD into the validator and then check that every field matches text a visitor can actually see on the page; markup that describes facts the page does not show is the one thing that reliably gets ignored.
Start with seo-audit if you have never looked at the site with these skills. It is the broadest of the six and tells you which of the others is worth running next. Reach for site-architecture only when URLs or internal links are the problem, and for schema only when a page already shows facts — prices, ratings, steps — that markup could describe.
No. ai-seo is about how clearly a page answers a question and where the facts come from: headings that match the question, an answer near the top, sources named. schema is about the markup on that page. You can do either alone, and doing ai-seo first tends to make schema easier because you already know which facts the page owns.
programmatic-seo plans pages, it does not make them. It is useful when you have a dataset that can answer many similar queries — one page per city, per integration, per error code — and useless when the pages would repeat the same paragraph with a noun changed. If you cannot name the field that changes from page to page, that is the answer.
It reviews crawlability, on-page signals and content issues and returns a prioritised list. It does not submit anything, request indexing or connect to a search console. Whatever it finds, the shipping happens on your side — the skill's value is the ordering of the work, not the doing of it.
The same place as every skill here: run the command on the row, or copy the folder to ~/.claude/skills/name/SKILL.md, where name is the skill's own folder name. The path must end at SKILL.md; an extra folder level on top is the usual reason a skill never activates.