URL structure best: 10 Best Practices That Work in 2026

A URL slug tells the user and the crawler what the page contains before they read a single word. Descriptive slugs improve click through rates in search results because users scan the URL for relevance. Google's URL structure guidelines state that descriptive words in the URL help users understand the page content.

Bad: example.com/p=123 Good: example.com/site-architecture-guide

The slug should include the primary keyword naturally. Do not stuff keywords. Write for human readability first.

Short URLs perform better in search results. Google truncates long URLs in the SERP display. A truncated URL hides the keyword signal. The ideal length is under 60 characters.

Ahrefs analyzed 1 billion pages and found that short URLs tend to rank higher. The correlation is not causal on its own, but shorter URLs align with cleaner site structure. Remove stop words like "a," "the," and "and" from slugs.

Hyphens are the only word separator Google reliably parses. Underscores are not treated as separators. Spaces are encoded as percent twenty, which creates unreadable URLs.

Google's URL format recommendation explicitly endorses hyphens over underscores. Use hyphens between every word in the slug. Never use spaces or encoded characters in the URL path.

The URL path should mirror the site architecture. A page about site architecture fundamentals belongs at /site-architecture/fundamentals rather than /page/fundamentals. The directory structure tells crawlers about content relationships.

Keep directory depth to three levels maximum. Each additional directory level adds a hop in the perceived hierarchy. A URL like /level1/level2/level3/page-slug is the practical limit.

URLs are case sensitive on most web servers. Google treats /Page and /page as different URLs. This creates duplicate content problems and dilutes authority across two paths.

Moz recommends enforcing lowercase URLs at the server level with redirects. Use 301 redirects to send all uppercase variants to the lowercase canonical version. Most static site generators and CMS platforms default to lowercase slugs.

Query parameters belong on filter and search pages, not on permanent content pages. A parameter like ?id=123 or ?page=2 creates URL variants that may be treated as separate pages. Google Search Central advises using URL parameters in the parameter handling tool for large sites.

For static content, rewrite parameters into clean paths. Convert /category?id=site-architecture to /category/site-architecture.

One keyword mention in the URL is enough. Repeating the same keyword across directory segments creates redundancy. /seo/seo-tips/seo-guide contains three versions of the same keyword. The user and the crawler only need one.

Pick the primary keyword for the page. Place it in the slug. Let the directory structure handle categorization.

Even with clean URL structures, some pages will have multiple access paths. www versus non-www, http versus https, trailing slash versus no trailing slash. Set a canonical URL for every page to consolidate signals.

Google's canonicalization guide explains how to specify the preferred URL. Each variant should 301 redirect or self-reference the canonical. This prevents authority fragmentation across duplicate URL forms.

Date based URLs like /2026/04/site-architecture-guide create future maintenance problems. The content becomes stale in the URL structure. Updating the content does not change the dated path.

Evergreen content belongs in date free URLs. News and time sensitive content can use dates. For tutorials, guides, and reference pages, omit the date entirely.

Changing URL structure after launch requires 301 redirects from every old URL to its new counterpart. Broken redirect chains waste crawl budget. Mapping old URLs to new URLs before deployment prevents this.

Google's site migration guide provides the full checklist. Test the redirect map before going live. Monitor crawl errors and index coverage after the migration.

Export your full URL list from the crawler. Check every URL against the ten practices above. Flag URLs with underscores, uppercase characters, query parameters, dates, or keyword stuffing. Flag URLs longer than 60 characters. Flag URLs deeper than three directory levels.

Create a redirect plan for every flagged URL. Staged migrations are safer than bulk rewrites. Run the audit again after each migration phase.

Note the gap between your current URL profile and these ten practices. Google's URL structure documentation covers the technical requirements. Ahrefs' study on URL length and rankings provides the data. Moz's URL best practices guide adds additional nuance.

Audit quarterly.