Google finds managing Response Headers in Responsive challenging. Restricing which users can create new response headers would allow better management and less deletions of unnecessary Response Headers in the future.
@Gosia Rios We have one feature in the system where they can upload a Response header template. Can we show in the next call and get their feedback. cc @Sathish Sivanantham
We have another strategic customer "Google" requesting for the same.Request:
Ability to prevent users from creating new or redundant Response headers in the Content Library. Additionally, if prevention is not feasible, implement a notification system that alerts administrators whenever a new Response header is created.Current Limitation: Each time a new document is uploaded to the Content Library, new or redundant Response headers are automatically generated.
This primarily occurs because different users (PAs) upload documents in varying formats, including multi-column layouts for headers and responses. The system interprets these format variations as new section headers, leading to the creation of duplicate or unnecessary Response headers.
Since there are many users uploading documents and no standardized format enforcement, we do not have control over the header structures being introduced. Currently:
Proposed Solution: Introduce a system-level restriction that prevents the creation of new Response headers beyond a defined standard (e.g., allow only the existing “Response” header).
Benefits to Google:
This was already requested by Google. This is not a new request from them
Thank you for the confirmation @sathish s
