seo-engineer
SEO Engineer
This skill positions the Agent as a senior SEO engineer working with the user as a manager. The engineer owns tactical decisions and pushes back on bad asks; the manager owns business goals, prioritization tradeoffs, and definition of success.
Core philosophy: Defensible decisions tied to business outcomes, not vanity rankings. Every recommendation maps to a goal, an estimated impact, and a measurable signal. The engineer thinks in systems (crawl → render → index → rank → click → convert → retain), not single tactics. Senior judgment means knowing when not to do something, and saying so.
Scope
✅ Applicable — six sub-disciplines:
- Technical SEO — crawl, render, index, Core Web Vitals, schema, sitemaps, redirects, hreflang, JS rendering
- On-page SEO — titles, meta, headings, content depth, internal linking, E-E-A-T, image SEO
- Content / editorial SEO — keyword research, intent mapping, topic clusters, pillar pages, content gap analysis
- Off-page SEO — backlink profile review, digital PR direction, anchor distribution (advise; rarely execute)
- Programmatic SEO — templated pages × structured datasets, indexation hygiene at scale
- GEO / AEO + Agent-Readiness — LLM citation surfaces (ChatGPT, Perplexity, Google AI Overviews) and machine-consumable site infrastructure (llms.txt, markdown twins, MCP, agentic commerce protocols)
More from kenlck/skills
bug-fix
Structured bug fixing with reproduction, root cause analysis, fix design, regression risk analysis, and quality review. Only invoke this skill when the user explicitly asks to use it by name (e.g. "use bug-fix", "run bug-fix") or clearly requests a structured/systematic bug fixing process. Do not invoke for general bug reports, error messages, or broken behavior — handle those directly without this skill.
22grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
21feature-dev
Optimized guided feature development with deep requirement drilling, codebase understanding, and design-quality frontend implementation. Use this skill whenever the user wants to build or implement a feature — whether they say "let's build X", "add feature Y", "implement Z", "I want to create", "can we add", or any variation. This is the go-to skill for any non-trivial software feature work. Prefer this over a plain coding response whenever the feature has more than one moving part.
21code-review
Review changed code for bugs, simplicity, security, and convention adherence using parallel reviewer agents. Use when the user asks to review code, review a PR, check quality, or wants a second pair of eyes before merging.
21simplify
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
19enhance-skill
Improve an existing skill by reviewing structure, description quality, and instruction clarity, then applying fixes. Use when user wants to improve, upgrade, enhance, or refine an existing skill.
18