Pretty URLs at a Glance - Fluid Topics - Fluid Topics at a Glance

Fluid Topics
Fluid Topics at a Glance

Pretty URLs at a Glance

Fluid Topics automatically generates an original set of URLs each time an administrator publishes content to a portal. While these URLs are designed to remain unique and robust, they are not user-friendly. Pretty URLs replace original URLs with a more informative URL that gives the user an idea of what the content is about.

Business Value

Using the Pretty URL feature offers the following advantages:

  • Content managers can create links that remain stable even as documents change over time, thus eliminating the risk of sharing a dead link.
  • Users can easily understand and remember a Pretty URL.
  • Document and topic URLs become meaningful.
  • From an SEO perspective, search engines use Pretty URLs in the same way as canonical URLs.
  • Pretty URLs are easy to read in Google Analytics or in any other analytics platform that uses URLs.

Feature Overview

It is possible to define a Pretty URL within content or configure one or more templates for Fluid Topics to use in order to automatically generate a Pretty URL for all or part of document during the publishing process.

When defining templates, it is possible to add metetadata requirements so that template A applies to document type A, template B to document type B, and so on.

For example, the Pretty URL generator has created the following URL for the current version of the Fluid Topics User Guide:

Note that the Pretty URL for the latest version of any document does not include a version number. The version number is only used for older versions, as in the following examples:

Once defined, the Pretty URL is considered to be the canonical URL and is used everywhere a URL is required.

Pretty URL template settings


  • Because it is considered to be the current/canonical URL, the Pretty URL has to be UNIQUE and link to one and only one topic or document, now and in the future. This is important to consider when creating templates.
  • Using templates (as opposed to manually defining a Pretty URL within the content) offers greater flexibility. A template can include a document's name, topic's name, version, language, or any other metadata that helps differenciate one piece of content from another.
  • Fluid Topics launches a reprocess job to apply Pretty URLs as soon as the templates are defined and saved. Since reprocess jobs can be long (depending on content volume), it is more efficient to define all templates at once, rather than one at a time.
  • A Customer Success Manager can help if needed.


It is necessary to have the ADMINor KHUB_ADMINuser role in order to define Pretty URL templates.


Here are a few examples of Pretty URLs and how they were created.

Enable and Configure the Pretty URLs Feature