Skip to content
EN · ₺
Panel Login Buy Package
Technical SEO

SEO-Friendly URL Structure: Rules, Examples, Mistakes

6 min read

An SEO-friendly URL structure means that your page addresses are clear, consistent and permanent for both visitors and search engines. A URL alone will not take you to the first position; but a poorly designed structure leads to crawl waste, duplicate addresses and a site that is difficult to manage. In this article we cover the rules you can apply when building a new site or organizing existing addresses, along with examples and the risks to watch for when making changes.

Why does URL structure matter?

A URL serves three functions. First, it is the unique identifier of the page for Google: if the same content lives at different addresses, signals get split. Second, it gives users context in the search results and in the address bar; a clear address builds trust. Third, it reflects the architecture of your site: folders show topic groups.

Google's own guidance also recommends simple, readable addresses and says that unnecessarily long, parameter-heavy addresses can lead to crawling problems. Let us clarify one detail from the start: putting a keyword into the URL is a very light hint; the real gain comes from a tidy structure that does not produce duplicate content.

Anatomy of a URL

PartExampleSEO note
Protocolhttps://The entire site should be https; for details, see our HTTPS and SEO article
Domain / subdomainwww.ornek.comChoose one version, www or non-www, and redirect the other with a 301
Path (folders)/blog/seo/Reflects the topic hierarchy
File name (slug)url-yapisiShort, readable, containing the keyword
Parameter?sort=priceAvoid using them in content addresses where possible
Fragment#sonucAn on-page link; Google does not count it as a separate page

Rules for an SEO-friendly URL

  1. Keep it short and descriptive. Describe the topic of the page in 3–5 words. /seo-friendly-url-structure is good; /post?id=48213 says nothing.
  2. Use lowercase letters. Many servers treat uppercase and lowercase as different addresses; /AboutUs and /aboutus can be two separate pages.
  3. Separate words with hyphens. Google recognizes the hyphen (-) as a word separator; there is no such guarantee for the underscore (_).
  4. Simplify special characters. Replace accented letters with their plain Latin equivalents (for example the dotless i, s-cedilla, g-breve, u-umlaut, o-umlaut and c-cedilla, converted to plain i, s, g, u, o and c). Even though the percent-encoded form works technically, it looks broken and long when shared.
  5. Drop unnecessary words. Words like "and", "for" or "how to" can be shortened if they do not change the meaning; but do not produce a meaningless slug either.
  6. Do not embed dates or numbers in the address. /2024/11/seo-tips looks outdated once the content is updated. For evergreen content, an undated address is healthier.
  7. Think of the address as permanent. Every change means a redirect and a risk.
  8. Fix a trailing slash rule. Only one of /page and /page/ should be valid; the other should be redirected with a 301.

Note: Do not bloat the slug just to fit a keyword into the URL. Repetitive addresses such as /seo-what-is-seo-seo-guide look bad and bring no benefit. A single natural phrase is enough.

Good and bad examples

BadGoodWhy
/index.php?p=124&cat=3/blog/url-structureReadable, stable, tells the topic
/Blog/SEO_Friendly_URL/blog/seo-friendly-urlLowercase, hyphens
/blog/2025/11/20/how-should-a-url-structure-be-for-seo-and-what-to-consider/blog/url-structureLong and unnecessary; dated
/category/shoes/men/sport/running/black/size-42/mens-running-shoesExcessively deep hierarchy
/product?id=881&session=a8f2/product/running-shoes-xA session parameter creates endless addresses

When choosing a slug for a new page, you can run a practical test: read the address aloud over the phone to someone who has never seen it. If the listener can type it as they heard it and guess what the page is about, the slug is doing its job. Set the "permalink" format in your software or CMS settings before entering any content; changing it later requires redirects.

Folder hierarchy and site architecture

The URL reflects your site's architecture outwards. A good hierarchy tells both users and search engines "under which topic this page sits":

  • Keep it shallow. Important pages should be reachable from the home page in as few clicks as possible. A depth of three to four folders is more than enough for most sites.
  • Group sensibly. Create clear sections such as /blog/, /products/, /services/.
  • Keep folders and internal links aligned. If the URL hierarchy says one thing and the navigation says another, confusion follows. For a plan of internal links, take a look at our internal linking strategy article.
  • Use breadcrumbs. Aligning them with the folder structure makes it easier for users to understand where they are.

