What user needs should URL design consider?

ProcrustesPR

From a user’s perspective, URL design should address four things: readability, ease of sharing, a clear sense of hierarchy, and continued access to content over time. Domain names should be readable and reflect the site’s content, while paths can align with navigation to help users recognize categories. Copied and pasted links should open correctly. When a site moves or is renamed, old URLs should lead to the new locations. Whether to use subdomains or special characters should depend on how users find content, not just on appearance.

ProcrustesPRProcrustesPRHow should you balance CNAME convenience and performance?

Names should be understandable, and links should be easy to share

A community discussion recommends domain names that are easy to read and reflect the site’s content, rather than just a string of keywords followed by “.com”. The point is not just length, but whether users can understand the name and recognize what kind of site it represents. This is user-focused advice, not a guarantee of search rankings.

URLs should also keep working when copied and reposted. Another community discussion notes that URLs containing spaces may cause difficulties when users post links in forums. Even if search engines can follow a correctly formed link, the link may still break if server-side software cannot recognize the full URL. It is therefore important to check not only whether the original page opens, but also whether a shared link still leads to the right content.

Paths should help users understand their location and move up a level

A community response suggests that the folder hierarchy in a URL should match the site’s navigation: as users enter more specific categories, the path should reflect those levels. Another suggestion is to allow users to shorten URLs one level at a time, with the remaining path still leading to a valid page. For example:

  • /images/2010/summer: View images from the summer of a particular year.
  • /images/2010: Remove the season to view images from that year.
  • /images/: Remove the year as well to return to the images page.

This design lets users move back up by editing the URL directly, but only if each level has a corresponding page. The path cannot merely look like a category structure. These are community design suggestions, not a format that every website must follow.

Subdomains should reflect meaningful divisions in content

A community discussion suggests that subdomains may be useful when content differs substantially—for example, to separate videos from articles or organize travel content by city. Whether to split content should depend on user and business needs, rather than an assumption that finer divisions are always better.

A respondent also suggests that separate subdomains for different business units may appear more credible. This is the respondent’s view, however, and does not establish that separating them inherently increases trust. These examples are possible arrangements, not fixed rules.

Old URLs should keep working after content changes

A community discussion advocates keeping URLs as stable as possible while continuing to update the content. If a move is necessary, Google documentation recommends retaining redirects for as long as possible, generally at least a year, to give search systems time to transfer signals. For users, the documentation recommends keeping redirects permanently; one year should not be interpreted as a deadline for removing them.

The same document also notes that redirects add to waiting time. Alongside retaining redirects, it recommends updating internal links and contacting external sites to ask them to link to the new URLs, starting with those that send more visitors. This keeps old URLs usable while helping users reach the content directly and more quickly.

ProcrustesPRProcrustesPRShould you use a 302 redirect to a temporary alias for the new server during a DNS update?

User needs in URL design: perspectives from across the web

Are shorter domain names always better?

Length should not be the only priority; the name should also be easy to read and help people recognize the site's content. A community response suggests that longer domains are not necessarily penalized by search engines, but placing a string of keywords before the domain suffix does not necessarily add value for users either. This is advice about naming trade-offs, not a ranking guarantee.

If a URL contains an article ID and title, should users be able to remove the title?

Consider allowing users to remove the title and still reach the same content using the ID. For example, if the full path is /news/564/seo-improvements, shortening it to /news/564 could still display the content or redirect to the full URL. This suggestion applies to designs where the ID uniquely identifies the item and the trailing portion is primarily for readability; the website must still implement support for this behavior.

If search engines can follow a URL, does that mean users can share it without problems?

Not necessarily. A community discussion notes that URLs containing spaces may not form complete links when copied and pasted into places such as forums. Even if search engines can follow a correctly formed link, the link may still break if server-side software cannot recognize the full URL. So, as well as checking that the original link works, check separately that the shared link still opens correctly.

ProcrustesPRHow does HSTS protect websites and subdomains?

References

  1. 網站遷移與移轉作業 | Google 搜尋中心  |  Documentation  |  Google for Developersdevelopers.google.com — Source used in the article above.
  2. Include full category hierarchy in URL or only the "leaf"?webmasters.stackexchange.com — Source used in the article above.
  3. Google isn't indexing URLs after a redirect that differs only in percent-encoding/decoding?webmasters.stackexchange.com — Discusses: If search engines can follow a URL, does that mean users can share it without problems?
  4. Does character length of domain affect seo rankings?webmasters.stackexchange.com — Discusses: Are shorter domain names always better?
  5. Are page ranks for subdomains independent?webmasters.stackexchange.com — Source used in the article above.
  6. SEO - which URL's are the best?webmasters.stackexchange.com — Discusses: If a URL contains an article ID and title, should users be able to remove the title?

Related articles

How should you balance CNAME convenience and performance?Should you use a 302 redirect to a temporary alias for the new server during a DNS update?How does HSTS protect websites and subdomains?How do SSL certificates protect websites, and why are they needed?Should a Tumblr blog use the platform’s domain or the company’s domain?What types of URLs are there, and what are they used for?When should you use relative or absolute paths in WordPress?What are www subdomains and relative links used for?
ProcrustesPR
ProcrustesPR