Web Content: Friendly URLs

The benefits

1. Using friendly URLs assists in quickly finding analytics for specific guides.
2. I will no longer pull Analytics for specific non-friendly URLs.
3. Friendly URLs are easier to remember and copy and paste. When you see a URL in a document or email or chat transcript, you’ll have a better idea of what page it is for.

3 Steps

1. The most important is the base URL for your guide.
2. Don’t forget to give EACH page a friendly URL as well. It doesn’t just stop with the guide’s home.
3. Use the friendly URL whenever you are linking. If you are creating a link and use the non-friendly URL, the browser will not switch over to the friendly URL which will display the wrong URL in Analytics.

The importance of readable, understandable, and friendly URLs is often debated as various browsers hide the full contents of the address bar (or hide it completely) and more and more users type in searches rather than URLs.

However, URLs are structured and can provide metadata for search algorithms as well as users who come across raw URLs in documents such as syllabi, emails, and printed and visual media. We should also not fail to think about having to convey URLs via audible means, such as over the phone, video call, or for non- or low-sighted users.

Wikipedia, WordPress, LibGuides, and countless other platforms allow for the use of friendly URLs, as they still serve a purpose even though they might not have the presence in front of users as they once did.

Universal Design Principles can be applied to URLs that are landing pages, starting points, or close to the top of a site's hierarchy (first or second spot in a breadcrumb).

Therefore, "friendly" URLs should be conveyable. A short, understandable, keyword which is somewhat memorable.

• Short: Aside from blog posts that convey the article title in the link, friendly URLs should not be more than two or three keywords.
• Understandable: Use keywords separated by hyphens (easier to read and convey vocally). While discouraged, abbreviations may be used for recognizable titles or departments within an organization. Note that users outside an organization may have trouble understanding abbreviations. Even though 'hr" is recognized among English speakers in the United States and could be used, "human-resources" is preferred. And, although "oiss" may not be recognized outside of the institution, spelling it out would be too long. Abbreviations should be recognized outside of the library (i.e. at least university-wide).
• Hierarchical: Use the slash "/" to denote hierarchy. Search engines use this to determine a site's hierarchy and how pages relate to each other. Google, for example, has begun to create breadcrumbs on its search results.

It is recognized that not all platforms allow for friendly URLs, but when given the option it should be used.

In LibGuides, for example, note that not only can a guide have a friendly URL, but also each page under it.

"URL as UI" by Jakob Nielsen on Nielsen Norman Group (From 1999 but updated in 2005 and 2007 and will continue to be updated as user habits and expectations change.)