Guides URL structure optimization for SEO: readability, hierarchy, and best practices.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionurl-structureExecute the skills CLI command in your project's root directory to begin installation:
Fetches url-structure from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate url-structure. Access via /url-structure in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site structure.
Identify:
| 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 |
| 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) |
| Pattern | Example |
|---|---|
| Path prefix | /zh/page, /en/page |
| Subdomain | zh.example.com, en.example.com |
| ccTLD | example.cn, example.com |
| 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) |
.html, .php, .aspx — keeps URLs technology-agnostic, shorter, easier to refactor/seo-guide not /seo-guide.html| 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 |
| 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 |
| 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 |
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
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
kostja94/marketing-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend url-structure for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
url-structure has been reliable in day-to-day use. Documentation quality is above average for community skills.
url-structure fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in url-structure — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: url-structure is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for url-structure matched our evaluation — installs cleanly and behaves as described in the markdown.
url-structure is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend url-structure for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: url-structure is focused, and the summary matches what you get after install.
Keeps context tight: url-structure is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 49