Your URL structure is a minor direct ranking factor and a significant indirect one. Google has confirmed that keywords in URLs carry a small amount of ranking weight. But the indirect effects are larger: clean URLs improve click-through rates in search results, make internal linking more predictable, simplify site migrations, and help search engines understand your site’s hierarchy.
That doesn’t mean URL structure deserves weeks of agonising. It means getting it right early saves you from problems later. If you’re building a new site, spend an hour establishing good URL conventions before any pages are created. If you have an existing site with functional but imperfect URLs, changing them is rarely worth the redirect overhead unless the current structure is actively causing problems.
What Is a URL?
A URL (Uniform Resource Locator) is the address of a specific page on the internet. Every page has one, and understanding its components helps you make better decisions about structure.
A typical URL looks like this:
https://www.example.com/services/seo-audits?ref=homepage#pricing
Breaking that down:
- Protocol:
https://(the secure version of HTTP; your site should always use HTTPS) - Subdomain:
www.(optional; most modern sites work with or without it, but pick one and redirect the other) - Domain:
example.com(your root domain) - Path:
/services/seo-audits(the directory structure leading to the specific page) - Parameters:
?ref=homepage(query strings that pass additional data; usually irrelevant for SEO) - Fragment:
#pricing(a link to a specific section of the page; ignored by Google for indexing purposes)
For SEO, the path is the part you have the most control over and the part that matters most.
What Makes a URL SEO-Friendly?
Keep URLs Short and Descriptive
Short URLs tend to outperform long ones in search results. A Backlinko study of 11.8 million search results found that pages with shorter URLs ranked slightly higher on average. More practically, short URLs are easier to read, share, and remember.
Good: example.com/services/seo-audits
Acceptable: example.com/services/technical-seo/seo-audits
Poor: example.com/services/our-services/technical-services/seo-audit-service-page
Aim for 3-5 words in the URL slug (the part after the last forward slash). Every additional folder depth and word adds visual noise without adding value.
Include Your Primary Keyword
Including your target keyword in the URL provides a small ranking signal and helps users understand what the page is about before they click. If your page targets “seo audits,” the URL /services/seo-audits is better than /services/technical-review-service.
Don’t force it. If the keyword doesn’t fit naturally into the URL path, prioritise readability over keyword inclusion. The title tag and H1 carry far more ranking weight than the URL.
Use Hyphens to Separate Words
Google treats hyphens as word separators. Underscores are treated as joiners (so seo_audits is read as one word, “seoaudits”). Use hyphens between words: seo-audits, not seo_audits or seoaudits.
Use Lowercase Only
URLs are case-sensitive on most web servers. Example.com/Services/SEO and example.com/services/seo can technically serve different content, which creates duplicate content risk. Use lowercase exclusively and set up server-side rules to redirect any uppercase variations to the lowercase version.
Create a Logical Hierarchy
Your URL path should reflect your site’s information architecture. For a site with services, the pattern might be:
example.com/services/ (services hub page)
example.com/services/technical-seo (specific service)
example.com/services/seo-audits (specific service)
example.com/blog/ (blog hub)
example.com/blog/site-migration-seo (blog post)
This hierarchy tells both users and Google how your content is organised. Each URL path segment represents a level in your site’s architecture.
Don’t nest too deeply. More than three levels of folder depth (/a/b/c/page) starts to create URLs that are long, hard to read, and signal to Google that the content might be deeply buried (and therefore potentially less important). Keep critical pages within two clicks of the homepage where possible.
Avoid Parameters Where Possible
URLs with parameters (?id=123&sort=price&colour=blue) are harder for search engines to handle. They create potential duplicate content issues (the same page accessible through multiple parameter combinations) and they look messy to users.
If your site generates parameter URLs (common with e-commerce filtering, session tracking, or CMS-generated pagination), use canonical tags to point Google to the clean base URL, and consider implementing proper URL rewriting so that user-facing URLs are clean paths rather than parameter strings.
Avoid Dates in Blog URLs
The WordPress default of /2026/03/02/article-title embeds the publication date in every URL. This creates unnecessarily long URLs and makes content appear dated. If you update an article in 2028, the URL still says 2026.
Use /blog/article-title instead. If you’re on WordPress, change the permalink structure to “Post name” (/%postname%/) or a custom structure that includes your preferred folder prefix. Do this before publishing any content, because changing permalink structures on an established site means redirecting every existing URL.
URL Structure for Different Page Types
Different sections of your site have different URL conventions:
Homepage: example.com/ (just the root domain)
Service pages: example.com/services/service-name (one level of nesting under a hub page)
Blog posts: example.com/blog/post-title (flat structure under the blog directory)
Location pages: example.com/locations/city-name (for multi-location businesses)
Product pages: example.com/products/product-name or example.com/category/product-name depending on whether you want category context in the URL
Category pages: example.com/category-name/ (for e-commerce) or example.com/blog/category/category-name (for blog categories, though many sites exclude categories from URLs entirely)
The key principle is consistency. Pick a convention and apply it across every page of the same type. Inconsistent URL patterns (some services at /services/x, others at /x, others at /our-services/x) confuse both users and search engines.
What to Do About Existing URLs
If your site already has URLs that don’t follow best practices, the question is whether to change them. My general advice:
Don’t change URLs unless they’re actively causing problems. A URL like /services/our-technical-seo-service-page is suboptimal but functional. Changing it to /services/technical-seo requires a 301 redirect, and that redirect needs to stay in place permanently. Multiply that across a large site and you’re accumulating redirect overhead for marginal SEO benefit.
Do change URLs if: - They contain parameters that create duplicate content issues - They’re so long or confusing that they harm user experience - You’re doing a site migration anyway and can clean up URLs as part of the redirect mapping - The CMS is generating nonsensical paths (auto-generated IDs, session tokens, database keys)
Always redirect the old URL. If you change any URL, a 301 redirect from the old URL to the new one is non-negotiable. Without it, you lose whatever link equity and rankings the old URL had, and anyone with a bookmark or external link to the old URL hits a 404 error.
URL Structure and Site Migrations
URL changes are one of the highest-risk elements of any site migration. When you migrate from one CMS to another, the URL structure almost always changes (WordPress, Shopify, Squarespace, and Wix all generate URLs differently by default).
The critical steps:
- Map every old URL to its new equivalent before the migration launches
- Implement 301 redirects for every changed URL
- Test the redirect map thoroughly before go-live
- Monitor Search Console after launch for 404 errors and indexing issues
I’ve covered this process in detail in my site migration guide. The URL structure section is the most important part of any migration plan.
URL Mistakes That Actually Matter
Not every URL imperfection is a problem. Here’s what I focus on in technical SEO audits versus what I consider cosmetic:
Genuine problems: - Multiple URLs serving identical content without canonical tags - Parameter URLs being indexed and creating thousands of thin duplicate pages - Broken redirect chains (URL A redirects to B, B redirects to C, C redirects to D) - Mixed HTTP/HTTPS or www/non-www without proper canonicalisation - URLs containing session IDs or tracking tokens that create unique URLs per visitor
Not worth worrying about: - URLs that are slightly longer than ideal but perfectly readable - Historical URLs that use underscores instead of hyphens (redirect overhead isn’t worth the fix) - Minor inconsistencies in folder naming conventions on a site with fewer than 100 pages - Trailing slash versus no trailing slash (pick one and canonicalise, but don’t lose sleep over it)
The best URL structure is one you set up correctly at the start and then rarely think about again. If you’re spending significant time optimising URLs on a site that already functions well, that time is almost certainly better spent on content, internal linking, or technical SEO foundations that have a larger ranking impact.