url-routing-seo

Design SEO-friendly URL structures and metadata for Next.js and Laravel apps.

2|1|Updated Jan 20, 2026

Search Tags:#routing #nextjs #laravel #canonical #seo #open-graph #slugs

Ready to run

npx skills add https://github.com/sraloff/gravityboots --skill url-routing-seo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: url-routing-seo
Source: https://github.com/sraloff/gravityboots/tree/main/.agent/skills/url-routing-seo
Command: npx skills add https://github.com/sraloff/gravityboots --skill url-routing-seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing scalable, SEO-friendly URLs and accurate metadata to improve search visibility and user navigation.

Core Features & Use Cases

URL Structure: Use kebab-case slugs, balanced hierarchy, and consistent trailing slash handling to avoid duplicate content and improve crawlability.
SEO Tags: Ensure unique title tags, meta descriptions, canonical references, and Open Graph metadata to optimize social sharing.
Implementation: Guidance for Next.js and Laravel projects to apply routing and SEO standards across pages.

Quick Start

Configure routes with kebab-case slugs, enforce consistent trailing slashes, and implement canonical and Open Graph metadata.

Frequently Asked Questions about url-routing-seo

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

FAQPage Schema

How do I create SEO-friendly URL routing for dynamic content in Next.js?▼

To create SEO-friendly URL routing in Next.js, use kebab-case slugs, maintain a balanced hierarchy, and enforce consistent trailing slash handling to avoid duplicate content. You also need to generate unique titles, meta descriptions, canonical URLs, and Open Graph metadata for each dynamic page.

Why does inconsistent trailing slash handling cause duplicate content issues?▼

Inconsistent trailing slash handling causes duplicate content issues because search engines treat URLs with and without a slash as separate pages. Enforcing consistent trailing slash behavior across your routing structure resolves this by consolidating link equity into a single canonical URL.

Can I use this routing and canonical guidance for a Laravel application?▼

Yes, you can apply this routing and canonical guidance to Laravel applications. The approach supports implementing kebab-case slugs, hierarchical routing, trailing slash consistency, and on-page SEO metadata for dynamic content across both Laravel and Next.js projects.

What's the best way to implement canonical tags and Open Graph metadata for dynamic routes?▼

The best way to implement canonical tags and Open Graph metadata for dynamic routes is to generate them dynamically based on your content data. Ensure each page receives a unique canonical URL to prevent duplicates, and populate Open Graph metadata to optimize social sharing previews.

When do I need canonical URLs for hierarchical routing structures?▼

You need canonical URLs for hierarchical routing structures when multiple valid paths can reach the same dynamic content. Canonical tags resolve ambiguity by defining the primary URL, ensuring search engines index the correct page and preserve your crawl budget.