Keep URLs concise

SkillDev tools

Length is a skill for AI agents that handles URL slug work. It generates clean slugs from article titles, audits URL structures for unnecessary depth or length, and reviews URL patterns in a CMS or router configuration.

Use Keep URLs concise in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Keep URLs concise and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Keep URLs concise skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Have an AI agent that supports loading skills.

Keep URLs conciseStart free

What your AI can do with it

  • Generate URL slugs from article titles
  • Audit URL structures for unnecessary depth
  • Audit URL structures for excess length
  • Review URL patterns in a CMS configuration
  • Review URL patterns in a router configuration

Getting started

  1. Have an AI agent that supports loading skills.
  2. Add the length skill to the agent's available skills.
  3. Ask the agent to generate a slug from a title or audit a URL structure, and provide the titles or configuration to review.

What this skill tells your AI

The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/length/SKILL.md and read by ahel’s review.

While Google has no strict URL length limit beyond technical constraints, long URLs with deep nesting, excessive parameters, or redundant words are harder for users to read, copy, and share. Google's John Mueller has confirmed that shorter, cleaner URLs are easier to understand and may perform slightly better in search.

Quick Reference

  • Keep URL paths under 100 characters; Google recommends short, descriptive URLs without unnecessary parameters
  • Remove stop words (the, a, of, in) from slugs — /guide-css-grid is better than /a-guide-to-css-grid
  • Deeply nested paths (/blog/2024/03/category/subcategory/post-title) are harder to share and signal distance from the root

Check

For each page URL, extract the path component (excluding domain and query string). Flag: (1) Path length over 100 characters. (2) More than 4 path segments (e.g., /a/b/c/d/e has 5 segments). (3) Common stop words in slugs (the, a, an, of, in, at, to, for, with). (4) Dates in URL paths for evergreen content (e.g., /blog/2024/03/css-guide). (5) Session IDs, tracking parameters, or other dynamic values in paths.

Fix

  1. Shorten slugs by removing stop words:
    • /how-to-optimise-your-websites-core-web-vitals → /optimise-core-web-vitals
    • /a-comprehensive-guide-to-css-grid-layout → /css-grid-guide
  2. Flatten URL structure where category hierarchy is not essential:
    • /blog/2024/march/technology/css-grid → /blog/css-grid
  3. Remove dates from evergreen content URLs (with 301 redirects from old URLs).
  4. Remove session IDs and tracking parameters from URLs used as canonical-url URLs.
  5. Implement changes with 301 redirects from old to new URLs to preserve link equity.
  6. Update sitemaps and internal links after URL changes.

Explain

Google recommends keeping URLs 'simple, descriptive, and readable'. Long URLs are more prone to being truncated in search snippets, harder to share, and more confusing to users. Deep URL structures (many subdirectories) do not directly harm rankings, but they can increase crawl distance from the root, reducing crawl frequency for deep pages on large sites.

Code Review

Parse the pathname of each URL. Count path segments (split by /). Measure character length of the path. Flag slugs containing common stop words. Report the longest 10 URLs by character count and deepest 10 by segment count. Check whether URL generation utilities strip stop words and limit segment depth.


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

Rule page: https://frontendchecklist.io/en/rules/seo/length

Signals

GitHub stars
74k
Forks
7k
Last commit
Oct 2026
Hacker News mentions
20

Questions

When should the agent use this skill?
Use it when generating URL slugs from article titles, auditing URL structures for unnecessary depth or length, or reviewing URL patterns in a CMS or router configuration.
Does it work with any CMS or router?
It reviews URL patterns in a CMS or router configuration that you provide to the agent.
Advanced
Item type
skill
Key
length
Source
github.com/thedaviddias/front-end-checklist