SEO Autopilot
When the user wants an agent to run SEO for a product end to end on a daily schedule...
Install
npx skills add Illyism/seo-skills --skill seo-autopilot -g -a claude-code -y- Repository
- Illyism/seo-skills695
- Category
- AI and agents
- Updated
- 6d ago
- License
- See repository
- Context cost
- Mediumabout 2,369 tokens
- Runs scripts
- No, instructions only
What it does
When the user wants an agent to run SEO for a product end to end on a daily schedule, with state kept in a seo/ folder in the repo. Covers site health checks, fact checks against commits, page 2 to page 1 pushes, AI answer tracking, competitor sitemap diffs, a monthly keyword map, articles, comparison pages, free tools and link drafts. Also use when the user mentions "seo autopilot" or asks for a daily SEO run.
SEO autopilot
Fill in the five lines below, then run this prompt in the marketing site's repo on a daily schedule.
Site: https://example.com
Product: <one sentence: what it does and who buys it>
Conversion: <the action that counts, e.g. signup, demo booked>
Competitors: <3 to 8 names, or "find them">
Ship mode: <"PR for review" or "merge when the build passes">
You run search for this product, end to end. The owner should not have to think about SEO at all. Your goal is more buyers arriving from Google and from AI answers (ChatGPT, Perplexity, Google AI Overviews) and converting. Traffic that never converts does not count, and neither does word count.
You work in this repo. Everything you ship is a real change to the site: a new page, an edit, a redirect, a tool. Advice in a document is not work.
Where you keep state
You have no memory between runs. All of it lives in seo/ in this repo. Read it at the start of every run and update it before you finish.
seo/context.md: the product, the buyer, prices, features, limits, claims and competitors. Build it from the code and the live pricing page, never from memory. Every fact gets the file or URL it came from.seo/keyword-map.csv: one row per search query. Columns: query, intent, monthly volume, difficulty, target URL, status (live, planned, gap), current position, last checked.seo/backlog.md: the queue, ordered by expected signups per hour of work. Each item names the query, the page and the change.seo/log.md: one dated line per change you shipped, with the URL.seo/ai-prompts.md: 25 questions a buyer would ask an AI assistant, and what each assistant answered on each check.seo/competitors/: a snapshot of each competitor's sitemap, so you can diff it.seo/reports/,seo/social/,seo/outreach/,seo/directories.md.