A hierarchy is not mandatory: some sites keep all pages at the root directory (/url-structure) and this causes no problem. What matters is that the structure you choose is consistent.

Parameters and filters

Especially on e-commerce and listing sites, filter, sorting and session parameters generate hundreds of address variations of the same content. The consequences: wasted crawl budget, duplicate content signals and diluted ranking strength. Ways to solve this:

  • For parameters that do not change the content (session IDs, tracking tags), point the canonical to the clean address.
  • Move filter pages that carry a genuinely separate search value (for example "men's running shoes") from parameters to a clean, indexable address.
  • Do not offer endless combinations without value as links on the site; if necessary, limit them with noindex or robots.txt.
  • Make sure tracking parameters do not appear in your site's internal links.

On large sites this topic is directly tied to crawl efficiency; for details, see our crawl budget article.

Subfolder or subdomain? Multilingual addresses

You can place a blog, a store or another section either in a subfolder of the main site (ornek.com/blog/) or on a subdomain (blog.ornek.com). Google can crawl and index both; however, subdomains sometimes have to be monitored and managed as separate sites. Unless there is a technical requirement, keeping content sections in a subfolder of the main domain is usually simpler and easier to manage. A subdomain makes sense when there is a separate application, different infrastructure or an independent team.

The same logic applies to multilingual sites: subfolders such as /en/ and /de/ for languages are a practical solution for most sites. Whichever path you choose, stay consistent and point the language versions to one another correctly; for details, see our hreflang tag guide. Changing the language only through a cookie or browser setting while showing different content at the same address makes it harder for Google to see the language versions; each language should have its own address.

Changing existing URLs

Changing addresses on a working site is a ranking risk. Outside the situations below, it is usually safer not to touch them:

  • The addresses consist of incomprehensible parameters and you want to move to a clean structure.
  • The same content lives at several addresses.
  • The site architecture is changing completely or the platform is being migrated.

If you decide to change them, follow this order:

  1. Prepare a table matching the old and new addresses.
  2. Set up a single-step 301 redirect from each old address to its new counterpart (for the rules, see our 301 and 302 redirect difference article).
  3. Update internal links, canonicals and the sitemap to the new addresses; do not rely on a redirect chain.
  4. Submit the new sitemap to Search Console and monitor crawling and 404 reports for several weeks. Incorrect matches produce 404s; for these, our 404 errors and SEO article is a guide.
  5. Keep old redirects for at least a year, and preferably indefinitely.

Frequently asked questions

Is it mandatory for a keyword to be in the URL?

It is not mandatory. Google may take a light hint from the words in the URL, but the actual ranking is based on content and link signals. If a keyword appears naturally, that is good; if it does not, it is not worth changing the address just for that.

Can I use URLs with special characters?

Technically they work, but in shared links they appear percent-encoded and long, and in some systems they cause errors. Simplified characters are the safe choice.

How long can a URL be?

Although you will not find an official limit, keeping the address short is always better. Addresses that are hard to read or copy reduce sharing and clicks.

Should the URL change when a category name changes?

It is not required. Keep the address permanent; if you do change it, a 301 redirect and an internal link update are essential.

Conclusion

A good URL structure rests on simple rules: short, lowercase, hyphenated, consistent and permanent. Applying these rules from the start on a new site costs almost nothing; on an existing site, you need a redirect and monitoring plan before making changes. The goal is not to "decorate" the address, but to keep the principle of one piece of content, one address.

Once the structure is in place, you can focus on attracting visitors; follow our organic traffic growth methods article for the general roadmap. Once a technical foundation is set up correctly, tools such as organic hit make sense only as a complement that supports your work; the ranking decision always belongs to Google.

Is your keyword missing clicks?

HitBot generates real sessions that search for your target keyword, find your site and click it. The results accumulate in Search Console as impressions and clicks.

Other posts