url-structure

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," "s...

Security Scan

The skill's instructions match its stated purpose (URL structure/SEO) and it requests no credentials or installs, but it tells the agent to read local project-context files that are not declared in the metadata — a small mismatch worth noting before use.

Purpose & Capability

Name, description, and SKILL.md content all focus on URL structure and SEO best practices. There are no unrelated required binaries, environment variables, or install steps — the requested capabilities align with the stated purpose.

Instruction Scope

The runtime instructions explicitly tell the agent to 'read' project context files (.claude/project-context.md or .cursor/project-context.md) if they exist to gather site structure. That file access is reasonable for site-specific recommendations, but the SKILL.md references local project files that are not declared in the skill's metadata (required config paths). Any instruction that reads local files should be called out in the metadata so users know what will be accessed. Otherwise the instructions are scoped to URL analysis and related SEO tasks and do not direct data to external endpoints beyond included benign references.

Install Mechanism

Instruction-only skill with no install spec and no code files. This is the lowest-risk install mechanism — nothing is written to disk by an install step.

Credentials

The skill requests no environment variables, credentials, or external config paths in its metadata. However, the SKILL.md does instruct reading local project files for context. While these files are relevant to the skill's purpose, the access is not declared in requires.config or similar metadata, creating a minor proportionality/documentation mismatch.

Persistence & Privilege

always is false, the skill has no install step, and it does not request persistent system privileges or modify other skills or system-wide settings. Autonomous invocation (disable-model-invocation: false) is the platform default and is not in itself a new risk here.

What to consider before installing

This skill appears to do what it says — SEO-focused URL structure advice — and it does not require credentials or install anything. Before enabling it: (1) Inspect any local project-context files (.claude/project-context.md, .cursor/project-context.md) the skill would read and remove or sanitize sensitive data; (2) If you want explicit guarantees, ask the skill author to declare those config paths in the skill metadata so file access is transparent; (3) If you run agents on sensitive codebases, test the skill in a non-sensitive environment first; (4) Note the skill references other related skills (url-slug-generator, canonical-tag) — those are not installed automatically, so check how/when the agent will call them. If you are comfortable with the skill reading project-context files for tailored advice, the risk is low; if not, avoid installing or remove/sanitize those files first.

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

Principle	Guideline
Readable	Use words, not IDs; /blog/seo-guide not /p/12345
Short	Shorter is generally better; avoid unnecessary depth
Keyword	Include target keyword when natural
Lowercase	Use lowercase; avoid mixed case
Hyphens	Use hyphens to separate words: seo-guide
Avoid	Special chars, query params for core content, session IDs

Hierarchy

Pattern	Example	Use
Flat	/page-name	Simple sites
Category	/blog/post-name, /tools/tool-name	Content sites
Nested	/category/subcategory/page	Deep hierarchies (keep shallow)

Multi-language

Pattern	Example
Path prefix	/zh/page, /en/page
Subdomain	zh.example.com, en.example.com
ccTLD	example.cn, example.com

Static vs Dynamic vs Pseudo-Static URLs

Type	Example	Use
Static	/blog/seo-guide	Direct file; best SEO; content stable
Dynamic	/product?id=123	Program-generated; avoid for indexable content
Pseudo-static	/blog/seo-guide (rewritten from .php)	Combines both; common in CMS
Rule	Prefer 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

Scenario	Approach
UTM / tracking	Canonical to base URL; params in query string only
Search results	Canonical to search page; avoid indexing result URLs
Filters / sort	Canonical to base; or robots-txt Clean-param
Session IDs	Use cookies; never in indexable URLs

Use Cases

Scenario	Focus
New site	Plan hierarchy upfront; avoid later restructuring
Migration	301 mapping; canonical; see canonical-tag
Large site	Dynamic URLs, params, multi-language — canonical + robots
SEO audit	Check structure, params, canonical consistency

Common Issues

Issue	Fix
Long URLs	Shorten; remove redundant words
Dynamic params	Use canonical; clean params in robots (Yandex Clean-param)
Mixed case	Redirect to lowercase
Changed URLs	301 redirect old to new

Output Format

• URL structure recommendation
• Slug conventions
• Hierarchy for key content types
• Redirect plan if changing URLs
• References: Alignify URL optimization; Google URL guidelines

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