Skip to Main Content

LibGuide Sustainability & Troubleshooting

Find ways to Jazz up your LibGuides with new content, bells, & whistles. Also checkout these tips for refreshing, upkeep, & troubleshooting your LibGuides

Adding Friendly URLs to Your Guide's Individual Pages

Page URL: SUGGESTED for Accessibility

  • Contains friendly URL
  • Readable to patrons and screen readers
  • Semi-descriptive of the content within

Assign a friendly URL to a guide & individual pages

Just like your guide, each of its pages will also have a unique ID number. Combined, the URL for a page will look something like this:

https://library.fiu.edu/webart/c.php?g=123456
  • Where g=123456 represents the guide's ID number and p=78901 represents the page's ID number.
  • If you've given your guide a friendly URL, then you can also give each page one, as well. This allows you to replace the portion of the URL following your domain name with your own custom string (also known as a "slug"). For example:
https://library.fiu.edu/webart/museum-news
  • The friendly URL of each page will display after the friendly URL of the guide, just like it's a subdirectory. In the example above, history is the friendly URL of the guide and databases is the friendly URL of an individual page of that guide.

To customize a single page's friendly URL

  1. While editing your guide, click on the page you want to customize in your guide's navigation menu.

  2. Click on the pencil icon next to the Page URL field at the top of the guide, right above your content columns.

before adding

  1. In the window that appears, add, edit, or remove the text for the guide's friendly URL

    • The friendly URL may only contain alphanumeric characters, dashes, forward slashes, and underscores.

    • While uppercase letters are supported, we recommend using lowercase letters to keep things simple.

  2. ​Click the Save button

adding editing friendly urls 

Sample Page

after url change

Descriptive & Readable Friendly URLs

In our January 2017 edition of SpringyNews, we highlighted the importance of properly formatting friendly URLs for your LibGuides. Not only do properly-formatted friendly URLs help with the SEO of your LibGuides, but they can also impact the 'readability' of your friendly URLs. 

URLs are not always human-readable or even screen reader friendly. And, if you don't give your LibGuide and individual pages within your LibGuides a friendly URL, then the combination of numbers, dashes, and ampersands will make even less sense to your users. 

Even if you are adding in friendly URLs to all your LibGuides pages, are they descriptive enough when read on their own? If you sent a patron a link to a LibGuide inside an email or tweet, would they be able to decipher the context of that webpage by reading the friendly URL alone?

Are your URLs 'hackable'? Can patrons move to higher levels of your LibGuides' architecture by hacking off the end of the URL? 

Let's check-out some illustrative examples

- Taken directly from Springshare's 5 Tips to Help You Build Accessible LibGuides Content