SEO-Friendly URL Structure: Rules and Examples

Updated 2026-08-31 · 3 min read

What a good URL looks like

example.com/blog/seo-friendly-url-structure tells a person and a crawler what the page covers before it loads. example.com/p?id=8823&cat=4 tells them nothing. Descriptive URLs also earn better click-through when they appear in search results and chat previews.

Seven rules that matter

• Use lowercase only — some servers treat case as distinct URLs
• Separate words with hyphens, never underscores or spaces
• Keep slugs to 3–5 meaningful words
• Include the primary keyword once, naturally
• Drop filler stop words when they add no meaning
• Avoid dates unless the content is genuinely time-bound
• Keep folder depth shallow — two levels is plenty

Hyphens vs underscores

Google documents hyphens as word separators and underscores as word joiners, so url-structure reads as two words while url_structure can read as one. Use hyphens.

Changing an existing URL

Only rename a URL if the gain is real, because you reset its accumulated links and history. When you do, add a 301 redirect from the old path, update internal links, and resubmit the sitemap so the new URL is discovered quickly.

Site architecture comes before slugs

A slug is the last decision, not the first. Decide the shape of the site, then name the pages. A flat structure (/tools/word-counter) suits catalogues where every item competes for its own keyword. A grouped structure (/guides/seo/url-structure) suits editorial content where topical clusters help both readers and crawlers understand your coverage.

Whichever you pick, every page should be reachable from the homepage in three clicks or fewer, and every URL should be linked from somewhere. A page that only exists in the sitemap is a page search engines will treat as low priority.

Parameters, filters and duplicate content

Faceted navigation is the biggest silent generator of duplicate URLs: sorting, pagination and filter combinations can turn 50 products into tens of thousands of crawlable addresses that all show near-identical content. Crawl budget goes to those variants instead of your real pages.

• Set a self-referencing canonical on every filtered variant pointing at the clean category URL.
• Keep parameter order consistent so the same result set always produces the same string.
• Do not link to sort and view parameters in navigation; apply them with JavaScript where they add no unique content.
• Keep genuinely useful facets (a real "blue running shoes" page) as clean, indexable, linked URLs with their own copy.

Getting a migration right

URL changes lose traffic when they are done partially. A safe migration follows a fixed order: export every current URL and its traffic, map each one to exactly one destination, implement 301 redirects (never 302, never a chain of more than one hop), update every internal link to point at the new address directly, regenerate the sitemap, and only then deploy.

Afterwards, watch Search Console coverage and server logs for two to four weeks. Expect a temporary dip; a permanent one usually means redirects are missing, chained, or all pointing at the homepage instead of the equivalent page.

Non-Latin characters and internationalisation

Arabic, Cyrillic and Chinese slugs are technically valid and display correctly in modern browsers, but they percent-encode into unreadable strings when copied into emails, chat apps and analytics reports. Transliterating to ASCII keeps URLs shareable, which is why most multilingual sites use romanised slugs with the language in the path: /fr/outils/compteur-de-mots.

Whatever you choose, add hreflang annotations so search engines connect the language variants of one page instead of treating them as competitors.

A quick pre-publish checklist

Run every new URL through these checks before it goes live — all of them take seconds and each one prevents a hard-to-reverse mistake:

• Lowercase, hyphen-separated, no spaces or percent-encoded characters
• Under about 60 characters in total, with 3–5 meaningful words in the slug
• Primary keyword present once, filler words removed
• No dates or session ids unless genuinely required
• Matches the trailing-slash convention used everywhere else on the site
• Present in the sitemap, linked from at least one other page, and returning a 200 status

Generate clean slugs automatically

The Slug Generator lowercases text, transliterates accents, strips punctuation and lets you cap the word count. Pair it with the Meta Tag Generator so the title, description and canonical URL all line up.

Frequently asked questions