url-architecture

Structure clean URLs and manage 301 redirects for site architecture.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ikastner/skills-larockette --skill url-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: url-architecture
Source: https://github.com/ikastner/skills-larockette/tree/main/40-qa-performance/url-architecture
Command: npx skills add https://github.com/ikastner/skills-larockette --skill url-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a clear framework to structure URLs, enforce 301 redirects during site refactors, establish naming conventions, and generate a sitemap XML to improve SEO and site maintainability.

Core Features & Use Cases

  • URL structuring: enforce lowercase, dash-separated paths that reflect site hierarchy.
  • 301 redirection planning: plan and implement permanent redirects for refactors, domain changes, and content removals.
  • Sitemap & configuration: guide sitemap generation and Next.js configuration to ensure SEO-friendly indexing.
  • Use Case: When migrating a site or restructuring navigation, apply these conventions to keep URLs consistent and preserve link equity.

Quick Start

Configure your Next.js site to use lowercase, dash-separated URLs, implement 301 redirects for refactors, and generate a sitemap XML after every build.

Frequently Asked Questions about url-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure clean URLs for a Next.js site migration?

Structure clean URLs by enforcing lowercase, dash-separated paths that reflect the site hierarchy. This convention keeps navigation consistent across marketing, product, and documentation sites during a refactor.

How do I implement 301 redirects when refactoring site navigation?

Implement 301 redirects by planning permanent redirection rules for refactors, domain changes, and content removals. This preserves link equity and prevents users from hitting dead ends after restructuring.

Does this URL architecture approach work for marketing and documentation sites?

Yes, the URL architecture conventions apply across marketing, product, and documentation sites. It adapts naming conventions and Next.js configuration to suit different site types.

What's the best way to configure Next.js for SEO-friendly URLs and sitemaps?

Configure your Next.js site by setting lowercase dash-separated URLs, implementing 301 redirects for refactors, and generating a sitemap XML after every build to ensure SEO-friendly indexing.

When do I need to plan 301 redirects for a site refactor?

Plan 301 redirects when migrating a site, restructuring navigation, changing domains, or removing content. This enforces permanent redirects that preserve link equity and maintain site maintainability.