Skip to content
Back to skills

Slug Keywords

ASecurity

Use when applies to blog posts, product pages, and any content page with editable URL slugs. Use when building a URL strategy for a new site or auditing existing URLs for keyword inclusion.

  • 74,358 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 5, 2026
developmentgofrontend

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add thedaviddias/Front-End-Checklist --skill slug-keywords --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Slug Keywords?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Slug Keywords
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedaviddias-slug-keywords/badge)](https://www.skillsdirectory.com/skills/thedaviddias-slug-keywords)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: slug-keywords
description: "Use when applies to blog posts, product pages, and any content page with editable URL slugs. Use when building a URL strategy for a new site or auditing existing URLs for keyword inclusion."
metadata:
  category: seo
  priority: medium
  difficulty: beginner
  estimatedTime: "10"
  source: frontendchecklist.io
  url: https://frontendchecklist.io/rules/seo/slug-keywords
---

# Include keywords in URL slugs

Descriptive URL slugs help users and search engines understand page content before visiting — a URL like `/buy-running-shoes-women` communicates topic intent that `/products/4832` does not.

## Quick Reference

- URL slugs should contain the primary keyword of the page in lowercase, hyphen-separated words
- Avoid numeric IDs (`/page?id=12345`), random strings, or meaningless paths (`/p/a/`)  in public URLs
- Keep slugs concise: 3–5 meaningful words is typical; avoid keyword stuffing
- Google uses URL words as a weak ranking signal and users use them to assess page relevance before clicking

## Check

Crawl the site and examine URL paths. Flag URLs that contain: numeric IDs only, random strings, session tokens, dates without a descriptive slug, or overly generic words (`/page`, `/item`, `/post`). Verify slugs are lowercase and hyphen-separated.

## Fix

Rewrite slugs to include the page's primary keyword in natural language. Use lowercase letters and hyphens as word separators. Set up 301 redirects from old URLs to new slugs. Update internal links, sitemaps, and canonical tags.

## Explain

Explain how keyword-rich URL slugs improve click-through rates in search results, serve as a weak relevance signal for search engines, and make URLs easier to share and understand.

## Code Review

Review metadata generation, rendered HTML, structured data, and response headers related to Include keywords in URL slugs. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.

---

For full implementation details, code examples, and framework-specific guidance,
see `references/rule.md`.

Rule page: https://frontendchecklist.io/rules/seo/slug-keywords

Files in this skill

  • SKILL.md2.1 KB
  • references/rule.md3.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…