URL structure best practices: build addresses people and search engines can read

The short answer

A good URL is short, readable and describes the page in lowercase words separated by hyphens. Use a logical folder structure, avoid unnecessary parameters and dates, keep one version of each address, and change a live URL only when you must, with a 301 redirect from the old address to the new one.

What a URL is made of

Take an example address: https://www.example.com/services/web-design/. It has several parts. The protocol is https. The domain is www.example.com. The path is /services/web-design/, and it is the path that you control page by page.

Some addresses also carry a query string, which begins with a question mark, for example ?colour=blue&size=m. These are usually produced by filters, search boxes and tracking, and they are where addresses start to multiply.

Each of these parts affects how easily a person can read the address and how many separate addresses a search engine thinks you have.

Why URL structure matters

Search engines can work with untidy addresses, so structure is not a magic ranking lever. The reasons to care are practical.

• People read them. An address appears in browser bars, emails, messages and sometimes in search results. A readable one tells people where they are going.
• They show your site's logic. Folders reveal how pages relate to each other, which helps you and your team keep the site organised.
• They affect duplicates. If the same page loads at five different addresses, search engines have to guess which one counts.
• They are hard to change. Once a page is linked and indexed, changing its address creates work and risk.

Because of that last point, it is cheaper to choose well at the start than to repair later.

Ten habits of a good URL

1. Describe the page. Use the words a visitor would use: /blog/url-structure-best-practices-for-seo/ beats /blog/post-4827/.
2. Use lowercase. Some servers treat upper and lower case as different addresses.
3. Separate words with hyphens. Google's documentation recommends hyphens over underscores; check the current URL structure guidance.
4. Keep it reasonably short. Drop filler words such as "and", "the" and "of" where meaning stays clear.
5. Avoid special characters and spaces. They get encoded into unreadable strings.
6. Skip dates unless dates matter. A year in the address makes old content look stale, and changes it when you update.
7. Do not stuff keywords. Repeating a phrase three times in an address helps nobody.
8. Pick one trailing-slash style. Either with or without, but consistently.
9. Use https everywhere.
10. Pick one host. Either with www or without, and redirect the other.

Folders and hierarchy

Folders should mirror how a visitor thinks about your business, not your internal org chart. A service business might group pages as /services/, /industries/, /guides/ and /about/. Under /services/ each service gets its own page.

Keep the depth modest. Each extra level adds length and rarely adds meaning. As a rough guide, if you need more than three or four levels to describe a page, the site structure itself may need a rethink.

Matching the folder path to the visible navigation also helps breadcrumbs, which show visitors the route to the page; see how breadcrumbs help. If a page could sit in two places, choose one home for it and link to it from the other, rather than publishing it twice.

Parameters, filters and duplicates

The canonical tag tells search engines which address is the preferred one when several show the same content. It is a hint, so make sure internal links also point to the preferred version. Online stores with filters should read faceted navigation and SEO for a fuller approach.

Changing a URL safely

Sometimes you must change an address: a page is renamed, a folder is reorganised, or you are moving to a new domain. Handle it in this order.

1. List every old address and its new address in a spreadsheet.
2. Set up a permanent (301) redirect from each old address to the matching new one, not to the home page.
3. Update internal links, the sitemap and canonical tags to the new address so they do not point through a redirect.
4. Test a sample of old addresses to confirm they land on the right page in one step.
5. Keep the redirects in place for a long time.

Avoid stacking one redirect on top of another; see how to find and fix redirect chains and loops. For a full domain change, follow this domain change checklist.

Rewriting weak URLs: an example

This is an invented example for illustration. A company sells training courses and its addresses currently look like this: /index.php?id=312&cat=7, /Courses/First_Aid_Basic%20Level and /2019/03/new-course-page-final-v2/.

None of these tells a visitor what they will find. A tidier plan would give each page a clear, stable address, such as /courses/first-aid/ and /courses/first-aid/basic/. The folder says what kind of page it is, the last part says what it is about, and there is no number, date or file extension to go out of date.

Before making changes like this on a live site, ask three questions. First, is the old address getting traffic or links? If yes, redirect it carefully. Second, will the new pattern still make sense in two years, when you have twice as many courses? Third, who will keep to the pattern? Write the rule on one page for your team: lowercase, hyphens, no dates, folder names from this list.

Content management systems often generate addresses automatically from page titles. That is convenient, but check the result before publishing. A long title becomes a long address, and a title edited later does not always update the address, which leaves them out of step. Most systems let you edit the address by hand, and it is worth doing so for important pages.

A final note on language: if your site serves several countries, decide early whether each country gets its own folder or its own domain, because moving later is a large job. Our guide to hreflang explains how those versions are linked.

A short checklist to finish

• Are addresses readable, lowercase and hyphenated?
• Does each page have one preferred address?
• Are parameters under control?
• Do folders match the real structure of the site?
• Are any pages reachable only by a non-linked address? Those may be orphan pages.

If you are unsure how your own site measures up, crawl it and export the list of addresses. Reading the list top to bottom, as a stranger would, shows quickly where the pattern breaks. Where a rule is unclear, check the current Google documentation on URL structure.

Related guides

• SEO services
• Redirect Chains and Loops: How to Find and Fix Them
• Orphan Pages: What They Are and How to Fix Them
• Url structure for seo
• Website redesign seo checklist
• Website navigation and menu structure

Questions and answers

Should my URLs include keywords?

A few descriptive words are useful for people and fine for search engines. Do not repeat or stuff them.

Are underscores or hyphens better?

Google's documentation recommends hyphens to separate words. Check the current guidance.

Should I change old URLs to improve them?

Usually not, unless there is a real problem. Changing a live address carries risk, so weigh the gain first and redirect properly if you proceed.

Does URL length matter?

Very long addresses are harder to read and share. There is no exact limit to aim for, so keep them as short as sense allows.

Should I include the date in blog URLs?

Only if the date is part of the content, as with a news item. For guides you plan to update, leave it out.