SEO-Friendly URL Structure: Rules That Still Matter
URLs are a small ranking factor and a large usability and maintenance factor. Their real value is stability: a URL you never have to change is a URL that keeps its links, its rankings and its bookmarks.
This guide covers the rules that still matter, the ones that no longer do, and how to change a URL when you genuinely must.
The rules worth following#
These are consistent across search engines and, more importantly, across the years — they are as much about maintenance as about ranking.
- Lower case only. Some servers treat /Page and /page as different URLs, which creates duplicates by accident.
- Hyphens between words, not underscores or camel case.
- Short and descriptive. If someone reads the URL aloud, they should be able to guess the page.
- No stop words needed: /guides/website-planning beats /guides/how-to-plan-a-website-for-your-business.
- No file extensions on content pages. /about, not /about.php — it hides the implementation and survives a migration.
- One canonical trailing-slash decision, enforced with a redirect.
- ASCII where practical; non-ASCII URLs work but become percent-encoded when copied, which is ugly and error-prone.
The single most valuable property is stability. A slightly imperfect URL that never changes is worth more than an optimised one that changes twice.
What no longer matters much#
Several long-standing beliefs about URLs have limited effect today, and following them can actively hurt.
| Belief | Reality |
|---|---|
| Exact-match keyword URLs rank better | Marginal at best; stuffing looks spammy |
| Deep folder structure signals hierarchy | Click depth matters, path depth barely does |
| Dates in URLs help freshness | They make evergreen content look stale |
| Shorter is always better | Descriptive beats terse; /p/4821 helps nobody |
| Subdomain versus subfolder is decisive | Subfolders are simpler to manage; either can work |
| Query strings cannot be indexed | They can, but they multiply duplicates — prefer clean paths |
Multilingual URL patterns#
For a site in several languages, the URL pattern is one of the hardest things to change later, because it interacts with hreflang, canonicals and every redirect you will ever write.
| Pattern | Example | Trade-off |
|---|---|---|
| Subdirectory | site.com/de/guides | Simplest; one domain accumulates all authority |
| Subdomain | de.site.com/guides | Cleaner separation; more setup, split signals |
| Country domain | site.de/guides | Strongest local signal; a separate site to run |
| Parameter | site.com/guides?lang=de | Avoid — weak signals and duplicate risk |
Whichever you choose, decide separately whether the slug itself is translated. Translating slugs helps local relevance; keeping them identical is simpler to maintain. Both are defensible — changing your mind afterwards is not.
Changing a URL without losing traffic#
Sometimes a change is genuinely necessary. The procedure is mechanical, and skipping any step is where the traffic goes.
- Confirm it is worth it. A URL change always costs something; an incremental wording improvement rarely pays it back.
- Map old to new, one to one. Every old URL gets a specific destination, not a category page.
- Implement 301s, not 302s, and verify each one returns a single hop.
- Update internal links to point at the new URL directly. Do not rely on your own redirects.
- Update the sitemap, and leave the redirects in place indefinitely — external links never get updated.
- Watch Search Console coverage and your top-page report for four to six weeks.
- Expect a dip, and investigate only if it is still deepening after a month.
Frequently asked questions
Should I include keywords in URLs?
Include the words that describe the page, which usually are the keywords. What you should not do is stuff variants: /website-development-services-cheap-website-development is worse than /website-development-services in every way, including for the humans who see it in search results.
Subdomain or subfolder for a blog?
Subfolder, in most cases. site.com/blog is simpler to manage, shares the domain’s accumulated signals, and needs no separate technical setup. Subdomains make sense when the section is genuinely a separate application, has a separate team, or must run on different infrastructure.
How long should I keep old redirects?
Indefinitely. They cost almost nothing to keep and external links to your old URLs will never be updated. What you should do is periodically collapse chains created by successive migrations, so every old URL points directly at the current destination in a single hop.
Do URL parameters hurt SEO?
They are not harmful in themselves, but they multiply near-duplicate URLs quickly — sorting, filtering and tracking parameters can generate thousands of variants of one page. Use clean paths for anything you want indexed, and canonicalise or noindex the parameter variants.
seo friendly urlurl structurepermalinksurl best practicesmultilingual urlsurl redirects
