Best URL Structure for SEO
- Last Edited April 19, 2026
- by Garenne Bigby
URL structure sounds like a solved problem — shorter is better, use hyphens, include a keyword — but it is one of the SEO details most often done badly. A clean URL tells users what the page is about before they click, tells search engines how your site is organized, and survives the link-sharing and text-pasting that shapes organic discovery. A sloppy URL does the opposite.
Below are 17 URL best practices worth following, updated for 2026 — including a fix to the old “underscores are fine” myth that still shows up in SEO advice, plus the current Google guidance on pagination, redirects, and canonical handling.
1. Remove Extra Words
Strip stop words (“the,” “and,” “that,” “a,” “of”) and any clarifying filler. A URL like /blog/the-7-ways-that-helped-me-get-more-sleep reads better as /blog/7-ways-to-sleep-more. Users scan URLs when deciding whether to click, and short, declarative slugs convert better than long ones. Just make sure the slug still tells a complete story — readability wins over aggressive compression.
2. Use Relevant Keywords
Include one or two primary keywords that match what the page is actually about. URLs get shared raw — in text messages, in social posts without previews, in copy-pasted citations — so the URL itself often doubles as the anchor text. Keywords in the URL are a small ranking signal on their own, but the bigger win is user-facing: seeing the keyword in the URL confirms for readers that the link goes where they expect.
3. Keep URLs Readable
A human should be able to glance at the URL and know what the page is. The rule of thumb: if you had to read the slug aloud over the phone, would the other person understand what the page is about? If not, rewrite. Prefer words over IDs, descriptive over cryptic, short over long.
4. Use Hyphens (Not Underscores)
This is one of the few URL rules where Google’s guidance is absolutely explicit: use hyphens to separate words, not underscores. Google’s own documentation and multiple public statements from John Mueller and Matt Cutts have confirmed that hyphens are treated as word separators, while underscores are treated as word joiners.
The practical effect: seo-tips reads to Google as two words (“seo” and “tips”), while seo_tips reads as one single token (“seo_tips”) — which is never what you want. Avoid spaces too, since they URL-encode as %20 and hurt readability. Stick to hyphens as the only word separator.
5. Use Subfolders, Not Subdomains (When You Can)
Both subfolders (example.com/blog/) and subdomains (blog.example.com) can rank — Google has said the choice does not fundamentally matter. In practice, subfolders consolidate link equity and ranking signals on the root domain more cleanly, while subdomains are treated more like distinct sites and have to build their own authority. Unless you have a technical or organizational reason to use subdomains (very different product, separate team, separate stack), default to subfolders.
Whichever you pick, keep the click-depth shallow — two or three clicks from the homepage to any page. Deep, buried pages accumulate less internal link authority and get crawled less often.
6. Canonicalize When Pages Overlap
When two URLs contain effectively the same content — a www and a non-www version, an HTTP and an HTTPS version, a trailing-slash and no-trailing-slash version, a faceted filter that lists the same products as the base category — pick one canonical and either rel="canonical" the others to it or 301 redirect to it. Leaving them competing splits ranking signals between near-duplicates. See our full guide on duplicate content issues for the detailed handling.
7. Minimize Dynamic Parameters
URLs like /product?id=4832&cat=12&sort=price&page=2 work technically but read terribly, fragment crawl budget, and invite duplicate-content issues when different parameter combinations return similar pages. Where possible, rewrite to clean static paths: /product/4832 or /running-shoes/brooks-ghost-16. For unavoidable parameters (faceted navigation, session tokens), use canonical tags to point back to the clean base URL and configure parameter handling in Google Search Console.
8. Match URLs to Page Titles
The URL slug should closely match the page title and H1. This is partly aesthetics — the three together set a consistent expectation for what the page is about — and partly click-through: SERP snippets often display the URL prominently, and a URL that disagrees with the title looks either spammy or accidental. An exact character-for-character match is not required; a close paraphrase is fine.
9. Remove Unnecessary Punctuation
Alphanumerics and hyphens cover 99% of needs. Commas, apostrophes, ampersands, and accented characters URL-encode into visual noise (%2C, %27, %26). Accented characters also open IDN-handling questions that vary by browser. Strip punctuation aggressively in slugs; keep the readable alphanumeric version.
10. Limit Folder Depth
The number of folders in a URL does not directly hurt rankings — Google has confirmed that crawl depth matters more than URL segment count. But deep nesting (/blog/2024/march/seo/url-structure/technical/advanced-tips) signals a buried page to users and makes URLs unwieldy to share. Aim for two or three meaningful segments beyond the domain. Flatter structures are easier to edit, easier to share, and easier to audit.
11. Limit Redirect Chains
A single redirect is fine. Two redirects in a chain is tolerable. Three or more hops starts to cost crawl budget, slow page loads, and give Googlebot reasons to abandon the chain before reaching the final URL. Google recommends keeping chains to no more than three hops. For full technical coverage — 301 vs 302 vs 307 vs 308, chain limits, and the soft-404 trap — see our guide to redirection and SEO.
12. Always Use Lowercase
Case handling in URLs varies by server. Apache on Linux treats /About and /about as different URLs; IIS on Windows usually treats them as the same. This inconsistency is a trap that shows up as accidental duplicates in Search Console reports. The fix is simple: always use lowercase in URLs, everywhere. Configure your server to 301 any mixed-case requests to the lowercase equivalent so typos and old bookmarks still work.
13. Avoid Keyword Stuffing
One or two keywords in the URL is helpful; packing a slug with every target phrase is transparent and counterproductive. Google’s spam systems detect this pattern easily — URLs like /best-cheap-running-shoes-for-men-women-kids-discount-online-store flag as low-quality before the page even loads. Stick with the most relevant term that matches the content.
14. Handle Tracking Parameters Carefully
UTM parameters and analytics tracking tags are necessary, but they should never be part of the canonical URL. Two rules: (1) always set a rel="canonical" to the clean URL without tracking parameters, and (2) configure Google Search Console’s URL Parameters tool (or the modern equivalent) so Google knows which parameters are for tracking versus content. This prevents tracking variations from being indexed as separate pages.
15. Shorter Is Better
Short URLs win on readability, shareability, and click-through. Studies of SERP CTR consistently correlate shorter URLs with higher clicks, largely because they look cleaner in the snippet. A useful ceiling: aim for URLs under 75 characters where the content allows; treat anything over 100 characters as a signal to trim. Brand-plus-slug usually lands well under that.
16. One URL for Your Home Page
Your homepage is typically the most-linked page on the site. Settle on one canonical form — usually https://example.com/ — and 301 redirect every other variant (http://, www vs non-www, /index.html, /home, etc.) to it. Any link, menu item, or canonical tag that points at the homepage should use the canonical form.
17. Handle Paginated URLs Properly
Paginated category pages are easy to mess up. The historical advice was to use rel="next" and rel="prev" markup — but Google deprecated those in March 2019 (and admitted at the time they had not used them for years). The current best practice:
- Use self-referencing canonicals on every paginated page — page 2 canonicalizes to itself, not to page 1. This keeps products or articles that only appear on later pages fully indexable.
- Use descriptive parameters:
?page=2is clearer than cryptic alternatives. - Link pages together with clear Prev/Next navigation in the HTML for user and crawler discoverability.
- Never
noindexpaginated pages — that hides the products on them from Google.
Frequently Asked Questions
Should I use hyphens or underscores in URLs?
Hyphens, always. Google treats hyphens as word separators (“seo-tips” = “seo tips”) but treats underscores as word joiners (“seo_tips” = “seo_tips”). Multiple public statements from Google engineers confirm this — the myth that they are equivalent is one of the most persistent bits of outdated SEO advice.
Do URL keywords still help rankings?
Slightly. Keywords in the URL are a small ranking signal, but the bigger benefit is user-facing: URLs frequently get shared raw, and a descriptive slug confirms to readers what they are clicking. Prioritize clarity over keyword cramming.
Should I change existing URLs to match these best practices?
Usually no. Changing an established URL costs the equity tied to the old URL, even with a 301 redirect. Apply these rules to new pages, and only rewrite existing URLs when a page is being redesigned anyway or when the current URL is actively breaking something (tracking issues, duplicate content, broken structure).
Does URL length actually affect SEO?
Not directly in most cases — Google does not have a strict length penalty. Indirectly, long URLs reduce click-through in the SERP because they look cluttered, and they often contain the keyword-stuffing or parameter-fragmentation patterns that do hurt rankings. Short, clean URLs avoid those adjacent problems.
Bottom Line
Good URLs are short, readable, keyword-relevant, lowercase, hyphen-separated, and consistent. They match the page title, avoid duplicates via proper canonicalization, and handle pagination with self-referencing canonicals rather than the deprecated rel=next/prev markup. Apply these rules to new pages and leave existing ones alone unless you have a specific reason to rewrite. The best URL is the one you can read aloud and a user can remember.
Categories
- Last Edited April 19, 2026
- by Garenne Bigby