Is there any way to render the Page instead of item name with the specific field of text?

Question

I got the requirement from our client that he wants to render the Page instead of page item name with the specific field text.

Ex: I have a page item name as "findyourmarket". So this page will browse by https://domainname/findyourmarket. Now this page has a field "SEO URL" and value is "Find-your-market". Now this page will be rendered as https://domainname/Find-your-market.

We have suggested the "display name" property and Aliases concept but he is not agreed with those.

If any inputs are really helpful for us. Thanks in advance.

Answer 1

To create custom URL's based on a custom field, you will have to write your own linkprovider and plug it in. https://doc.sitecore.com/developers/sxa/17/sitecore-experience-accelerator/en/add-and-select-a-custom-link-provider.html

With the link provider you can generate different URL's.

Next, you need to add a custom itemresolver in the httprequestbegin pipeline to translate the url back into the item. In this class you will need to read the url, and find the item using your custom "SEO url". You will need to set the sitecore context item.

public class CustomItemResolver : HttpRequestProcessor
{
    public override void Process(HttpRequestArgs args)
    {
        var path = args.Url.ItemPath;
        var item = FindItem(path);

        if (item != null)
        {
            Context.Item = item;
        }
    }
}

Answer 2

If it is about getting SEO friendly names then you can use <encodeNameReplacements> configuration from Sitecore.config. Create a patch file for this and add configuration to replace spaces(" ") and other symbols with SEO friendly names. This would not effect item names and happens at runtime. Sitecore will handle it out of the box. The example patch can look like this:

<configuration>
    <sitecore>
        <encodeNameReplacements>
            <replace mode="on" find=" " replaceWith="-" />
        </encodeNameReplacements>
    </sitecore>
</configuration>

Otherwise, If this is not the case then I would support the solution given by Bart.

I hope this helps.