When the user wants to create, optimize, or validate URL slugs for content pages. Also use when the user mentions "URL slug," "URL path," "blog URL," "article URL," "short URL," "clean slug," "permalink," "slug optimization," "URL structure," "SEO-friendly URL," "create URL slug," or "SEO slug." For site-wide URL policy, use url-structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Guides creation of SEO-friendly URL slugs for blog posts, articles, and content pages. Research on 11.8M Google results shows shorter URLs tend to rank higher; position #1 URLs average 50–60 characters.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
ai-people-search in /blog/ai-people-search)| Guideline | Target |
|---|---|
| Slug length | Under 60 characters total (including path prefix) |
| Word count | 3–5 words |
| Principle | Shorter = easier to read, share, remember; less truncation in SERPs; see serp-features |
Example: "The Complete Guide to AI Search Engine for Finding People" → ai-people-search (3 words) or ai-search-finding-people (4 words), not ai-search-engine-finding-people-speed-discovery-outreach (9 words, 51 chars).
| Rule | Do | Avoid |
|---|---|---|
| Separators | Hyphens (-) | Underscores (_), spaces, periods |
| Case | Lowercase only | Mixed case (causes duplicate content) |
| Characters | Letters (a-z), numbers (0-9), hyphens | Special chars |
| Stop words | Remove when possible: the, a, and, or, to | Keep when needed: "how-to" |
| Rule | Guideline |
|---|---|
| Primary keyword | Include near start; one focus per URL |
| Descriptive | Clear what page is about from slug alone |
| No keyword stuffing | One keyword mention is enough |
| No dates | Omit unless time-specific (news, annual roundups) |
| Scenario | Rule |
|---|---|
| Accented letters | Convert to ASCII: é→e, ü→u, ñ→n, ç→c |
| Non-Latin scripts | Use UTF-8 percent-encoding if required; prefer ASCII for compatibility |
| Example | jalapeno not jalapeño; cafe not café |
/post/12847 — always customize| Title / Topic | ❌ Too long | ✅ Recommended |
|---|---|---|
| AI Search Engine for Finding People: Speed vs. Discovery | ai-search-engine-finding-people-speed-discovery-outreach | ai-people-search or ai-search-finding-people |
| The Ultimate SEO Checklist for 2025 | the-ultimate-seo-checklist-for-2025 | seo-checklist-2025 |
| How to Increase Website Traffic | how-to-increase-the-traffic-to-your-website | increase-website-traffic |
| Best Running Shoes for Marathon Training | best-running-shoes-for-marathon-training-in-2025 | best-running-shoes-2025 |
When creating or auditing a slug:
Recommended slug (3–5 words)
Character count (slug only)
Primary keyword included
Alternatives if multiple valid options
Reference: Alignify URL optimization
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.