skills/components/utility/url-slug/SKILL.md
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.
npx skillsauth add kostja94/marketing-skills url-slug-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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
testing
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate maintenance." For IndexNow, use indexnow.
development
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.
testing
When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.