agentleFS
gaznilgaznil/seo-skills-by-gaznil/skills/url-structure/SKILL.md

url-structure

Skill0 starsChanged 3 months agoMITView on GitHub

When the user wants to optimize URL structure, fix URL issues, or plan URL hierarchy. Also use when the user mentions "URL structure," "URL optimization," "slug," "clean URLs," "URL hierarchy," "URL path," "permalink structure," "URL best practices," "dynamic URLs," or "URL parameters." For per-page slug wording, use url-slug-generator. For canonical consolidation, use canonical-tag.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site structure.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SEO On-Page: URL Structure

Guides URL structure optimization for SEO: readability, hierarchy, and best practices.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Scope (On-Page SEO)

  • URL hierarchy: Path structure, categories, depth
  • URL format: Static vs dynamic; omit file extensions
  • URL slug: See url-slug-generator for slug creation (3–5 words, under 60 chars)
  • Duplicate variants: See canonical-tag for HTTPS, www, trailing slash

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site structure.

Identify:

  1. Site structure: Categories, subcategories, content types
  2. Current URLs: Existing patterns and issues
  3. Multi-language: URL structure for zh/en (e.g., /zh/, /en/ or subdomains)

Best Practices

URL Guidelines

PrincipleGuideline
ReadableUse words, not IDs; /blog/seo-guide not /p/12345
ShortShorter is generally better; avoid unnecessary depth
KeywordInclude target keyword when natural
LowercaseUse lowercase; avoid mixed case
HyphensUse hyphens to separate words: seo-guide
AvoidSpecial chars, query params for core content, session IDs

Hierarchy

PatternExampleUse
Flat/page-nameSimple sites
Category/blog/post-name, /tools/tool-nameContent sites
Nested/category/subcategory/pageDeep hierarchies (keep shallow)

Multi-language

PatternExample
Path prefix/zh/page, /en/page
Subdomainzh.example.com, en.example.com
ccTLDexample.cn, example.com

Static vs Dynamic vs Pseudo-Static URLs

TypeExampleUse
Static/blog/seo-guideDirect file; best SEO; content stable
Dynamic/product?id=123Program-generated; avoid for indexable content
Pseudo-static/blog/seo-guide (rewritten from .php)Combines both; common in CMS
RulePrefer static or pseudo-static; if dynamic, keep params ≤2; use canonical-tag and robots-txt (Clean-param)

File Extensions

  • Omit .html, .php, .aspx — keeps URLs technology-agnostic, shorter, easier to refactor
  • Example: /seo-guide not /seo-guide.html

URL Parameter Handling

ScenarioApproach
UTM / trackingCanonical to base URL; params in query string only
Search resultsCanonical to search page; avoid indexing result URLs
Filters / sortCanonical to base; or robots-txt Clean-param
Session IDsUse cookies; never in indexable URLs

Use Cases

ScenarioFocus
New sitePlan hierarchy upfront; avoid later restructuring
Migration301 mapping; canonical; see canonical-tag
Large siteDynamic URLs, params, multi-language — canonical + robots
SEO auditCheck structure, params, canonical consistency

Common Issues

IssueFix
Long URLsShorten; remove redundant words
Dynamic paramsUse canonical; clean params in robots (Yandex Clean-param)
Mixed caseRedirect to lowercase
Changed URLs301 redirect old to new

Output Format

Related Skills

  • website-structure: Plan structure and URL paths; apply url-structure rules after structure is defined
  • canonical-tag: HTTPS, www, trailing slash — handles duplicate URL variants
  • url-slug-generator: Slug creation for content pages; length, keywords, format
  • category-page-generator: E-commerce category URL hierarchy, faceted URLs
  • products-page-generator: Product URL hierarchy
  • services-page-generator: Service URL hierarchy
  • robots-txt: Clean-param for query params
  • internal-links: URL structure affects link patterns

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.