Set Up SEO-Friendly and Reader-Friendly URLs
If you are publishing to HTML, you will need to use one or more HTML layouts. The layouts have default settings in place that are designed to provide a good starting point.
By default, the HTML layouts have the "SEO-friendly URLs" and "Reader-friendly URLs" features disabled, as this is needed for long-term Paligo customers. But on new Paligo instances, it is better to have these settings enabled.
To set up SEO-friendly and reader-friendly URLs:
Select Layout in the top menu.
Paligo displays a list of Layouts. The list is empty if there are no custom Layouts in your Paligo instance.
Select the Layout you want to update or Create a Layout.
Tip
You can copy the URL of the Layout Editor and paste it into a new tab in your browser. This can be useful if you frequently switch between your Paligo content and the Layout settings.
Select General in the sidebar.
Enable the SEO-friendly output file names feature.
Enable or disable the Reader-friendly fragment identifiers (hash links) setting. (HTML5 Help Center Layouts only).
Set to Enable to use text URLs.
Set to Disable if you prefer to use the UUIDs for hashtag identifiers.
Important
For HTML5 Help Center outputs, you need to enable both SEO-friendly output file names and Reader-friendly fragment identifiers (hash links).
Note
Reader-friendly fragment identifiers is disabled by default, so that it does not affect any Paligo customers who want to continue using UUID in hash links.
If you have previously shared links that used the UUID in the URL, you can choose to continue supporting them. The URLs with UUIDs will still work, even though the URL for the subsection will use reader-friendly text instead of the UUID.
Use Preserve legacy anchors if using reader-friendly fragment identifiers to choose whether links with UUIDs will continue to work.
Set to Enable to preserve the UUIDs so that links will continue to work.
Set to Disable to lose the UUID, so that only links to the new reader-friendly text version of the link will work.
Note
If you preserve the UUID, it does not mean that the UUID is used in the URL (the UUID is still in the topic, hidden in the code, but it is not part of the URL). The URL will use the new reader-friendly version. If you use the copy to link feature, the copy will also use the reader-friendly URL.
Select Save.
When you use the layout to publish your content, your chosen settings will be applied to the HTML output.
Note
If you have a publication that contains multiple topics or sections with the same title, you would get duplicate hash fragment identifiers.
If you have such duplicates, Paligo will add a suffix to differentiate them. The suffix is generated from the id of the second topic/section. But you can avoid using suffixes by manually providing a reader-friendly fragment identifier. To do this, use the xinfo:outname attribute on the section element of each duplicate topic/section.
Please refer to the SEO Best Practice page for more information on implementing SEO best practices in Paligo.