- An SEO-friendly URL is short, readable, lowercase, uses hyphens between words and describes the page.
- Google says to use simple, descriptive words in URLs (Search Central URL structure guidance, checked November 2026).
- URLs are a small ranking signal; they mainly matter for clarity and clicks, so do not overclaim them.
- Only change an existing URL with a one-hop 301 redirect, then update internal links, canonicals and the sitemap.
An SEO-friendly URL is short, readable, lowercase, uses hyphens between words and describes what the page is about. Google's own URL structure guidance (checked November 2026) says to use simple, descriptive words, so a URL should read like the page's topic, not a string of IDs or numbers.
This guide covers what makes a good URL, with good versus bad examples, whether URLs affect rankings, subfolders versus subdomains, and how to change URLs safely with one-hop 301 redirects.
What is an SEO-friendly URL?
An SEO-friendly URL is easy for both people and search engines to read. It is short, all lowercase, uses hyphens to separate words, and says what the page is about before anyone clicks.
- Short. Fewer words are easier to read, copy, share and remember.
- Readable. Use real words, not IDs like
p=12345orid=abc-99. - Lowercase. Mixed-case URLs can be treated as different addresses by some servers.
- Hyphens between words. Use
seo-friendly-urls, notseo_friendly_urlsorseofriendlyurls. - Descriptive. The URL alone should suggest the page's topic.
Google's URL structure guidance says a site's URL structure should be simple and use descriptive words, because URLs appear in search results and help people decide whether to click.
Do URLs affect rankings?
URLs are a small ranking signal, not a major one. They mainly matter for clarity and clicks: a readable URL reassures searchers and gets clicked more, and descriptive words in the URL give Google a light topic clue. Do not overclaim them — content, links and indexing still matter far more than the words in a URL.
Keywords in a URL can help a little, but stuffing a URL full of keywords looks spammy and does not help. Use the main keyword naturally when it fits, and write the URL for a reader first.
URL best practices
These are the habits that separate good URLs from bad ones. The table contrasts a good URL with a common bad alternative.
| Good | Bad | Why |
|---|---|---|
/blog/seo-friendly-urls | /blog/seo_friendly_urls | Google treats hyphens as word separators; underscores are not, so hyphens are clearer for readers and search engines. |
/blog/url-structure | /blog/URL-Structure | Keep URLs lowercase; mixed case can be treated as separate addresses and is harder to type. |
/blog/url-structure | /blog/p?id=12345&session=abc | Drop session IDs and needless parameters; they create ugly, duplicative URLs that look broken to searchers. |
/blog/url-structure | /blog/cat/subcat/item/url-structure | Keep folder depth shallow; deep nesting buries pages and makes URLs long and hard to manage. |
/blog/url-structure | /blog/the-best-url-structure-guide-tips | Include the main keyword naturally; do not stuff every related keyword into the slug. |
/blog/url-structure | /blog/2024/01/15/url-structure | Leave dates out of evergreen URLs; they age the page and make it look outdated even when the content is fresh. |
Subfolders versus subdomains?
Use subfolders unless you have a specific reason for a subdomain. example.com/blog/ keeps authority and signals within one site, while blog.example.com can be treated as a separate site. The choice is mostly neutral for rankings, so pick what fits your setup and stay consistent — do not move content between them without a redirect plan.
Should you change existing URLs?
Only change an existing URL when you have a real reason, such as a rebrand, a migration or fixing a badly broken structure. Changing URLs for a small keyword tweak is usually not worth the risk.
If you do change a URL, do it safely:
- Set up a one-hop 301 redirect from the old URL directly to the new URL. Avoid redirect chains and loops.
- Update internal links across your site to point at the new URL.
- Update canonicals so the new URL is the self-referencing canonical.
- Update the sitemap to list the new URL and remove the old one.
Read more about choosing the right redirect in the 301 vs 302 redirects guide. A permanent move uses a 301; a temporary change uses a 302.
URL parameters and duplicates
Parameters such as tracking IDs, sort options and session tokens create duplicate URLs for the same page. Decide which URL is canonical and consolidate the variants so signals are not split.
Use a canonical tag on parameterised URLs pointing at the clean version, or redirect redundant parameters. See the canonical tags guide for how to pick and keep one canonical, and the duplicate without user-selected canonical guide when Google has picked a version you did not choose.
Questions and answers
SEO-friendly URL structure questions
Should I use hyphens or underscores in URLs?
Hyphens. Google treats hyphens as word separators, so seo-friendly-urls reads as separate words; underscores do not separate words the same way. Always use hyphens between words in a URL.
How long should a URL be?
As short as possible while still describing the page. There is no hard limit, but shorter URLs are easier to read, copy, share and remember, and they show better in search results.
Should I remove stop words from URLs?
Only if it keeps the URL short and still clear. Drop words like "the" or "a" when they add nothing, but do not strip so much that the URL loses its meaning.
Can I change a URL after publishing?
Yes, but only with a one-hop 301 redirect from the old URL to the new one, then update internal links, canonicals and the sitemap. Do not change URLs for a tiny keyword tweak.
Do dates belong in evergreen URLs?
No. Dates age a page and can make fresh content look outdated. Leave dates out of evergreen URLs and keep the slug timeless.
Sources
- URL structure — Google Search Central, on simple descriptive words in URLs


