An SEO-friendly URL is a web address that uses readable words to describe its page, separates those words with hyphens, avoids unnecessary parameters, and stays consistent in format. Each trait comes from Google’s URL guidance.
Google sets no 60-character limit; its Search Advocate John Mueller says length doesn’t matter for ranking. Removing stop words is a style convention, and Google has no rule on it. Keywords in a URL do count, though only a little: Google says they have “hardly any effect” beyond appearing in breadcrumbs.
What makes a URL SEO-friendly
An SEO-friendly URL is one a person can read and understand before clicking, and a search engine can crawl without confusion. It names the page in plain words, uses hyphens between words, avoids session IDs and tracking parameters, and points to a single version of the page.
Compare two addresses for the same page:
https://example.com/wiki/Aviationhttps://example.com/index.php?topic=42&area=3a5ebc944f41daa6f849f730f1
Both come from Google’s URL structure guide, which recommends the first: “use readable words rather than long ID numbers.”
A URL has a few parts. In https://j6venture.com/blogs/seo-friendly-url/, the protocol is https, the domain is j6venture.com, the folder is /blogs/, and seo-friendly-url is the slug: the part that identifies this specific page. When people talk about “optimizing a URL,” they almost always mean the slug and the folders in front of it.
That narrows the job. Most of the decisions in this guide come down to the words you put in the slug and the folders you place before it.
How to create an SEO-friendly URL: 7 rules Google documents
Google’s documentation covers seven practical rules. Each one targets readability, crawlability, or a single clean address per page.
- 1Use readable, descriptive words. Google recommends “readable words rather than long ID numbers” (URL structure guide). Its SEO Starter Guide adds that parts of the URL can appear in search results as breadcrumbs, so readable words help searchers judge whether a result is useful.
- 2Use your audience’s language. If your readers search in German, use German words in the URL (Google). Percent-encode non-ASCII characters in links (Google).
- 3Separate words with hyphens. Google recommends hyphens “as it helps users and search engines better identify concepts in the URL,” and advises against joining words together (
greendress). It also doesn’t recommend underscores, which are commonly used to keep concepts together (Google). - 4Use as few parameters as you can. Trim parameters that don’t change the content, such as session IDs and referral tags (Google). Every extra combination creates another URL for Google to crawl, which is how crawl budget gets wasted on large sites.
- 5Pick one letter case and stick to it. Google treats
/APPLEand/appleas different URLs. If your server treats them the same, convert everything to one case (Google). Lowercase is the easiest standard to keep. - 6Don’t use
#fragmentsto change content. Google generally doesn’t support URL fragments, so content loaded atexample.com/#/potatoesmay not be seen as its own page. For JavaScript sites, Google suggests the History API (Google); our guide to JavaScript SEO covers what else Googlebot does and doesn’t render. - 7Keep each page at one address. Google’s SEO Starter Guide says to “ensure that each piece of content on your site is only accessible through one individual URL.” Point duplicates to one canonical version with redirects or
rel="canonical"(more on this below).
Read together, these rules serve two goals: a URL people can read and one address per page. Google documents them as good practice, and the next section separates them from popular advice that has no such support.
Fact or folklore? Common URL advice, checked
Many popular URL rules are readability conventions, and Google’s statements give them little or no ranking weight. Google’s John Mueller has said URL length and the number of slashes don’t matter for ranking. The only role for length Mueller knew of is choosing which duplicate becomes canonical, and Google’s own guide gives URL keywords only a tiny role.
How long should a URL be? There’s no length limit for ranking; Mueller says he personally keeps URLs under 1,000 characters “just to make monitoring easier.”
| Common advice | Verdict | What the evidence says |
|---|---|---|
| Prefer hyphens to underscores | Google-documented | Google recommends hyphens and explicitly doesn’t recommend underscores (URL structure guide). It describes no penalty for them. |
| Prefer readable words to IDs | Google-documented | “Use readable words rather than long ID numbers” (Google). |
| Keep the same case everywhere | Google-documented | URLs are case sensitive to Google (Google). |
| Put your keyword in the URL to rank | Tiny effect | “From a ranking perspective, the keywords in the name of the domain (or URL path) alone have hardly any effect beyond appearing in breadcrumbs” (SEO Starter Guide). Use the topic’s words because they help readers; the ranking gain is negligible. |
| Keep URLs under 60 (or 75) characters | Myth for ranking | “The URL length doesn’t matter. We use URLs as identifiers” (John Mueller, Google Search Central, quoted by Search Engine Journal). The only place Mueller knew of where length plays a role is canonicalization, where “a shorter and clearer URL” tends to be picked, and he added that “this does not affect ranking.” |
| URLs over 60 characters get 15% fewer clicks | Unsupported | This figure circulates on agency blogs; Justwords, for example, attributes it to “a 2025 Stan Ventures study.” We could not find the study or its method. Treat it as unverified. |
| Fewer folders rank better | Myth for ranking | “The number of slashes in there also doesn’t matter” (Mueller, same answer). Internal links determine how easily a page is found; folder depth doesn’t. On large sites, folders can still help Google learn how often each section changes (SEO Starter Guide). |
| Remove stop words (a, the, of) | Convention | No Google guidance either way. Removing them makes slugs shorter and easier to scan; keep them when removing one changes the meaning. |
| Don’t put dates in URLs | Convention | No ranking effect documented. Dates make evergreen content look stale and tempt you to change the URL when you update the post, so leave them out unless the date is the point (news, annual reports). |
| Use subdirectories over subdomains | Business choice | “From a business point of view, do whatever makes sense for your business” (SEO Starter Guide). |
| Duplicate URLs cause a penalty | Myth | Content reachable at multiple URLs is “inefficient, but it’s not something that will cause a manual action” (SEO Starter Guide). Google still has to choose one version, and may not pick yours, so consolidate them. |
Real sites that break the “rules” and rank anyway
- Wikipedia uses underscores:
en.wikipedia.org/wiki/List_of_HTTP_header_fields. - YouTube uses an ID parameter for every video:
youtube.com/watch?v=WmEpP9aPq8o(the video in which Google says URL length doesn’t matter). - Search Engine Journal adds a numeric ID to its slugs:
/does-url-length-affect-seo/425230/. - Search Engine Land does the same:
/seo-friendly-urls-what-you-need-to-know-457531.
These examples show that unconventional URLs aren’t fatal. They can’t show how much URL format helps, because these sites carry many other strong signals. For the size of the effect, rely on Google’s own statements above: hardly any for keywords, none for length. That makes URL work mostly hygiene: it helps readers and prevents duplicate URLs.
Why AI answers repeat the folklore
When we searched Google AI Mode for “seo friendly url” on October 5, 2026 (US settings), it told us to keep “the full URL under 60 characters,” said folder depth matters because “search engines favor pages closer to the root domain,” and said URL keywords give “a minor ranking signal” that “helps increase your organic click-through rate.” The first two have no support in Google’s documentation, and we found no evidence for the click-through claim.
The lead sources shown for those lines were a web agency (Americaneagle.com), a URL-shortener company (Bitly), and a YouTube video; Google’s own documentation was cited only on the hyphens point. AI answers summarize what the web repeats, so a rule can sound authoritative because many pages copy it. Check important rules against Google’s documentation.
SEO-friendly URL examples: before and after
The fixes that matter most are removing IDs and parameters, choosing readable words, and keeping one consistent pattern. Shorter URLs usually follow as a side effect.
| Page type | Before | After | What changed |
|---|---|---|---|
| Blog post | /blog/?p=4521 |
/blog/email-follow-up-templates/ |
Readable words replace an ID |
| Blog post (title-generated) | /blog/here-are-the-12-best-email-follow-up-templates-for-2026/ |
/blog/email-follow-up-templates/ |
No year (the post will be updated), no filler |
| Product | /product.php?id=00291&color=blue&ref=homepage |
/shoes/trail-running-shoe-blue/ |
Referral parameter removed; product named |
| Category | /cat?c=12&sort=price_asc |
/shoes/trail-running/ |
Sort order stays a parameter, but the indexable page is clean |
| Service page | /services/Services_SEO_Services/ |
/services/technical-seo/ |
One case, hyphens, and no repeated words |
| Location page | /locations/loc_7/ |
/locations/austin/ |
City name replaces an internal code |
| Help article | /help/#/article/how-to-reset |
/help/reset-password/ |
Content moves from a fragment to its own URL |
| Campaign link | /pricing?utm_source=newsletter&utm_medium=email |
/pricing/ (canonical) |
Tracking stays in links you share; the canonical points to the clean URL |
| Multilingual page | /de/products/peppermint/ |
/de/produkte/pfefferminz/ |
Words in the audience’s language, as Google recommends |
| Too vague | /guide/ |
/seo-audit-guide/ |
The slug names what the page covers |
All “before” and “after” URLs are illustrative. Apply the same reasoning to your own templates and write slugs that fit your pages.
Set a URL pattern your CMS will keep
Decide the pattern before you publish at scale, because every later change means redirects. Each platform fixes some parts of the URL and leaves others to you:
- Folders: group content to mirror how your site is organized; Mueller says folder depth doesn’t affect ranking. On sites with more than a few thousand URLs, Google’s SEO Starter Guide says grouping topics in directories “can help Google learn how often the URLs in individual directories change,” so a
/promotions/folder can be crawled more often than/policies/. - WordPress: set Settings > Permalinks to “Post name” so URLs use words in place of
?p=123, and edit the auto-generated slug before publishing, since it copies the full title. - Shopify: the
/products/,/collections/, and/pages/prefixes are fixed, so put your effort into the handle after them. - Webflow: each CMS collection gets its own folder, such as
/blog/. Set it before the first item goes live, since renaming it later changes every URL in the collection.
The common thread: the defaults you accept at launch become the URLs you maintain for years. A few minutes on settings and slugs now can save a redirect project later.
Duplicate URLs: parameters, letter case, trailing slashes, and canonicals
Duplicate URLs arise when one page answers at several addresses, such as http and https, www and non-www, with and without a trailing slash, in two letter cases, or with tracking and sort parameters. Google won’t penalize you for this. It picks one version as canonical and consolidates signals like links into it. If you don’t state a preference, Google chooses for you, and it may not choose the URL you want. On large sites, duplicates also waste crawling.
Google lists three ways to tell it which version you prefer, in order of strength (consolidating duplicate URLs):
| Method | Strength | Use it when |
|---|---|---|
| Permanent redirect (301 or 308) | Strong | You want the duplicate URL gone, for example http to https, or www to non-www |
rel="canonical" link |
Strong | Both URLs need to keep working, for example filtered or tracked versions of a page |
| Sitemap inclusion | Weak | Supporting signal on large sites; list only the canonical versions |
Google notes that these signals stack, so using two together increases the chance your preferred URL appears in results. It also recommends a self-referencing canonical on the canonical page itself, and warns against giving different canonicals through different methods for the same page.
Three checks catch most duplicate problems:
- 1Protocol and host: do
http://,https://,www., and the bare domain all end at one version through a permanent redirect? - 2Trailing slash and case: do
/pricing,/pricing/, and/Pricing/all resolve to one URL? - 3Parameters: do pages with
?utm_,?sort=, or?ref=carry a canonical pointing to the clean URL?
For large stores with filters, Google’s guide on faceted navigation covers how to stop filter combinations from creating thousands of crawlable URLs. Since duplicates carry no penalty, these checks are about control: they decide whether Google shows the URL you chose.
Should you change an existing URL?
Usually not. If a page already ranks, has backlinks, or is shared in emails and documents, changing its URL for cosmetic reasons swaps a small readability gain for real risk. In the same answer about length, Mueller advises “a URL structure that works for you and which you can keep for the long run.”
Leave it alone when the flaw is cosmetic (extra words, an old pattern, an underscore) or the real problem is the page itself, such as thin content or weak internal links.
Change it when the current pattern creates duplicate URLs, the page’s purpose has changed, a #fragment or session ID stops it being indexed, or you’re migrating a whole section to one structure.
How to change a URL safely
If a change is justified, put most of your care into the redirect; the new slug is the easy part.
- 1Use a permanent redirect (301 or 308) at the server. Google treats a permanent redirect as a signal that the new URL should be shown in results; temporary redirects (302, 307) usually keep the old URL showing (Google on redirects).
- 2Map each old URL to its closest equivalent. Google warns that redirecting many old URLs to one irrelevant destination, such as the homepage, may be treated as a soft 404 (site moves guide).
- 3Redirect in one hop. Googlebot follows up to 10 hops, but Google advises redirecting to the final destination directly and keeping any chain “ideally no more than 3” (site moves guide).
- 4Keep the redirects. Google says to keep them for as long as possible, generally at least a year, and to consider keeping them indefinitely for users (site moves guide).
- 5Update everything you control: internal links, navigation, the canonical tag on the new page, and your sitemap, so every signal points to the new URL.
- 6Check it live. Request the old URL and confirm the first response is a 301 or 308 and the destination returns 200. Then watch the Page indexing report in Search Console, and traffic, over the following weeks.
If you’re changing many URLs at once, the site audit framework helps you sort which issues are worth fixing first.
Do URLs matter for AI search?
We found no evidence that URL formatting affects whether AI tools cite a page. Dan Taylor of SALT.agency, writing in Search Engine Land, looked at 3,123 URLs cited in Google AI Mode across 580 travel, ecommerce, and SaaS queries. He found an average length (excluding the domain) of 53 characters, against 52 for the regular blue-link results for the same queries (Search Engine Land). On length, at least, cited URLs looked the same as ordinary search results; the study didn’t test other URL traits.
Permanence protects AI citations. A citation that points to a URL you later change or delete becomes a broken link unless you redirect it; Taylor’s piece makes the same case, noting that AI tools often cite URLs that later return 404 errors. Some AI tools also show the URL beside a citation, so a readable one helps people decide whether to click. Choose a clear URL once and keep it.
With no evidence that URL format drives citations, content is the likelier lever; see how to improve your odds of getting cited by ChatGPT.
A quick checklist before you publish
Run each new URL through these seven checks. Together they cover readability, a single address, and a slug that survives future updates.
- The slug names the page in plain words your audience would use
- Words are separated by hyphens; one letter case throughout
- No session IDs, referral tags, or
#fragments in the indexable URL - No date, unless the date is the point of the page
- The page answers at one address; other versions redirect or carry a canonical
- The slug still makes sense if you update the post next year
- If this replaces an old URL: a one-hop 301 or 308 kept for at least a year, plus updated internal links and sitemap
J6 Venture helps brands rank on Google and get cited in AI answer engines. If you’re planning a migration or a URL restructure and want to keep your rankings, book a strategy session.