Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.

Get the references of product detail and recipe detail pages in adobe SaaS implementation

Avatar

Level 1

7/17/24

Request for Feature Enhancement (RFE) Summary:
 

In the Adobe SaaS platform, product detail and recipe detail pages are implemented using the CIF framework, meaning there are no physical pages for recipes and products. The current issue is the inability to identify internal references to specific recipe detail and product detail pages.

Use-case:

When we try to unpublish SaaS says there are Referenced pages but does not give the list of referenced pages, this is a serious limitation. This feature existed on the previous D2 platform. In Unilever platform some brands have over 800 pages and webmasters keep adding and removing pages on a very regular basis. There are many pages where Product URLS are also referred. Whenever a page or product is deleted or removed we do add 301 redirects. If there is an internal link if we don’t update those links then when user clicks on the link it redirects a new page url, This is being flagged by SEO error. Before unpublish a page the System is showing error but it is not showing which pages have reference and we have no way of knowing and it results in SEO ranking. In D2 the PDP Pages were published as pages and we used to unpublish before deleting. In SaaS there is no PDP page unpublish as we don't have any physical pages for recipe and products , hence when a PDP is deleted or renamed we have no way of knowing.

Current/Experienced Behavior: Currently we get notification that there is a reference for a page but the list of references are not provided
Improved/Expected Behavior: Need a way to identify the internal references for a product and recipe detail page.
Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release :2024.6.16971.20240628T122619Z
Customer-name/Organization name: Unilever
Screenshot (if applicable):  
Code package (if applicable):  
1 Comment

Avatar

Administrator

9/13/24

@kshamitha1 

Thanks for proposing this idea.
This has been reported to the engineering under the internal reference SITES-24116. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira status.
Status changed to: Investigating