Custom List Item Pages in Search Result

Question

Hi there,
We are using SharePoint 2013 and have built a custom web part that displays a series of items from a list. When you click on one of the items, it takes you to a custom page that displays the selected list item, styled with our company branding. This works
perfectly. However when a user performs a search, the search results includes the link to the SharePoint list item, and not the custom branded page. We'd like to have the search results include this custom page, instead of the standard SharePoint dispform.aspx
page. Is there anyway to exclude the dispform.aspx and include our CustomItem.aspx in this search results? If so, how is this possible?
For instance, a standard search returns the result:
https://mydomain.com/Lists/Announcements/DispForm.aspx?ID=23
Our custom branded page, which we want included in Search results is this:
https://mydomain.com/AnnouncementsDetail.aspx?ID=23
Thanks in advance!
cflbasser

Answer 1

Does you custom page have a managed property associated with its location, say 'myURL'?  I think you should be able to achieve this by customizing one of the Search Display Templates.  There are a couple of things involved here.  For Result
Display rendering, Item_Default.html display template will have a "ctx.RenderBody(ctx)" call, in this case calling Item_CommonItem_Body.html template to display each item. 
Take a look through Item_CommonItem_Body.html and there should be a place where instead of the OOTB managed property like Path or Url, you could put in your custom managed property to be displayed.  It's best to not update the default display templates
but create custom ones and use custom result types with them.  In this scenario, you are not touching what's being indexed, but simply changing the UI layer.
Another idea would be to use CEWS (Content Enrichment Web callout) and simply take the existing managed property responsible for printing out the link (like URL or Path), re-write it using some regex or similar logic and output it to the existing managed
property or a new one.  You could have a trigger to only do this in specific scenarios to narrow this down, such as only to fire if an input path prefix matches a condition. 
I would recommend doing this with Display Templates if possible, since introducing CEWS can have a performance impact on crawls, depending on how many items will need to be touched.